Bug 156605

Please try running 'system-config-printer' from a shell prompt and do the same
thing.  Is there any output in the terminal window?

Sorry - slight mistake in my diagnosis.  It wasn't due to the server being taken
offline: other printers on that server can be edited without problem.  It's just
one specific printer, an Epson EPL-2050.  Output in the terminal window (before
the hang) as follows:

Cannot read file /usr/share/foomatic/db/source/driver/epl2050.xml!
Driver file /usr/share/foomatic/db/source/driver/epl2050.xml corrupted, missing,
or not readable!
Couldn't load driver information.
Traceback (most recent call last):
  File "/usr/share/printconf/util/queueTree.py", line 600, in edit_button_clicked
    if self.editQueue.editQueueDialog (iter):
  File "/usr/share/printconf/util/editQueue.py", line 414, in editQueueDialog
    self.write_driver_options ()
  File "/usr/share/printconf/util/editQueue.py", line 923, in write_driver_options
    for option_tuple in option_list:
TypeError: iteration over non-sequence

1. What does 'rpm -q foomatic' say, and
2. What does 'rpm -V foomatic' say?

Have you installed a version of foomatic from a different source than Fedora Core?

[root@chris chris]# rpm -q foomatic
foomatic-3.0.2-13.4
[root@chris chris]# rpm -V foomatic
[root@chris chris]#

No, I've only updated to foomatic-3.0.2-13.4.i386.rpm from Fedora Updates
(released 20-Apr-2005).

I've just done an rpm -qlp on it, though, and that package doesn't contain the
file epl2050.xml.

But presumably system-config-printer shouldn't just hang forever, even if the
printer driver file is missing?

The file isn't missing: it's broken.  printconf requires foomatic to be working
-- it can't do anything without it.  Having a broken database is the cause of
this problem.

Where did the epl2050.xml file come from?  Does the datestamp give any clues? 
What is the history of this installation?  Could you attach the file please?

No, it really is definitely missing:

[root@chris chris]# locate -i epl2050
[root@chris chris]#

epl2050.xml was present in foomatic-3.0.2-3.i386.rpm as distributed with Fedora
Core 3, but (see above) it's not contained in the latest
foomatic-3.0.2-13.4.i386.rpm from Fedora Updates.

According to /usr/share/foomatic/db/source/printer/Epson-EPL-N2050.xml, that
printer can now use the epkowa-laser.xml driver.  So I suppose the simple
solution is just to delete the printer in system-config-printer and add a new
one which uses that driver.  I still think it should be possible to do that by
editing the old one, though, rather than having to delete it and create a
completely new one.

Thanks for the help.

Aha, the problem is that the queue configuration didn't get upgraded to reflect
the change of driver.  I've added that to
/usr/share/printconf/util/updateconf.py like this:

changed_driver_names = {
    'stp': 'gimp-print-ijs',
    'gimp-print': 'gimp-print-ijs',
    'hpijs-rss': 'hpijs',
    'ep2050': 'eplaser'
    }

Fixed in CVS.

Thanks, but bad news: I've made that change here, but still no joy (same error
message as above, including the reference to epl2050.xml).

I then changed 'ep2050' to 'epl2050' (same result), and then changed 'eplaser'
to 'epkowa-laser' (same result).

Sorry...

I should have been clearer: the updateconf.py program gets run when
system-config-printer is upgraded (it happens in the %post scriptlet).

What about if you run it by hand?:

/usr/share/printconf/util/updateconf.py

Does that fix the queue?

Ah, I see - sorry.  Running it with your modification as-is doesn't do the job,
I'm afraid.  But changing the line you've added to:

    'epl2050': 'epkowa-laser'

works a treat.  Thanks again for the help!

Ah, okay -- this driver name has changed once again(!) to 'eplaser' in the
version of foomatic in Fedora development.

OK, great.  The left-hand part should still be changed to 'epl2050', though (not
'ep2050').

Oops, fixed.  Sorry, I missed that from your earlier comment.