From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10.1 Description of problem: I can't configure printers using Fedora Core 2 i386. When I open "Printer configuration" with system-config-printer and click New, a popup says "Loading printer information. Please wait...". So I wait forever and nothing happens. Just a rotating hourglass. I have to force-kill the program. Version-Release number of selected component (if applicable): system-config-printer-0.6.98-1 How reproducible: Always Steps to Reproduce: 1.Run system-config-printer. 2.Click Add. 3. Actual Results: Program stays in hung state. Expected Results: Should have given me a window where I can configure / add new printers. Additional info:
Please run 'system-config-printer' from a terminal window, and see if the same thing happens. If so, please copy the output here. Thanks.
I get the same in Core 3 with system-config-printer-gui-0.6.116.1.1-1.i386.rpm and system-config-printer-0.6.116.1.1-1.i386.rpm.
Please copy the output you get here.
I got the same freeze on FC4 test2 (rawhide updated): system-config-printer-0.6.128-1 system-config-printer-gui-0.6.128-1 The first time I ran system-config-printer and clicked 'Add' the dialogs came up fine, the second (and third..) time (after cancelling and importing a PPD, I may have restarted the program) it hung. rm -rf /var/cache/foomatic made it work as expected upon next launch. Hope this helps: [olov@localhost ~]$ system-config-printer Traceback (most recent call last): File "/usr/share/printconf/util/queueTree.py", line 579, in new_button_clicked self.use_foomatic () File "/usr/share/printconf/util/queueTree.py", line 502, in use_foomatic self.conf.foomatic_init_overview () File "/usr/share/printconf/util/printconf_conf.py", line 1771, in foomatic_init_overview foomatic_pickle () File "/usr/share/printconf/util/printconf_conf.py", line 1621, in foomatic_pickle os.mkdir (dirname, 0755) OSError: [Errno 17] File exists: '/var/cache/foomatic'
Thanks for the report. Should be fixed in 0.6.129-1. This is certainly a different problem than the original report, but I will close this for now. Original reporter: please re-open this if it still occurs, and provide the required information. Thanks.