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
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
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 n
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
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
Should be fixed by commit: 9bd45eea17deb4a93c774697550238251b048f07
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/541040
Title:
nepomukservicestub crashed with SIGSEGV in QIODevice::write()
To mana
