Bug 308691
Summary: | device descriptor read/64, error -62, leads to printing problems | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mumrel <mumrel> |
Component: | hal-cups-utils | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | triage, twaugh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-06-17 02:30:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 236808 | ||
Attachments: |
Description
Mumrel
2007-09-27 10:21:26 UTC
Still present in 2.6.22.9-91.fc7 https://bugzilla.redhat.com/show_bug.cgi?id=323981 (posted also as a CUPS problem, since i am not really sure) Definitely seems like a kernel or hardware problem of some sort. 1. What does 'lsusb -v' say when you run it as root (i.e. 'su -' first)? 2. What does '/usr/lib/cups/backend/usb' say before you switch off the printer? 3. What does '/usr/lib/cups/backend/usb' say after you switch the printer back on? *** Bug 323981 has been marked as a duplicate of this bug. *** Created attachment 221431 [details] lsusb-v after booting. Printer HAS BEEN OFF and was it during this command. Posting this also, because a diff lsusb_off lsusb_offagain brings up this, but i can't decide wether that is important or not. 60c60 < PortPwrCtrlMask 0x06 --- > PortPwrCtrlMask 0xc6 126c126 < PortPwrCtrlMask 0x06 --- > PortPwrCtrlMask 0xc6 189c189 < PortPwrCtrlMask 0x06 --- > PortPwrCtrlMask 0xc6 Created attachment 221441 [details]
lsusb -v AFTER turning the printer ON the first time
Created attachment 221461 [details]
After turning the printer OFF again.
Note that some values changed compared to the state when the printer was yet
off.
As I said, no idea if this is important or just normal.
Created attachment 221471 [details]
After turning the printer ON for the FIRST time.
Created attachment 221481 [details]
After turning the printer ON for the second time.
Code changed from 10001 (on for the first time) to 10003 (on for the second
time )
Just to be sure, please do the following:
1. Stop CUPS:
/sbin/service cups stop
2. Edit /etc/cups/cupsd.conf and change the 'LogLevel' line to read:
LogLevel debug2
3. Clear the error_log
>/var/log/cups/error_log
4. Start CUPS:
/sbin/service cups start
5. Switch off your printer, then switch it on.
6. Now try printing something.
7. Wait a few minutes, then attach /var/log/cups/error_log
8. Reset the LogLevel line back to 'LogLevel info' afterwards.
Created attachment 222321 [details]
cups debug2 error log, obtained by executing the above mentioned steps
Printer was switched on again at line ~290 and later (wc -l)
test-document was printed after line ~473
Waited at least 3 minutes.
If you need anything else, just let me know.
Thank you so far!
Greetings
Do you have any clue what's producing that kind of behavior? Is it the kernel? Greetings Mumrel And again, still present in 2.6.23.1-10.fc7. Hi there, somehow there exists an workaround for me now. kernel 2.6.23.1-21.fc7 cups 1:1.2.12-8.fc7 The problem with my configured Samsung printer (calles 'samsung' here) still exists and is the same. But now after i turn on the printer for a second time, some wodoo goes on an the panel informs me that a new printer called 'ML-1510' was found. If I send my print jobs to this printer everything works fine. Thank you greetings Mumrel What does 'lpstat -s' say? It says: # lpstat -s Kein systemweites Standardziel Gerät für ML-1510_700: usb://Samsung/ML-1510_700 Gerät für samsung: hal:///org/freedesktop/Hal/devices/usb_device_4e8_3242_2R21BADWA02453D0_if0_printer_noserial Okay, marking as a possible hal-cups-utils problem (hal-cups-utils provides the print backend for hal: URIs). This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. Fedora 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |