Bug 82434 - redhat-config-printer-tui --Ximport --merge < filename.xml fails
Summary: redhat-config-printer-tui --Ximport --merge < filename.xml fails
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-printer
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-01-22 03:16 UTC by chris couples
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-01-22 15:49:03 UTC


Attachments (Terms of Use)
exported printers file for my site (9.24 KB, text/plain)
2003-01-22 15:22 UTC, chris couples
no flags Details

Description chris couples 2003-01-22 03:16:23 UTC
Description of problem:

When attempting to merge a newer version of the printer file dumped with:

/usr/sbin/redhat-config-printer-tui --Xexport > somefile.xml

using the command:

/usr/sbin/redhat-config-printer-tui --Ximport --merge < /home/setup/somefile.xml

I receive the following messages:

Traceback (most recent call last):
  File "/usr/sbin/redhat-config-printer-tui", line 8, in ?
    printconf_tui.startup_and_find_cmd()
  File "/usr/share/printconf/util/printconf_tui.py", line 2319, in
startup_and_find_cmd
    main.cmd_handlers[cmd]()
  File "/usr/share/printconf/util/printconf_tui.py", line 2003, in import_cmd_run
    ctx = AdmContext(xml = xmlstr)
RuntimeError: failed to create a context

...and the merge fails

In the above example, the exported file is copied onto an nfs share, so that a
number of identically configured machines will pick up any changes at the next
lpd restart.

Comment 1 Tim Waugh 2003-01-22 13:29:22 UTC
Please attach the XML file you are using; I haven't been able to reproduce this
here yet, and it might be something specific to that file.

Comment 2 chris couples 2003-01-22 15:22:14 UTC
Created attachment 89525 [details]
exported printers file for my site

Comment 3 Tim Waugh 2003-01-22 15:31:08 UTC
That seems to have the whole thing twice.  If you just use the first copy, does
that work?

Comment 4 chris couples 2003-01-22 15:39:04 UTC
Yeah, that worked. Sorry for the 'bug'.

Comment 5 Tim Waugh 2003-01-22 15:49:03 UTC
No problem.

Comment 6 chris couples 2003-01-22 15:50:29 UTC
I spoke too soon. I may need to open a new bug, but:

for the printer passilla, changing the type from jetdirect, with ip of
165.106.10.246 and port of 9100, to an lpd queue, with ip address of
165.106.10.246 and queue of '' (that's empty, as asked for by an Apple LW
16/600PS), applying (occasioning lpd restart), and then saving changes
(occasioning a second lpd restart), and then using the config-printer-tui tool
to export the "new" config

results in a file with passilla still being a jetdirect queue, with the initial
specs.

Might this prob. be that config-printer-tui expects some value for queue, and
because Apple's implementation is non-standard and doesn't take a queue name
when printing via TCP directly to the printer?

Comment 7 chris couples 2003-01-22 15:53:07 UTC
uh, nevermind. major configuration screwup on my part. I am _really_ sorry for
the confusion.


Note You need to log in before you can comment on or make changes to this bug.