Description of problem: Cannot create any print queues. Program hangs. Version-Release number of selected component (if applicable): system-config-printer-1.3.3-1.fc15.x86_64 How reproducible: always Steps to Reproduce: 1. Run system-config-printer as root. 2. Click to add a new printer. Actual results: Program freezes, "busy" spinner included. When run from a shell, the following is dumped to stdout/err: Traceback (most recent call last): File "/usr/share/system-config-printer/asyncipp.py", line 197, in send_reply handler (self._conn, result) File "/usr/share/system-config-printer/asyncconn.py", line 93, in reply_handler self._reply_handler (self, self._reply_data, *args) File "/usr/share/system-config-printer/asyncconn.py", line 204, in _subst_reply_handler reply_handler (self, *args) File "/usr/lib/python2.7/site-packages/cupshelpers/cupshelpers.py", line 602, in _reply_handler self._client_reply_handler (connection, devices) File "/usr/share/system-config-printer/newprinter.py", line 1371, in <lambda> current_uri)) File "/usr/share/system-config-printer/newprinter.py", line 1401, in local_devices_reply self.add_devices (result, current_uri) File "/usr/share/system-config-printer/newprinter.py", line 1802, in add_devices physdev = model.get_value (iter, 1) TypeError: iter must be a GtkTreeIter
To work around this problem, I found it necessary to use the web interface for CUPS administration at https://localhost:631/
I haven't been able to reproduce it here. Do you see the problem if you run system-config-printer as regular user ?
Would be great to see a screenshot of the window at the point that you get the traceback, too.
(In reply to comment #2) > I haven't been able to reproduce it here. > Do you see the problem if you run system-config-printer as regular user ? No, I don't. I did not go all the way through the process of adding a printer (as a regular user), but I was able to click the add button and the spinner continued spinning. We have a ton of shared printers so discovery takes quite awhile. (So many, in fact, that the discovery process is of little help since only the make/model is presented and without useful bits like description/location it's practically impossible to know what printer you're selecting, but that's another problem.) Back on track, I ran this three ways: * via sudo * directly as root * directly as non-root Only the last way did not reproduce the problem.
(In reply to comment #3) > Would be great to see a screenshot of the window at the point that you get the > traceback, too. Sure. Attaching two scrapes: * system-config-printer-before.png is just prior to pressing the Adjust Firewall button. * system-config-printer-after.png is just after pressing the Adjust Firewall button. Once I press that button the dialog window for adjusting the firewall disappears and the first two windows ('Printing - localhost' and 'New Printer') completely freeze and no longer redraw themselves as other windows temporarily obscure them.
Created attachment 510263 [details] before pressing Adjust Firewall
Created attachment 510264 [details] after pressing Adjust Firewall
I have what may be another clue. When I run as regular user, I don't see the dialog about adjusting the firewall. I thought I did before when running as a regular user, but won't swear to it. I always see it when run as root, regardless of how many times I've hit the Adjust Firewall button. I'm assuming that the firewall never gets adjusted because the program hangs before any adjustments are made. I haven't looked at the source to see what adjustment specifically is needed, but I can say that port 631 is already open in my rules. Also, once this crash happens the iptables service is stopped and my system is wide open. (I saw that it was stopped yesterday to my surprise and now I know why.) To be clear, I did make sure that iptables was running when doing the above tests.
Would be great to see the full output of running system-config-printer --debug as root. I can't reproduce this either.
Created attachment 510300 [details] Output of system-config-printer --debug (run as root) Captured via system-config-printer --debug &> /tmp/system-config-printer-debug.
Created attachment 510306 [details] audit.log entries upon pressing Adjust Firewall button Maybe this a SEL policy at fault. My SEL alert widget in the KDE system tray kept appearing with: Opps, sealert hit an error! Traceback (most recent call last): File "/usr/bin/sealert", line 692, in <module> run_as_dbus_service(username) File "/usr/bin/sealert", line 112, in run_as_dbus_service app = SEAlert(user, dbus_service.presentation_manager, watch_setroubleshootd=True) File "/usr/bin/sealert", line 326, in __init__ from setroubleshoot.browser import BrowserApplet File "/usr/lib64/python2.7/site-packages/setroubleshoot/browser.py", line 46, in <module> import report.io.GTKIO ImportError: No module named GTKIO That looks like another problem altogether, but it caused me to investigate what the audit.log was showing and if there was any relationship to the system-config-printer problems I've been seeing. Indeed there's correlation as can be seen in the attachment.
(In reply to comment #11) > File "/usr/lib64/python2.7/site-packages/setroubleshoot/browser.py", line 46, > in <module> > import report.io.GTKIO > ImportError: No module named GTKIO That's another problem. I see it too today. There's a problem that latest libreport-gtk wrongly obsoletes report-gtk package which setroubleshoot needs.
Fixed upstream in 60efcbb.
system-config-printer-1.3.4-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/system-config-printer-1.3.4-1.fc15
Package system-config-printer-1.3.4-1.fc15: * should fix your issue, * was pushed to the Fedora 15 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.3.4-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/system-config-printer-1.3.4-1.fc15 then log in and leave karma (feedback).
Package system-config-printer-1.3.5-1.fc15: * should fix your issue, * was pushed to the Fedora 15 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.3.5-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/system-config-printer-1.3.5-1.fc15 then log in and leave karma (feedback).
Package system-config-printer-1.3.5-2.fc15: * should fix your issue, * was pushed to the Fedora 15 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.3.5-2.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/system-config-printer-1.3.5-2.fc15 then log in and leave karma (feedback).
Package system-config-printer-1.3.5-3.fc15: * should fix your issue, * was pushed to the Fedora 15 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.3.5-3.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/system-config-printer-1.3.5-3.fc15 then log in and leave karma (feedback).
system-config-printer-1.3.5-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
system-config-printer-1.2.9-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/system-config-printer-1.2.9-1.fc14
system-config-printer-1.2.9-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.