[jaunty] system-config-printer & new python hangs with 100% CPU

I am seeing the same behavior in jaunty beta/RC
Rolling back to interpid version of system-config-printer* packages fixes the issue
I have 4 printers defined in /etc/cups/printers.conf

I’ve eventually figured out the issue being profile-specific and a workaround being the removal of a configuration file in your profile directory:

rm $HOME/.gconf/desktop/gnome/interface/%gconf.xml

It seems to be related to some font or desktop theme settings set in that configuration file.
I also noticed that the problem may come back after altering the font and theme details through the applet in System -> Preferences -> Aspect. Anyway removing the above mentioned file fixes the issue once again.

Subscribing the ubuntu-desktop team as it seems to be a GNOME bug.

Removing the %gconf.xml file, as suggested above, did NOT help me. How's progress on this one going?

This bug affects me. It appears suddenly, this morning everything worked fine. I have tried to purge and reinstall two packages :
system-config-printer-common 1.1.3+git20090218-0ubuntu19.2
system-config-printer-gnome 1.1.3+git20090218-0ubuntu19.2

I have also tried to switch to :
system-config-printer-common 1.1.3+git20090218-0ubuntu19
system-config-printer-gnome 1.1.3+git20090218-0ubuntu19

with no luck...

I have then tried :
_________________________________________
stan@stan-laptop:~$ system-config-printer --debug
Connected as user stan
refresh
Created subscription 40
<monitor.Monitor instance at 0x8a88ccc>: printers and jobs lists provided
update_jobs
<monitor.Monitor instance at 0x8a88ccc>: +<statereason.StateReason (REPORT,LaserJet-P4014,connecting-to-device)>
Ignoring stale connecting-to-device
{}
Ignoring stale connecting-to-device x
Authentication pass: 1
Authentication: password callback set
Authentication pass: 1
Authentication: password callback set
Authentication pass: 1
Authentication: password callback set
____________________________________________

The terminal is stuck on this

I don't know what to do !!

I am under jaunty

stan@stan-laptop:~$ uname -a
Linux stan-laptop 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009 i686 GNU/Linux

PS: I can still print of already configured printers...

I have just tried to purge and reinstall cups (and all dependances) and system-printer-config works fine, but I have to re configure all the printers... Thanks to cups, that tasks is very easy (It makes everybody on Windows jealous)

Hope this will help others !

I just got hit by this bug when I attempted to set up a new TCP/IP socket. I have multiple printers set up via a variety of sockets. This bug is a serious regression.

$ system-config-printer --debug
Connected as user xxx
refresh
Created subscription 236
<monitor.Monitor instance at 0x2abe878>: printers and jobs lists provided
update_jobs
Authentication pass: 1
Authentication: password callback set
Authentication pass: 1
Authentication: password callback set
Authentication pass: 1
Authentication: password callback set

same as nanog here... ubuntu jaunty 64bit with latest upgrades applied

Connected as user xxx
refresh
Created subscription 106
<monitor.Monitor instance at 0x19be830>: printers and jobs lists provided
update_jobs
Authentication pass: 1
Authentication: password callback set
Authentication pass: 1
Authentication: password callback set
Authentication pass: 1
Authentication: password callback set

Don't know if it is related but I can't access the CUPS web interface anymore using my normal user account (which IS in the lpadmin group): whenever I try to access the web interface using my account the cups daemon crashes without any message on the cups/error_log.

To access the cups web interface I had to set a password for the root user and subsequently I can perform tasks through the web interface without any problem, but I can't still use the system-config-printer applet.

If this is related (and it IS imho) the problem can reside in CUPS and not in the pyton application as the problem seems to happen upon authentication. The pyton script still need not to leak memory or cpu in case such things happens.

I have changed this back to "NULL Project" as this was linked to the wrong upstream project.

After upgrading to Lucid, this bug appeared. I can't open system-config-printer. When I do, a python process appears which just uses 100% CPU. A window never appears. I tried removing the gconf file, but that didn't fix it. CUPS is accessible via the web interface. Running system-config-printer --debug gives the same output that Stan had.

Josh, have you already tried to remove your

$HOME/.gconf/desktop/gnome/interface/%gconf.xml

file? Does this help?