|
Bugzilla – Full Text Bug Listing |
| Summary: | cups-auotconfig or yast2-printer mix up models and DeviceURIs | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Johannes Meixner <jsmeix> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | printer | ||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/cups-autoconfig.log
/var/log/YaST2/y2log output of "lpinfo -l -v" tar.gz of /var/log/YaST2/* yast2-printer overview screenshot y2log for the above screenshot |
||
|
Description
Johannes Meixner
2008-05-16 09:54:37 UTC
Created attachment 215894 [details]
/var/log/cups-autoconfig.log
Created attachment 215895 [details]
/var/log/YaST2/y2log
Created attachment 215896 [details]
output of "lpinfo -l -v"
Chris, Michal, see the logs above. At the moment I cannot decide if it was cups-autoconfig or yast2-printer which did set up the nonsenese queue. For me it seems a bit as if it was yast2-printer because in y2log there is ----------------------------------------------------------- 2008-05-15 14:31:13 <1> nelson(4588) [YCP] Printer.ycp:504 Detected printer $["device":"deskjet 3320", "device_db":"DESKJET3320", "info":"hp deskjet 3320", "location":"USB printer on //EPSON/Stylus%20Photo%20RX420", "unique_key":"PYMB.K0l8BX37UwB", "uri":"usb://EPSON/Stylus%20Photo%20RX420", "vendor":"hp", "vendor_db":"HP"] ----------------------------------------------------------- where the DeviceURI is wrong. Therefore I assign it to Michal to check y2log and set NEEDINFO to Chris to check cups-autoconfig.log Or does the above snippet in y2log about "Detected printer" mean that it is actually a "detected queue" (i.e. this wrong queue did already exists when yast2-printer was run) so that it might have been created by cups-autoconfig but cups-autoconfig.log also looks as if the queue "deskjet3320" did already exist? Created attachment 215915 [details] tar.gz of /var/log/YaST2/* To be safe a tar.gz of /var/log/YaST2/* but there is no "3320" in any of the other logs. I saved y2log as y2log.save (this is attachment #215895 [details]) because meanwhile I updated yast2-printer from what is in beta-3 to yast2-printer-2.16.26 which I built from what is currently in /work/src/done/STABLE/yast2-printer/ I think it is really yast2-printer which confuses DeviceURIs, manufacturer, and model names because my current yast2-printer-2.16.26 shows in the overview this nonsense: ---------------------------------------------------------------- Queue Name Device Model ... not configured //hp/deskjet 3320 EPSON hp deskjet 3320 ---------------------------------------------------------------- Created attachment 215928 [details]
yast2-printer overview screenshot
Created attachment 215930 [details]
y2log for the above screenshot
cups-autoconfig pulls strings from HAL and the cups backends. I don't think it's responsible. Reassign it to me if you can show otherwise. There is new yast2-printer module which fixes most of the bugs. If this problem occurs in this version, please reopen bugreport. http://mzugec.blogspot.com/2008/08/new-yast2-printer-configuration-module.html |