Bug ID | 902407 |
---|---|
Summary | system-config-printer can't find driver, doesn't offer manual selection |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | 13.2 RC 1 |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Major |
Priority | P5 - None |
Component | Printing |
Assignee | jsmeix@suse.com |
Reporter | sb56637@gmail.com |
QA Contact | jsmeix@suse.com |
Found By | --- |
Blocker | --- |
Hi there, In view of bug 889187, I tried to add a network printer via dnssd with system-config-printer. It does find the printer, but under KDE some kind of "helper" screen (apper related maybe?) appears with an error. (See attachment #1 [details]) Then, after dismissing the error, system-config-printer gets stuck at "searching for drivers". (See attachment #2 [details]) At this point, it gets stuck. I have let it sit there for 5 minutes on a very fast computer, and I have very few drivers installed (no Gutenprint or HPLIP) so it definitely should not be searching for long. I believe that an internal python process is crashing, as the terminal spits out this error when it starts searching for drivers: ---------------------- ERROR:dbus.proxies:Introspect error on :1.344:/org/freedesktop/PackageKit: dbus.exceptions.IntrospectionParserException: Error parsing introspect data: <class 'xml.parsers.expat.ExpatError'>: unbound prefix: line 5, column 4 HTTP Status 403 None Exception in thread Thread-3: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/site-packages/cupshelpers/openprinting.py", line 54, in run self.callback (403, self.user_data, None) File "/usr/lib/python2.7/site-packages/cupshelpers/openprinting.py", line 163, in parse_result callback (status, user_data, result) File "/usr/share/system-config-printer/newprinter.py", line 3267, in openprinting_printers_found print traceback.extract_tb(printers[2], limit=None) TypeError: 'NoneType' object has no attribute '__getitem__' ---------------------- I don't really care if it finds the correct driver or not, as long as it lets me manually select my correct driver, which I can't do. When running system-config-printer as root in IceWM, the KDE "helper" error dialog doesn't appear. But it still gets stuck on "searching for drivers". Thanks for looking into this!