Unable to mount location -- Internal error: No mount object for mounted volume

[mattismyname]

Binary package hint: nautilus

First, some information about my system:

  matt@Aluminumy:~$ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=8.10
  DISTRIB_CODENAME=intrepid
  DISTRIB_DESCRIPTION="Ubuntu intrepid (development branch)"

  matt@Aluminumy:~$ uname -a
  Linux Aluminumy 2.6.26-5-generic #1 SMP Sun Aug 3 01:25:54 UTC 2008 i686 GNU/Linux

  matt@Aluminumy:~$ dpkg-query -s nautilus
  Package: nautilus
  Status: install ok installed
  Priority: optional
  Section: gnome
  Installed-Size: 2340
  Maintainer: Ubuntu Desktop Team <email address hidden>
  Architecture: i386
  Version: 1:2.23.6.1-0ubuntu1

  matt@Aluminumy:~$ dpkg-query -s gvfs
  Package: gvfs
  Status: install ok installed
  Priority: optional
  Section: libs
  Installed-Size: 1916
  Maintainer: Ubuntu Desktop Team <email address hidden>
  Architecture: i386
  Version: 0.99.4-0ubuntu1

Now the problem description:

I open the "computer:///" in nautilus. One of the items listed is "5.0 GB Media" with an unmounted drive icon next to it. This drive is not listed in /etc/fstab. I double-click on the drive to mount it. Nautilus pops up a dialog box that says "Unable to mount location -- Internal error: No mount object for mounted volume". However, the drive does actually become mounted. An icon pops up on the desktop and I can browse the files. When the volume is mounted, 'df' shows it as: "/dev/sda6 4767428 4122020 403232 92% /media/disk".

[Sebastien Bacher (seb128)]

thank you for your bug report. do you have the using using any drive or just this one? is that specific to the computer location?

[mattismyname (mattismyname)]

It seems to only occur with this one drive. I use many other
flash/camera/flickrfs/etc filesystems with the system and they all
work fine.

On Mon, Aug 11, 2008 at 12:37 AM, Sebastien Bacher <email address hidden> wrote:
> thank you for your bug report. do you have the using using any drive or
> just this one? is that specific to the computer location?
>
> ** Changed in: nautilus (Ubuntu)
> Importance: Undecided => Low
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: New => Incomplete
>
> --
> Unable to mount location -- Internal error: No mount object for mounted volume
> https://bugs.launchpad.net/bugs/256749
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Petri Järvisalo (reaby)]

Same problem here, but it's on all volumes not just for one spesific.

[Daniel Hollocher (chogydan)]

This happens for me when I try to mount different partitions on my disk, and just in the way described. Changing status to confirmed since it is unclear what information was being requested.

[Sebastien Bacher (seb128)]

the issue is an upstream one, could somebody having the bug open it on bugzilla.gnome.org?

[KevinM (kevbert1)]

This bug also occurs in Intrepid Alpha5 64 bit - Kernel 2.6.27-2-generic.
The message is displayed, but the drive still mounts (see attached)

[Daniel Hollocher (chogydan)]

well, the error message has gone away, so its time to invalidate this bug. But, there is still a lingering problem. Before, the drive was mounted, and an error message was displayed. Now, the drive is mounted.

The ORIGINAL behaviour was to mount the drive and then also open a nautilus window showing the drive.

So maybe a new bug report should be filed? I dunno, but Im invalidating these bugs for the time being.

[Panayiotis Savva (psavva)]

I got this exact same problem.

I have 2 ntfs drives that i mount, and also comes up with "Internal error: No mount object for mounted volume"

I got Interpid Ibex Beta

[Alastair Sherringham (asherringham)]

Any partition not mounted but available in the "Computer" option.

If I double-click either of the 2 other unmounted partitions I have, I get this message (but the mount happens).

