Unable to mount location Not Authorized after nautilus upgrade

Bug #518533 reported by David Gradwell
150
This bug affects 32 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: nautilus

Following an automatic upgrade to Ubuntu 9.10 between mid January and 6th February 2010 I can no longer mount any disks except the File System disc /.
The same problem occurs on two different Ubuntu machines, both running Ubuntu 9.10.
Both machines have two identical SATA discs - one has the File System on it and the other has other files which were accessible but now are not. One machine has a USB disc and that can not be mounted either.

All disks are visible in Computer File Browser but double clicking gets a pop up window message "Unable to Mount Location Not Authorized."

System->Administration->Disk Utility gets me to the Palimpsest Disk Utility that can see both disks in question and lists them as /dev/db and /dev/sdc

In Terminal I get:
david@tekels1:~$ sudo mount /dev/sdb
mount: can't find /dev/sdb in /etc/fstab or /etc/mtab

and indeed they are not listed in those files.

This is of course business critical as I'm in the process of moving my business servers from Windoze to Ubuntu ! Fortunately they are not live yet.

david@tekels1:~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

david@tekels1:~$ apt-cache policy nautilus
nautilus:
  Installed: 1:2.28.1-0ubuntu3
  Candidate: 1:2.28.1-0ubuntu3
  Version table:
 *** 1:2.28.1-0ubuntu3 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        100 /var/lib/dpkg/status
     1:2.28.1-0ubuntu1 0
        500 http://gb.archive.ubuntu.com karmic/main Packages

ProblemType: Bug
Architecture: i386
Date: Sun Feb 7 19:59:59 2010
DistroRelease: Ubuntu 9.10
Package: nautilus 1:2.28.1-0ubuntu3
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-19-generic i686

Revision history for this message
David Gradwell (david-gradwell) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Do you remember what you upgraded? The list should be in /var/log/dpkg.log. Did it work before?
The mount command has nothing to do with GNOME and it seems to issue there is not a nautilus one. Did you have fstab lines for those drives before?

Changed in nautilus (Ubuntu):
importance: Undecided → Low
Revision history for this message
David Gradwell (david-gradwell) wrote :
Revision history for this message
David Gradwell (david-gradwell) wrote :
Revision history for this message
David Gradwell (david-gradwell) wrote :

I certainly had access to both disks last time I looked which would have been 3 or 4 days ago probably.

Samba 2:3.4.0-3ubuntu5.4 was installed on 31 Jan (See end of previous dpkg.log) and was working.

linux-image-2.6.31-19-generic <none> 2.6.31-19.56 went in on 7th Feb at 19:18 along with other updates. This was followed by upgrade linux-generic 2.6.31.17.30 2.6.31.19.32 a minute later.

Is there any merit in rolling back these upgrades and if so how ?

Revision history for this message
David Gradwell (david-gradwell) wrote :

Further analysis:
a) I was connecting remotely using vnc4server.
b) Connecting locally allows me to mount any of the"problem" discs OK.
c) If I mount the disk locally and then access the server through vnc4server I can open and access the disk.

Thus the problem seems to be related to use of vnc4server and possibly permission settings that got changed on upgrade ?

Revision history for this message
Sebastien Bacher (seb128) wrote :

not sure about the vnc, what permissions did get changed?

Revision history for this message
David Gradwell (david-gradwell) wrote :

The work-around is to mount at boot time, i.e. add suitable lines to the end of /etc/fstab such as:

/dev/sdc1 /media/FreeAgent ntfs defaults 0 2
/dev/sdb1 /media/t1backup ext4 defaults 0 2

Then both problem disks are accessible even when working over a remote vnc connection.

Revision history for this message
Anand Kumria (wildfire) wrote :

Well I get this bug on 10.04 (lucid lynx); so it is likely permission related - the problem is finding what permission is required for /media.

Revision history for this message
rdasilva (rdasilva-acm) wrote :

I experience the same problem as David G. when logging into my Ubuntu 9.10 box with NX. Seems to have changed with a recent update; this worked in the original 9.10 install.

Seems to be an issue with remote access (vnc, NX, etc.). Can open volumes normally if logged in to the physical system. Error only appears when logged in remotely.

Revision history for this message
Mark (ubuntu-markkremers) wrote :

I also have the exact same problem as David G. and rdasilva. Logged in locally I am able to mount usb devices without any problem but logged in through a remote NX connection I get the reported error message. (Ubuntu 9.10).

