[Bug 596421] New: Using Yast2 to configure printer, printer not found in Milestone 5
http://bugzilla.novell.com/show_bug.cgi?id=596421 http://bugzilla.novell.com/show_bug.cgi?id=596421#c0 Summary: Using Yast2 to configure printer, printer not found in Milestone 5 Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: linxt@comcast.net QAContact: jsrain@novell.com Found By: --- Blocker: --- Created an attachment (id=354229) --> (http://bugzilla.novell.com/attachment.cgi?id=354229) log files and screenshot User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100401 SUSE/3.6.3-1.5 Firefox/3.6.3 After zypper dup to Milestone 5 from factory, attempted to configure my printer (Brother HL-1440). The printer is connected via a parallel to usb cable. Yast2 could not find a printer (see screenshot). This printer, with the same connection, was found in previous milestones. The printer works properly under Knnopix and windoze. The returned message is: No Connections: Try More Connections' or use the 'Connection Wizard' Tried using both "More Connections" and "Connection Wizard" but printer was still not found. Reproducible: Always Steps to Reproduce: 1.Upgrade via zypper dup to M5 2.Open Yast2 and attempt to configure printer (Yast2 > hardware > printer) 3.Click on add, after short interval message "not found" appears Actual Results: Yast2 attempted to find printer but failed to detect it. Expected Results: Printer to be found and filter options to be displayed System: Dell Studio 1745 Printer: Brother HL-1440 with parallel to usb cable -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596421 http://bugzilla.novell.com/show_bug.cgi?id=596421#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596421 http://bugzilla.novell.com/show_bug.cgi?id=596421#c Michael Calmer <mc@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mc@novell.com AssignedTo|yast2-maintainers@suse.de |mzugec@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596421 http://bugzilla.novell.com/show_bug.cgi?id=596421#c2 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@novell.com InfoProvider|jsmeix@novell.com |linxt@comcast.net Summary|Using Yast2 to configure |Parallel port printer with |printer, printer not found |parallel->USB cable not |in Milestone 5 |found by CUPS since | |Milestone 5 --- Comment #2 from Johannes Meixner <jsmeix@novell.com> 2010-04-14 09:58:38 UTC --- According to your temp3/y2log in attachment #354229 you had initially a print queue brotherhl1440series (with URI usb://Brother/HL-1440%20series and driver Brother HL-1440 Foomatic/ljet4) which you deleted. Then you launched the "Add Printer" dialog which shows that no printer is autodetected. You also used the "Connection Wizard" where you selected "usb" which also shows that no USB printer is autodetected. As far as I see everything in YaST works perfectly well. It just shows the truth to you: No printer is autodetected by CUPS on your system. As root verify this by running # lpinfo -l -v (in the end the same command is run by YaST when it calls /usr/lib/YaST2/bin/autodetect_printers) The reason why no printer is autodetected by CUPS on your system is whatever lower-level stuff (perhaps whatever change in the lower-level libusb and/or USB kernel level). See http://en.opensuse.org/SDB:Installing_a_Printer what you should try out first of all regaring USB printers, in particular as root do # rmmod usblp # modprobe usblp and then run the CUPS usb backend directly # /usr/lib/cups/backend/usb compare http://en.opensuse.org/SDB:CUPS_in_a_Nutshell "The Backends" Furthermore you may search in /var/log/messages for USB related error messages. Regarding a workaround for parallel port <-> USB converters see https://bugzilla.novell.com/show_bug.cgi?id=264219#c1 For a related (but even more complicated) issue have a look at bug #562282 what else might be done to debug your particular case. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596421 http://bugzilla.novell.com/show_bug.cgi?id=596421#c3 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|linxt@comcast.net | Resolution| |INVALID --- Comment #3 from Johannes Meixner <jsmeix@novell.com> 2010-04-30 07:57:37 UTC --- No info provided. This is no bug in YaST so that I close it as invalid for YaST. If the issue happens again with a newer openSUSE 11.3 milestone or release candidate or in openSUSE 11.3 final/GA/whatever_they_call_it, file a new separated bug report regarding "Printing" or "Kernel" depending on what you think on which lower level it actually fails and provide information about the lower-level stuff according to the above comment #2. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com