The reporter of the duplicate bug #192033 tells:
The cause of my troubles was that i had not marked the printers as "published"
- when I did that, it found them, and everything worked as advertised.
Still, crashing is not the right thing to do, and this crash will still occur
if people choose the obsecurity of an unpublished printer.
I have tried to simulate this situation by unpublishing a printer on my
Intrepid server (unmark "Shared" in the right-click menu in system-
config-printer) and then trying to create an IPP queue pointing to it on
my Jaunty client. I did not get asked for the manufacturer but directly
received the screen to enter the queue name (because in a more recent
version of system-config-printer I have taken into account that this
kind of queue does not need a driver as it takes the server's driver if
it is configured as a raw queue). With this version of system-config-
printer I am not abl;e to reproduce the crash.
In addition, this bug is already 15 months old and the part of the code
where the crash occured got substantially changed.
Therefore I am closing the bug as fixed. Please reopen and add step-by-
step instructions and also tell abot the configuration of both server
and client if the problem still occurs for you.
** Changed in: system-config-printer (Ubuntu)
Status: Confirmed => Fix Released
--
system-config-printer.py crashed with ValueError in nextNPTab()
https://bugs.launchpad.net/bugs/178727
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