Revision history for this message
Daniel Walton (daniel-walton) wrote :

I have the same problem. using ubuntu 10.04 had same issue with 9.10.
Locally logged in I can mount drives , but when using remote connections using NX I cannot mount drives.

I have a pc with Debian Lenny and that has no issues at all mounting drives.
Although it doesn't

Based on what I have been able to google it looks like it is probably related to the policy kit stuff

there may be some script which is ran when the system is run locally but isn't run in NX sessions.

Revision history for this message
Kuyper (kuyper) wrote :

Same problem here. Using NX I cannot mount anything (or create DVDs with brasero).

Revision history for this message
Eric Morgan (gemorgan) wrote :

Same here, when shelled in using NX, cannot mount DVD's or USB devices using nautilus.

Revision history for this message
Pendelton (a79315-hotmail) wrote :

Same here, 9.10. Can'r mount any usb drives when connect using NX.

Revision history for this message
Timo Repo (rusna) wrote :

Same here, 10.04 and cannot mount any SATA drives using NX.

Revision history for this message
David Baucum (maxolasersquad) wrote :

Same here. Rather annoying. I agree that it seems to be a policy kit issue.

Revision history for this message
r000t (vistro) wrote :

My drive was available before upgrading to 10.04, but after upgrading, I can't mount it. Not authorized in nautilus or the disk utility. If I nautilus as root, the drive fails to show up whatsoever. I get a similar error as OP when I try it via the terminal.

This is a big problem. I don't know why it is not being given higher importance.

Revision history for this message
MvW (2nv2u) wrote :

Same problem, mounting a drive sometimes result in the "Not Authorized" error.
Rebooting helps most of the time, but i do have to reboot with the terminal because within gnome it will redirect me to the login screen (Same for shutdown).

Revision history for this message
Richard Coates (ihateemael) wrote :

Not sure whether to report this as the same bug?
My system is a clean install of 10.04 with current patches applied.
For the past few weeks if I try to access my second sata drive (from Nautilus) straight after boot up I get...
"Unable to mount location Not Authorized".
The shutdown icon greys out and I'm forced to "sudo reboot" from the terminal.
It appears if I wait a minute or two after bootup everything is ok.

Revision history for this message
Richard Coates (ihateemael) wrote :

hasn't done it for a while but..........
problem still there with: "2.6.32-24-generic-pae"
back to rebooting...

Revision history for this message
MvW (2nv2u) wrote :

Same here, this issue still happens to me although it seems to be less frequent for some reason.

Revision history for this message
James Jones (jamesjones01) wrote :

Yesterday this started happening to me. Until then I was able to connect my Cowon S9 and have it mount automatically, but now I get an "Unable to mount COWON S9 Not Authorized" popup. I typically connect it and use gpodder to get current podcast episodes on it each weekday before work, so most likely whatever changed to break it happened between the morning of September 20th around 9:00 a.m. CDT and the morning of September 21st around 9:00 a.m. CDT. I attach /var/log/dpkg.log to show what I installed or upgraded during that interval.

Revision history for this message
James Jones (jamesjones01) wrote :

Strange. After updating and rebooting, I can once again mount the Cowon S9. Attached is the diff between dpkg.log before and dpkg.log after.

Revision history for this message
Zeblue (ezsaxman) wrote :

I *just* had this issue, today.

Posted in forums @ http://ubuntuforums.org/showthread.php?p=9893684#post9893684

tags: added: patch
Revision history for this message
rowlandm (rowland-mosbergen) wrote :

I had this issue today on a brand new install of 10.04.1 LTS

Boot up - could not mount my hard drives.
Saw other issues too like could not change my account type in Users and Groups. No prompt for sudo password, just no response at all.
Could access sudo prompt for update manager though.

sudo halt
Reboot
Could mount my hard drives now.

Revision history for this message
Peter da Silva (resuna) wrote :

Same problem with a new install of 10.04 LTS on a laptop. No combination of rebooting or other fiddling suggested on the forums has helped.

Revision history for this message
Peter da Silva (resuna) wrote :

Can't mount partitions with palimpsest, either, unless I do "sudo palimpsest".

Revision history for this message
David Gradwell (david-gradwell) wrote :

This happened to me again when I did a new clean install of Ubuntu 10.10 (on two different machines with the same problem).

The only workaround that works (for me) is to open two terminal windows and in the first go:

  sudo blkid