If I plug in a USB stick - it automounts on desktop and a nautilus window opens. OK.
If I close the browser and right-click/unmount the USB stick, icon goes away.
If I double-click the USB stick in the "Computer" window, to re-mount, I get the error message.

This is a fully updated Intrepid as of 2008-10-19.

[Daniel Hollocher (chogydan)]

well, if you guys want me to reopen this bug, I can. If you are quite sure of yourself about this bug, and its reproducibility, then lets reopen. BTW, you guys can open the bug yourself too.

But, you may want to wait till the release candidate is released, to see if this bug is still around.

[Stephen (stephenfranciscogomez)]

I can confirm that this bug is absolutely genuine and reproducible.

This is purely speculation but could this be a synchronisation problem between nautilus and gvfs? Selecting a link in the "Computer" menu should result in the volume first being mounted and then being opened in a nautilus window. Is it possible that nautilus is jumping the gun so to speak, and trying to open the volume before it has been mounted?

[VladimirCZ (vlabla)]

I can confirm:

What KevinM wrote, but for Beta 64bit, fully updated:
"This bug also occurs in Intrepid Alpha5 64 bit - Kernel 2.6.27-2-generic.
The message is displayed, but the drive still mounts (see attached)"

And this:
!!! happens only when I double-click any unmounted drive in the main pane of nautilus in the location "computer:///"
!!! when I single click any unmounted drive in the side pane of nautilus, then mounting is done without the false message

Specs:
OS Ubuntu 8.10 Beta 64-bit fully updated

[wraj (aamit-wraj-gmail)]

I can confirm it too...

The only difference being that I am on the Final Release that I downloaded yesterday...
I too get the same erratic dialog when I double click over it and the things still goes fine after neglecting that message that pops out...But when I right click and choose the mount option,things goes kinda fine and the drive is shown mounted and I can enter into it without any hassle by double clicking it !!!

I repeat my specs : Ubuntu 8.10 (Final Release) plus all the updates released till date (excluding linux-headers-2.6.27-7,linux-headers-2.6.27-7-generic & linux-image-2.6.27-7 generic)

[David Balažic (xerces8)]

8.10 i386 (boot live from the desktop cd)

 - go Places / Computer
 - open (doubleclick) a HD partition (ntfs in my case)
The dialog appears:

Unable to mount location
Internal error: No mount object for mounted volume
[OK]

But it is mounted and usable. An icon for it appears on the desktop.

Why is the bug "Invalid" ?

[Marion Smith (msmith-extremeprogrammers)]

I can also confirm this error. It happens for me exactly as David Balazic describes it. I also get it when mounting a USB. I have not tested it with a SD chip.

[manzur (sl-solaris)]

i have the same problem, it sometimes show me this error, but it mount the volume anyway, you can see it in the screen shot i send you, can you see PRESARIO volume icon on desktop?

[seldon7 (ubuntu-pengo)]

I can confirm also that the problem remains in 8.10 final.

A bit annoying because I use this machine to stream video to a media device and every time I boot it up I have to go into the computer, click the ntfs drive I want to mount, get the error message and then click it again. I seem to remember that 8.04 mounted the ntfs drive automatically on bootup which meant I just had to power on this machine and itd do the rest itself.

[Stu Zhao (sao3)]

I can confirm this. it's really annoying when you click a unmounted disk in 'computer:///' and you got a error message. But there is just nothing wrong, the disk is mounted correctly, but nautilus won't enter the disk.

[Marion Smith (msmith-extremeprogrammers)]

I am pleased to report that this has been fixed on my system. I did nothing myself, so I assume it came from a pushed patch. Thanks to all the great developers that work so hard to give us a choice other than M$.

[Antariksh (lonalo-donado)]

Dear Smith,

How did u get it removed, by some update or what. Kindly suggest

cheers
Antariksh

________________________________
From: Marion Smith <email address hidden>
To: <email address hidden>
Sent: Sunday, November 16, 2008 6:17:54 PM
Subject: [Bug 256749] Re: Unable to mount location -- Internal error: No mount object for mounted volume

