Re: [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

2013-03-01 Thread 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

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


Re: [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

2013-02-28 Thread 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
10a470623400013606718180005290009_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 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


Re: [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

2013-02-17 Thread 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 1053...@bugs.launchpad.net 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/000: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


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

Re: [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

2013-02-16 Thread 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 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/000: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/000: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/000: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 

[Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

2013-02-11 Thread 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?

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