to see the UUIDs of all devices.

In the second go

  sudo gedit /etc/fstab

and add an additional line for the device(s) that you can't mount.

A couple of examples that work for me are:

  UUID=87b43805-e339-4953-9c9c-328e71c0abdc /media/budisc ext4 users,rw 0 0
  UUID=744C979E4C975A26 /media/seagate ntfs users,rw 0 0

Have system/administration/disk utility open at the same time. Mount seems to work once the /etc/fstab file is updated.

Revision history for this message
David Black-Schaffer (david-black-schaffer) wrote :

This is also happening to me, but in a slightly different manner. Again on a clean install of 10.10.

If I am logged in to the console X session the USB disks will mount.

However, I get errors in other VNC sessions (e.g., extra X sessions) that I don't have permission to mount the disk. Indeed, if I am not logged in at the console the drive will not mount even though I am logged in via another VNC session.

This points to a more fundamental issue with the detection of when a user should have rights to do something.

Interestingly, I can no longer shutdown from the menu bar at this point as others have said. (http://ubuntuforums.org/showthread.php?p=10402198)
I could do this before I installed and ran VNC server.
I suspect this means that having two Gnome sessions running at once, or having one running inside VNC, or installing vnc, caused the problem.

Possibly also related, I ran into the also-reported problem that my VNC session started up with the key "d" mapped to "hide all windows" and had to unmap this. Perhaps there is some corruption going on here?

Revision history for this message
malfist (jeromehollon) wrote :

I can confirm this is happening to me also when I login via NX and attempt to mount an external USB harddrive. I would be happy to provide more details if requested.

Revision history for this message
Carlos Felipe Forigua Rodríguez (carlos-forig) wrote :

Didn't work. Installed thunar and i can mount filesystems as a normal user using thunar

Revision history for this message
beef zbeef (zbeefy) wrote :

Although I am on 11.10, I can't access my local hdds either. Same message pops out: "Unable to mount 320 GB Filesystem - Not Authorized". I did some updates today via apt-get upgrade, but I can't tell now what's been upgraded. I don't even know where to start looking, what is causing this. Even my DVD drive doesn't show up in Devices list in Nautilus... Anybody has any ideas?

Revision history for this message
Rocko (rockorequin) wrote :

Yes, the latest nautilus update has broken the ability to mount drives again. I've got nautilus 1:3.1.90-0ubuntu3 installed.

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

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

the recent oneiric issues were due to lightdm and fixed in the current version

Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
status: Invalid → Confirmed
Revision history for this message
Baditaflorin (baditaflorin) wrote :

Not Fixed, Same Problem. AND TELL ME if you need infos, whan cmd command to give. I have this problem for 4 years.

Revision history for this message
Baditaflorin (baditaflorin) wrote :

Ubuntu 12.04

Revision history for this message
Baditaflorin (baditaflorin) wrote :

With the latest update, complete remove and reinstall, re-reinstall. Delete and reinstall, reinstal ubuntu. Install and reinstall. all this i tried

Revision history for this message
Jay Banks (transporter-ii) wrote :

I can confirm this issues still exists in a clean install of 12.04 LTS using FreeNX. I did find that if I hook a keyboard and a mouse up and log in locally, I can access the usb thumb drive normally. However, over FreeNX it says something like "Access Denied - Unauthorized." I can also access the drive over FreeNX after I have accessed it locally.

Since I mainly use the system remotely, I did find a way to access the thumb drive over FreeNX without it being too much of a hassel. I made a DiskUtil.sh script where I do not have to type in my sudo password every time:

#!/bin/sh
echo "yourSudoPassword" | sudo -S palimpsest

When in the graphical Disk Utility, I can mount the usb drive and then click on the link on the right hand side that says "Mount Point: Mounted at /media/Transcend" and it will open up and I can copy to and from the drive normally. Note that even mounted, I cannot access the files through Nautilus at the mount point. I have to click the link in palimpsest or it will not work. But hey, at least I can access my thumb drive remotely.

And for the record, I know that script file is not the best way to do that, but I tried several ways to do it correctly and they didn't work for me...so yeah, there is a script file somewhere on a system that has my password in it.

Revision history for this message
Sebastien Bacher (seb128) wrote :

there has been no mentioned of similar issues in years and it's likely resolved, closing but feel free to open a new report if you still have problems in newer versions

Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
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.