Bug 206808 - FC6 Test 3 fails to auto mount flash drive from cold boot.
Summary: FC6 Test 3 fails to auto mount flash drive from cold boot.
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-volume-manager
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: David Zeuthen
QA Contact:
Whiteboard: bzcl34nup
Keywords: Reopened
Depends On:
TreeView+ depends on / blocked
Reported: 2006-09-16 21:43 UTC by John Baer
Modified: 2013-03-06 03:47 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2008-05-06 16:21:38 UTC

Attachments (Terms of Use)

Description John Baer 2006-09-16 21:43:38 UTC
Description of problem:

Fails to mount inserted USB flash drive from cold boot. Detects and mounts USB
flash drive correctly after login.

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

FC6 Test 3

How reproducible:


Steps to Reproduce:
1. Insert USB flash drive when the computer is off
2. Turn on computer
3. Login as user, drive is not mounted
Actual results:

Drive is not mounted when drive is attached before cold boot. Works with this
hardware under FC5.

Expected results:

Expected the USB flash drive to be mounted after login.

Additional info:

Comment 1 Harald Hoyer 2006-09-25 12:03:42 UTC
udev does not mount

Comment 2 John Baer 2006-09-25 14:10:46 UTC
The functionality reported in this bug is available and working correctly in FC5.

Comment 3 Harald Hoyer 2006-09-25 14:23:47 UTC
ok... then I'll reassign to gnome-volume-manager

Comment 4 Matthew Miller 2007-04-06 19:57:49 UTC
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.

[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]

Comment 5 Bug Zapper 2008-04-04 03:46:22 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 6 Bug Zapper 2008-05-06 16:21:36 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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