Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

[Mykel B]

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)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Innocent Bystander (innocent-bystander)]

I have exactly the same problem. In fact it gets worse. If I force the shut down I find that on restart a full file system check is forced and I am getting file system corruption!!!

My workaround is to log off before I shutdown. I log off and get a message that an unknown program is running and I force the logoff. Then I shut down. This seems to avoid the problem of file system corruption. However it means that shutdown has an annoying 2 minute wait (for the program to be terminated during logon) then I have to shut down.

Another workaround is to press the restart button on the computer. If I do this there is no annoying 2 minute wait and no file system corruption. It amazes me that hitting the red button is less problematic than doing an orderly shutdown.

So there are several problems here

1. I run kalarm and terminate it correctly. This results in a problem shutting the system down and at best a 2 minute delay. Problem #1.
2. The name of the offending program that is delaying the shutdown is not displayed. You only get "unknown". Problem number
#2.
3. There is a 2 minute delay after you choose to force termination of the program. Problem #3
4. File system check forced on restart. Problem #4.
5. File system corruption detected on restart. Problem #5.

This is the flakiest linux install since Slackware with Linux 0.99 which was flaky mainly due to the X driver.

[Innocent Bystander (innocent-bystander)]

The file system error/check bug is here http://ubuntuforums.org/showthread.php?t=1973178

This problem is not limited to kalarm.

[alcachi (alcachi)]

I was suffering the same problem in Ubuntu 12.04 both in Unity and Gnome Desktops, so I tried to look for the source and even if you can close kalarm correctly the nepomuk and akonadi servers continue to run in the background.

After exiting kalarm if you kill manually akonadi and nepomukserver then you can close the unity/gnome session in Ubuntu 12.04 without errors.

So the problem seems to be related to nepomuk and akonadi.

NOTE: This problem has been reported also in the KDE Bugtracking System but it seems it only affects Ubuntu.

[Nelly (launch-ecostat)]

I also have this bug.
I use KAlarm and my computer with Ubuntu 12.04 (Gnome desktop) took several minutes to shutdown.

Link http://ubuntuforums.org/showthread.php?t=1764048 gave me the hint how to solve this problem. This link contains methods to prevent te starting up of nepomuk and akonadi in 3 steps.
If you don't want to use KAlarm, it might be safe to apply all three steps. However, doing so, KAlarm could not be used. It asked to start-up akonadi first. So I tried what would happen if I only used the two steps preventing the (complete) start-up of nepomuk, and that worked great. KAlarm works and Ubuntu 12.04 shuts down within a few seconds. The steps to apply are:

