Bug 855569

Summary: The other partions do not be mounted
Product: [Fedora] Fedora Reporter: sangu <sangu.fedora>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: alexl, bnocera, ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-21 00:12:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
$udisks --dump none

Description sangu 2012-09-09 02:10:47 UTC 
Description of problem:
The other partions do not be mounted

Version-Release number of selected component (if applicable):
3.5.91-1.fc18.x86_64

How reproducible:
always

Steps to Reproduce:
1. Open Nautilus
2. Click partion in Devices or Click mount in context menu
3.
  
Actual results:


Expected results:


Additional info:
click mount in context menu -> Pop error dialog
=================================
|Unable to access "Partion Name" |
|An operation is already pending |
=================================

gvfs-1.13.7-2.fc18.x86_64
Comment 1 Tomáš Bžatek 2012-09-10 10:01:06 UTC 
Could you be more precise, such as what type of devices are you trying to mount, does it require root privileges, what filesystem etc.? Udisks dump would be nice to have as well.
Comment 2 sangu 2012-09-10 10:36:11 UTC 
Created attachment 611391 [details]
$udisks --dump

(In reply to comment #1)
> Could you be more precise, such as what type of devices are you trying to
> mount, does it require root privileges, what filesystem etc.? 
ntfs, ext4

>Udisks dump would be nice to have as well.
Comment 3 sangu 2012-09-21 00:12:12 UTC 
After updating GNOME 3.6rc (gvfs-1.13.9-1.fc18), this bug is fixed.

Thanks!