Hide Forgot
abrt 1.0.3 detected a crash. backtrace ----- Summary: TB491b738f userdefault.py:81:set:RuntimeError: (1, 'lpoptions: Unknown printer or class!') Traceback (most recent call last): File "/usr/share/system-config-printer/userdefault.py", line 164, in on_response self.userdef.set (self.name) File "/usr/share/system-config-printer/userdefault.py", line 81, in set raise RuntimeError (exitcode, stderr.strip ()) RuntimeError: (1, 'lpoptions: Unknown printer or class!') Local variables in innermost frame: stdout: None default: gryffindor self: <UserDefaultPrinter (None)> p: <subprocess.Popen object at 0xb737adac> stderr: lpoptions: Unknown printer or class! exitcode: 1 cmdline: python /usr/share/system-config-printer/system-config-printer.py component: system-config-printer executable: /usr/share/system-config-printer/system-config-printer.py kernel: 2.6.31.5-127.fc12.i686.PAE package: system-config-printer-1.1.13-10.fc12 uuid: 491b738f
Created attachment 384990 [details] File: backtrace
Thank you for the report. Can you show the output of 'lpstat -t' and 'lpoptions -d gryffindor' ?
Fixed upstream. Also affects Fedora 11.
system-config-printer-1.1.16-9.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/system-config-printer-1.1.16-9.fc11
system-config-printer-1.1.16-9.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/system-config-printer-1.1.16-9.fc12
system-config-printer-1.1.16-9.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-printer'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0755
system-config-printer-1.1.16-9.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-printer'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-0776
system-config-printer-1.1.16-11.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-printer'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-0776
system-config-printer-1.1.16-11.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-printer'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0755
system-config-printer-1.1.16-13.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-printer'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0755
system-config-printer-1.1.16-13.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-printer'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-0776
system-config-printer-1.1.16-13.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
system-config-printer-1.1.16-13.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.