Description of problem: xfce desktop takes ~2min to open logout panel when started from runlevel-3 and startx xscreensaver seems implicated - but the screensaver and the screenlock were disabled from the xfce desktop, so this shouldn't be so. Version-Release number of selected component (if applicable): xfdesktop-4.10.0-3.fc18.x86_64 kernel-3.6.0-0.rc2.git2.1.fc18.x86_64 xorg-x11-drv-qxl-0.0.22-5.20120718gitde6620788.fc18.x86_64 xscreensaver-base-5.19-3.fc18.x86_64 How reproducible: 100% Steps to Reproduce: 1.startx 2.click on logout from panel menu 3. Actual results: - takes ~2min before logout popup occurs - click "logout" - error window: "Received error while trying to log out" - click "close" on error window - click on "logout" again and it exits, but originating shell shows (first part scrolled off): on was broken. xfce4-session: Querying suspend failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. qxl_surface_create: Zero width or height ** Message: applet now removed from the notification area /etc/xdg/xfce4/xinitrc: line 107: 857 Segmentation fault xfce4-session xinit: connection to X server lost xscreensaver: 11:55:39: SIGHUP received: restarting... waiting for X server to shut down xscreensaver: 11:55:39: running as ellson/ellson (1000/1000) Freeing 0x7f1792214010 .xscreensaver: 11:55:40: Can't open display: :0.0 xscreensaver: 11:55:40: running as ellson/ellson (1000/1000) xscreensaver: 11:55:40: Errors at startup are usually authorization problems. But you're not logging in as root (good!) so something else must be wrong. Did you read the manual and the FAQ? http://www.jwz.org/xscreensaver/faq.html http://www.jwz.org/xscreensaver/man.html Server terminated successfully (0). Closing log file. Expected results: responsive logout Additional info: If the QXL driver is implicated, then this may be related to Bug #844463
This is almost surely a duplicate of bug 806491 Please run 'startx -- vt01' while on tty1 and see if the problem persists.
I don't agree that its a duplicate og bug #806491, but it may be related. Both "startx" and "startx -- vt01" work for me, but both exhibit the long delay when trying to logout (this bug).
Are you actually on tty1 when running 'startx -- vt01' ? Can you attach: ck-list-sessions and systemd-loginctl list-sessions output?
[ellson@fc18-64 ~]$ tty /dev/tty1 [ellson@fc18-64 ~]$ ck-list-sessions Session1: unix-user = '1000' realname = 'John Ellson' seat = 'Seat1' session-type = '' active = TRUE x11-display = '' x11-display-device = '' display-device = '/dev/tty1' remote-host-name = '' is-local = TRUE on-since = '2012-08-26T16:52:52.479610Z' login-session-id = '1' [ellson@fc18-64 ~]$ systemd-loginctl list-sessions SESSION UID USER SEAT 1 1000 ellson seat0 1 sessions listed. [ellson@fc18-64 ~]$ This is on the primary console of a KVM virtual host (before startx).
Do you have ConsoleKit installed? rpm -qa | grep -i consolekit
Yes, and systemd "knows" about it, but I'm not sure how to interpret what it knows. [root@fc18-64 ~]# rpm -qa | grep -i consolekit ConsoleKit-x11-0.4.5-3.fc18.x86_64 ConsoleKit-libs-0.4.5-3.fc18.x86_64 ConsoleKit-0.4.5-3.fc18.x86_64 [root@fc18-64 ~]# systemctl --all | grep -i console systemd-...d-console.path loaded inactive dead Dispatch Password Requests to Console Directory Watch console-...daemon.service loaded active running Console Manager console-...-start.service loaded active exited Console System Startup Logging gpm.service loaded active running Console Mouse manager netconsole.service loaded inactive dead SYSV: Initializes network console logging systemd-...onsole.service loaded inactive dead Dispatch Password Requests to Console systemd-...-setup.service loaded active exited Setup Virtual Console [root@fc18-64 ~]#
Interesting. Does a startx as root work as expected?
(after remembering to do a "switchdesk XFCE" as root) Same problem. Desktop starts OK, but takes foreever to present logout-button window.
BTW - selinux is in permissive more
If you install lightdm-gtk and do: systemctl enable --force lightdm.service ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target and reboot and login via lightdm, does it start working as expected?
[ more -> mode ] I don't think the Xorg QXL driver is implicated. The Cirrus driver is broken, but I can reproduce this bug when using the VGA driver.
I was trying lightdm earlier - retrying with your extra softlink ... No. With "rhgb quiet" the last message I see is about some failure of Authorization-Manager, then the console goes completely black ....for about 2min (good job I hadn't sent this yet), then a login panel appears (which includes userids which are not regular users). Select xfce session (shouldn't that be the default since I did a switchdesk XFCE?) and logged in. Login was unreasonably slow -- 20sec. Clicked on logout from the menu -- wait ~2min goes back to all black screen....for about 2min .. then the user login window opens again. Seeing stuff in /var/log/messages about: console-kit-daemon[581]: CRITICAL: polkit_authority_check_authorization: assertion `POLKIT_IS_AUTHORITY (authority)' failed Aug 26 13:56:36 fc18-64 dbus-daemon[527]: dbus[527]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out Investigating .....
Ah ha. Was this an upgrade? does a 'yum reinstall polkit' get it working? (if this is it, you are missing a polkitd user and group).
Well .. erm .. yes, since fc18 hasn't been released yet. And Yes :-) login and logout are much better now. Wouldn't a simple version bump and rebuild get polkit reinstalled automatically? Different bug, I guess :-( I guess this one is solved. Thanks very much for your help, Kevin.
Sorry it took so long to get there. ;) Marking this a dupe of the polkit bug... *** This bug has been marked as a duplicate of bug 841451 ***