Description of problem: Hardware: Intel I7 x86_64, 24GB ram, Nvidia GTX 260 card, dual headed display. On a fresh install, I noticed that when launching KDE desktop that the logout, reboot, shutdown buttons would not work; they didn't bring up the confirm dialog, no errors, no nothing. This sounded originally like bug 951039, but on further investigation determined it wasn't limited to SELinux, and wasn't limited to NVidia drivers, tho it seems to be worse with NVidia drivers over nouveau drivers. Near 100% repeatable with NVidia, about 30-50% with nouveau. It could also be similar to 877215, tho there isn't much detail in that report to confirm the same problem. Sometimes when it does work correctly, especially with nouveau the startup sounds and desktop apps will be very noticeable delayed (10-20 seconds). There seems to be about 15-20 seconds, where if it startups correctly in that period, the rest of the kde session will be fine. But if it doesn't in that time period, it never will for the session. While I'm not 100% able to reproduce, when it happens it has the following symptoms (the symptoms are 100% when it happens). 1. First I notice is the KDE startup sound does not play. 2. The saved KDE windows/apps from the previous session don't launch. 3. If I try to launch a program (Konsole) in the first ~20 seconds, I will get nothing for several seconds, then an error dialog to the effect "kLauncher isn't running or the application didn't start". After this error, I hear a brief sound for the first time, and then I am able to relaunch Konsole and it startups up correctly. 4. The logout, reboot, shutdown actions from any source (desktop right click, launch button, etc) don't ever work. The confirm dialog box is never displayed. The logout buttons fail even after point #3 corrects where apps can be launched. 5. I've found nothing in the system logs so far to provide more detailed info. I've tried logging in with other users, even root. Same basic unpredictable results. Version-Release number of selected component (if applicable): Fedora 19, fresh install, all patches. Both prior to NVidia drivers loaded and after. How reproducible: I am not 100% able to reproduce, is much worse with NVidia drivers, but can occur without. Probably some race condition; perhaps since NVidia drivers start in character based text mode, that may change the conditions of the race. Steps to Reproduce: 1. Login to KDE desktop 2. If no startup sound, hit logout button. 3. Actual results: If no startup sound, and Konsole can't be immediately started, then the logout/shutdown buttons will fail to work. Expected results: Startup sounds, Konsole launch works, logout button all work. Additional info:
It could also be related to bug #983110 somehow.
tentatively marking this as depending on that, indeed the symptoms are very similar.
I agree, it's a same bug as #983110.
It could be very significant that I just had a SUCCESSFUL KDE desktop start, sound, apps, logout dialog, the whole thing. First time since I've install NVidia driver that it has worked... What changed?? I received a desktop startup crash as described (and I reported) on bug #974705. So whatever the crash freed up, allowed the rest of things to work correctly for the first time.
Which display manager are you using when this occurs, please?
Standard KDE, I don't know the process name, you probably know better than I, but if it helps, here is a "ps -eaf" once logged in, and btw, this login did not work correctly, so the logout, sound, etc - all aspects of this writeup - are in play.. ps -eaf UID PID PPID C STIME TTY TIME CMD root 1 0 0 21:57 ? 00:00:01 /usr/lib/systemd/systemd --switched-root --system --deserialize 21 root 2 0 0 21:57 ? 00:00:00 [kthreadd] root 3 2 0 21:57 ? 00:00:00 [ksoftirqd/0] root 4 2 0 21:57 ? 00:00:00 [kworker/0:0] root 5 2 0 21:57 ? 00:00:00 [kworker/0:0H] root 6 2 0 21:57 ? 00:00:00 [kworker/u:0] root 7 2 0 21:57 ? 00:00:00 [kworker/u:0H] root 8 2 0 21:57 ? 00:00:00 [migration/0] root 9 2 0 21:57 ? 00:00:00 [rcu_bh] root 10 2 0 21:57 ? 00:00:00 [rcu_sched] root 11 2 0 21:57 ? 00:00:00 [watchdog/0] root 12 2 0 21:57 ? 00:00:00 [watchdog/1] root 13 2 0 21:57 ? 00:00:00 [migration/1] root 14 2 0 21:57 ? 00:00:00 [ksoftirqd/1] root 15 2 0 21:57 ? 00:00:00 [kworker/1:0] root 16 2 0 21:57 ? 00:00:00 [kworker/1:0H] root 17 2 0 21:57 ? 00:00:00 [watchdog/2] root 18 2 0 21:57 ? 00:00:00 [migration/2] root 19 2 0 21:57 ? 00:00:00 [ksoftirqd/2] root 20 2 0 21:57 ? 00:00:00 [kworker/2:0] root 21 2 0 21:57 ? 00:00:00 [kworker/2:0H] root 22 2 0 21:57 ? 00:00:00 [watchdog/3] root 23 2 0 21:57 ? 00:00:00 [migration/3] root 24 2 0 21:57 ? 00:00:00 [ksoftirqd/3] root 25 2 0 21:57 ? 00:00:00 [kworker/3:0] root 26 2 0 21:57 ? 00:00:00 [kworker/3:0H] root 27 2 0 21:57 ? 00:00:00 [watchdog/4] root 28 2 0 21:57 ? 00:00:00 [migration/4] root 29 2 0 21:57 ? 00:00:00 [ksoftirqd/4] root 30 2 0 21:57 ? 00:00:00 [kworker/4:0] root 31 2 0 21:57 ? 00:00:00 [kworker/4:0H] root 32 2 0 21:57 ? 00:00:00 [watchdog/5] root 33 2 0 21:57 ? 00:00:00 [migration/5] root 34 2 0 21:57 ? 00:00:00 [ksoftirqd/5] root 35 2 0 21:57 ? 00:00:00 [kworker/5:0] root 36 2 0 21:57 ? 00:00:00 [kworker/5:0H] root 37 2 0 21:57 ? 00:00:00 [watchdog/6] root 38 2 0 21:57 ? 00:00:00 [migration/6] root 39 2 0 21:57 ? 00:00:00 [ksoftirqd/6] root 40 2 0 21:57 ? 00:00:00 [kworker/6:0] root 41 2 0 21:57 ? 00:00:00 [kworker/6:0H] root 42 2 0 21:57 ? 00:00:00 [watchdog/7] root 43 2 0 21:57 ? 00:00:00 [migration/7] root 44 2 0 21:57 ? 00:00:00 [ksoftirqd/7] root 45 2 0 21:57 ? 00:00:00 [kworker/7:0] root 46 2 0 21:57 ? 00:00:00 [kworker/7:0H] root 47 2 0 21:57 ? 00:00:00 [khelper] root 48 2 0 21:57 ? 00:00:00 [kdevtmpfs] root 49 2 0 21:57 ? 00:00:00 [netns] root 50 2 0 21:57 ? 00:00:00 [bdi-default] root 51 2 0 21:57 ? 00:00:00 [kintegrityd] root 52 2 0 21:57 ? 00:00:00 [kblockd] root 53 2 0 21:57 ? 00:00:00 [ata_sff] root 54 2 0 21:57 ? 00:00:00 [khubd] root 55 2 0 21:57 ? 00:00:00 [md] root 56 2 0 21:57 ? 00:00:00 [kworker/0:1] root 57 2 0 21:57 ? 00:00:00 [kworker/1:1] root 58 2 0 21:57 ? 00:00:00 [kworker/2:1] root 59 2 0 21:57 ? 00:00:00 [kworker/3:1] root 60 2 0 21:57 ? 00:00:00 [kworker/4:1] root 61 2 0 21:57 ? 00:00:00 [kworker/5:1] root 62 2 0 21:57 ? 00:00:00 [kworker/6:1] root 63 2 0 21:57 ? 00:00:00 [kworker/7:1] root 65 2 0 21:57 ? 00:00:00 [kswapd0] root 66 2 0 21:57 ? 00:00:00 [ksmd] root 67 2 0 21:57 ? 00:00:00 [khugepaged] root 68 2 0 21:57 ? 00:00:00 [fsnotify_mark] root 69 2 0 21:57 ? 00:00:00 [crypto] root 77 2 0 21:57 ? 00:00:00 [kthrotld] root 78 2 0 21:57 ? 00:00:00 [kworker/u:1] root 80 2 0 21:57 ? 00:00:00 [scsi_eh_0] root 81 2 0 21:57 ? 00:00:00 [scsi_eh_1] root 82 2 0 21:57 ? 00:00:00 [scsi_eh_2] root 83 2 0 21:57 ? 00:00:00 [scsi_eh_3] root 84 2 0 21:57 ? 00:00:00 [scsi_eh_4] root 85 2 0 21:57 ? 00:00:00 [scsi_eh_5] root 86 2 0 21:57 ? 00:00:00 [kworker/u:2] root 87 2 0 21:57 ? 00:00:00 [kworker/u:3] root 88 2 0 21:57 ? 00:00:00 [kworker/u:4] root 89 2 0 21:57 ? 00:00:00 [kworker/u:5] root 90 2 0 21:57 ? 00:00:00 [kworker/u:6] root 91 2 0 21:57 ? 00:00:00 [kpsmoused] root 92 2 0 21:57 ? 00:00:00 [kworker/0:2] root 93 2 0 21:57 ? 00:00:00 [deferwq] root 94 2 0 21:57 ? 00:00:00 [kworker/u:7] root 95 2 0 21:57 ? 00:00:00 [kworker/u:8] root 99 2 0 21:57 ? 00:00:00 [kauditd] root 216 2 0 21:57 ? 00:00:00 [kworker/2:2] root 227 2 0 21:57 ? 00:00:00 [scsi_eh_6] root 228 2 0 21:57 ? 00:00:00 [scsi_eh_7] root 233 2 0 21:57 ? 00:00:00 [firewire] root 245 2 0 21:57 ? 00:00:00 [kworker/0:1H] root 259 2 0 21:57 ? 00:00:00 [kworker/1:2] root 320 2 0 21:57 ? 00:00:00 [kdmflush] root 334 2 0 21:57 ? 00:00:00 [jbd2/dm-0-8] root 335 2 0 21:57 ? 00:00:00 [ext4-dio-unwrit] root 341 2 0 21:57 ? 00:00:00 [kworker/4:2] root 365 2 0 21:58 ? 00:00:00 [kworker/7:1H] root 385 1 0 21:58 ? 00:00:00 /usr/lib/systemd/systemd-journald root 395 2 0 21:58 ? 00:00:00 [kworker/3:2] root 405 1 0 21:58 ? 00:00:00 /usr/sbin/lvmetad root 408 1 0 21:58 ? 00:00:00 /usr/lib/systemd/systemd-udevd root 442 2 0 21:58 ? 00:00:00 [kworker/3:1H] root 448 2 0 21:58 ? 00:00:00 [edac-poller] root 454 2 0 21:58 ? 00:00:00 [kworker/1:1H] root 456 2 0 21:58 ? 00:00:00 [kworker/5:1H] root 466 2 0 21:58 ? 00:00:00 [hd-audio0] root 469 2 0 21:58 ? 00:00:00 [kvm-irqfd-clean] root 491 2 0 21:58 ? 00:00:00 [kdmflush] root 505 2 0 21:58 ? 00:00:00 [kcryptd_io] root 506 2 0 21:58 ? 00:00:00 [kcryptd] root 509 2 0 21:58 ? 00:00:00 [kdmflush] root 510 2 0 21:58 ? 00:00:00 [kcryptd_io] root 511 2 0 21:58 ? 00:00:00 [kcryptd] root 525 2 0 21:58 ? 00:00:00 [kworker/5:2] root 537 2 0 21:58 ? 00:00:00 [kworker/7:2] root 538 2 0 21:58 ? 00:00:00 [jbd2/sda1-8] root 539 2 0 21:58 ? 00:00:00 [ext4-dio-unwrit] root 541 2 0 21:58 ? 00:00:00 [kdmflush] root 542 2 0 21:58 ? 00:00:00 [kdmflush] root 544 2 0 21:58 ? 00:00:00 [kdmflush] root 547 2 0 21:58 ? 00:00:00 [kdmflush] root 551 2 0 21:58 ? 00:00:00 [kdmflush] root 553 2 0 21:58 ? 00:00:00 [kdmflush] root 556 2 0 21:58 ? 00:00:00 [kdmflush] root 559 2 0 21:58 ? 00:00:00 [kdmflush] root 567 2 0 21:58 ? 00:00:00 [kworker/6:1H] root 568 2 0 21:58 ? 00:00:00 [kworker/6:2] root 569 2 0 21:58 ? 00:00:00 [flush-8:0] root 570 2 0 21:58 ? 00:00:00 [flush-253:0] root 571 2 0 21:58 ? 00:00:00 [flush-253:1] root 572 2 0 21:58 ? 00:00:00 [flush-253:2] root 588 2 0 21:58 ? 00:00:00 [jbd2/dm-10-8] root 589 2 0 21:58 ? 00:00:00 [ext4-dio-unwrit] root 594 2 0 21:58 ? 00:00:00 [jbd2/dm-7-8] root 595 2 0 21:58 ? 00:00:00 [ext4-dio-unwrit] root 602 2 0 21:58 ? 00:00:00 [jbd2/dm-8-8] root 603 2 0 21:58 ? 00:00:00 [ext4-dio-unwrit] root 605 2 0 21:58 ? 00:00:00 [jbd2/dm-6-8] root 606 2 0 21:58 ? 00:00:00 [ext4-dio-unwrit] root 610 1 0 21:58 ? 00:00:00 /sbin/auditd -n root 619 610 0 21:58 ? 00:00:00 /sbin/audispd root 620 619 0 21:58 ? 00:00:00 /usr/sbin/sedispatch root 624 1 0 21:58 ? 00:00:00 /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.co root 626 1 0 21:58 ? 00:00:00 /usr/bin/python /usr/sbin/firewalld --nofork --nopid root 627 1 0 21:58 ? 00:00:00 /usr/sbin/smartd -n root 628 1 0 21:58 ? 00:00:00 /sbin/rsyslogd -n root 630 1 0 21:58 ? 00:00:00 /usr/sbin/irqbalance --foreground root 639 1 0 21:58 ? 00:00:00 /usr/sbin/abrtd -d -s root 641 1 0 21:58 ? 00:00:00 /usr/bin/abrt-watch-log -F Backtrace /var/log/Xorg.0.log -- /usr/bin/a root 643 1 0 21:58 ? 00:00:00 @sbin/mdadm --monitor --scan -f --pid-file=/var/run/mdadm/mdadm.pid root 646 1 0 21:58 ? 00:00:00 /usr/sbin/gpm -m /dev/input/mice -t exps2 chrony 651 1 0 21:58 ? 00:00:00 /usr/sbin/chronyd -u chrony root 660 1 0 21:58 ? 00:00:00 /usr/bin/abrt-watch-log -F BUG: WARNING: at INFO: possible recursive l root 662 1 0 21:58 ? 00:00:00 /usr/lib/systemd/systemd-logind avahi 664 1 0 21:58 ? 00:00:00 avahi-daemon: running [blackbird.local] dbus 669 1 0 21:58 ? 00:00:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --sy root 673 1 0 21:58 ? 00:00:00 /usr/sbin/mcelog --ignorenodev --daemon --foreground avahi 675 664 0 21:58 ? 00:00:00 avahi-daemon: chroot helper root 732 1 0 21:58 ? 00:00:00 /usr/sbin/NetworkManager --no-daemon root 774 2 0 21:58 ? 00:00:00 [kworker/4:1H] polkitd 940 1 0 21:58 ? 00:00:00 /usr/lib/polkit-1/polkitd --no-debug root 973 1 0 21:58 ? 00:00:00 /usr/sbin/modem-manager root 982 1 0 21:58 ? 00:00:00 /usr/sbin/bluetoothd -n root 1115 2 0 21:58 ? 00:00:00 [flush-253:6] root 1116 2 0 21:58 ? 00:00:00 [flush-253:7] root 1117 2 0 21:58 ? 00:00:00 [flush-253:8] root 1118 2 0 21:58 ? 00:00:00 [flush-253:10] root 1121 2 0 21:58 ? 00:00:00 [kworker/2:1H] root 1134 732 0 21:58 ? 00:00:00 /sbin/dhclient -d -sf /usr/libexec/nm-dhcp-client.action -pf /var/run/ root 1141 1 0 21:58 ? 00:00:00 /usr/sbin/libvirtd rpc 1162 1 0 21:58 ? 00:00:00 /sbin/rpcbind -w root 1176 2 0 21:58 ? 00:00:00 [rpciod] root 1177 2 0 21:58 ? 00:00:00 [nfsiod] root 1182 2 0 21:58 ? 00:00:00 [nfsv4.0-svc] root 1194 1 0 21:58 ? 00:00:00 sendmail: accepting connections root 1209 1 0 21:58 ? 00:00:00 /usr/sbin/crond -n root 1210 1 0 21:58 ? 00:00:00 /usr/sbin/atd -f root 1215 1 0 21:58 ? 00:00:00 /usr/sbin/sshd -D smmsp 1248 1 0 21:58 ? 00:00:00 sendmail: Queue runner@01:00:00 for /var/spool/clientmqueue root 1253 1 0 21:58 ? 00:00:00 /usr/lib/vmware/bin/vmware-vmblock-fuse -o subtype=vmware-vmblock,defa root 1302 1 0 21:58 ? 00:00:00 /usr/bin/vmnet-bridge -s 6 -d /var/run/vmnet-bridge-0.pid -n 0 root 1310 1 0 21:58 ? 00:00:00 /usr/bin/vmnet-netifup -s 6 -d /var/run/vmnet-netifup-vmnet1.pid /dev/ root 1338 1 0 21:58 ? 00:00:00 /usr/bin/vmnet-dhcpd -s 6 -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf root 1341 1 0 21:58 ? 00:00:00 /usr/bin/vmnet-natd -s 6 -m /etc/vmware/vmnet8/nat.mac -c /etc/vmware/ root 1343 1 0 21:58 ? 00:00:00 /usr/bin/vmnet-netifup -s 6 -d /var/run/vmnet-netifup-vmnet8.pid /dev/ root 1350 1 0 21:58 ? 00:00:00 /usr/bin/vmnet-dhcpd -s 6 -cf /etc/vmware/vmnet8/dhcpd/dhcpd.conf -lf root 1362 1 0 21:58 ? 00:00:00 /usr/sbin/vmware-authdlauncher root 1379 1 0 21:58 ? 00:00:00 /usr/bin/vmware-usbarbitrator root 1702 1 0 21:58 ? 00:00:00 /usr/lib/vmware/bin/vmware-hostd -a /etc/vmware/hostd/config.xml root 1748 1 0 21:58 ? 00:00:00 login -- brian brian 1757 1748 0 21:58 tty1 00:00:00 -bash brian 1844 1757 0 21:58 tty1 00:00:00 -bash brian 1863 1844 0 21:58 tty1 00:00:00 xinit /etc/X11/xinit/xinitrc -- /usr/bin/X :0 vt1 -auth /home/brian/.s root 1864 1863 7 21:58 ? 00:00:08 /usr/bin/X :0 vt1 -auth /home/brian/.serverauth.1844 brian 1870 1863 0 21:58 ? 00:00:00 /bin/sh /usr/bin/startkde brian 1877 1 0 21:58 ? 00:00:00 dbus-launch --sh-syntax --exit-with-session brian 1878 1 0 21:58 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session brian 1945 1 0 21:58 ? 00:00:00 /usr/libexec/imsettings-daemon brian 1948 1 0 21:58 ? 00:00:00 /usr/libexec/gvfsd brian 1952 1 0 21:58 ? 00:00:00 /usr/libexec//gvfsd-fuse -f /run/user/1101/gvfs brian 1993 1870 0 21:58 ? 00:00:00 /usr/bin/ssh-agent /home/brian/.Xclients brian 2029 1 0 21:58 ? 00:00:00 /usr/libexec/kde4/start_kdeinit +kcminit_startup brian 2030 1 0 21:58 ? 00:00:00 kdeinit4: kdeinit4 Running... brian 2033 1 0 21:58 ? 00:00:00 kded4 brian 2035 1 0 21:58 ? 00:00:00 /usr/libexec/gam_server brian 2039 1 0 21:58 ? 00:00:00 /bin/kglobalaccel brian 2052 1 0 21:58 ? 00:00:00 /bin/kwalletd brian 2055 1 0 21:58 ? 00:00:00 kcminit_startup brian 2056 1 0 21:58 ? 00:00:00 /bin/kactivitymanagerd root 2057 1 0 21:58 ? 00:00:00 /usr/libexec/upowerd root 2104 1 0 21:58 ? 00:00:00 /usr/lib/udisks2/udisksd --no-debug brian 2112 1870 0 21:58 ? 00:00:00 kwrapper4 ksmserver brian 2113 2030 0 21:58 ? 00:00:00 ksmserver brian 2129 2113 5 21:58 ? 00:00:06 kwin -session 101fd1cf2161d7000137420220000000037480000_1375330249_957 brian 2135 1 0 21:58 ? 00:00:00 /bin/knotify4 brian 2139 1 6 21:58 ? 00:00:07 /bin/plasma-desktop brian 2145 2139 0 21:58 ? 00:00:00 ksysguardd brian 2149 1 0 21:58 ? 00:00:00 /usr/bin/kuiserver brian 2153 1 0 21:58 ? 00:00:00 /bin/akonadi_control brian 2155 2153 0 21:58 ? 00:00:00 akonadiserver brian 2156 2030 0 21:58 ? 00:00:00 kdeinit4: kio_trash [kdeinit] trash local:/tm brian 2158 2155 0 21:58 ? 00:00:00 /usr/libexec/mysqld --defaults-file=/home/brian/.local/share/akonadi/m brian 2190 1 0 21:58 ? 00:00:00 /usr/bin/vmtoolsd -n vmusr brian 2191 2030 0 21:58 ? 00:00:00 /bin/nepomukserver brian 2193 2191 0 21:58 ? 00:00:00 /bin/nepomukservicestub nepomukstorage brian 2198 2193 2 21:58 ? 00:00:03 /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_kn2193.ini + brian 2214 2153 0 21:58 ? 00:00:00 /bin/akonadi_agent_launcher akonadi_akonotes_resource akonadi_akonotes brian 2215 2153 0 21:58 ? 00:00:00 /bin/akonadi_archivemail_agent --identifier akonadi_archivemail_agent brian 2216 2153 0 21:58 ? 00:00:00 /bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts brian 2217 2153 0 21:58 ? 00:00:00 /bin/akonadi_agent_launcher akonadi_ical_resource akonadi_ical_resourc brian 2218 2153 0 21:58 ? 00:00:00 /bin/akonadi_agent_launcher akonadi_maildir_resource akonadi_maildir_r brian 2219 2153 0 21:58 ? 00:00:00 /bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_ brian 2220 2153 0 21:58 ? 00:00:00 /bin/akonadi_mailfilter_agent --identifier akonadi_mailfilter_agent brian 2221 2153 0 21:58 ? 00:00:00 /bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder brian 2258 2191 0 21:58 ? 00:00:00 /bin/nepomukservicestub nepomukfileindexer brian 2259 2191 0 21:58 ? 00:00:00 /bin/nepomukservicestub nepomukfilewatch root 2284 2 0 21:59 ? 00:00:00 [kworker/1:3] brian 2287 1 0 21:59 ? 00:00:00 /usr/bin/pulseaudio --start --log-target=syslog rtkit 2288 1 0 21:59 ? 00:00:00 /usr/libexec/rtkit-daemon brian 2315 2030 0 21:59 ? 00:00:00 klauncher --fd=12 brian 2317 2030 3 21:59 ? 00:00:02 /usr/lib/vmware/bin/vmware brian 2329 1 0 21:59 ? 00:00:00 /usr/libexec/gconfd-2 brian 2348 2030 3 21:59 ? 00:00:02 /usr/lib64/firefox/firefox brian 2375 1 0 21:59 ? 00:00:00 /usr/libexec/at-spi-bus-launcher brian 2376 2030 20 21:59 ? 00:00:13 /usr/lib64/thunderbird/thunderbird brian 2393 1 1 21:59 ? 00:00:00 /usr/lib/vmware/bin/vmware-tray poweredOn brian 2927 1 1 21:59 ? 00:00:00 /usr/lib/vmware/bin/vmware-unity-helper --daemon brian 3456 1 99 21:59 ? 00:01:02 /usr/lib/vmware/bin/vmware-vmx -s vmx.stdio.keep=TRUE -# product=1;nam root 3495 1 0 21:59 ? 00:00:00 /usr/sbin/pcscd --foreground --auto-exit root 3515 1 0 21:59 ? 00:00:00 /usr/libexec/packagekitd root 3519 3515 7 21:59 ? 00:00:02 /usr/bin/python /usr/share/PackageKit/helpers/yum/yumBackend.py get-up brian 3521 1 2 22:00 ? 00:00:00 konsole --workdir /home/brian brian 3523 3521 0 22:00 pts/0 00:00:00 /bin/bash brian 3605 3523 0 22:00 pts/0 00:00:00 ps -eaf
I'm seeing the same issue on two computers with Fedora 19 (fresh KDE configurations). Both computers are using nvidia graphics and the situation seems worse with the nvidia driver, compared to the nouveau driver. Most of the time, kde does not start completely on login. No krunner, klaunch, polkit-kde-authentication-agent-1, or other autostart (like klipper, kmix). Logout also does not work. Symptoms exactly like described. When doing enough logins (and killing X with ctrl+alt+bksp), eventually it will work properly once. Running kdm. No change when setting selinux to permissive mode.
Brian, I don't see the kdm process, or any other display manager. How precisely are you logging into your session, please? Lukas, I suppose your problem is the same as in bug #983110.
TBH, I was a little miffed why kdm wasn't listed either (I looked for it). There isn't a typo or missing line, it just wasn't running; and is very repeatable. I am using the nvidia module, with character (multi-user.target), run level 3. Then after login, "startx". Then today to research for this feedback, I switched back to the graphical (run level 5) login. Now I do have /usr/bin/kdm running as shown here along with anything directly started from kdm.: ps -eaf|grep kdm root 321 2 0 19:30 ? 00:00:00 [kdmflush] root 495 2 0 19:30 ? 00:00:00 [kdmflush] root 519 2 0 19:30 ? 00:00:00 [kdmflush] root 538 2 0 19:30 ? 00:00:00 [kdmflush] root 540 2 0 19:30 ? 00:00:00 [kdmflush] root 541 2 0 19:30 ? 00:00:00 [kdmflush] root 544 2 0 19:30 ? 00:00:00 [kdmflush] root 547 2 0 19:30 ? 00:00:00 [kdmflush] root 550 2 0 19:30 ? 00:00:00 [kdmflush] root 553 2 0 19:30 ? 00:00:00 [kdmflush] root 555 2 0 19:30 ? 00:00:00 [kdmflush] root 1784 1 0 19:30 ? 00:00:00 /usr/bin/kdm vt1 root 1791 1784 2 19:30 tty1 00:00:06 /usr/bin/X :0 vt1 -background none -nolisten tcp -auth /var/run/kdm/A:0-b1XHlb root 2627 2501 0 19:36 pts/0 00:00:00 grep --color=auto kdm [root@blackbird ~]# ps -eaf|grep 1784 root 1784 1 0 19:30 ? 00:00:00 /usr/bin/kdm vt1 root 1791 1784 1 19:30 tty1 00:00:06 /usr/bin/X :0 vt1 -background none -nolisten tcp -auth /var/run/kdm/A:0-b1XHlb root 1811 1784 0 19:30 ? 00:00:00 -:0 root 2629 2501 0 19:36 pts/0 00:00:00 grep --color=auto 1784 But even this this process running, the same symptoms of the original bug report are still present, no startup sound or apps, desktop icons, logout dialog, etc. No change on that front. Looking at the process tree, looks like X is a child of kdm. With the startx approach, X is a child of xinit (startx). I always thought kdm was the window manager, but guess it is the login manager. Guess that's why I'm opening bugs rather than resolving them :) Hope this helps.
This bug is pretty much invalid if you log in using startx (you don't go through the whole PAM process as defined in the DM's configuration so you don't have the environment set properly) but if it happens when KDM is used to log you in, it's an issue though. Just to clarify, you actually logged in through KDM, did you? If you did, this is a duplicate of #983110 so we'll just close this and continue there.
Just to add that I am getting something similar in 32bit Fedora 19 with KDM login/start and nvidia drivers.
To be clear, It happens both ways, with equal regularity. But I object to the believe that if it only happened with startx it isn't a bug, how can you say that. Command-line login with startx is a perfectly documented valid way to start a desktop, been that way for more years than I can count, and if it wasn't valid... then why is the startx command present?
As far as I remember, pulseaudio just does not support logging in without a DE and it's also a component that breaks first when there's something wrong with the session management stack. I have to admit you got me a bit unsure as it seems it could actually work with PA... in my past attempts to run KDE on its own it didn't though. Anyway, marking as a duplicate of #983110, symptoms are the same, let's please continue there. *** This bug has been marked as a duplicate of bug 983110 ***