Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 114248 - KDE doesn't respond to logout, reboot or shutdown requests. (KDE-3.5.5)
Summary: KDE doesn't respond to logout, reboot or shutdown requests. (KDE-3.5.5)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-02 03:42 UTC by Brian Kreulen
Modified: 2007-05-24 11:35 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Kreulen 2005-12-02 03:42:59 UTC
Whenever I click on the K Menu->Logout, KDE does not respond to any of the
options (Logout, Reboot, Shutdown). No error messages, no indications of any
problems. I can continue to work with no problems. I'm forced to log in as root
in a konsole and type reboot.

Reproducible: Always
Steps to Reproduce:
1. Click on KMenu->Logout
2. Select an option
3.




KDE: 3.4.3

Emerge info:
Portage 2.0.51.22-r3 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r2,
2.6.13-gentoo-r5 i686)
=================================================================
System uname: 2.6.13-gentoo-r5 i686 AMD Athlon(tm) XP 2600+
Gentoo Base System version 1.6.13
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env
/usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://ftp.tu-clausthal.de/pub/linux/gentoo/
http://linuv.uv.es/mirror/gentoo/"
LINGUAS="fr"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 X aalib alsa apache2 apm arts audiofile avi berkdb bitmap-fonts bzip2
cdparanoia cdr crypt cups curl dbus dvd dvdr dvdread eds emboss encode esd exif
expat fam ffmpeg flac foomaticdb fortran gd gdbm gif glut gphoto2 gpm gstreamer
gtk2 hal idn imagemagick imlib ipv6 java jpeg junit kde lcms libg++ libwww mad
mhash mikmod mng motif mozilla mp3 mpeg mysql ncurses nls nvidia ogg oggvorbis
opengl oss pam pcrepda pdflib perl php pic png python qt quicktime readline ruby
samba sdl slang spell sqlite ssl svga tcltk tcpd tiff truetype truetype-fonts
type1-fonts udev usb xine xml2 xmms xv xvid zlib linguas_fr userland_GNU
kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS
Comment 1 Benno Schulenberg 2005-12-18 05:48:55 UTC
Have you tried Control Center > System Administration > Login Manager > Administrator Mode > the tab Shutdown > and allow Local Shutdown to Everybody?

If that wasn't it, maybe it has meanwhile been solved by itself?  If so, could you list which packages you've emerged since then, with a 'genlop -l --date 17 days ago'?
Comment 2 Brian Kreulen 2005-12-20 23:14:58 UTC
Unfortunately neither is the case. My Shutdown tab shows 'Everybody' has local shutdown rights, and the problem still exists.
Comment 3 Benno Schulenberg 2005-12-21 05:31:22 UTC
Hmm, looking at your CONFIG_PROTECT you already have (had) KDE 3.5 installed.  If you had it installed, make deinstallation complete by removing the *kdepaths-3.5 file from /etc/env.d/, removing the remains of /usr/kde/3.5, running env-update, and then restart kdm.

If that doesn't solve it, please attach your /usr/kde/*/share/config/kdm/kdmrc.
Comment 4 Volker Hemmann 2006-02-19 19:46:11 UTC
Hi,
I have a similar problem, with is also present in KDE 3.5.0, 3.5.1

If I click on logout/shutdown/restart in ca 75% of times, nothing happens. If I click again on logout, it logs me out /restarts/makes it shutdown.

But, if I shutdown via root on a console after the first unsuccessfull try, the shutdown seems confused - the box does not power down at the end of the shutdown and on start, fsck is needed in 50% of cases.

