I'm sorry, I told you the wrong command. Could you please execute 'ps -eO stat | grep nepomuk' during a hung shutdown? I'll be particularly interested in any 'D's in the second or third column.
I'm interested in knowing which (if any) nepomuk services are hanging during a shut down. If they aren't hanging, but ubuntu is just forgetting to shut them down (which looks like it might be the case from your last comment) then I'm afraid that is something ubuntu specific and nothing to do with me - I just fix bugs in nepomuk sometimes. I emphasise that I need the ps executed *while* shutdown is hung - I want to know which process is blocking, so listing processes when they are not blocked doesn't help so much. Thanks On 12 February 2013 05:06, Nelly <1053...@bugs.launchpad.net> wrote: > nepomuk processes running in situation with good shutdown (after adding > the lines to ~/.kde/share/config/nepomukserverrc as described in my > message of feb 11 and deleting > /usr/share/autostart/nepomukcontroller.desktop) > > nelly 2066 1862 0 09:37 ? 00:00:00 > /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder > nelly 2098 1 0 09:37 ? 00:00:00 /usr/bin/nepomukserver > nelly 2920 2864 0 10:01 pts/0 00:00:00 grep --color=auto nepomuk > > > I have no NFS system running (rpcinfo not installed, no file /etc/exports) > > I have deleted the extra lines in ~/.kde/share/config/nepomukserverrc > and put the nepomukcontroller.desktop again in the map > /usr/share/autostart/. Shutdown was OK (file appears only affect the > system after a fresh start-up) > > Now nepomuk processes running are: > > nelly 2083 2007 0 10:28 ? 00:00:00 > /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder > nelly 2132 1 0 10:28 ? 00:00:00 /usr/bin/nepomukserver > nelly 2139 2132 0 10:28 ? 00:00:00 > /usr/bin/nepomukservicestub nepomukstorage > nelly 2157 2132 2 10:28 ? 00:00:04 > /usr/bin/nepomukservicestub nepomukfilewatch > nelly 2158 2132 0 10:28 ? 00:00:00 > /usr/bin/nepomukservicestub nepomukfileindexer > nelly 2159 2132 0 10:28 ? 00:00:00 > /usr/bin/nepomukservicestub nepomukbackupsync > nelly 2160 2132 0 10:28 ? 00:00:00 > /usr/bin/nepomukservicestub nepomukqueryservice > nelly 2392 2338 0 10:31 pts/0 00:00:00 grep --color=auto nepomuk > > ( the akonadi processes running were: > > nelly 2007 1 0 10:27 ? 00:00:00 /usr/bin/akonadi_control > nelly 2009 2007 0 10:27 ? 00:00:00 akonadiserver > nelly 2011 2009 0 10:27 ? 00:00:00 /usr/sbin/mysqld > --defaults-file=/home/nelly/.local/share/akonadi/mysql.conf > --datadir=/home/nelly/.local/share/akonadi/db_data/ > --socket=/home/nelly/.local/share/akonadi/socket-ecostat5/mysql.socket > nelly 2075 2007 0 10:28 ? 00:00:00 > /usr/bin/akonadi_agent_launcher akonadi_akonotes_resource > akonadi_akonotes_resource_0 > nelly 2076 2007 0 10:28 ? 00:00:00 > /usr/bin/akonadi_agent_launcher akonadi_contacts_resource > akonadi_contacts_resource_0 > nelly 2077 2007 0 10:28 ? 00:00:00 > /usr/bin/akonadi_agent_launcher akonadi_ical_resource > akonadi_ical_resource_0 > nelly 2078 2007 0 10:28 ? 00:00:00 > /usr/bin/akonadi_agent_launcher akonadi_kalarm_resource > akonadi_kalarm_resource_0 > nelly 2079 2007 0 10:28 ? 00:00:00 > /usr/bin/akonadi_agent_launcher akonadi_kalarm_resource > akonadi_kalarm_resource_1 > nelly 2080 2007 0 10:28 ? 00:00:00 > /usr/bin/akonadi_agent_launcher akonadi_kalarm_resource > akonadi_kalarm_resource_2 > nelly 2081 2007 0 10:28 ? 00:00:00 > /usr/bin/akonadi_agent_launcher akonadi_maildir_resource > akonadi_maildir_resource_0 > nelly 2082 2007 0 10:28 ? 00:00:00 > /usr/bin/akonadi_maildispatcher_agent --identifier > akonadi_maildispatcher_agent > nelly 2083 2007 0 10:28 ? 00:00:00 > /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder > nelly 2465 2338 0 10:37 pts/0 00:00:00 grep --color=auto akon > > The nepomukserverrc file had no effect omn the akonadi processes > running) > > I added again the extra lines in ~/.kde/share/config/nepomukserverrc and > removed the nepomukcontroller.desktop from in the map > /usr/share/autostart/. Shutdown was slow (all nepomuk processes were > still running) and the pop-up stating that an unknown process was still > running appeared again. After this restart the shutdown was OK again > (within a few seconds). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1053783 > > Title: > Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with > package info. > > Status in “gnome-session” package in Ubuntu: > Confirmed > > Bug description: > In Ubuntu 12.04, the shutdown is stalling - for about 2 minutes - but > only on occasions when I have opened - and then quit - KAlarm. > A window pops up Stating that, 'A Program is still running'; Unknown > (not responding); and, there are 3 buttons to choose: 'Lock Screen', > 'Cancel' and 'Shutdown Anyway'. > > Initial report was Bug #1053779 but had no package information. > > ProblemType: Bug > DistroRelease: Ubuntu 12.04 > Package: gnome-session-bin 3.2.1-0ubuntu8 > ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27 > Uname: Linux 3.2.0-30-generic-pae i686 > NonfreeKernelModules: nvidia > ApportVersion: 2.0.1-0ubuntu13 > Architecture: i386 > Date: Fri Sep 21 13:22:35 2012 > ExecutablePath: /usr/bin/gnome-session > InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 > (20120423) > ProcEnviron: > LANGUAGE=en_AU:en > PATH=(custom, no user) > LANG=en_AU.UTF-8 > SHELL=/bin/bash > SourcePackage: gnome-session > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs