Launchpad has imported 2 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=207121.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2006-09-19T15:17:44+00:00 Daniel 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. Reply at: https://bugs.launchpad.net/baltix/+source/nautilus/+bug/60959/comments/1 ------------------------------------------------------------------------ On 2006-09-19T17:55:14+00:00 Matthias wrote: This will be fixed in 2.16.0-3 Reply at: https://bugs.launchpad.net/baltix/+source/nautilus/+bug/60959/comments/2 ** Changed in: gnome-vfs2 (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/60959 Title: Nautilus and Dbus errors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-vfs/+bug/60959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
