View Full Version : kde/kdm won't log out
Sep 30th 2009, 09:16 PM
when I choose to log out kdm seems to hang at a black screen. i can ralt+prtsc+k to restart it though. any fix for this?
restart and shut down options work ok though
Sep 30th 2009, 10:22 PM
I haven't found a fix for this and am having the same problem.
Oct 1st 2009, 05:55 AM
No solution, just a poke in what may be a useful direction...
What does /var/log/kdm.log say after this happened?
Oct 1st 2009, 01:04 PM
after restarting x and logging back in this is all there is in kdm.log
(EE) XKB: No components provided for device Virtual core keyboard
[config/dbus] couldn't register object path
kdmgreet: Fatal IO error: client killed
X.Org X Server 1.6.3
Release Date: 2009-7-31
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-24-xen i686 Ubuntu
Current Operating System: Linux buzzmandt-laptop 2.6.31-11-generic #36-Ubuntu SMP Fri Sep 25 06:37:51 UTC 2009 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=73689172-9c6b-4382-aca4-488820d60064 ro quiet splash
Build Date: 05 August 2009 09:13:05PM
xorg-server 2:1.6.3+git20090805+server-1.6-branch.f274e595-0ubuntu0sarvatt (firstname.lastname@example.org)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 1 08:59:53 2009
(==) Using default built-in configuration (39 lines)
(EE) Failed to load module "i810" (module does not exist, 0)
Oct 1st 2009, 07:14 PM
same problem here but its known issue i hope that can be resolved by a normal update
the only workaround i found us this :
Cntl-Alt-F1 for a console and run sudo stop kdm; sudo start kdm for a workaround.
look at this link : https://wiki.ubuntu.com/KarmicKoala/Beta/Kubuntu ;)
Oct 2nd 2009, 11:46 AM
There's a bug in the Intel video driver that causes this. It's been fixed in a recent commit, but you'd need to use the xorg-edgers ppa or compile the driver yourself to get a driver updated to it.
Will Karmic get the 2.9.0 version of the driver? If not, this bug will probably stay throughout Karmic's lifetime (save backports). The workaround is to change /etc/kde4/kdm/kdmrc to have X terminate the server and restart a new one when logging out, instead of trying to reuse the same process (regeneration).
Find the line TerminateServer in the [X-*-Core] section and make sure it's uncommented and set to true.
[...] this is a known breakage. We don't
recommend that people run with regeneration though...
It's usually a display manager (gdm or kdm) option. On gdm it's
AlwaysRestartServer, on kdm it might be AllowClose=true (not sure about that).
Basically what you want to do is start a new X server everytime, rather than
trying to reuse the server you just logged out from.
I found the settings
to /etc/kde4/kdm/kdmrc under [X-*-Core]
Now log off works.
Comment #19 From Keith Packard 2009-09-17 18:20:14 PST -------
Fixed in commit 33f98e4056706f4c30bb4327677ac49e82058231 by leaving GEM running
across server reset.
Don't destroy bufmgr at CloseScreen time
Under KMS, the bufmgr is not initialized at InitOutput time and so it won't be re-initialized during server regen. Thus we must leave the bufmgr running during regen and cannot destroy it in CloseScreen. Under UMS, each place the bufmgr is initialized, it checks to see if it has already happened. Hence, we can safely leave the bufmgr running across server regen for UMS too.
Signed-off-by: Keith Packard <email@example.com>
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.