Bug 1379086 - 3.22 version of Nautilus +other locations ->click on a listed partition does not mount that partition
Summary: 3.22 version of Nautilus +other locations ->click on a listed partition does ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 25
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-24 19:56 UTC by Leslie Satenstein
Modified: 2017-05-08 15:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-08 15:06:53 UTC
Type: Bug


Attachments (Terms of Use)

Description Leslie Satenstein 2016-09-24 19:56:42 UTC
Description of problem:

Nautilus (files).  

Step 1
Clicking "+Other Locations" presents a list of partitions that I can mount.
I choose one, the spinning "wait" is presented, and no activity takes place.
I get the feeling that Nautilus is waiting on a lock so that a mount can be performed.  

Step 2
If I cancel, and retry,  No partitions are listed when "+Other Loations" is reselected.  It appears to require a reboot to return to Step 1 

As well, the same problem is present with the liveworkstation iso version 

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

https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20160924.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-netinst-x86_64-25-20160924.n.0.iso

https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20160922.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-25-20160922.n.0.iso

How reproducible:

Tested with real system (x64, 8 gigs ram, and 10+ partitions listed. 

Steps to Reproduce:
1.
2.
3.

Actual results:

No mounts occurred

Expected results:


Additional info:

Command line mount of any partition succeeds.

Comment 1 Leslie Satenstein 2017-05-08 15:06:53 UTC
Gnome Maintenance corrected the problem


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