emerge --info
Portage 2.1_pre4-r1 (default-linux/amd64/2005.1, gcc-3.4.5, glibc-2.3.6-r3, 2.6.16-rc3 x86_64)
=================================================================
System uname: 2.6.16-rc3 x86_64 AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.12.0_pre16
ccache version 2.4 [enabled]
dev-lang/python:     2.3.5, 2.4.2-r1
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1-r1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -fweb -ftracer -fpeel-loops -msse3 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -O2 -fweb -ftracer -fpeel-loops -msse3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://ftp.tu-clausthal.de/pub/linux/gentoo/"
LC_ALL="de_DE@euro"
LINGUAS="de"
MAKEOPTS="-j1"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 S3TC X aac acpi aio alsa aotuv asf audiofile avi bash-completion berkdb bitmap-fonts bluetooth bzip2 cairo cdparanoia clamav cpudetection crypt css curl dio dnd dpms dri dv dvd dvdr dvdread emul-linux-x86 encode experimental fame ffmpeg fftw flac foomaticdb fortran ftp gif gimp glitz glut glx gnokii gpm gstreamer gtk gtk2 icq id3 imagemagick imlib input_devices_joystick input_devices_keyboard input_devices_mouse irmc jabber java javascrip javascript joystick jp2 jpeg jpeg2k kde kdeenablefinal kdepim lame lesstif libwww lm_sensors lzo lzw lzw-tiff mad matroska memlimit mime mjpeg mmap mng mp3 mpeg mpeg2 mplayer ncurses nls no-old-linux nocd nosendmail nowin nptl nsplugin nvidia offensive ogg opengl oscar pam pdf pdflib perl pertty physfs player png posix python qt quicktime rar readline real reiserfs rtc scanner sdl sendfile sharedmem sms sndfile sockets spell sqlite ssl stencil-buffer subtitles svg sysfs tcpd tga theora threads tiff toolbar transcode truetype truetype-fonts type1 type1-fonts unicode usb userlocales v4l v4l2 vcd video_cards_nv video_cards_nvidia video_cards_v4l videos visualization vorbis wmf xanim xcomposite xine xml xml2 xpm xrandr xsl xv xvid xvmc yv12 zlib zvbi elibc_glibc kernel_linux linguas_de userland_GNU"
Unset:  ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LANG, LDFLAGS


cat /usr/kde/3.5/share/config/kdm/kdmrc
[General]
ConfigVersion=2.3
ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6
PidFile=/var/run/kdm.pid
ReserveServers=:1,:2,:3
ServerVTs=-7
StaticServers=:0

[Shutdown]
BootManager=None
HaltCmd=/sbin/halt
RebootCmd=/sbin/reboot

[X-*-Core]
AllowNullPasswd=false
AllowRootLogin=false
AllowShutdown=Root
AutoReLogin=false
ClientLogFile=.xsession-errors-%s
Reset=/usr/kde/3.5/share/config/kdm/Xreset
Session=/usr/kde/3.5/share/config/kdm/Xsession
SessionsDirs=/usr/share/xsessions
Setup=/usr/kde/3.5/share/config/kdm/Xsetup
Startup=/usr/kde/3.5/share/config/kdm/Xstartup

[X-*-Greeter]
AntiAliasing=false
ColorScheme=
EchoMode=OneStar
FaceSource=AdminOnly
FailFont=Sans Serif,10,-1,5,75,0,0,0,0,0
ForgingSeed=1139151832
GUIStyle=QtCurve
GreetFont=Serif,20,-1,5,50,0,0,0,0,0
GreetString=Willkommen zu %s auf %n
GreeterPos=50,50
HiddenUsers=
Language=de
LogoArea=Logo
LogoPixmap=/usr/kde/3.5/share/icons/tagon.png
MaxShowUID=65000
MinShowUID=1000
Preloader=/usr/kde/3.5/bin/preloadkde
SelectedUsers=
ShowUsers=NotHidden
SortUsers=true
StdFont=Sans Serif,10,-1,5,50,0,0,0,0,0
Theme=/usr/kde/3.5/share/apps/kdm/themes/circles
UseBackground=true
UserCompletion=false
UserList=true

[X-:*-Core]
AllowNullPasswd=true
AllowShutdown=All
NoPassEnable=false
NoPassUsers=
ServerArgsLocal=-nolisten tcp
ServerCmd=/usr/X11R6/bin/X -br

[X-:*-Greeter]
AllowClose=false
DefaultUser=energyman
FocusPasswd=true
LoginMode=DefaultLocal
PreselectUser=Previous

[X-:0-Core]
AutoLoginAgain=false
AutoLoginDelay=0
AutoLoginEnable=false
AutoLoginLocked=false
AutoLoginUser=energyman
ClientLogFile=.xsession-errors

[Xdmcp]
Enable=false
Willing=/usr/kde/3.5/share/config/kdm/Xwilling

xorg is 7.0 (but problem was there with earlier version too).
Comment 5 Benno Schulenberg 2006-02-20 12:15:41 UTC
There are no significant differences between your kdmrc and mine, so that doesn't look like it's the problem.  Have you looked in ~/.xession-errors after a first click on Shutdown or such has failed, Volker?   Do you still have a kde-3.4 installed?  Does the problem go away if you prune this and clean up /etc/env.d/?
Comment 6 Volker Hemmann 2006-02-20 13:55:26 UTC
Hi,
KDE 3.4 is still installed

I had a severe case this afternoon, after the third click on 'shutdown' the options did not even pop up anymore, but as soon as I switched to a console and did an /etc/init.d/xdm stop, the box shut down cleanly.

I will have a look at .xsession-erros if this happen again.

I would prefer not to uninstall kde 3.4 at the moment, but if there is a certain reason that it may be the culprit, I could do it.
Comment 7 Benno Schulenberg 2006-02-21 10:57:35 UTC
Yes, it's fine to leave the older KDE installed.  But it would be nice to figure out what is happening when it refuses to shutdown.  Maybe there's still something mounted, or a process that doesn't want to die?  Does it maybe happen after playing a CD?  Does it maybe only happen after running a certain application?  You could try logging in and immediately out again a few times, to see if it happens then too.  Or just start up and stop the applications you usually use and then try to reboot, to try and find what triggers it.

(I've taken the liberty of adding you to the CC list, Volker.  Please forgive if that is not what you want.)
Comment 8 Volker Hemmann 2006-02-21 12:52:39 UTC
Hi,

cc'ing me was nice, I always forgot to do it myself ;)

hm, about the logout problem:
there are three apps, I have always run: 
konqueror
kmail
xdtv

and they do not influence the behaviour, because I openend&closed them just minutes ago, and logout worked on the first try ... 

First, I loged out of a session were I played ut2004, vegastrike-cvs (which needs xhost + local:) , had amarok running. No hang, logout worked on the first time. I choosed reboot - and box hang on reboot while initializing the drives... ok, I got through it with pressing the power button, because reset did not help.
I booted into a clean session, choose reboot, got out on the first try - box hanged again. I think, my box does not like restarting anymore :(

The thing is, ut2004, vegastrike, amarok, konqueror, kmail and xdtv are also used, when it does not work on the first try - I had even moments, when all I did was looking for new mails and it did not logout afterwards. So I am not sold to the 'maybe an apps fault' idea.

Oh, and I removed .xsession-errors before starting X (I always start xdm from a root account, this way I can decide, if I want the nvidia module loaded or not, before it can taint the kernel), and after a hung logout (worked on the second try) there was no new one.

The only consistent behaviour I can see is: if it hangs on logout and I do an /etc/init.d/xdm stop, it shuts down like it should, as soon as kdm is 'dead'. While if I repeat my tries, the box sometimes hangs after the 'halted' kernel massage. So I suspect some strange interaction between kdm and pam and kernel.
Comment 9 Benno Schulenberg 2006-02-22 12:48:04 UTC
About the .xsession-errors file: you do login as a normal user?  If so, then the .xsession-errors file should be in your normal homedir.

(To /etc/init.d/local I've added a line that appends the .xsession-errors file to a file in /var/log, so I can later inspect what happened in the past weeks, and look for patterns.  Doing that just now I notice that kicker has been crashing on shutdown since about ten days ago.  Hrmm...)
Comment 10 Volker Hemmann 2006-02-22 14:12:02 UTC
Hi,

emm, I was not clear.
I had a .xsession-errors file in ~/
I removed it and started X (as root /etc/init.d/xdm start)
I logged into KDE as normal user.
I had the logout problem.
No new .xsession-errors file in ~/

I checked the .xsession-errors file before I removed it and it was full with the usual amarok-errors ...

strangely, the last three logouts (some of them after very heavy usage, azureus, mldonkey, ut2004, wesnoth, kmail and konqueror used for hours) were fine.... I cleaned out /tmp, but I did so before and still got hangs...

So the behaviour is totally unpredictable.
Comment 11 Benno Schulenberg 2006-02-23 10:28:22 UTC
Hmm, is the .xsession-errors file present when you're logged in?  If not, have you tried touching it?  (Maybe the new Xorg doesn't create it when it doesn't exist?)  Maybe the file is elsewhere (/tmp, /var/tmp)?

Other things to try when the logout problem recurs:
  Quit all applets in the system tray before logging out.
  Create a new, "clean" user and see if this one can log out fine.
  In the ControlCenter, KDE Components > Session Manager flip all the options
    and Apply, then choose the things you want again and Apply.
  Do the same for System Administration > Login Manager.
Comment 12 Volker Hemmann 2006-02-23 11:41:37 UTC
Hi,

the .xseesion-errors will created, when I run amarok, for example.

I removed .xsessiom-errors. I had problem logging out, not new .xsession-errors file
I used amarok, a lot of stuff in the newly created .xsession-errors file all amarok related, still logout problems.

There is no difference in the probability of logout hangs and the state of .xsession-errors.
When it hangs, and there was none, there will be no new one
When it hangs, and there was one, it is always the same stuff (amarok, for example).
When it logs out cleanly, and there was none, no new one woll be created
When it logs out cleanly, and there was one, it is always the same amarok stuff, but nothing related to the logout, kicker or any menu.

Last night, I logged out fine three times, on the fourth try it hanged.

I will create a new user, but it may take some time until it hangs again.

To put some numbers into it:
in 7 out of 10 trys, restart/shutdown hangs and has to retried.
in 5 of this 7 tries, it will shutdown/restart on the second attempt.
in the 2 other ones, nothing will happen. Shut down xdm-service as root will start the shutdown/restart sequence.
in one of the 7 tries to restart/shutdown, it will hang after displaying 'System halted' (shutdown) or while initializing the drives (restart).
If this happens, there is a 50% chance, that fsck complains on boot about uclean fs and usually finds some stuff in the journal (I am using reiserfs).
Comment 13 Benno Schulenberg 2006-02-23 12:41:22 UTC
But while you're logged in, there is an .xsession-errors file present?  And it disappears when the logout fails?
Comment 14 Volker Hemmann 2006-02-23 16:24:05 UTC
Hi,
well, if I remove it, it stays removed, until an error happens or amarok runs ;)

If I log in, and there was one from an earlier session, it will stay in my home-dir.

It does not magically disappear.
 I removed it several times, hoping that a hanging logout would fill it up, but the only event, that fills it, is starting amarok :(
Comment 15 Volker Hemmann 2006-03-19 07:46:18 UTC
Hi,

some news:

when something is in the systray area (the right part of kicker where small icons of some running apps like amarok, kdewallet,kamix, are residing), it is much more prone to hang on logout. If this app is kwallet, it will hang almost always, kamix, amarok, licq makes it hang in roughly 50% of logout attemps. If absolutly nothing is in the systray area (except the clipboard) logouts attemps are almost always successfull.

I did not recognize this, because there are almost always some apps there ... but with kwallet, it is the worst. Even several logout attemps fail, kicker crashes on logout, long pauses with black screen and so on.
Comment 16 Charlie Shepherd (RETIRED) gentoo-dev 2006-11-23 05:22:03 UTC
Is this still an issue with kde-3.5.5?
Comment 17 Volker Hemmann 2006-11-23 07:11:11 UTC
yes, it is.

Some more info: if something is running in the systray, the hang is almost guaranteed.
If you right click on the desktop and choose 'logout', the hang is LESS likely.

If the hang occurs (it does not react to the shutdown request), and it does not react to it on the second try, it won't react top any other request.

If it hangs, and from a vt root does a /etc/init.d/xdm stop, the box will immidiatly shut down.

If the hang occurs and it still hangs after the second try, and you kill xdm, you will get a message that localmount could not unmount local partitions, because xdm still runs.
Comment 18 Charlie Shepherd (RETIRED) gentoo-dev 2006-11-23 09:19:58 UTC
reopened
Comment 19 Volker Hemmann 2006-12-28 11:55:33 UTC
Hi,
 
good news, I can't reproduce the problem since the sysvinit update sys-apps/sysvinit-2.86-r6 and sys-apps/baselayout-1.12.7
Comment 20 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2007-04-03 16:08:07 UTC
Volker,

I'm closing the bug according to your last comment. If you have the problem again, let us know.
Comment 21 Volker Hemmann 2007-05-24 11:35:21 UTC
I have the problem again for some weeks- and I found the/a culprit.

With KDE 3.5.6, logout requests would be ignored the first two tries and a third one would not be possible - but after and sysrq-i the reboot/shutdown request would be unstuck.

With 3.5.7 I got the 'system message' that kamix canceled the shutdown request.

kamix doesn't do that everytime - directly after a boot, the box shuts down nicely, even with kamix in the systray. But after some hours, I get that 'shutdown request canceled by kamix' message when trying to shutdown/reboot for the first time.