You are not logged in.
I admit I'm too adventurous to use the new nvidia driver 180.35, it is probably not working properly. But, in this case, it is really strange.
After upgrading to nvidia-beta-180.35-1 and also the nvidia-util-beta, and reboot, and login to kde 4.2, I cannot logout. I tried logout and kde hangs. I can switch to console, though. I observed that, right after login to kde, there is some defunct processes, like in the following output of `ps xww'
PID TTY STAT TIME COMMAND
2810 ? Ss 0:00 /bin/sh /usr/bin/startkde
2834 ? Ss 0:00 ssh-agent
2846 ? S 0:00 dbus-launch --sh-syntax --exit-with-session
2847 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
2852 ? Ss 0:00 kdeinit4: kdeinit4 Running...
2853 ? S 0:00 klauncher
2855 ? S 0:00 kded4
2893 ? S 0:00 kwrapper4 ksmserver
2894 ? Sl 0:00 ksmserver
2897 ? R 0:28 kwin -session 10d5c4d974000123423077700000028700014_1235568016_935934
2898 ? S 0:00 /usr/bin/kwrited
2902 ? Sl 0:00 /usr/bin/knotify4
2903 ? Sl 0:00 /usr/bin/nepomukserver
2904 ? Sl 0:08 /usr/bin/plasma
2906 ? Sl 0:06 /usr/bin/nepomukservicestub nepomukstorage
2923 ? S 0:00 /usr/bin/nepomukservicestub nepomukontologyloader
2924 ? S 0:00 /usr/bin/nepomukservicestub nepomukqueryservice
2925 ? S 0:00 /usr/bin/nepomukservicestub nepomukfilewatch
2926 ? SNl 0:01 /usr/bin/nepomukservicestub nepomukstrigiservice
2940 ? S 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-jin/klauncherMT2853.slave-socket local:/tmp/ksocket-jin/plasmawx2904.slave-s
2946 ? S 0:00 /usr/bin/kaccess
2952 ? Z 0:00 [nepomukserver] <defunct>
2954 ? Sl 0:04 /usr/bin/krunner
2963 ? Z 0:00 [nepomukservices] <defunct>
2966 ? Z 0:00 [nepomukservices] <defunct>
2967 ? Z 0:00 [nepomukservices] <defunct>
2968 ? Z 0:00 [nepomukservices] <defunct>
2969 ? Z 0:00 [nepomukservices] <defunct>
2970 ? Z 0:00 [kmix] <defunct>
2971 ? S 0:00 kmix -session 10d5c4d974000123308358000000044790009_1235568006_482140
2972 ? Z 0:00 [python] <defunct>
2974 ? S 0:00 /usr/bin/qstardict -session 10d5c4d974000123556633700000028660019_1235568006_482648
2975 ? S 0:00 python /usr/bin/printer-applet
2976 ? S 0:00 python -O /usr/lib/wicd/wicd-client.py
2978 ? S 0:00 /usr/bin/klipper
These defunct processes can't be killed and probably that is why kde stuck at loging out. But I have no idea how nvidia driver can course this effects. Nevertheless, I tried reverse back to nvidia driver version 180.29, and everything is back to normal.
In case you are wondering what happens with nvidia driver version 180.29, here is it. Normal behavior
PID TTY STAT TIME COMMAND
2791 ? Ss 0:00 /bin/sh /usr/bin/startkde
2815 ? Ss 0:00 ssh-agent
2826 ? S 0:00 dbus-launch --sh-syntax --exit-with-session
2827 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
2832 ? Ss 0:00 kdeinit4: kdeinit4 Running...
2833 ? S 0:00 klauncher
2835 ? S 0:00 kded4
2874 ? S 0:00 kwrapper4 ksmserver
2875 ? Sl 0:00 ksmserver
2877 ? S 0:09 kwin -session 10d5c4d974000123423077700000028700014_1235568016_935934
2878 ? S 0:00 /usr/bin/kwrited
2882 ? Sl 0:00 /usr/bin/knotify4
2883 ? Sl 0:00 /usr/bin/nepomukserver
2884 ? Sl 0:06 /usr/bin/plasma
2886 ? Sl 0:05 /usr/bin/nepomukservicestub nepomukstorage
2904 ? S 0:00 /usr/bin/nepomukservicestub nepomukqueryservice
2905 ? S 0:00 /usr/bin/nepomukservicestub nepomukontologyloader
2906 ? SNl 0:01 /usr/bin/nepomukservicestub nepomukstrigiservice
2907 ? S 0:00 /usr/bin/nepomukservicestub nepomukfilewatch
2922 ? S 0:00 kdeinit4: kio_desktop [kdeinit] desktop local:/tmp/ksocket-jin/klauncherMT2833.slave-socket local:/tmp/ksocket-jin/plasmaLG2884.s
2923 ? S 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-jin/klauncherMT2833.slave-socket local:/tmp/ksocket-jin/plasmaOj2884.slave-s
2924 ? S 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-jin/klauncherMT2833.slave-socket local:/tmp/ksocket-jin/kio_desktopMT2922.sl
2926 ? S 0:00 /usr/bin/kaccess
2934 ? Sl 0:02 /usr/bin/krunner
2952 ? S 0:00 kmix -session 10d5c4d974000123308358000000044790009_1235568006_482140
2954 ? S 0:00 /usr/bin/qstardict -session 10d5c4d974000123556633700000028660019_1235568006_482648
2956 ? S 0:00 python /usr/bin/printer-applet
2957 ? S 0:00 python -O /usr/lib/wicd/wicd-client.py
2959 ? S 0:00 /usr/bin/klipper
Anybody got some hint?
Last edited by jxy (2009-02-25 17:43:42)
Offline
Same here. I'll try downgrading..
Offline
i was able to logout with nvidia 180.35
Acer Aspire V5-573P Antergos KDE
Offline
http://www.nvnews.net/vbulletin/showthread.php?t=128992
Here's the nvnews thread about it.
Offline
Ha, looks like a hell lot of problems. I'm too lazy to register on nvnews forums. But if someone doesn't mind to add my post to nvnews, there is one more interesting behavior. Any program I put in `~/.kde4/Autostart' to start when login also got defunct brothers. It's like they got launched by kde, and then somehow got defunct. And kde launches them again, and this time it works. How bizarre!
Offline
Downgrading to 180.29 solves the problem for me (using the nvidia console installer). I recommend to upgrade the stable repository to 180.29 until there is a new nvidia version, the developers must be aware of this issue now.
Offline