Bug 680764

Anything in ~/.xsession-errors ? 

Does 'ck-list-sessions' show you are a valid local session before you try and shutdown/restart? 

Anything in /var/log/gdm/ that looks related?

[mrunge@sofja ~]$ ck-list-sessions 
Session2:
	unix-user = '500'
	realname = 'Matthias Runge'
	seat = 'Seat1'
	session-type = ''
	active = TRUE
	x11-display = ':0'
	x11-display-device = '/dev/tty7'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2011-02-27T14:40:59.605127Z'
	login-session-id = '2'

trying to clean up and post .xession-errors.

Created attachment 481434 [details]
xsession errors from starting/restarting

Interesting. 

Is xfce4-power-manager installed/running? 

If you kill gnome-settings-daemon and gnome-power-manager does it start operating correctly?

[mrunge@sofja ~]$ ps ax | grep power
 1845 ?        Sl     0:00 /usr/libexec/upowerd
 3426 ?        Ssl    0:00 xfce4-power-manager --restart --sm-client-id 2723046ae-59a9-4631-8bd2-6fddeaca4b65
 3828 pts/1    S+     0:00 grep --color=auto power
[mrunge@sofja ~]$ ps ax | grep gnome
 3183 ?        Sl     0:00 /usr/libexec/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1
 3277 ?        Sl     0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
 3414 ?        Ss     0:00 gnome-screensaver
 3460 ?        Sl     0:00 gnome-sound-applet
 3660 ?        S      0:00 gnome-pty-helper
 3971 pts/1    S+     0:00 grep --color=auto gnome
[mrunge@sofja ~]$ 

It seems, it operates *sometimes* correctly. Currently, I'm unable to predict, when...

Odd. It works everytime here... so not sure whats going on. 

Does it happen everytime or never on a newly created user?

I'm seeing this too, both on newly created account and older ones, so far I haven't seen it working a single time so it appears quite reproducable. OTOH suspend from the logout menu does work.

I'll try to investigate over the weekend.

Just as a data point, restart does work on F14 with XFCE 4.8 from cwickert's repository so it's something in F15, not XFCE 4.8 per-se.

As I mentioned earlier, *sometimes* it worked for me. In nearly all cases, it doesn't. Sadly, I don't really understand, what's going on during logout/restart.

Restart/shutdown from Gnome does work for me.

Heh, the problem is that Xorg segfaults at the moment 'xfce-session-logout --logout|reboot|shutdown' is executed and things kinda go downhill from there...

So this is probably a bug in xorg-x11-server rather than xfce.

FWIW, the Xorg crash filed as bug 684188.

Since this works reliably for Kevin, maybe it's hw-specific. Matthias, what video card you have? As a datapoint, mine is ATI Radeon 9600.

I'm seeing a crash of Xorg here, too. 

lspci -vv shows:
01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Mobility Radeon X300] (prog-if 00 [VGA controller])
	Subsystem: IBM Device 056e
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 43
	Region 0: Memory at c0000000 (32-bit, prefetchable) [size=128M]
	Region 1: I/O ports at 2000 [size=256]
	Region 2: Memory at b0100000 (32-bit, non-prefetchable) [size=64K]
	[virtual] Expansion ROM at b0120000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: radeon
	Kernel modules: radeon, radeonfb

is it radeon-related?

I have an intel card here. ;(

Two systems with a Radeon card failing and one with Intel working is a fair indication that it's a driver issue, but it'll need someone who knows X to figure it out...

Hi,
I want to say that I have the same problem in the GNOME3. When I am restarting system I get GDM instead. Then I look to the SELinux log and I see blocked /bin/bash when he is starting /bin/systemctl. Disabled enforcing mode confirms that it is this problem.

My temporary solution is:
sudo setenforce 0

This is my SELinux log:
http://pastebin.com/rYFAMp4s

This is fixed in xfdesktop-4.8.2-1.fc15. Or rather, worked around - see https://bugzilla.xfce.org/show_bug.cgi?id=7442

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping