You are not logged in.
All 3 of my Arch machines run KDE4, and they all take what seems like forever to logout. This happens irrespective of the speed the computer, as the experience is the same with a netbook with an Atom processor as with a quad-core. After you select the logout option and confirm it, 8-10 seconds will elapse before the screen goes blank, and it'll stay that way for at least another 10 seconds or more before returning to KDM (or going to runlevel 0 or 6).
Is this just normal for KDE4? I've only been using KDE4 since about version 4.4.2, so I admittedly don't know what to expect. GNOME seemed to logout very quickly, but I honestly can't stand GNOME and was only using it because KDE4 wasn't all that impressive to me until version 4.4.
I've tried to see if any one process is hanging up the system when in the process of logging out, by hitting ctrl+alt+f2 and running top, then logging out and switching back, and I don't see anything that persists and hogs CPU/memory.
Offline
I got the same problem I tried disabling logout sound and it helped a little. Now it logs out in 4 to 5 seconds.
Offline
Since 3 days I have the problem, that my logout doesn't work anymore. I click on the shutdown button and then my system hangs. To shutdown I have to go to tty1 and type shutdown manually. Anyone else experience this problem?
Offline
Is Akonadi running when you logout?
Try disabling via Akonadi Configuration > Akonadi Server Configuration before logging out to see if it's the cause.
Last edited by rusty99 (2010-09-09 09:40:05)
Offline
I already had the logout sound disabled. Akonadi was running. I shut it off and logged out, no difference.
Offline
Since 3 days I have the problem, that my logout doesn't work anymore. I click on the shutdown button and then my system hangs. To shutdown I have to go to tty1 and type shutdown manually. Anyone else experience this problem?
Yes, me too. Right click on desktop, select "Leave" and the screen goes dim, but then just sits there. Have to go to console and cntrl-c to get to a command prompt. I do have a logout sound. I just turned that off and I'll see if I can "Leave" out later tonight.
Offline
Disabling the logout sound made KDE exit quickly as before. Why would the logout sound cause the the slow logout?
Offline
I found the problem (at least in my case). I narrowed the issue down to the GTK tray icon for wicd network manager. Whenever I closed it before logging out or shutting down, there would be no delay at all.
I found a KDE client for wicd in the AUR, though the maintainer needs to update the PKGBUILD. It depends on wicd, when it should depend on the AUR package wicd-nogtk, or else both the KDE and GTK clients will be loaded upon login.
I built and installed wicd-nogtk, then modified the dependency in the PKGBUILD for wicd-client-kde and built and installed it. Since doing so, I've had no delay in loging out or shutting down.
Offline
Well, it didn't help with the long logout, but i like the kde-client anyway.
Offline
My logout/restart/shutdown button stops work when I change the multimedia backend in KDE4 from Xine to GStreamer. When I return to Xine it's simply working without any delay or something.Maybe it's phonon related problem...
Offline
I tried "sudo poweroff" in a konsole (within kde) and the system shuts down very quickly. So it might be kde itself that is slow to issue the command. Effects mentioned before in the forum might simply be side effects.
For reference :
all sound effects are off
phonon uses the xine backend
akonadi server is running
the regular wicd is used
Offline
Disabling the logout sound made KDE exit quickly as before. Why would the logout sound cause the the slow logout?
Did the same thing and logout is quick again. so something is causing a delay in the sound system of KDE.
Last edited by fettouhi (2010-11-05 20:01:27)
Offline
For me, turning off the confirmation dialog that pops up has given me a big speed boost (I also have sounds turned off).
flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)
Offline
I have the same problem, doesn't matter with or without shutdown sound. Using gstreamer or xine seems to change things a bit, but for me it feels like gstreamer is a bit faster, as it doesn't work with amarok, thats not an option anyway..
Using xine I experience the problem described obove:
After you select the logout option and confirm it, 8-10 seconds will elapse before the screen goes blank, and it'll stay that way for at least another 10 seconds or more before returning to KDM (or going to runlevel 0 or 6).
Switching to gstreamer, the time till loguout from kde is about the same, but kdm loads a lot faster then.
Any more suggestions?
Offline
Are you using any GTK-based apps that have tray icons (or otherwise run in the background)? I was able to solve my issue by switching from wicd to a combination of wicd-nogtk and wicd-client-kde (both from AUR).
Offline
no I dont. i just tried to run a empty profile of a brand new user but the problem remains also with only the aplications loaded that are loaded with a fresh .kde4 directory. for wireless im using network manager with the plasmoid.
Offline
I solved this issue deleting all the akonadi stuff (files and dir) from my $HOME (.local and .config included)
now kde4 shutdown is finally fast
Offline
didn't do any good for me,
Offline
Just for info, i had the same problem until a few days ago.
The problem was i couldn't shutdown my system using KDE's logout icon, either via plasmoid or the menu.
When KDE desktop started off, i also had an error message stating something about KDE init or KDE launch daemon
This showed off around the 05th or 06th nov. (as in post #3) and the only thing i did before was an update of the system and probably shutdown til the next morning. What i remember is that it updated stuff related to X like (iirc) xinit.
Now, a couple of days ago, i did update again my system, where it installed once again X server packages, including xinit 1.3.0-1 (X64 here).
So, i have no idea if it's related but now, the problem is gone for me and the error message i had seems related (to me) with xinit.
Hope this helps
Cheers
Last edited by HFC (2010-11-22 11:44:55)
Offline
Turning off the logout sound for KDE has stopped working for me.
Offline
Well, great. I'm back to the long logout as well.
EDIT: Think I found the culprit. I replaced go-openoffice with libreoffice and it installed a symlink to some stupid quickstarter in ~/.config/autostart. I deleted the symlink and killed the quickstarter process, then logged out. There was still a delay that time, but since then I've logged in and out several times without any delay.
Last edited by archtaku (2010-12-03 05:26:27)
Offline
see if this helps:
https://bbs.archlinux.org/viewtopic.php … 22#p862122
the road to hell is paved with good intentions.
Offline
That doesn't seem like the same issue, this thread is about the logout process taking a long time.
Offline
Thanks guys, the LibreOffice thing sorted it out for me. I just un-ticked the box for "Enable systray Quickstarter" in the Tools/Options/LibreOffice/Memory tag
One life - live it. (and drink the best wine first)
Offline
Whoops, posted too soon the problem of non-responsive "shutdown" buttons is back today!
One life - live it. (and drink the best wine first)
Offline