Bug 885879 - Printer not found when attempting to print after undocking then docking laptop
Summary: Printer not found when attempting to print after undocking then docking laptop
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 17
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-10 21:27 UTC by James
Modified: 2012-12-22 15:51 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-22 15:51:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
'dmesg -c' after undocking and resume (5.61 KB, text/plain)
2012-12-14 00:12 UTC, James
no flags Details
'dmesg -c' after docking and resume (8.09 KB, text/plain)
2012-12-14 00:12 UTC, James
no flags Details
strace /usr/lib/cups/backend/parallel 2>&1 strace.txt (19.23 KB, text/plain)
2012-12-19 15:48 UTC, James
no flags Details

Description James 2012-12-10 21:27:22 UTC
Fedora seems to lose track of attached printers when a laptop is undocked. I can consistently replicate this behavior. This printer is attached using a parallel port on the docking station.


Steps to Reproduce:
1. Turn on laptop
2. Close screen and undock laptop
3. Open screen to revive laptop
4. Close screen and dock laptop
5. Open screen and print anything
6. Observe message about missing printer
  

Additional info:
If I reboot with the failed print job in the queue, the job begins to print *before* login.

Comment 1 Tim Waugh 2012-12-11 09:56:04 UTC
Could you run "su -c 'dmesg -c'" at each stage and note what it says?  This will show the kernel messages caused by each action.

Comment 2 James 2012-12-14 00:12:09 UTC
Created attachment 663266 [details]
'dmesg -c' after undocking and resume

Comment 3 James 2012-12-14 00:12:41 UTC
Created attachment 663267 [details]
'dmesg -c' after docking and resume

Comment 4 Tim Waugh 2012-12-17 09:42:36 UTC
At step 5, before printing something, could you please run this command?:

su -c 'lpinfo --include-schemes=parallel -v'

What output, if any, do you get?

Also of interest is the output of this command:

su -c 'strace /usr/lib/cups/backend/parallel' 2>&1

Comment 5 James 2012-12-19 15:45:26 UTC
# lpinfo --include-schemes=parallel -v
direct parallel:/dev/lp0

Comment 6 James 2012-12-19 15:48:05 UTC
Created attachment 666195 [details]
strace /usr/lib/cups/backend/parallel 2>&1 strace.txt

Comment 7 Jiri Popelka 2012-12-19 15:53:07 UTC
Removing the 'private' flag as I don't see any private info in comments or attachments.

Comment 8 Tim Waugh 2012-12-19 16:50:47 UTC
What exactly does the message about a missing printer say?

When you see this message, it would be useful to run strace on the running 'parallel' process.

Run 'ps axf' and look for the 'parallel://...' process that has been run by cupsd.  Note the process ID (first column), then run:

strace -p the-id-you-noted 2>strace.txt

Leave it for, say, two minutes. Then press Control-C to stop the strace process, and attach strace.txt here.

Thanks.

Comment 9 James 2012-12-22 15:51:49 UTC
Okay, I'm not sure what changed or if those commands forced something but it works okay now.


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