Your message dated Wed, 30 Jun 2010 22:05:48 +0200
with message-id <[email protected]>
and subject line Re: Bug#573720: gvfs: busy loop fight between nautilus and
gnome-panel
has caused the Debian Bug report #573720,
regarding gvfs: busy loop fight between nautilus and gnome-panel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
573720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573720
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gvfs
Version: 1.4.3-1
Severity: important
Hello,
First, this is not the same machine as #573717, this one is worse :)
When I log in, everything is very slow, things don't work, ...
top tells me dbus-daemon isn't happy:
28039 messageb 20 0 3012 1368 728 R 21 0.3 1:26.80 dbus-daemon
30337 root 20 0 4920 2552 2152 S 20 0.5 1:17.24 devkit-disks-da
4355 bgoglin 20 0 2848 1084 604 S 10 0.2 0:15.84 dbus-daemon
4297 bgoglin 20 0 25688 5932 4936 S 3 1.2 0:04.93 x-session-manag
4433 bgoglin 20 0 19600 8548 2252 S 3 1.7 0:06.37 python
4378 bgoglin 20 0 18036 6996 5904 S 2 1.4 0:03.70 gnome-power-man
4379 bgoglin 20 0 25076 9916 5852 S 1 2.0 0:05.03 seahorse-daemon
4422 bgoglin 20 0 17536 2228 1304 S 1 0.4 0:01.91 gnome-screensav
4368 bgoglin 20 0 10432 6036 1988 S 1 1.2 0:02.51 gvfsd
gdb just tells me that dbus-daemon and devkit-disks-daemon are inside
the poll syscall or something like that, nothing useful to debug.
In .xsession-errors, I see what looks like a busy fight between
gnome-panel and nautilus, with dozens of lines like:
(nautilus:4404): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed
for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message
did not receive a reply (timeout by message bus)
(nautilus:4404): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.552 for
volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding
drives/volumes/mounts
(gnome-panel:4403): GVFS-RemoteVolumeMonitor-WARNING **: invoking List()
failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply:
Message did not receive a reply (timeout by message bus)
(gnome-panel:4403): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.558 for
volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding
drives/volumes/mounts
(nautilus:4404): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed
for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message
did not receive a reply (timeout by message bus)
(nautilus:4404): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.554 for
volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding
drives/volumes/mounts
(gnome-panel:4403): GVFS-RemoteVolumeMonitor-WARNING **: invoking List()
failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply:
Message did not receive a reply (timeout by message bus)
(gnome-panel:4403): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.560 for
volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding
drives/volumes/mounts
(gnome-panel:4403): GVFS-RemoteVolumeMonitor-WARNING **: invoking List()
failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply:
Message did not receive a reply (timeout by message bus)
(gnome-panel:4403): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.562 for
volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding
drives/volumes/mounts
(nautilus:4404): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed
for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message
did not receive a reply (timeout by message bus)
(nautilus:4404): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.556 for
volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding
drives/volumes/mounts
(nautilus:4404): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed
for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message
did not receive a reply (timeout by message bus)
(nautilus:4404): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.558 for
volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding
drives/volumes/mounts
And it ends up with
...Too much output, ignoring rest...
Let me know if you want to see the full output.
I don't have any strange drive attached to this machine, just one hard
drive with "normal" partitions. So I don't know what these guys are
fighting for. But it's really making the machine hardly usable.
The only workaround I found is to stop the dbus daemon before logging in,
but obviously it causes some other problems...
I removed my whole .gconf, .gnome*, .gvfs directories, it didn't help...
Brice
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: lang=fr...@euro, lc_ctype=fr...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages gvfs depends on:
ii devicekit-disks 009-3 abstraction for enumerating block
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libdbus-1-3 1.2.20-2 simple interprocess messaging syst
ii libgconf2-4 2.28.0-1 GNOME configuration database syste
ii libgdu0 2.28.1-3 GObject based Disk Utility Library
ii libglib2.0-0 2.22.4-1 The GLib library of C routines
ii libgnome-keyring0 2.28.2-1 GNOME keyring services library
ii libudev0 151-2 libudev shared library
ii x11-utils 7.5+2 X11 utilities
Versions of packages gvfs recommends:
ii dbus 1.2.20-2 simple interprocess messaging syst
ii policykit-1-gnome 0.96-2 GNOME authentication agent for Pol
Versions of packages gvfs suggests:
ii gvfs-backends 1.4.3-1 userspace virtual filesystem - bac
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, Mar 13, 2010 at 01:02:30PM +0100, Brice Goglin wrote:
> Package: gvfs
> Version: 1.4.3-1
> Severity: important
>
> Hello,
>
> First, this is not the same machine as #573717, this one is worse :)
>
> When I log in, everything is very slow, things don't work, ...
[...]
>
> In .xsession-errors, I see what looks like a busy fight between
> gnome-panel and nautilus, with dozens of lines like:
[...]
> The only workaround I found is to stop the dbus daemon before logging in,
> but obviously it causes some other problems...
>
> I removed my whole .gconf, .gnome*, .gvfs directories, it didn't help...
Hello,
I got tired of this problem so I uninstalled almost all packages,
manually removed all remaining dbus/gconf/... files that I found
on the machine, reinstalled everything back, and now I don't have
this problem anymore.
I guess this old install got screwed by some intermediate upgrade
in the last years...
Closing this bug now...
Brice
Note to Julien: you don't have the same problem if it only happens
with a single user. This bug was somewhere in the system-wide files.
--- End Message ---
