Bug 153264

Summary: Media insertion into USB card reader is treated as removable drive instead of removable media
Product: [Fedora] Fedora Reporter: Msquared <142.bugzilla.redhat>
Component: gnome-volume-managerAssignee: John (J5) Palmieri <johnp>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: jkeck
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-04 15:08:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Msquared 2005-04-04 09:17:26 UTC
Description of problem:

When inserting a CF/MMC/SD card into a USB card reader, it's treated as a
removable drive, not as removable media, and is mounted according to "Mount
removable drives when hot-plugged" rather than "Mount removable media when

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

Whichever version shipped with FC4t1.

How reproducible:


Steps to Reproduce:
1. Open Preferences/Removable Drives and Media
2. Turn on "Mount removable drives when hot-plugged"
3. Turn off "Mount removable media when inserted"
4. Plug a USB card reader in
5. Wait for 30 seconds to let the system register the reader
6. Insert a CF/MMC/SD memory card
Actual results:

The CF/MMC/SD memory card is mounted.

Expected results:

The CF/MMC/SD memory card should not be mounted unless the "Mount removable
media when inserted" option was turned on.

Additional info:

Comment 1 John (J5) Palmieri 2005-04-04 15:08:30 UTC
This is correct behavior.  Confusing but correct.  A USB card is a removable
drive.  DVD's and CD's are removable media.  Well a USB card in a USB reader is
actually both but for policy we keep it as a drive.  I'm going to patch it out
as one option and leave the two gconf keys for people who want finer grained
access at some point.

Comment 2 Msquared 2005-04-05 08:20:18 UTC
(In reply to comment #1)

> This is correct behavior.  Confusing but correct.

I can understand the technical reasons why it's correct, but it it confuses the
user then it misses the point.  There's no reason to create if there's nobody to

Oh well, a bit of a moot point if you're removing the distinction in the user
interface.  :o)

Comment 3 David Zeuthen 2005-04-05 15:16:35 UTC
The patch mentioned in comment 1 should go upstream too.