After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 344447 - Unmountable USB media
Unmountable USB media
Status: RESOLVED DUPLICATE of bug 172749
Product: gnome-panel
Classification: Other
Component: menu
2.14.x
Other All
: Normal minor
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-09 23:13 UTC by Nick G
Modified: 2006-06-15 05:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Nick G 2006-06-09 23:13:18 UTC 
I would like to suggest a right click option on the Places Menu. I tend to disable devices from appearing on my Desktop as I use it for holding the files I am currently working with. On connecting to a server over ftp, first incorrectly, and then a 2nd time correctly, I am left with two mounts in the Places menu. Without an icon on the desktop I can not remove them so I have to go into gconf-editor, enable them. Unmount the volume, disable them again in Gconf and close.

Are there any easier ways/fixes?

Also, I didn't want to file this as a bug, but trying to format a USB disk under GNOME is a pain! - as soon as it's wiped, gnome remounts, meaning that you have to unmount it and then drop to the command line to use fdisk. It's even worse trying to use gparted 
Try it out - not fun :( 

Other information:
Comment 1 Nick G 2006-06-09 23:14:37 UTC 
Sorry but the title would best be Unmountable REMOTE media - wasn't decided whether to write a seperate report on each. Again, sorry!
Comment 2 Teppo Turtiainen 2006-06-15 05:09:56 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

The first issue is a duplicate of bug 172749. You can use the Disk Mounter applet until that bug is fixed. The second issue is a duplicate of bug 309067.


*** This bug has been marked as a duplicate of 172749 ***