Bug 450493 - Can't write to USB memory programmatically (but can from the console)
Summary: Can't write to USB memory programmatically (but can from the console)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-09 07:25 UTC by Mark Summerfield
Modified: 2008-07-03 15:56 UTC (History)
0 users

Fixed In Version: 2.6.25.9-40.fc8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-03 03:15:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mark Summerfield 2008-06-09 07:25:59 UTC
I have a standard Fedora 8 system which I keep up to date whenever the update
manager says there are updates. When I updated last I got a new kernel:
2.6.25.4-10.fc8

When I run my custom backup program it fails to write to my USB memory sticks
giving "Operation not permitted" error messages.
When I use cp at the console I can copy the backup files to my USB memory sticks
without any problems.

If I reboot and use the old kernel, 2.6.24.7-92.fc8, everything works fine.

(PS I don't think it is an SELinux problem. I have that set to permissive but
retried with it disabled and neither setting made a difference.)

Comment 1 Chuck Ebbert 2008-06-11 22:01:59 UTC
bug 449080 in F9

Comment 2 Chuck Ebbert 2008-06-15 21:20:38 UTC
Fix went in 2.6.25.6-30

Comment 3 Fedora Update System 2008-06-30 16:37:06 UTC
kernel-2.6.25.9-40.fc8 has been submitted as an update for Fedora 8

Comment 4 Fedora Update System 2008-07-01 05:25:41 UTC
kernel-2.6.25.9-40.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update kernel'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-5880

Comment 5 Fedora Update System 2008-07-03 03:14:54 UTC
kernel-2.6.25.9-40.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Mark Summerfield 2008-07-03 06:00:00 UTC
I don't know how to get that kernel. Here's what yum says:
: yum list "kernel*"
Installed Packages
kernel.i686                              2.6.25.6-27.fc8        installed
kernel.i686                              2.6.24.7-92.fc8        installed
kernel-headers.i386                      2.6.25.6-27.fc8        installed
Available Packages
kernel.i586                              2.6.25.6-27.fc8        updates
kernel-PAE.i686                          2.6.25.6-27.fc8        updates
kernel-PAE-debug.i686                    2.6.25.6-27.fc8        updates
kernel-PAE-debug-devel.i686              2.6.25.6-27.fc8        updates
kernel-PAE-devel.i686                    2.6.25.6-27.fc8        updates
kernel-debug.i686                        2.6.25.6-27.fc8        updates
kernel-debug-devel.i686                  2.6.25.6-27.fc8        updates
kernel-devel.i586                        2.6.25.6-27.fc8        updates
kernel-devel.i686                        2.6.25.6-27.fc8        updates
kernel-doc.noarch                        2.6.25.6-27.fc8        updates
kernel-xen.i686                          2.6.21.7-3.fc8         updates
kernel-xen-2.6-doc.noarch                2.6.21.7-3.fc8         updates
kernel-xen-devel.i686                    2.6.21.7-3.fc8         updates

Comment 7 Mark Summerfield 2008-07-03 15:56:15 UTC
I just got an update message and updated my kernel so now I have 2.6.25.9-40.fc8.
After rebooting I got the same scary USB messages (which I don't get with
2.6.24* but did get with 2.6.25.6*):

hub 1-0:1.0: unable to enumerate USB device on port 3
hub 1-0:1.0: unable to enumerate USB device on port 6
hub 1-0:1.0: unable to enumerate USB device on port 8

but despite those messages, everything now seems to work fine!

Thanks!



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