[Hardy A6] remote HDD: Thunar's eject failes, Terminal works

Bug #200936 reported by Linard Verstraete
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
Fix Released
Medium
Unassigned
thunar-volman (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: thunar

*** Platform ***
Xubuntu Hardy 8.04 Alpha 6
Thunar: 0.9.0-4ubuntu1

*** Reproduction ***
Step 1. Insert USB cable
Step 2. Spin up external HDD
Step 3. Right-click on a partition and choose "Eject Volume"
Step 4. Notice pop-up window "Eject Failed - Unable to eject : An unknown error occured"
Step 4b. Notice pop-up window of every partition of your external HDD

*** Expected ***
Step 1. to Step 3. the same
Step 4. A successful Eject of HDD

*** Additional testing ***
Through terminal command: sudo eject pathToPartition
Returns no errors, but thunar gives both options ("Mount volume" & "Eject volume") in GUI for every partition on external HDD?! (See screenshots)

Tags: likely-dup
Revision history for this message
Linard Verstraete (linardv) wrote :
Revision history for this message
Linard Verstraete (linardv) wrote :
Revision history for this message
Brandon Lewis (brandon-lewis) wrote :

same for me, in release versoin of hardy.

Revision history for this message
Brandon Lewis (brandon-lewis) wrote :

this has also been a problem since feisty.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

Does the eject work from the command line?
Does the user or root own the drive/partition?
Can you try opening a root thunar (gksu thunar) and see if the eject works

Thanks!

Changed in thunar:
assignee: nobody → charlie-tca
status: New → Incomplete
Revision history for this message
Linard Verstraete (linardv) wrote :

My apologies for the lack of information. Let me give another shot at it:

To start, I shall give some information about my external HDD (see Bug attachments: fdisk on external HDD) In brief, a 300 GB disk, with a primary partition of 150 GB in NTFS and 150 GB in FAT32.

First I place my laptop on the table and next to it I place my external HDD. Then I connect my laptop with the external HDD through a USB-cable. After that I fire up my external HDD, and when the external HDD is spinning at operation speed, I fire up my laptop.

My laptop then boots Xubuntu 8.04.1 (Linux Druif 2.6.24-18-generic #1 SMP Wed May 28 20:27:26 UTC 2008 i686 GNU/Linux) and I login with my user name and password. On my desktop I see both partitions, of my external HDD, with there corresponding labels. When I right click on one of those partitions, I see that the option "mount" as well as "eject" are active. (Like in Bug attachment: Both options with partition #).
If I left click twice on one of those partitions, I get a thunar-window with a list of the files and folders of the chosen partition, just as you would expect and the partition is mounted. If I then return to my desktop and right click on the partition icon, and chose the "eject" option I get what's described in my bug description at Step 4: a pop-up window "Eject Failed - Unable to eject "BACKUP" : An unknown error occured" (where BACKUP is the label of one of my partitions) and thunar-windows of every partition of my external HDD.

So I have done some additional testing and I have come up with following results:
* Mounting a partition of my external HDD
Via left clicking twice on icon on desktop: works
Via right clicking on icon on desktop and choosing "mount": works
Via terminal command "sudo mount /dev/sdb1": fails
-> Error message "mount: can't find /dev/sdb1 in /etc/fstab or /etc/mtab"

* Unmounting a partition of my external HDD
Via terminal command "sudo umount /dev/sdb1": works

* Ejecting my external HDD
Via right clicking on icon on desktop and choosing "eject": fails
-> Error window "Eject Failed - Unable to eject ' ': An unknown error occured" (with partition's label between the ' ')
-> all partitions are of my external HDD are mounted.
-> thunar-windows of every partition of my external HDD.
Via terminal command "sudo eject /dev/sdb": fails
-> No error message
-> all partitions are of my external HDD are mounted.
-> thunar-windows of every partition of my external HDD.
Via terminal command "gksu thunar" and right click "eject": fails
-> Error window "Eject Failed - Unable to eject ' ': An unknown error occured" (with partition's label between the ' ')
-> all partitions are of my external HDD are mounted.
-> thunar-windows as user of every partition of my external HDD and thunar-windows as root of every partition of my external HDD

And the answer to your question who owns the drive/partition: See Bug attachments "ls -l of drive and partitions". In brief: the root owns the drive and partitions.

I hope I have the information you asked for, and if you need anything else, just ask ;)

Revision history for this message
Linard Verstraete (linardv) wrote :
Changed in thunar:
status: Incomplete → Confirmed
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Is this a duplicate of bug 199005, Unmount is not possible on floppy drives? Even though different storage is involved, both give an error when using "Eject Volume" in Thunar.

Changed in thunar:
assignee: charlie-tca → nobody
Revision history for this message
Linard Verstraete (linardv) wrote :

Personally I think that having more than one filesystem on the external HDD, with one of them NTFS, is the source of the problem. I have read posts on ubuntuforums.org which are stating just the same problem.

And Bug 199005 gives an different error message than this one, so the trigger for the error message can be different and so can be the cause for the error.

Changed in thunar-volman:
status: New → Confirmed
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in thunar:
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - the Jaunty Jackalope. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information.

Changed in thunar (Ubuntu):
status: Triaged → Fix Released
Changed in thunar-volman (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Fix Released
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.