Ubuntu
nautilus package

nautilus doesn't work without dbus service

Bug #57389 reported by Matti Lindell
2
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu Edgy
Architecture: i386
Version: 2.15.92.1-0ubuntu1

nautilus doesn't seem to work without up and running dbus service.
dbus is not listed on nautilus package Depends, is this a feature or a bug?

$ nautilus .

(nautilus:13833): 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.
13833: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2778.
This is normally a bug in some application using the D-BUS library.
13833: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2778.
This is normally a bug in some application using the D-BUS library.

** (nautilus:13833): CRITICAL **: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused

** ERROR **: file oobs-session.c: line 104 (oobs_session_init): should not be reached
aborting...
Aborted

Revision history for this message
Mateusz Drożdżyński (matid) wrote :

Thanks for your bug report. Nautilus depends on libgnomevfs2-0, which depends on libdbus-1-2, what de facto makes it depend on libdbus-1-2.

You can issue this command to see that these dependencies are there:
apt-cache --recurse depends nautilus | grep dbus

Changed in nautilus:
status: Unconfirmed → Rejected
Revision history for this message
Mateusz Drożdżyński (matid) wrote :

I rejected your bug. Feel free to reopen it after rephrasing your problem if you think that it is still a bug.

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

Mateusz, I think this bug report is about nautilus dealing with stuff like
  sudo /etc/init.d/dbus restart
which is problematic and not easy to solve, but a minor bug, as we don't just restart dbus.

Revision history for this message
Mateusz Drożdżyński (matid) wrote :

Daniel: That's why I asked to reopen if that's the problem.

Changed the status to needs info.

mlind: Could you please clarify how can one reproduce your bug?

Changed in nautilus:
status: Rejected → Needs Info
Revision history for this message
Matti Lindell (mlind) wrote :

I ran into this while using Edgy on a chroot, which has no /dev or /var/run/dbus --bind mounted, so Edgy's nautilus can't see running dbus. I didn't think of looking dependencies recursively, so I guess this is sorted.

That dbus restart bug seems to plague many (all?) applications that connect to running dbus instance. I've experienced it with rhythmbox and banshee at least.

You can close this as rejected.

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

Thanks for following up. Closing the bug.

Changed in nautilus:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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