Bug 674871 - cannot unmount a drive by button
Summary: cannot unmount a drive by button
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-03 15:40 UTC by Masami Ichikawa
Modified: 2015-03-03 22:58 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-05-19 04:49:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Masami Ichikawa 2011-02-03 15:40:26 UTC
Description of problem:
nautilus cannot unmount a USB hard disk drive by a button which is next to device name.
I only tested USB hard disk.

Version-Release number of selected component (if applicable):
[liveuser@localhost ~]$ rpm -qa | grep nautilus
nautilus-sendto-2.90.0-11.fc15.x86_64
nautilus-extensions-2.91.8-4.fc15.x86_64
totem-nautilus-2.91.6-2.fc15.x86_64
nautilus-2.91.8-4.fc15.x86_64
file-roller-nautilus-2.91.6-1.fc15.x86_64
evince-nautilus-2.91.6-1.fc15.x86_64
brasero-nautilus-2.91.6-1.fc15.x86_64


How reproducible:
always.

Steps to Reproduce:
1.Insert a USB hard disk
2.Wait for a while 
3.When nautilus is appeared, click a button which is next to the device name.
  
Actual results:
nothing happend. USB disk is still mounted.

Expected results:
USB disk is unmounted.
 
Additional info:
I use this live cd image: http://fedoraproject.org/wiki/Test_Day:2011-02-03_GNOME3_Alpha

Comment 1 Charles R. Anderson 2011-02-04 17:12:19 UTC
Ditto here, but sometimes clicking on it a second time worked.  I played around clicking about and eventually the eject button worked...

Hardware: http://www.smolts.org/client/show/pub_3a2cf40c-0037-46c0-a593-c730c3cb4bcf

Comment 2 Cosimo Cecchi 2011-02-04 18:13:31 UTC
I think you're hitting https://bugzilla.gnome.org/show_bug.cgi?id=640741

Comment 3 Matthias Clasen 2012-05-19 04:49:38 UTC
Lets assume this is fixed then.


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