No Object for D-Bus Interface

Bug #1295927 reported by Jeffrey Walton
52
This bug affects 11 people
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have a multiboot laptop with 4 OS'es. The laptop is UEFI, and the disks use GPTs.

When I navigate Places -> SHARED (SHARED is a NTFS GPT drive), then I receive an error "No Object for D-Bus Interface" (see attached).

In fact, any of the drives that are listed in the menu cause the error. The list of drives are "SHARED", "Windows 8", "Debian", "Recovery", and "Fedora".

I'm using GNOME Fallback because this is a laptop, and not a tablet.

$ uname -a
Linux ubuntu-q500 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda9 during installation
UUID=cf88a77e-e7cb-4525-b892-6b0397437ee1 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda2 during installation
UUID=C2C9-8440 /boot/efi vfat defaults 0 1
# swap was on /dev/sda5 during installation
UUID=41d91b42-fbd0-4e05-9ba0-b5fff026b8fc none swap sw 0 0

Revision history for this message
Jeffrey Walton (noloader) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dbus (Ubuntu):
status: New → Confirmed
Revision history for this message
adrhc (adrhc) wrote :

I have Asrock N3150DC-ITX with UEFI and a SATA 2 WD 500Gb with same problem.

adr@adr-desktop:~$ uname -a
Linux adr-desktop 3.19.0-30-generic #33-Ubuntu SMP Mon Sep 21 20:58:04 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

adr@adr-desktop:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=e86c824e-d5b8-4814-8a40-87156e9fedb1 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=8194-56FD /boot/efi vfat umask=0077 0 1
# swap was on /dev/sda3 during installation
UUID=6bf0cd90-f11f-4ee6-8ee0-d362ab69015b none swap sw 0 0

Revision history for this message
g.ptic (g.ptic-deactivatedaccount) wrote :

Recently, the same problem appears on my system too:

- Ubuntu 15.10 x64
- 5 internal drives (out of which 3 are auto-mounted via fstab)

Trying to mount those 2 drives via Nautilus which are not auto-mounted via fstab failed with the above mentioned error message. Via gnome-disks I could mount the same drives without any problem. The error appeared independently on two different user accounts.

The same issue is also reported here with instructions for how to fix the issue:
https://askubuntu.com/questions/627621/no-object-for-d-bus-interface-when-mounting-with-nautilus

On Ubuntu 15.10, the following commands worked for me:

sudo umount -fl /run/user/[USER ID]/gvfs
sudo rm -rf /run/user/[USER ID]/gvfs

However, the error re-appeared after some time, so the fix may only be a temporary solution.

Revision history for this message
Thilo Cestonaro (tephraim) wrote :

Another workaround is:
Every time you want to mount a partition with this error, open gparted, wait until drive informations were refreshed and close it. After that nautilus is able to mount it.

Anyway, please fix this! :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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