I am pleased to report that this has been fixed on my system. I did
nothing myself, so I assume it came from a pushed patch. Thanks to all
the great developers that work so hard to give us a choice other than
M$.

--
Unable to mount location -- Internal error: No mount object for mounted volume
https://bugs.launchpad.net/bugs/256749
You received this bug notification because you are a direct subscriber
of the bug.

Status in Nautilus: Invalid
Status in “nautilus” source package in Ubuntu: Invalid

Bug description:
Binary package hint: nautilus

First, some information about my system:

  matt@Aluminumy:~$ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=8.10
  DISTRIB_CODENAME=intrepid
  DISTRIB_DESCRIPTION="Ubuntu intrepid (development branch)"

  matt@Aluminumy:~$ uname -a
  Linux Aluminumy 2.6..26-5-generic #1 SMP Sun Aug 3 01:25:54 UTC 2008 i686 GNU/Linux

  matt@Aluminumy:~$ dpkg-query -s nautilus
  Package: nautilus
  Status: install ok installed
  Priority: optional
  Section: gnome
  Installed-Size: 2340
  Maintainer: Ubuntu Desktop Team <email address hidden>
  Architecture: i386
  Version: 1:2.23.6.1-0ubuntu1

  matt@Aluminumy:~$ dpkg-query -s gvfs
  Package: gvfs
  Status: install ok installed
  Priority: optional
  Section: libs
  Installed-Size: 1916
  Maintainer: Ubuntu Desktop Team <email address hidden>
  Architecture: i386
  Version: 0.99.4-0ubuntu1

Now the problem description:

I open the "computer:///" in nautilus. One of the items listed is "5.0 GB Media" with an unmounted drive icon next to it. This drive is not listed in /etc/fstab. I double-click on the drive to mount it. Nautilus pops up a dialog box that says "Unable to mount location -- Internal error: No mount object for mounted volume". However, the drive does actually become mounted. An icon pops up on the desktop and I can browse the files. When the volume is mounted, 'df' shows it as: "/dev/sda6 4767428 4122020 403232 92% /media/disk".

[Tormod Volden (tormodvolden)]

I see this bug has been marked "Invalid". However I see it on two different Intrepid systems. One freshly installed from the Ubuntu 8.10 Desktop CD, then fully updated today. The other has also all updates from intrepid-proposed. The partitions I click on are not in /etc/fstab, in one case it is a FAT32, in another ext3.

[Sebastien Bacher (seb128)]

does gvfs-mount work correctly to mount those?

[Tormod Volden (tormodvolden)]

Will try. Just to make it clear, the mounting actually works. If I double-click a second time, the mounted folder pops up, and it is mounted on /media/<disk-label>

[Tormod Volden (tormodvolden)]

