Xorg display locks after idle time
by Alex
Hi,
I have a fedora21 box and periodically the display stops responding. The
display on the monitor is blank, and trying to wake it again with the
mouse or keyboard is not successful.
I can VNC into the system, and while the screensaver is on with the
clock in the center, the clock does continue to update.
It's like my keystrokes aren't being acknowledged, I'd say.
I can access the system remotely via ssh. I've tried killing Xorg, but
nothing changes. It just comes back in this screensaver mode and the
monitor is still unresponsive.
I'm using the default driver that's chosen at install time for an ATI
Radeon chipset.
I've looked through the Xorg.9.log file and there is nothing indicating
any type of helpful error message.
How can I troubleshoot this further? Perhaps it's a known problem?
Thanks,
Alex
9 years, 3 months
Installing Cinnamon on f21 fails with dependency problems
by Alex
Hi,
I have a fedora21 workstation install with gnome3, and trying to replace
the desktop with Cinnamon.
Running 'yum groupinstall "Cinnamon Desktop"' results in the following
# yum groupinstall "Cinnamon Desktop"
[package list trimmed...]
--> Running transaction check
---> Package blas.x86_64 0:3.5.0-10.fc21 will be installed
---> Package hawtjni-runtime.noarch 0:1.10-3.fc21 will be installed
---> Package jansi-native.x86_64 0:1.5-8.fc21 will be installed
--> Processing Conflict: fedora-release-workstation-21-2.noarch
conflicts fedora-release-nonproduct
--> Processing Conflict: fedora-release-nonproduct-21-2.noarch conflicts
fedora-release-workstation
--> Finished Dependency Resolution
Error: fedora-release-nonproduct conflicts with
fedora-release-workstation-21-2.noarch
Error: fedora-release-workstation conflicts with
fedora-release-nonproduct-21-2.noarch
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Any ideas how to proceed? It's not normal to skip-broken, so I thought I
would see if there was a more common problem here...
Thanks,
Alex
9 years, 3 months
Notification Area not running
by JD
Jan 18 13:27:49 localhost
org.mate.panel.applet.NotificationAreaAppletFactory:
notification-area-applet: Fatal IO error
11 (Resource temporarily unavailable) on X server :0.
Jan 19 15:34:39 localhost org.freedesktop.Notifications:
mate-notification-daemon: Fatal IO error 11 (Resource temporari
ly unavailable) on X server :0.
So, I ran
nohup /usr/libexec/mate-notification-daemon &
But the notification area is still not being displayed.
The process died!!
$ ps -ef | grep notification | grep -v grep
Nothing is displayed.
As root, I see older dates than today (Jan 20th, 15), which show the
process dies or issues warnings.
# grep -i "mate\-notification\-daemon" /var/log/*messages*
/var/log/messages:Jan 19 15:34:39 localhost
org.freedesktop.Notifications: mate-notification-daemon: Fatal IO error
11 (Resource temporarily unavailable) on X server :0.
/var/log/messages-20141228:Dec 22 20:07:48 localhost
org.freedesktop.Notifications: (mate-notification-daemon:1816):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 51: Document ended unexpectedly inside a
comment or processing instruction
/var/log/messages-20141228:Dec 23 11:58:29 localhost
org.freedesktop.Notifications: (mate-notification-daemon:4392):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 51: Document ended unexpectedly inside a
comment or processing instruction
/var/log/messages-20141228:Dec 23 13:19:14 localhost
org.freedesktop.Notifications: (mate-notification-daemon:5057):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 1: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
/var/log/messages-20141228:Dec 26 19:27:48 localhost
org.freedesktop.Notifications: (mate-notification-daemon:3658):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 30: '<at' is not a valid name
/var/log/messages-20141228:Dec 26 19:27:48 localhost
org.freedesktop.Notifications: (mate-notification-daemon:3658):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 30: '<at' is not a valid name
/var/log/messages-20141228:Dec 27 09:58:56 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2532):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 18: '<at' is not a valid name
/var/log/messages-20141228:Dec 27 10:08:44 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2675):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 38: '<at' is not a valid name
/var/log/messages-20141228:Dec 27 16:55:45 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2061):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 30: '<at' is not a valid name
/var/log/messages-20141228:Dec 28 11:21:09 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2769):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 41: 'skype:18772841566?call' is not a valid
name: '?'
/var/log/messages-20150105:Dec 28 12:41:53 localhost
org.freedesktop.Notifications: (mate-notification-daemon:3848):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 23: '<at' is not a valid name
/var/log/messages-20150105:Jan 2 11:20:58 localhost
org.freedesktop.Notifications: (mate-notification-daemon:1987):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 10: Element 'markup' was closed, but the
currently open element is 'DKIM'
/var/log/messages-20150105:Jan 2 13:10:06 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2992):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 44: '<' is not a valid name
/var/log/messages-20150105:Jan 2 11:20:58 localhost
org.freedesktop.Notifications: (mate-notification-daemon:1987):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 10: Element 'markup' was closed, but the
currently open element is 'DKIM'
/var/log/messages-20150105:Jan 2 13:10:06 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2992):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 44: '<' is not a valid name
/var/log/messages-20150105:Jan 2 16:32:14 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2788):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 1: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
/var/log/messages-20150105:Jan 2 17:52:04 localhost
org.freedesktop.Notifications: (mate-notification-daemon:3049):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 1: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
/var/log/messages-20150105:Jan 3 05:44:37 localhost
org.freedesktop.Notifications: (mate-notification-daemon:6394):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 41: 'tomrcrocker(a)hotmail.com' is not a
valid name: '@'
/var/log/messages-20150111:Jan 6 10:46:54 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2183):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 1: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
/var/log/messages-20150111:Jan 6 11:06:54 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2383):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 1: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
/var/log/messages-20150111:Jan 6 11:17:13 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2447):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 1: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
/var/log/messages-20150111:Jan 6 12:57:28 localhost
org.freedesktop.Notifications: (mate-notification-daemon:9636):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 1: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
/var/log/messages-20150111:Jan 6 19:18:29 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2212):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 1: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
/var/log/messages-20150111:Jan 8 10:52:32 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2391):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 51: Document ended unexpectedly inside a
comment or processing instruction
/var/log/messages-20150111:Jan 9 11:22:47 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2679):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 1: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
/var/log/messages-20150111:Jan 9 18:27:31 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2845):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 41: 'jungleboogie0(a)gmail.com' is not a
valid name: '@'
/var/log/messages-20150111:Jan 9 18:27:31 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2845):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 41: 'jungleboogie0(a)gmail.com' is not a
valid name: '@'
/var/log/messages-20150111:Jan 10 19:11:09 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2110):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 51: Document ended unexpectedly inside a
comment or processing instruction
/var/log/messages-20150118:Jan 14 11:29:00 localhost
org.freedesktop.Notifications: (mate-notification-daemon:3088):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
/var/log/messages-20150118:Jan 15 13:00:02 localhost
org.freedesktop.Notifications: (mate-notification-daemon:2747):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 51: Document ended unexpectedly inside a
comment or processing instruction
/var/log/messages-20150118:Jan 15 14:02:18 localhost
org.freedesktop.Notifications: (mate-notification-daemon:3199):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 2 char 36: 'lou(a)lrcd.com' is not a valid name: '@'
/var/log/messages-20150118:Jan 16 13:26:54 localhost
org.freedesktop.Notifications: (mate-notification-daemon:1965):
Gtk-WARNING **: Failed to set text from markup due to error parsing
markup: Error on line 1: Entity did not end with a semicolon; most
likely you used an ampersand character without intending to start an
entity - escape ampersand as &
Please trim off these messages when replying. Thanx.
9 years, 3 months
Radeon driver with FC20 latest kernel update
by Andy Paterson
Hi,
I am running fedora 20 X86_64
I have an Intel Processor:
Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz.
I have an AMD radeon based GPU card :
Advanced Micro Devices, Inc. [AMD/ATI] RV535 [Radeon X1650 PRO] (Secondary)
(rev 9e)
I have two monitors :
ACER Technolgies – on DVI-0 (1920x1080)
Viewsonic Corporation on DVI-1 (1920x1200)
They are (were!) driven by the radeon module :
lsmod :-
.....
radeon 1496040 2
.....
i2c_algo_bit 13257 1 radeon
.....
drm_kms_helper 89555 1 radeon
ttm 80807 1 radeon
.....
drm 296901 5 ttm,drm_kms_helper,radeon
/var/log/messages shows:
radeon 0000:01:00.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M
used)
radeon 0000:01:00.0: GTT: 512M 0x0000000020000000 - 0x000000003FFFFFFF
[drm] Detected VRAM RAM=512M, BAR=256M
[drm] RAM width 128bits DDR
X server log shows:
[ 88.037] (II) Loader magic: 0x80dd00
[ 88.037] (II) Module ABI versions:
[ 88.037] X.Org ANSI C Emulation: 0.4
[ 88.037] X.Org Video Driver: 14.1
[ 88.037] X.Org XInput driver : 19.2
[ 88.037] X.Org Server Extension : 7.0
[ 88.037] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 88.040] (--) PCI:*(0:1:0:0) 1002:71c1:174b:0840 rev 158, Mem @
0xd0000000/268435456, 0xfdaf0000/65536, I/O @ 0x0000ae00/256, BIOS @
0x????????/131072
[ 88.040] (--) PCI: (0:1:0:1) 1002:71e1:174b:0841 rev 158, Mem @
0xfdae0000/65536, BIOS @ 0x????????/65536
....
....
[ 88.058] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 88.058] (II) FBDEV: driver for framebuffer: fbdev
[ 88.058] (II) VESA: driver for VESA chipsets: vesa
[ 88.058] (++) using VT number 1
.....
.....
[ 88.059] (II) [KMS] Kernel modesetting enabled.
[ 88.059] (WW) Falling back to old probe method for modesetting
[ 88.059] (WW) Falling back to old probe method for fbdev
[ 88.059] (II) Loading sub module "fbdevhw"
[ 88.059] (II) LoadModule: "fbdevhw"
[ 88.059] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 88.060] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 88.060] compiled for 1.14.4, module version = 0.0.2
[ 88.060] ABI class: X.Org Video Driver, version 14.1
[ 88.060] (WW) Falling back to old probe method for vesa
[ 88.060] (II) RADEON(0): Creating default Display subsection in Screen
section
"Default Screen Section" for depth/fbbpp 24/32
[ 88.060] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[ 88.060] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp
pixmaps)
[ 88.060] (==) RADEON(0): Default visual is TrueColor
[ 88.060] (==) RADEON(0): RGB weight 888
[ 88.060] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[ 88.060] (--) RADEON(0): Chipset: "ATI Radeon X1650" (ChipID = 0x71c1)
.....
________________________________________________
All worked well up to kernel 3.17.7-200.fc20.x86_64.
________________________________________________
The recent update to kernel 3.17.8-200.fc20.x86_64
results in radeon.ko failing to load.
/var/log/messages shows:
[drm:radeon_init] *ERROR* No UMS support in radeon module!
%modrpobe radeon gives same message.
My monitors are then in low res mirorred mode (ugh!)
X server log shows:
....
[ 13345.844] (II) Loader magic: 0x80dd00
[ 13345.844] (II) Module ABI versions:
[ 13345.844] X.Org ANSI C Emulation: 0.4
[ 13345.844] X.Org Video Driver: 14.1
[ 13345.844] X.Org XInput driver : 19.2
[ 13345.844] X.Org Server Extension : 7.0
[ 13345.844] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 13345.844] setversion 1.4 failed
[ 13345.848] (--) PCI:*(0:1:0:0) 1002:71c1:174b:0840 rev 158, Mem @
0xd0000000/268435456, 0xfdaf0000/65536, I/O @ 0x0000ae00/256, BIOS @
0x????????/131072
[ 13345.848] (--) PCI: (0:1:0:1) 1002:71e1:174b:0841 rev 158, Mem @
0xfdae0000/65536, BIOS @ 0x????????/65536
.......
I understand UMS is User ModeSetting – which according to a quick browse of
the source for the radeon module means CONFIG_DRM_RADEON_UMS is not set.
Then I came across comments to the effect that this has been deprecated (a
mysterious word akin to legal-speak!) presumably replaced by KMS.
Has anybody got any clues how I can get the radeon driver loading and working
again?
Or even if its a bug whether it will soon be fixed?
Many Thanks
Andy
9 years, 3 months
Using old Creative CT-4810 sound card in F20 ??
by Fred Smith
I'm trying to get an old Creative CT4810 sound card working on my F20
machine. I've disabled, in the BIOS, the built-in sound hardware, plugged
the creative card into a PCI slot, booted up and lspci shows no sound
hardware.
I tried removing and reinstalling the alsa packages that were currently
installed to no avail. perhaps there's another one I need specifically
for that card? How to tell?
Any advice will be appreciated, thanks in advance!
Fred
--
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
The Lord is like a strong tower.
Those who do what is right can run to him for safety.
--------------------------- Proverbs 18:10 (niv) -----------------------------
9 years, 3 months
[OT] Compiling a module for the Fedora kernel
by Klaus-Peter Schrage
I am having a permanent fan problem with my obviously esoteric graphics
card (NVIDIA GeForce GT 630, see [1], [2]) for which I found a viable,
but tediuos workaround:
- get the kernel src.rpm
- apply a specific patch to the nouveau driver
- build and install new kernel rpms (see [3]).
I still have to do this on Fedora 21 with the actual kernel version
3.17.6-300, and I fear it will last a while until this problem might be
addressed (if ever).
Now doing this the way described in [3] always means copying and moving
GBs of code (not to mention the build time), although just a few lines
of code are affected.
So I thought about rebuilding only the nouveau module instead of
compiling the complete kernel source each time the Fedora kernel gets an
update. Of course, there are lots of instructions available on building
kernel modules, but I found none that refers to a Redhat/Fedora kernel
source (there is a section 'Building Only Kernel Modules' in the wiki
[3], but this is sort of inapprehensible for me and seems to be outdated).
So any hint would be greatly appreciated.
Klaus
[1]https://lists.fedoraproject.org/pipermail/users/2014-July/452276.html
[2]https://bugzilla.redhat.com/show_bug.cgi?id=1121331
[3]http://fedoraproject.org/wiki/Building_a_custom_kernel
9 years, 3 months
error after install any software
by William Biggs
I running 21 with gnome install when I try to install any software from
the software center . The first software install just fine . But when I
try to install anything else it will not install so . I try to install
it from command line with yum install program's name to see the error
and I get this error: db5 error(-30973) from dbenv->open: BDB0087
DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db5 - (-30973)
error: cannot open Packages database in /var/lib/rpm
CRITICAL:yum.main . Only way I can get it to work is to reboot . Dose
anyone know how to fix it ?
9 years, 3 months
LO crashes when opening draw docs
by Joachim Backes
Hi all,
having big LO problems if trying to open some odg file:
#A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f570bff2c05, pid=23025, tid=140011775326272
#
# JRE version: OpenJDK Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
# Java VM: OpenJDK 64-Bit Server VM (25.25-b02 mixed mode linux-amd64
compressed oops)
# Problematic frame:
# C [libsvtlo.so+0x200c05]
This happens with the actual libreoffice-4.3.5.2-7.fc21.x86_64. The last
running version (for me) was libreoffice-4.3.5.2-4.fc21.x86_64.
Other doc types as writer, calc or impress can be opened flawlessly.
Anybody has similar issues?
Any comments are welcome.
Joachim Backes
--
Fedora release 21 (Twenty One)
Kernel-3.18.3-200.fc21.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes
9 years, 3 months
Cooling a laptop
by JD
I am looking for a laptop cooling pad the fans of which are
"relocatable" so that I can position them to blow into the
air port hols/slots on the bottom of the laptop.
If anyone could please point me to one, would be very
very appreciated.
9 years, 3 months
Fedora-21 vs NFS
by Jonathan Ryshpan
I have just upgraded amito, the client from Fedora-20 to Fedora-21. The
server, weather, is still running Fedora-20. After the upgrade, an
attempt by amito to nfs mount a filesystem on weather fails with an
access denial by by weather. Before the upgrade, everything worked
fine.
It looks like the mount should succeed, since showmount indicates that
the export from weather is OK. Nevertheless it fails. How can I debug
this? I'm pretty much an NFS newbie.
Here is the relevant info:
[root@amito jonrysh]# cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Sun Jan 4 19:54:47 2015
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more
info
#
/dev/mapper/fedora00-root / ext4
defaults 1 1
UUID=7e3eb9f4-44eb-4120-8593-5570190feded /boot ext4
defaults 1 2
/dev/mapper/fedora00-home /home ext4
defaults 1 2
/dev/mapper/fedora00-Windows /srv/c vfat
shortname=winnt 0 0
/dev/mapper/fedora00-swap swap swap
defaults 0 0
# NFS Mounts
weather:/ /srv/weather nfs4
users,defaults 0 0
weather:/var /srv/weather/var nfs4
users,defaults 0 0
[root@amito jonrysh]# ls -l /srv
total 36
drwxr-xr-x. 11 root root 32768 Dec 31 1969 c
drwxr-xr-x. 2 root root 4096 Jan 16 22:01 weather
[root@amito jonrysh]# showmount -e weather
Export list for weather:
/home amito.gateway.2wire.net
/ amito.gateway.2wire.net
[root@amito jonrysh]# mount /srv/weather
mount.nfs4: access denied by server while mounting weather:/
9 years, 3 months