Bug 242789

Summary: After reboot, in F7, connected devices are not mounted and is not recognized by the gnome-volume-manager
Product: [Fedora] Fedora Reporter: aldoem <aldoem>
Component: udevAssignee: David Zeuthen <davidz>
Severity: high Docs Contact:
Priority: low    
Version: 7CC: mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-07-27 11:06:51 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description aldoem 2007-06-05 15:36:31 EDT
Description of problem:
After reboot, connected devices are not mounted and is not recognized by the

Version-Release number of selected component (if applicable):
kernel 2.6.21-1.3194.fc7

How reproducible:
connect USB mass-storage device to F7 system and reboot

Steps to Reproduce:
1. connect USB mass-storage device
2. reboot
3. log as a user
Actual results:
device is not mounted and is not recognized in the gnome-volumen-manager

Expected results:
device should be mounted automatically

Additional info:
This worked perfectly fine in FC6.
Comment 1 Kyrre Ness Sjøbæk 2007-07-26 21:05:54 EDT
It also refuses to mount my usb thumbdrive, alltough the external HDD works
fine. dmesg output shows that the thumbdrive is detected properly (i'll guess i
could mount it manually), but it doesn't even show up in "Computer".

Is this a HAL or a gnome-volume-manager bug? It seems like its a quite common
problem with F7 (from google/bugzilla searches), but where are the "main
bugreport" that is being worked on? I want to read the progress :)
Comment 2 Kyrre Ness Sjøbæk 2007-07-27 10:52:21 EDT
Looks like the same bug:
Comment 3 David Zeuthen 2007-07-27 11:06:51 EDT
This is caused events arriving in wrong order because of an udev bug, see bug

*** This bug has been marked as a duplicate of 249282 ***
Comment 4 NILMONI DEB 2007-07-27 13:23:07 EDT
Bug 242359 may be a duplicate.