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.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/256749
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:
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.
--
You received this bug
** Changed in: nautilus
Status: New = Fix Released
** Changed in: nautilus
Importance: Unknown = Low
--
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 member of
This is my report: The same bug here and about 15 others users have the
same problem.
--
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 member of Ubuntu
Desktop Bugs, which
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
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)
This should be fixed by the latest gvfs update. If you still experience
this bug in Jaunty, please feel free to reopen this bug.
** Changed in: gvfs (Ubuntu)
Sourcepackagename: nautilus = gvfs
Status: Triaged = Fix Released
--
Unable to mount location -- Internal error: No mount object
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
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
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
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
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?
--
Unable to mount location -- Internal error: No mount object for mounted volume
https://bugs.launchpad.net/bugs/256749
You received
I still see it on Jaunty. But I don't see it all the time, maybe a race
condition.
--
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 member of Ubuntu
Desktop Bugs, which is
** Changed in: nautilus
Status: Invalid = New
--
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 member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I have this problem regularly in Fedora 10 with Gnome. Oddly enough, I
haven't seen it happen once for me in Intrepid.
--
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
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.
--
Unable to mount location -- Internal
** Changed in: nautilus (Ubuntu)
Status: New = Confirmed
--
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 member of Ubuntu
Desktop Bugs, which is a bug assignee.
** Changed in: nautilus (Ubuntu)
Status: Confirmed = Triaged
--
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 member of Ubuntu
Desktop Bugs, which is a bug
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
I have the same issue on 8.10 final, even with all updates installed.
--
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 member of Ubuntu
Desktop Bugs, which is a bug
does gvfs-mount work correctly to mount those?
** Changed in: nautilus (Ubuntu)
Status: Confirmed = 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
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
--
Unable to mount location -- Internal error: No mount object for mounted volume
https://bugs.launchpad.net/bugs/256749
You received
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.
--
Unable to mount location -- Internal error: No mount object for mounted volume
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
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
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
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.
--
Unable to mount location -- Internal error: No mount object for mounted
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?
** Attachment added: Screenshot-1.png
http://launchpadlibrarian.net/19412880/Screenshot-1.png
--
Unable to
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
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.
--
Unable to mount location -- Internal error: No mount object for mounted volume
https://bugs.launchpad.net/bugs/256749
You received
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
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.
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
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
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.
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
--
Unable to mount location -- Internal error: No mount object for mounted volume
https://bugs.launchpad.net/bugs/256749
You
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
** Changed in: nautilus
Status: New = Invalid
--
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 member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
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)
** Attachment added: Drive mounted, but error displayed.
http://launchpadlibrarian.net/17350003/Drive%20mounting.png
--
Unable to mount location --
** Changed in: nautilus (Ubuntu)
Status: Incomplete = Triaged
--
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 member of Ubuntu
Desktop Bugs, which is a bug
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.
** Changed in: nautilus (Ubuntu)
Status: Incomplete = Confirmed
--
Unable to mount location --
the issue is an upstream one, could somebody having the bug open it on
bugzilla.gnome.org?
** Changed in: nautilus (Ubuntu)
Status: Confirmed = Incomplete
--
Unable to mount location -- Internal error: No mount object for mounted volume
https://bugs.launchpad.net/bugs/256749
You received
** Bug watch added: GNOME Bug Tracker #549946
http://bugzilla.gnome.org/show_bug.cgi?id=549946
** Also affects: nautilus via
http://bugzilla.gnome.org/show_bug.cgi?id=549946
Importance: Unknown
Status: Unknown
--
Unable to mount location -- Internal error: No mount object for
** Changed in: nautilus
Status: Unknown = New
--
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 member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Same problem here, but it's on all volumes not just for one spesific.
--
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 member of Ubuntu
Desktop Bugs, which is a bug
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
--
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 PROTECTED] wrote:
thank you for your bug report. do you have the using using any drive or
just
** Attachment added: Screenshot of error dialog box
http://launchpadlibrarian.net/16695769/Screenshot-nautilus.png
--
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
49 matches
Mail list logo