I am not sure how to use gvfs-mount (and there's no man page!) but if I run "gvfs-mount NAME" where NAME is the one listed by "gvfs-mount --list" it returns "Error mounting location: volume doesn't implement mount".

[David Freitas (jddcef)]

I have the same issue on 8.10 final, even with all updates installed.

[Daniel Hollocher (chogydan)]

well, I'll be darned, this bug is still present. For me, the way to produce the error message is to go to Places > Computer, then double click an unmounted drive. An authentication window will popup. WAIT, until an additional dialog box pops up, with a fairly generic message like "Opening such and such media", then enter your password and hit 'ok'. You get the error.

I find, that if I am able to enter my password BEFORE that extra dialog pops up, there is no error message.

Can anyone confirm my experience?

[Barry Shilliday (teppic74)]

I have this problem regularly in Fedora 10 with Gnome. Oddly enough, I haven't seen it happen once for me in Intrepid.

[Stephen (stephenfranciscogomez)]

 Barry Shilliday wrote 21 minutes ago: (permalink)

"I have this problem regularly in Fedora 10 with Gnome. Oddly enough, I haven't seen it happen once for me in Intrepid."

That's interesting, the bug is present under both distributions on my machine.

[Tormod Volden (tormodvolden)]

I still see it on Jaunty. But I don't see it all the time, maybe a race condition.

[Chris Coulson (chrisccoulson)]

Hmmm, I just got hit by this whilst trying to fix ntfs-3g mounting in Jaunty. I'm pretty sure it's not a Nautilus bug, but I'm not sure if it is in gvfs or glib. The actual error comes from gvfs, and I think Tormod is probably right about this being a race condition.

The actual code that does the mounting seems to be in daemon/gvfsbackendcomputer.c, here:

static void
mount_volume_from_drive (GDrive *drive,
                         GVfsJob *job,
                         GMountOperation *mount_op)
{
  GList *volumes;
  GVolume *volume;

  volumes = g_drive_get_volumes (drive);
  if (volumes)
    {
      volume = G_VOLUME (volumes->data);
      g_volume_mount (volume,
                      0,
                      mount_op,
                      G_VFS_JOB (job)->cancellable,
                      mount_volume_cb,
                      job);
    }
  else
    {
      g_vfs_job_failed (G_VFS_JOB (job), G_IO_ERROR,
                        G_IO_ERROR_NOT_SUPPORTED,
                        _("Can't mount file"));
    }

  g_list_foreach (volumes, (GFunc)g_object_unref, NULL);
  g_list_free (volumes);
}

The error message actually comes from the callback "mount_volume_cb":

static void
mount_volume_cb (GObject *source_object,
                 GAsyncResult *res,
                 gpointer user_data)
{
  GVfsJobMountMountable *job = user_data;
  GError *error;
  GMount *mount;
  GVolume *volume;
  GFile *root;
  char *uri;

  volume = G_VOLUME (source_object);

  /* TODO: We're leaking the GMountOperation here */

  error = NULL;
  if (g_volume_mount_finish (volume, res, &error))
    {
      mount = g_volume_get_mount (volume);

      if (mount)
        {
          root = g_mount_get_root (mount);
          uri = g_file_get_uri (root);
          g_vfs_job_mount_mountable_set_target_uri (job,
                                                    uri,
                                                    FALSE);
          g_free (uri);
          g_object_unref (root);
          g_object_unref (mount);
          g_vfs_job_succeeded (G_VFS_JOB (job));
        }
      else
        g_vfs_job_failed (G_VFS_JOB (job), G_IO_ERROR,
                          G_IO_ERROR_FAILED,
                          _("Internal error: %s"), "No mount object for mounted volume");
    }
  else
    {
      g_vfs_job_failed_from_error (G_VFS_JOB (job), error);
      g_error_free (error);
    }
}

So, g_volume_get_mount returns NULL (not mounted) after g_volume_mount_finish was already called successfully.

[Chris Coulson (chrisccoulson)]

I've tried looking at the glib code but it's late and my head hurts. Perhaps someone else could have a look at it, or maybe poke the upstream developers of glib?

[Kevin Dunne (kevdunne)]

Hi all. I have been using Ubuntu 8.10 for some time now and did not notice this bug initially using Ubuntu. I noticed it when using Linux Mint 6, based on U8.10, as it was fairly obvious and annoying as the distribution is otherwise excellent. Recently though it has been happening using U8.10. It seems that after some recent updates it has become more prevalent. I can not pin it down further than that currently but will play with both dists and see if can figure something out. Have 5 partitions on HD each will mount but only after spitting out the Unable to Mount error message has been displayed

[Kevin Dunne (kevdunne)]

Hope this helps - I found that the error message only happens when double clicking on the drive icon in "Computer - File Browser" main window. If I double click the drive icon in the "Paces" side bar of the "Computer - File Browser" or in "Places" -> "Removable Media" -> "Drive Name" then the drive is mounted and opened without a "Unable to mount" error message.

[Cecond Power (cecondpower)]

I can also confirm this exact same problem from Linux Mint 6 (basically ubuntu 8.10): When I mount drives from the "Computer" Nautilus browser area, this error pops up. However, mounting it from "Places" gives no error at all.

hmmm, I've heard that if you choose to let your system automount partitions (NTFS) with the NTFS Configuration Tool, this message will not appear -- Will try that and see how it goes.

[Chris Coulson (chrisccoulson)]

This should be fixed by the latest gvfs update. If you still experience this bug in Jaunty, please feel free to reopen this bug.

[mattismyname (mattismyname)]

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Matt

PS: Here is the link:
https://www.linkedin.com/e/isd/544944469/2_FAA5eJ/

It is free to join and takes less than 60 seconds to sign up.

This is an exclusive invitation from Matt Gumbel to Bug 256749. For security reasons, please do not forward this invitation.

------------------------------------------

What is LinkedIn and why should you join?
http://learn.linkedin.com/what-is-linkedin

------
(c) 2009, LinkedIn Corporation

[Paul (treepata)]

Hi everyone,

As I cannot upgrade to Ubuntu Jaunty (common & horrible ATI legacy videocard Linux Support issue), I can confirm that the following solution works for those who use Ubuntu 8.10 (or Linux Mint 6 (Felicia) in my case).

(This fix was already suggested by Cecond Power in the post above)

1. Install the ntfs-config package through the Package Manager or your Terminal.
2. Make sure the problematic drives are unmounted (e.g. by rebooting).
3. Start the NTFS configuration tool found under 'administration' or 'settings' in your start menu.
4. Make sure the drives are selected in the tool and press ok. (and then ok again in the next screen).
5. Restart Linux and now the drives should mount automatically without issues.

It is only a workaround but it gets things fixed. And it is an easy fix for those with little experience with Linux (like myself).

[Penny Wing (pwing-devryu)]

I was having the same problem with this error message.

Here's what I was able to do to solve it:

I went to System, then Administration, then Disk Utility, then clicked on the drive, then clicked on the blue link that says: /media/disk

Pulls it right up and I was able to access all my files on that drive. You can drag and drop them to your Places easily or copy them onto CD's.

Hope this helps =)

