Version-Release number of selected component: system-config-printer-1.4.1-3.fc19 Additional info: reporter: libreport-2.1.4 cmdline: /usr/bin/python /usr/share/system-config-printer/system-config-printer.py dso_list: system-config-printer-libs-1.4.1-3.fc19.noarch executable: /usr/share/system-config-printer/system-config-printer.py kernel: 3.9.4-300.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: newprinter.py:3429:fillModelList:AttributeError: 'NoneType' object has no attribute 'getModels' Traceback (most recent call last): File "/usr/share/system-config-printer/newprinter.py", line 3425, in on_tvNPMakes_cursor_changed self.fillModelList() File "/usr/share/system-config-printer/newprinter.py", line 3429, in fillModelList models = self.ppds.getModels(self.NPMake) AttributeError: 'NoneType' object has no attribute 'getModels' Local variables in innermost frame: self: <NewPrinterGUI object at 0x1dc7af0 (newprinter+NewPrinterGUI at 0x1e572c0)>
Created attachment 756154 [details] File: backtrace
Created attachment 756155 [details] File: core_backtrace
Created attachment 756156 [details] File: environ
I'm fairly sure this was fixed upstream in commit 1cb9acd. I managed to reproduce it by going to add a new printer, then cancelling *after* the choice of models is presented, then repeating the process.
system-config-printer-1.4.1-6.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/system-config-printer-1.4.1-6.fc19
Package system-config-printer-1.4.1-6.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing system-config-printer-1.4.1-6.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10351/system-config-printer-1.4.1-6.fc19 then log in and leave karma (feedback).
system-config-printer-1.4.1-6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.