It happened again this morning. This time I didn't have a nautilus open,
and there were no 'D' processes. One of the 2 sshfs mounts is unmounted,
the other one not. Killing the remaining sshfs gets gnome-panel to be
responsive again.
This starts to look a bit like
thank you for your work, it's clearly not a gnome-panel issue so closing
this bug
** Changed in: gnome-panel (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in ubuntu.
to reply to comment #6 as well gnome-panel read the recently used files
and the gtk bookmarks to build the place menu list so if you are
references to those mounts there and it tries to get datas on the files
(to know if they are still available, what icon to display, etc) it will
hang if the call
I rebooted and installed symbol files and setup a script to get a
backtrace from gnome-panel.
The problem just reoccurred, but I did't manage to attach to the running
gnome-panel to make a backtrace. Attaching makes gdb hang.
The main symptom is the same as before: the gnome-panel is
This log might also be relevant.
** Attachment added: daemon.log
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/736730/+attachment/1923734/+files/daemon.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel
something like this also hangs:
...
/bin/ls --color=auto
...
I narrowed this down a bit, it hangs with /bin/ls -l /home/vries and
doesn't hang with /bin/ls /home/vries.
I have 2 sshfs mounts in my home dir which could cause this.
xxx.xxx:/home/vries on /home/vries/gateway type fuse.sshfs
** Package changed: ubuntu = gnome-panel (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in ubuntu.
https://bugs.launchpad.net/bugs/736730
Title:
gnome-panel in uninterruptible sleep after system call
--
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
