Bug 410221 - spurious usb printer detected after resume
spurious usb printer detected after resume
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
8
i386 Linux
low Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-04 07:22 EST by Mads Kiilerich
Modified: 2008-07-22 07:56 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-22 07:56:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
messages from boot and resume, and output of lsusb (52.14 KB, text/plain)
2007-12-04 07:22 EST, Mads Kiilerich
no flags Details

  None (edit)
Description Mads Kiilerich 2007-12-04 07:22:06 EST
Description of problem:
A USB printer is detected when resuming, but I have no USB printer...

Version-Release number of selected component (if applicable):
2.6.23.1-49.fc8

How reproducible:
Not. 
Just saw it when "I did as a use to do and nothing has changed" (famous last
words...).
I think I have seen it once before.

Steps to Reproduce:
1. suspend to ram
2. resume
3. hal_lpadmin: Added printer Unknown
  
Actual results:
a Printer configuration dialog appears for "Unknown Unknown" printer with URI
hal:///org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial_0_printer_noserial

Expected results:
I do not have any printer connected and no printer should be detected

Additional info:
I removed my USB-attached phone / flash-disk when I suspended - either before,
durring or after...

After resume gnome-power-manager always tells me that "suspend failed". I don't
know why it thinks that.
Comment 1 Mads Kiilerich 2007-12-04 07:22:06 EST
Created attachment 276871 [details]
messages from boot and resume, and output of lsusb

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