And I've only been on Ubuntu for 1 day ;)
Love this program, now to get rid of Windows =)

[Ludek (ludek-smolik)]

This is my report: The same bug here and about 15 others users have the same problem.

[Yuriy Tertichnyy (yuterbox)]

Confirm. This bug still exists in glib-2.0 for my LFS (glib 2.26-2.27). g_volume_get_mount always return NULL (not mounted) after block device was mounted successfully. Also gvfs-mount -m /dev/<anydev> alweys return "Error mounting location: Operation not supported".

[matthew72 (matthew72)]

still get this error in 10.04, with gvfs-mount NAME where NAME is listed by gvfs-mount --list. it works with gvfs-mount smb://server/share.

[matthew72 (matthew72)]

i also tried to mount the device (a luks encrypted one this time), this is the result:

$ gvfs-mount -d /dev/sda5
Enter a password to unlock the volume
The device "320 GB Hard Disk" contains encrypted data on partition 5.
Password:

(gvfs-mount:5120): GLib-GIO-CRITICAL **: g_mount_get_root: assertion `G_IS_MOUNT (mount)' failed

(gvfs-mount:5120): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
Mounted /dev/sda5 at (null)

(gvfs-mount:5120): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(gvfs-mount:5120): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

an icon appeared in the gnome-panel saying a device was added, but strangely it didn't create the desktop icon (not that i care much, but gvfs-mounting an smb share instead gives the desktop icon but not the notification in gnome-panel, and the same happens if i mount the partition in nautilus). the mountpoint was created anyway, and the mount was successful, so gvfs-mount -d seems to be a viable workaround. too bad gvfs-mount --list doesn't say the device; is there a reliable way to get the device node (i mean /dev/whatever) from its name?