Baltix
nautilus package

Nautilus and Dbus errors

Bug #60959 reported by Julien Pivotto
10
Affects Status Importance Assigned to Milestone
GnomeVFS
Fix Released
Medium
gnome-vfs2 (Fedora)
Fix Released
Medium
gnome-vfs2 (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs
Ubuntu ubuntu-6.10
nautilus (Baltix)
Invalid
Undecided
Unassigned

Bug Description

hello,

when I launch Nautilus from enlightment, Volume monitoring doesn't work and network idem.
I receive somme messages like:

(nautilus:14549): libgnomevfs-WARNING **: Failed to open session DBUS connection: Failed to connect to socket /tmp/dbus-sKV4BWrcDK: Connexion refusée
Volume monitoring will not work.
14549: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2785.
This is normally a bug in some application using the D-Bus library.
14549: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2785.
This is normally a bug in some application using the D-Bus library.
** Message: Failed to close thumbnail pixbuf loader for /home/jux/mcf_affiche_2006.jpg: Format d'image non reconnu
** Message: Failed to close thumbnail pixbuf loader for /home/jux/out.pnm: Format d'image non reconnu
** Message: Failed to close thumbnail pixbuf loader for /home/jux/mcf_affiche_2006.jpg: Format d'image non reconnu
** Message: Failed to close thumbnail pixbuf loader for /home/jux/out.pnm: Format d'image non reconnu

(nautilus:14549): libgnomevfs-WARNING **: Failed to open session DBUS connection: Failed to connect to socket /tmp/dbus-sKV4BWrcDK: Connexion refusée
Volume monitoring will not work.

(nautilus:14549): libgnomevfs-WARNING **: Failed to open session DBUS connection: Failed to connect to socket /tmp/dbus-sKV4BWrcDK: Connexion refusée
Volume monitoring will not work.

(nautilus:14549): libgnomevfs-WARNING **: Failed to create service browser: Bad state

(nautilus:14549): libgnomevfs-WARNING **: Failed to create service browser: Bad state

(nautilus:14549): libgnomevfs-WARNING **: Failed to create service browser: Bad state

(nautilus:14549): libgnomevfs-WARNING **: Failed to create service browser: Bad state

(nautilus:14549): gnome-vfs-modules-WARNING **: Failed to create client: Daemon not running

Couldn't get main dbus connection: Failed to connect to socket /tmp/dbus-sKV4BWrcDK: Connexion refusée
Couldn't get main dbus connection: Failed to connect to socket /tmp/dbus-sKV4BWrcDK: Connexion refusée

Note: the original reporter indicated the bug was in package 'nautilus'; however, that package was not published in Baltix.

Revision history for this message
In , Daniel (daniel-redhat-bugs) wrote :

Description of problem:
If an application displays a GTK FileChooserDialog dialog when there is no DBus
daemon available it ends up trying to use a NULL DBus connection violating DBus
assertions. Fortunately our DBus builds have assertion checking enabled, if this
were turned off the app would likely trigger SEGV deferencing a null pointer.

(vfsdbus.py:3756): libgnomevfs-WARNING **: Failed to open session DBUS
connection: Unable to determine the address of the message bus (try 'man
dbus-launch' and 'man dbus-daemon' for help)
Volume monitoring will not work.
3756: arguments to dbus_connection_send_with_reply_and_block() were incorrect,
assertion "connection != NULL" failed in file dbus-connection.c line 2785.
This is normally a bug in some application using the D-Bus library.
3756: arguments to dbus_connection_send_with_reply_and_block() were incorrect,
assertion "connection != NULL" failed in file dbus-connection.c line 2785.
This is normally a bug in some application using the D-Bus library.

This can be reproduced with the following PyGTK code:

$ cat > vfsdemo.py <<EOF
#!/usr/bin/python

import gtk

fcdialog = gtk.FileChooserDialog("VFS demo",
                                 None,
                                 gtk.FILE_CHOOSER_ACTION_OPEN,
                                 (gtk.STOCK_CANCEL, gtk.RESPONSE_CANCEL,
                                  gtk.STOCK_OPEN, gtk.RESPONSE_ACCEPT),
                                 None)
response = fcdialog.run()
EOF
$ DBUS_SESSION_BUS_ADDRESS= python vfsdbus.py

Version-Release number of selected component (if applicable):
libgnome-2.16.0-2.fc6
gnome-vfs2-2.16.0-1.fc6
dbus-0.92-1.fc6

How reproducible:
Always

Steps to Reproduce:
1. Unset the DBUS_SESSION_BUS_ADDRESS variable
2. Run an application which displays a FileChooserDialog
3. Watch console

Actual results:
DBUs assertion failures displayed

Expected results:
No error / failure messages shown.

At least the assertion failures need to be cleaned up, but I think it could be
desirable to hide this first raw DBus message from view too:

(vfsdbus.py:3756): libgnomevfs-WARNING **: Failed to open session DBUS
connection: Unable to determine the address of the message bus (try 'man
dbus-launch' and 'man dbus-daemon' for help)

It makes it look like a nasty application error (resulting in bogus application
bug reports), when in fact its perfectly legitimate to use GTK without DBus
present (eg, ssh'd to a box as root & running a GUI app). A simple 'DBus session
daemon not available, disabling volume monitoring' would be sufficient & much
less scary to the user than this.

Revision history for this message
In , Matthias (matthias-redhat-bugs) wrote :

This will be fixed in 2.16.0-3

Revision history for this message
namesk (thetimemachine) wrote :

hi,
I have the same problem with nautilus since I upgraded to Edgy (Knot3). But when I restart DBus (/etc/init.d/dbus restart) I can see all my partitions from /etc/fstab:

GTK Accessibility Module initialized

(nautilus:15795): libgnomevfs-WARNING **: Failed to open session DBUS connection: 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.
Volume monitoring will not work.
15795: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2873.
This is normally a bug in some application using the D-Bus library.
15795: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2873.
This is normally a bug in some application using the D-Bus library.
Initializing nautilus-open-terminal extension

Revision history for this message
Daniel Holbach (dholbach) wrote :

That sounds more lika a Enligthenment problem to me. Do they start gnome-volume-manager, gnome-vfs-daemon, etc with the session?

Changed in nautilus:
status: Unconfirmed → Needs Info
Revision history for this message
namesk (thetimemachine) wrote :

Sorry, I forgot to mention that I am using the gnome. I can see In the gnome session manager that only gnome-volume-manager is started (no gnome-vfs-deamon)

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

The extra messages is a known upstream issue and will be fixed before edgy (either upstream or we will ship the patch attached to the upstream page):
http://bugzilla.gnome.org/show_bug.cgi?id=356772

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Untriaged → Low
status: Needs Info → Fix Committed
Bug Watch Updater (bug-watch-updater)
Changed in gnome-vfs:
status: Unknown → Unconfirmed
Changed in gnome-vfs2:
status: Unknown → Rejected
Mantas Kriaučiūnas (mantas)
Changed in nautilus:
status: Unconfirmed → Rejected
Revision history for this message
Sebastien Bacher (seb128) wrote :

This upload fixes the issue:

" gnome-vfs2 (2.16.1-0ubuntu1) edgy; urgency=low
 .
   * New upstream version:
     - Fix some leaks
     - Upgrade to latest xdgmime version
     - Fix crash on shutdown in http module
     - Fix sftp crash
   * debian/patches/16_no_extra_dbus_messages.patch:
     - cleanup of warnings when dbus is not running (Ubuntu: #60959)
"

Changed in gnome-vfs2:
status: Fix Committed → Fix Released
Revision history for this message
danik (danik21) wrote :

Hi

i'm an Italian student and i've installed the new Ubuntu 6.10.

After few hours, nautilus is became too much slow. Typing in the terminal:

danik@DNKPC:~$ sudo nautilus

(nautilus:5253): libgnomevfs-WARNING **: Failed to open session DBUS connection: 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.
Volume monitoring will not work.

Unfortunately, I'm not able to use in the right way the patch that is at

http://bugzilla.gnome.org/show_bug.cgi?id=356772

I hope someone could help me.

Thanks, danik

Bug Watch Updater (bug-watch-updater)
Changed in gnome-vfs2:
status: Rejected → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

danik, your problem might be a different one, you probably want to open a new bug for it

Bug Watch Updater (bug-watch-updater)
Changed in gnome-vfs:
status: New → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in gnome-vfs:
importance: Unknown → Medium
Bug Watch Updater (bug-watch-updater)
Changed in gnome-vfs2 (Fedora):
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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