1. Add the following lines to ~/.kde/share/config/nepomukserverrc (and their sections if they don't exist) (change the value from "true" to "false" if they do exist and are set on "true";

[Basic Settings]
Start Nepomuk=false

[Service-nepomukmigration1]
autostart=false

[Service-nepomukstrigiservice]
autostart=false

2. Remove the file /usr/share/autostart/nepomukcontroller.desktop, if it exists.

[Bladud (bladud)]

When shutdown is hung, can you find out which nepomuk processes are still running?

You can do this by executing 'ps -ef | grep nepomuk' at a terminal.

Also, do you have any network filesystems?

[Innocent Bystander (innocent-bystander)]

I have no NFS file systems. I never have and I don't even know how to
set them up.

> df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda6 115345448 41550852 67935296 38% /
udev 4076624 4 4076620 1% /dev
tmpfs 1635464 936 1634528 1% /run
none 5120 0 5120 0% /run/lock
none 4088652 2596 4086056 1% /run/shm
/dev/sda7 336443396 257672676 61680376 81% /home3
/dev/sdb5 365367160 36495920 310311672 11% /home4
/dev/sdb1 115353540 37911128 71582708 35% /home2

Here is a PS as requested which I ran earlier. This was a ps auxf - as
 have turned nepo* off I can't readily do the exact command you
requested. This particular ps may in fact have been done before the
shutdown was requested.

tim 14522 1.7 0.3 647640 30540 ? Sl 23:08 0:00 \_
/usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
tim 14571 0.2 0.1 230884 11716 ? Sl 23:08 0:00
/usr/bin/nepomukserver
tim 14577 5.6 0.4 1255452 37948 ? SNl 23:08 0:00 \_
/usr/bin/nepomukservicestub nepomukstorage
tim 14600 2.0 0.3 644180 29452 ? SNl 23:08 0:00 \_
/usr/bin/nepomukservicestub nepomukfileindexer
tim 14601 1.3 0.3 475160 25016 ? SNl 23:08 0:00 \_
/usr/bin/nepomukservicestub nepomukqueryservice
tim 14602 1.5 0.3 543168 27536 ? SNl 23:08 0:00 \_
/usr/bin/nepomukservicestub nepomukbackupsync
tim 14603 6.2 0.3 702476 27396 ? SNl 23:08 0:00 \_
/usr/bin/nepomukservicestub nepomukfilewatch

I am willing to turn it on again if needed to get the diagnostic info.
Let me know.

Tim Josling

On Tue, Feb 12, 2013 at 4:42 PM, Bladud <email address hidden> wrote:
> When shutdown is hung, can you find out which nepomuk processes are
> still running?
>
> You can do this by executing 'ps -ef | grep nepomuk' at a terminal.
>
> Also, do you have any network filesystems?
>
> --
> 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:
> LANG...

[Nelly (launch-ecostat)]

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 ...

[Bladud (bladud)]

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 <email address hidden> 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_agen...

[Nelly (launch-ecostat)]

Answer to Bladud (#10)

I first tried ps -e0 stat | grep nepomuk during normal run-time to see what kind of results I might expect. It did not work.

 "ps -el | grep nepomuk" resulted in:
0 S 1000 2158 1 0 80 0 - 14441 poll_s ? 00:00:00 nepomukserver
0 S 1000 3467 3344 0 80 0 - 32744 poll_s ? 00:00:00 akonadi_nepomuk
0 S 1000 3520 1 0 80 0 - 14441 poll_s ? 00:00:00 nepomukserver

and
 "ps -eF | grep nepomuk" resulted in:
nelly 2158 1 0 14441 8700 0 10:42 ? 00:00:00 /usr/bin/nepomukserver
nelly 3467 3344 0 32744 26304 0 12:22 ? 00:00:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
nelly 3520 1 0 14441 8700 1 12:23 ? 00:00:00 /usr/bin/nepomukserver
nelly 3810 3723 0 1103 832 0 13:20 pts/0 00:00:00 grep --color=auto nepomuk

Is either of these the kind of output you are looking for? Which one?

[Bladud (bladud)]

Yes, -el is right. The second column is what I'm looking for. Could you
post the results during a hung shutdown with nepomuk enabled, please?

On 17 February 2013 07:28, Nelly <email address hidden> wrote:

> Answer to Bladud (#10)
>
> I first tried ps -e0 stat | grep nepomuk during normal run-time to see
> what kind of results I might expect. It did not work.
>
> "ps -el | grep nepomuk" resulted in:
> 0 S 1000 2158 1 0 80 0 - 14441 poll_s ? 00:00:00
> nepomukserver
> 0 S 1000 3467 3344 0 80 0 - 32744 poll_s ? 00:00:00
> akonadi_nepomuk
> 0 S 1000 3520 1 0 80 0 - 14441 poll_s ? 00:00:00
> nepomukserver
>
> and
> "ps -eF | grep nepomuk" resulted in:
> nelly 2158 1 0 14441 8700 0 10:42 ? 00:00:00
> /usr/bin/nepomukserver
> nelly 3467 3344 0 32744 26304 0 12:22 ? 00:00:00
> /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
> nelly 3520 1 0 14441 8700 1 12:23 ? 00:00:00
> /usr/bin/nepomukserver
> nelly 3810 3723 0 1103 832 0 13:20 pts/0 00:00:00 grep
> --color=auto nepomuk
>
> Is either of these the kind of output you are looking for? Which one?
>
> --
> 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
>

[Nelly (launch-ecostat)]

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.

[Bladud (bladud)]

Thank you, what you did was exactly right, and interestingly there is this
suggestive line:
"0 D 1000 2198 2108 7 99 - - 32215 sleep_ R 00:00:02 nepomukservices"

However, I really need ps to not truncate the output...does

" ps -wweo pid,state,args | grep nepomuk"

work for you? I only need the results from the first test again.

It should look something like:
2487 S /usr/bin/nepomukserver
9797 S /usr/bin/nepomukservicestub nepomukstorage
9857 S /usr/bin/nepomukcontroller -session
10a4706234000136067181800000005290009_1362030556_932758
9900 S /usr/bin/nepomukservicestub nepomukfileindexer
9901 S /usr/bin/nepomukservicestub nepomukfilewatch

but longer.

Could you also tell me exactly the version of the nepomuk package
installed?

Thanks

[Innocent Bystander (innocent-bystander)]

Hi

I've turned lots of things off so it might take me a while to get this
to you. I thought I had nepomuk completely suppressed however I see it
is still running.

I have attached the output from the command which I just issued. So
obviously something is still running. I am still getting corruption of
the file system also.

I have attached also a list from the Ubuntu sw management tool to show
which versions are installed.

Thanks for following this up.

Regards,
Tim Josling

On Fri, Mar 1, 2013 at 3:34 PM, Bladud <email address hidden> wrote:
> Thank you, what you did was exactly right, and interestingly there is this
> suggestive line:
> "0 D 1000 2198 2108 7 99 - - 32215 sleep_ R 00:00:02 nepomukservices"
>
> However, I really need ps to not truncate the output...does
>
> " ps -wweo pid,state,args | grep nepomuk"
>
> work for you? I only need the results from the first test again.
>
> It should look something like:
> 2487 S /usr/bin/nepomukserver
> 9797 S /usr/bin/nepomukservicestub nepomukstorage
> 9857 S /usr/bin/nepomukcontroller -session
> 10a4706234000136067181800000005290009_1362030556_932758
> 9900 S /usr/bin/nepomukservicestub nepomukfileindexer
> 9901 S /usr/bin/nepomukservicestub nepomukfilewatch
>
> but longer.
>
> Could you also tell me exactly the version of the nepomuk package
> installed?
>
>
> Thanks
>
> --
> 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

[Nelly (launch-ecostat)]

Hi Bladud,

I have again turned on nepomuk and shutdown. Started again and during the second shutdown, the command suggested by you,
"ps -wweo pid,state,args | grep nepomuk" gave the following result (during shutdown fase, every 2 sec ps command was given, results from are given from the last one (about 34 sec. after the shutdown command)):

2049 S /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
2094 S /usr/bin/nepomukserver
2099 S /usr/bin/nepomukservicestub nepomukstorage
2123 S /usr/bin/nepomukservicestub nepomukqueryservice
2124 S /usr/bin/nepomukservicestub nepomukfilewatch
2125 S /usr/bin/nepomukservicestub nepomukbackupsync
2126 S /usr/bin/nepomukservicestub nepomukfileindexer
2431 S grep nepomuk
     S /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
2094 S /usr/bin/nepomukserver
2099 S /usr/bin/nepomukservicestub nepomukstorage
2123 S /usr/bin/nepomukservicestub nepomukqueryservice
2124 S /usr/bin/nepomukservicestub nepomukfilewatch
2125 S /usr/bin/nepomukservicestub nepomukbackupsync
2126 S /usr/bin/nepomukservicestub nepomukfileindexer
2431 S grep nepomuk

My version of nepomuk is: kde-runtime-data 4:4.8.5-0ubuntu0.1

Success with finding the cause of the bug.

Nelly

[Bladud (bladud)]

Hey,

Ok, thanks. I see that in this second trace none of the processes are
stuck, they are just taking a while to shutdown.

The information you suggested to me suggests that this is a new
manifestation of a common shutdown bug where stopping down the various
nepomuk processes would race against each other.

This should have been fixed in the latest release, so my recommendation to
you would be to update your nepomuk, akonadi, soprano and kalarm packages
to the latest (4.10.1) version, when it becomes available next week. You
will be able to get them from the kubuntu ppa as explained here:

http://www.kubuntu.org/news/kde-sc-4.10

That should fix the slow shutdown, but to be clear, if your filesystem
isn't unmounting properly, that's nothing to do with nepomuk - it's an
ubuntu specific problem, and there's nothing I can do about it. Especially
since you say it seems to happen even with nepomuk switched off.

Thanks