Red Hat Bugzilla – Bug 249596
USB Flash-disk can't mount on kernel 2.6.22.1-27.fc7, kernel-2.6.22.1-33.fc7 (testing) in Gnome-environments
Last modified: 2008-01-09 12:22:20 EST
Description of problem: USB Flash-disk can't mount on kernel 2.6.22.1-27.fc7, kernel-2.6.22.1-33.fc7 (testing) in Gnome-environments. Version-Release number of selected component (if applicable): kernel-2.6.22.1-27.fc7, kernel-2.6.22.1-33.fc7 How reproducible: Steps to Reproduce: 1. Install kernel-pakets kernel-2.6.22.1-27.fc7.i686.rpm OR kernel-2.6.22.1-33.fc7.i686.rpm (testing) 2. Reboot 3. Log in system under simple user (NOT root). Use Gnome as desktop-environments. In applet "Removable Drives and Media Preferences" chose ('check') option "Mount removable drives when hot-plugged", "Mount removable drives when inserted" and "Browse removable drives when inserted". 4. Insert USB flash-disk (1G, Kingstone) in usb-slot. Actual results: Flash-disk not mount and not visible on Desktop. Expected results: Flash-disk, as removable drives, must browse when inserted on desktop. Additional info: At use of a kernel-2.6.21-1.3228.fc7 all works normally. At use of a kernel 2.6.22.1-27.fc7 OR kernel-2.6.22.1-33.fc7 (testing) normally mounted only CD/DVD-ROM and floppy.
This is a duplicate of bug #249161 (though you should report the info about the test kernel there).
Bug 249161 is becoming a mess-bug. This is more likely a dup of bug 249282, in the narrow sense.
Hello Alex, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged. Cheers Chris
As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug.