Answer to Bladud (#10 + #12) I have tried to run the command "ps -el | grep nepomuk" as long as possible after the shutdown command (given with the GUI logout button) using a BASH function giving that command every 2 sec and saving the results in a file. After 20-30 sec. the termninal window disappears and the function stops. I don't find differences in the result just before giving the logout command and during these seconds hanging. I have performed the test twice, once with the nepomuk functions working and programmed to start in the next logon, and once after I had prevented the starting of some nepomuk services at start-up (see #6). Surprisingly the results of these two tests differed slightly.
The first test gave: 0 S 1000 2062 1987 0 80 0 - 32753 poll_s R 00:00:00 akonadi_nepomuk 0 S 1000 2108 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 0 S 1000 2114 2108 2 99 - - 49593 poll_s R 00:00:00 nepomukservices 0 D 1000 2198 2108 7 99 - - 32215 sleep_ R 00:00:02 nepomukservices 0 S 1000 2199 2108 0 99 - - 32401 futex_ R 00:00:00 nepomukservices 0 S 1000 2200 2108 0 99 - - 26909 poll_s R 00:00:00 nepomukservices 0 S 1000 2201 2108 0 99 - - 25321 poll_s R 00:00:00 nepomukservices S 1000 2062 1987 0 80 0 - 32753 poll_s R 00:00:00 akonadi_nepomuk 0 S 1000 2108 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 0 S 1000 2114 2108 2 99 - - 49593 poll_s R 00:00:00 nepomukservices 0 D 1000 2198 2108 7 99 - - 32215 sleep_ R 00:00:02 nepomukservices 0 S 1000 2199 2108 0 99 - - 32401 futex_ R 00:00:00 nepomukservices 0 S 1000 2200 2108 0 99 - - 26909 poll_s R 00:00:00 nepomukservices 0 S 1000 2201 2108 0 99 - - 25321 poll_s R 00:00:00 nepomukservices and the second test: 0 S 1000 2052 1989 0 80 0 - 33984 poll_s R 00:00:00 akonadi_nepomuk 0 S 1000 2101 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 0 S 1000 2106 2101 0 99 - - 54348 poll_s R 00:00:00 nepomukservices 0 S 1000 2126 2101 0 99 - - 32400 futex_ R 00:00:00 nepomukservices 0 S 1000 2127 2101 0 99 - - 26945 poll_s R 00:00:00 nepomukservices 0 S 1000 2128 2101 0 99 - - 25321 poll_s R 00:00:00 nepomukservices 0 S 1000 2129 2101 0 99 - - 32536 poll_s R 00:00:03 nepomukservices S 1000 2052 1989 0 80 0 - 33984 poll_s R 00:00:00 akonadi_nepomuk 0 S 1000 2101 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 0 S 1000 2106 2101 0 99 - - 54348 poll_s R 00:00:00 nepomukservices 0 S 1000 2126 2101 0 99 - - 32400 futex_ R 00:00:00 nepomukservices 0 S 1000 2127 2101 0 99 - - 26945 poll_s R 00:00:00 nepomukservices 0 S 1000 2128 2101 0 99 - - 25321 poll_s R 00:00:00 nepomukservices 0 S 1000 2129 2101 0 99 - - 32536 poll_s R 00:00:03 nepomukservices Hope this helps. What happens during the rest of the shutdown cannot be tested easily because the computer is no longer accessible. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs