dbus-daemon and gnome-vfs-daemon constantly restart

Bug #128024 reported by Martin Emrich
2
Affects Status Importance Assigned to Milestone
gnome-vfs2 (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

After adding two lines with NFS mounts to my /etc/fstab and saving, my CPU usage jumps to 100% with no apparent process consuming it. Upon watching the process list, I see two processes with their PIDs constantly increasing:

martin 12966 0.0 0.0 2764 340 ? R 18:30 0:00 dbus-daemon --fork --print-address 18 --print-pid 20 --session
martin 12967 0.0 0.1 8380 2724 ? R 18:30 0:00 /usr/lib/gnome-vfs-2.0/gnome-vfs-daemon

Their parent process is this one:

martin 5118 3.2 0.0 2764 1020 ? Rs 18:22 0:30 dbus-daemon --fork --print-address 18 --print-pid 20 --session

Revision history for this message
Martin Emrich (emme) wrote :

Here is an strace of a few seconds of the parent process.

While trying to post it to launchpad, my computer became more and more unresponsive, and I had to reboot.
After rebooting, the problem persists. Only after removing the NFS mounts from my fstab and rebooting again I can use my computer again.

Here are the NFS lines:
192.168.80.1:/home/martin /home/martin/serverhome nfs rw,user,noauto,async,soft,intr,nfsvers=3 0 0
192.168.80.1:/home/martin/files/media nfs /home/martin/files/media rw,user,noauto,async,soft,intr,nfsvers=3 0 0

I am running gutsy (installed from the Tribe 2 CD) i386, with current updates.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-vfs2:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Martin Emrich (emme) wrote :

I don't think I can attach to them fast enough, as they constantly re-spawn with different PIDs. For now, I tried to get an strace with this script:

#!/bin/bash
DBPIDS=`ps aux | grep dbus-daemon | grep martin | grep -v grep | cut -b 10-15 | xargs echo`
VFSPIDS=`ps aux | grep gnome-vfs-daemon | grep martin | grep -v grep | cut -b 10-15 | xargs echo`
STRACE_ARGS=`echo $DBPIDS $VFSPIDS | perl -e '$x = <>; @p=split(/ +/,$x); print join(" -p ",@p);'`
strace -p $STRACE_ARGS -o ~/bug128024-gnome-vfs-daemon+dbus-daemon-trace.txt

I started it (tracing all dbus-daemon or gnome-vfs-daemon processes belonging to me, an a second later, I saved my fstab with the NFS entries. A few seconds later, I ended the trace.

BTW: If one of them would SEGV, shouldn't apport be popping up? Or works apport only for specific processes?

Ciao

Martin

Revision history for this message
Sebastien Bacher (seb128) wrote :

unconfirming, I don't get the issue and the bug doesn't look like a priority since there is no other bugs opened about it yet, maybe somebody else can work on it

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Are you still getting this problem?

Revision history for this message
Martin Emrich (emme) wrote :

Yes, it's still there. My current workaround is to mount my NFS shares from the command line, but I hope this gets fixed for gutsy.

Ciao

Martin

Revision history for this message
Martin Emrich (emme) wrote :

I tried once again to see if it is fixed, but it is still there. Today I had the Idea of running dbus-monitor.
Attached is the output of ca. 3-4 seconds dbus-monitor, after enabling the lines in fstab.

Ciao

Martin

Changed in gnome-vfs2:
status: Incomplete → New
Revision history for this message
Martin Emrich (emme) wrote :

I tried once again (in hardy) and now it is fixed. As nobody else complained about this in gutsy, I'd recommend to mark the bug as invalid now.

Revision history for this message
Sebastien Bacher (seb128) wrote :

closing the bug

Changed in gnome-vfs2:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for the update, feel free to reopen if you get the issue again on hardy

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.