You are not logged in.

#1 2010-04-04 18:38:15

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,597
Website

GVFS-RemoteVolumeMonitor-WARNING / Gnome 2.30 - 30 sec delay on startx

I rebooted and did a ctrl+alt+F1, then logged in as root and did a telinit 3, logged out then logged back in as my normal user, and did a startx, here is the output.

GNOME_KEYRING_CONTROL=/tmp/keyring-ufreq9
GNOME_KEYRING_PID=4151
GNOME_KEYRING_CONTROL=/tmp/keyring-ufreq9
GNOME_KEYRING_CONTROL=/tmp/keyring-ufreq9
SSH_AUTH_SOCK=/tmp/keyring-ufreq9/ssh
Window manager warning: Failed to read saved session file /home/user/.config/metacity/sessions/108e8c5390b72cd083127040563076447300000041360020.ms: Failed to open file '/home/user/.config/metacity/sessions/108e8c5390b72cd083127040563076447300000041360020.ms': No such file or directory

(polkit-gnome-authentication-agent-1:4190): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'

(polkit-gnome-authentication-agent-1:4190): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
* Detected Session: gnome

(gnome-power-manager:4191): GLib-GObject-WARNING **: gsignal.c:2273: signal `proxy-status' is invalid for instance `0x1537f20'
* Searching for installed applications...
Initializing nautilus-image-converter extension
** Message: Initializing gksu extension...
* NVIDIA on Xorg detected, exporting: __GL_YIELD=NOTHING
* Using the GTK Interface
* Starting Compiz
... executing: compiz --replace --sm-disable --ignore-desktop-hints ccp --indirect-rendering

(gnome-settings-daemon:4150): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with
dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Note that there is a LONG pause between the "executing: compiz..." line and the gnome-settings-daemon/GVFS-RemoteVolumeMonitor-WARNING lines which is about 30 seconds on my machine.  Could this be the source of the 30 sec delay I am experiencing with Gnome 2.30?

BTW, here is ~/.xinitrc:

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
exec ck-launch-session gnome-session

Last edited by graysky (2010-04-04 18:39:19)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#2 2010-04-05 02:58:40

jarryson
Member
Registered: 2007-02-18
Posts: 298

Re: GVFS-RemoteVolumeMonitor-WARNING / Gnome 2.30 - 30 sec delay on startx

try this, or your gvfs won't be able to mount disks.

exec ck-launch-session dbus-launch --auto-syntax --exit-with-session gnome-session

Offline

#3 2010-04-05 13:24:21

ulukai
Member
Registered: 2009-10-16
Posts: 82

Re: GVFS-RemoteVolumeMonitor-WARNING / Gnome 2.30 - 30 sec delay on startx

jarryson wrote:

try this, or your gvfs won't be able to mount disks.

exec ck-launch-session dbus-launch --auto-syntax --exit-with-session gnome-session

Tried it, doesn't work sad

Offline

#4 2010-04-05 13:38:14

samurai
Member
From: Turkey
Registered: 2010-04-03
Posts: 28

Re: GVFS-RemoteVolumeMonitor-WARNING / Gnome 2.30 - 30 sec delay on startx

The problem persists. Here is my .xsession-errors:

/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
GNOME_KEYRING_CONTROL=/tmp/keyring-eDLBEh
SSH_AUTH_SOCK=/tmp/keyring-eDLBEh/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-eDLBEh
SSH_AUTH_SOCK=/tmp/keyring-eDLBEh/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-eDLBEh
SSH_AUTH_SOCK=/tmp/keyring-eDLBEh/ssh
Pencere yöneticisi uyarısı: Kaydedilmiş /home/yigit/.config/metacity/sessions/1025a51e1c2a30a87c127047054595427000000019620013.ms oturum dosyası okunamadı: '/home/yigit/.config/metacity/sessions/1025a51e1c2a30a87c127047054595427000000019620013.ms' dosyasını açma başarısız: Böyle bir dosya ya da dizin yok

(gnome-power-manager:2021): GLib-GObject-WARNING **: gsignal.c:2273: signal `proxy-status' is invalid for instance `0xd80b20'

(polkit-gnome-authentication-agent-1:2019): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'

(polkit-gnome-authentication-agent-1:2019): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
Initializing nautilus-open-terminal extension
** Message: Initializing gksu extension...
 panal başlatıcısı için epiphany.desktop masaüstü dosyası açılamadı
 panal başlatıcısı için evolution.desktop masaüstü dosyası açılamadı
Pencere yöneticisi uyarısı: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200087 (Mozilla Fi)
Pencere yöneticisi uyarısı: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/nppdf.so [/usr/lib/mozilla/plugins/nppdf.so: yanlış ELF sınıfı: ELFCLASS32]
LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/nppdf.so [/usr/lib/mozilla/plugins/nppdf.so: yanlış ELF sınıfı: ELFCLASS32]

Offline

#5 2010-09-30 19:17:16

Bapabooiee
Member
From: Canada
Registered: 2009-10-15
Posts: 6

Re: GVFS-RemoteVolumeMonitor-WARNING / Gnome 2.30 - 30 sec delay on startx

I've been experiencing this issue myself (albeit, I use Gentoo), and it's driven me mad as well. But, it appears there's a solution to this problem.

Apparently, it's caused by the udisks daemon trying to probe for non-existent Floppy drive(s), and then having to wait for it to time-out. It's been recognized by upstream, and should be fixed in their next release. For now, here's a patch you can apply.

Offline

#6 2010-09-30 19:42:18

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: GVFS-RemoteVolumeMonitor-WARNING / Gnome 2.30 - 30 sec delay on startx

Bapabooiee wrote:

I've been experiencing this issue myself (albeit, I use Gentoo), and it's driven me mad as well. But, it appears there's a solution to this problem.

Apparently, it's caused by the udisks daemon trying to probe for non-existent Floppy drive(s), and then having to wait for it to time-out. It's been recognized by upstream, and should be fixed in their next release. For now, here's a patch you can apply.

that patch exists for couples of months in our udisks package


Give what you have. To someone, it may be better than you dare to think.

Offline

#7 2010-09-30 19:56:05

Bapabooiee
Member
From: Canada
Registered: 2009-10-15
Posts: 6

Re: GVFS-RemoteVolumeMonitor-WARNING / Gnome 2.30 - 30 sec delay on startx

wonder wrote:

that patch exists for couples of months in our udisks package

Ah, I see. I figured that since nobody said anything about this being fixed on the forum, it may have still been an on-going issue -- and I just wanted to pass the fix along.

But it's good to see that this is resolved, as this has been really frustrating to deal with on Gentoo.

Offline

Board footer

Powered by FluxBB