Bug 468609 - Error: cannot mount volume when clicking on internal NTFS partition
Summary: Error: cannot mount volume when clicking on internal NTFS partition
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-mount
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-26 17:54 UTC by You
Modified: 2013-03-06 03:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-01 16:16:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description You 2008-10-26 17:54:06 UTC
Description of problem:

Clicking on the NTFS partition after clicking the "Computer" icon on the desktop gives the following dialog box:

Error: cannot mount volume
Invalid mount option when attempting the mount The volume 'ACER'.

Followed a few seconds later by:

Opening "ACER".
You can stop this operation by clicking cancel.

and finally another dialog box:

Unable to mount location
DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.


Version-Release number of selected component (if applicable):

I installed Fedora 10 Snapshot 3 and updated to the latest packages.

Steps to Reproduce:
1. In gnome, click the "computer" icon on desktop, click on the NTFS volume
  
Actual results:

As mentioned above

Expected results:

The internal partition should be automatically available, perhaps after asking for authorisation the first time this happens.

Comment 1 You 2008-11-01 16:16:21 UTC
This seems to be fixed in latest (actually yestarday/day before's) rawhide - the NTFS partition is automatically mounting upon startup.


Note You need to log in before you can comment on or make changes to this bug.