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 e
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 o
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 corruptio
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 re
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 disap
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 r
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
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
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
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
tmpfs1635464 936 16345
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
Bugs, which is subscribed to
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 i
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 the
The file system error/check bug is here
http://ubuntuforums.org/showthread.php?t=1973178
This problem is not limited to kalarm.
--
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 1
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-session (Ubuntu)
Status: New => Confirmed
--
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
--
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:
17 matches
Mail list logo