Long time issues with Gnome starting - GVFS

lafayette · 2010-04-15 21:11:38

Hi all,

I'm a medium experienced Arch user, but since the install I'm having troubles getting GNOME to work in a proper manner.

I have configured DAEMONS array so to have only hal started, and not dbus (that starts anyway, probably called by hal), but I can't manage to start GNOME.
Screen hangs and the console is filled with errors such as:

(nautilus:4140): 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:4139): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: 
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

and so on.

The only way to start GNOME is stopping dbus first, and then it works but not perfectly, since I get errors at startup like "polkit-agent crashed" and bug buddy pops up.

Note that starting from GDM or through startx leads to same results.

Any idea?

lafayette · 2010-04-16 10:23:39

Any hint?
Which daemons should I leave in rc.conf to start at boot?

breakdown · 2010-04-17 09:41:02

lafayette wrote:

Any hint?
Which daemons should I leave in rc.conf to start at boot?

I have the very same problem, I think this is related to gnome-disk-utility, since screen hangs is due to the gdu-notification-daemon that enters in some kind of a loop, and printing that kind of errors in the X logs.
The only "temporarly fix" that works for me, though is some bit "extreme" is to change the /etc/dbus-1/system.d/org.freedesktop.UDisks.conf and set your username as owner.

lafayette · 2010-04-17 11:19:56

I'll try asap.
It's pretty frustrating, and seems a spread issue between a bunch of forum users.

Furthermore, today I noticed that if I switch to a terminal and then back to Gnome-Xserver, the screen stays black, and the only solution is killing gnome-session and starting back again.

wonder · 2010-04-17 11:24:22

that issue should be fixed in libgnome-keyring 2.30.0-2

lafayette · 2010-04-17 11:34:04

I'm running with all the latest updates as today

lafayette · 2010-04-20 20:06:24

Updated to libgnome-keyring 2.30.0-2, still outputs in console:

(gnome-settings-daemon:1878): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.179 for volume monitor
org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts

(gnome-panel:1896): 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-settings-daemon:1878): 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:1896): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.177 for volume monitor
org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts

Still no hints on what's happening, X system is not stable at all and it's unusable. No one can help?

vi3dr0 · 2010-05-20 22:52:12

Bump please. I've got the same issue as lafayette. I just installed Gnome just for fun, but can't start it.

lafayette · 2010-05-21 11:51:11

I think I have almost solved (even if this happened only after switching to ubuntu - anyway arch is not responsible).

Do you have any ndiswrapper installed?
Try to ndiswrapper -r every driver you can find, and reboot. I had luck doing this, and now gnome works

vi3dr0 · 2010-05-21 12:46:09

I don't, and never did, use ndiswrapper, it must be something else. However I get exactly the same error you did.

JGC · 2010-05-21 15:45:43

Be sure you don't have a floppydrive enabled in BIOS if you don't have one. GVFS/udisks will wait for a long time trying to query your ghost floppydrive leading to timeouts and slowdowns.

lafayette · 2010-05-21 17:25:24

I'm sorry. It took weeks for me to troubleshoot, and as I said before, only installing a new distro gave me more hints on how to solve the problem. Try to boot in a safe runlevel, with as few things as possible, and also try to exclude some modules from being loaded. It's a painful way

Arch Linux

#1 2010-04-15 21:11:38

Long time issues with Gnome starting - GVFS

#2 2010-04-16 10:23:39

Re: Long time issues with Gnome starting - GVFS

#3 2010-04-17 09:41:02

Re: Long time issues with Gnome starting - GVFS

#4 2010-04-17 11:19:56

Re: Long time issues with Gnome starting - GVFS

#5 2010-04-17 11:24:22

Re: Long time issues with Gnome starting - GVFS

#6 2010-04-17 11:34:04

Re: Long time issues with Gnome starting - GVFS

#7 2010-04-20 20:06:24

Re: Long time issues with Gnome starting - GVFS

#8 2010-05-20 22:52:12

Re: Long time issues with Gnome starting - GVFS

#9 2010-05-21 11:51:11

Re: Long time issues with Gnome starting - GVFS

#10 2010-05-21 12:46:09

Re: Long time issues with Gnome starting - GVFS

#11 2010-05-21 15:45:43

Re: Long time issues with Gnome starting - GVFS

#12 2010-05-21 17:25:24

Re: Long time issues with Gnome starting - GVFS

Board footer