Bug 113158 - hang attempting the create new printer definition
Summary: hang attempting the create new printer definition
Alias: None
Product: Fedora
Classification: Fedora
Component: foomatic (Show other bugs)
(Show other bugs)
Version: 1
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
: 113794 114975 116728 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-09 00:20 UTC by Gene Czarcinski
Modified: 2007-11-30 22:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-03-04 12:34:24 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
foomatic-db-engine-segfault.patch (966 bytes, patch)
2004-01-09 10:45 UTC, Tim Waugh
no flags Details | Diff

Description Gene Czarcinski 2004-01-09 00:20:52 UTC
Description of problem:
First try on Opteron system running the "preview" of x86_64 FC1

Version-Release number of selected component (if applicable):

Invoked printconf from a terminal window and got:

Traceback (most recent call last):
  File "/usr/share/printconf/util/queueTree.py", line 537, in
new_button_clicked    self.use_foomatic ()
  File "/usr/share/printconf/util/queueTree.py", line 467, in use_foomatic
    self.conf.foomatic_init_overview ()
  File "/usr/share/printconf/util/printconf_conf.py", line 1554, in
    root = parser.parse (foo)
line 134, in parse
xml.parsers.expat.ExpatError: no element found: line 1, column 0

Comment 1 Tim Waugh 2004-01-09 09:11:23 UTC
What does 'foomatic-configure -O' say?

Comment 2 Gene Czarcinski 2004-01-09 10:20:48 UTC
nothing (no output) ... either as root or regular user.

I also ran it on my "regluar" Athlon system and see that it is suppose
to produce lots of xml but on the Opteron ... nothing.

Comment 3 Tim Waugh 2004-01-09 10:45:07 UTC
Created attachment 96855 [details]

Please try this patch.

Comment 4 Tim Waugh 2004-01-09 10:45:34 UTC
Incidentally, this issue is already fixed upstream and in rawhide.

Comment 5 Gene Czarcinski 2004-01-09 12:17:06 UTC
Unless you have some overriding reason to try the patch, I would just
as soon pull the updates rpm from rawhide (development).

Comment 6 Gene Czarcinski 2004-01-09 17:10:48 UTC
OK, I downloaded foomatic-3.0.0-17.x86_64.rpm from development and
installed it.

printer configuration still does not work.

The output of running foomatic-configure -O is:

Can't locate Foomatic/Defaults.pm in @INC (@INC contains:
/usr/lib64/perl5/5.8.1/x86_64-linux-thread-multi /usr/lib/perl5/5.8.1
/usr/lib64/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.1
/usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl/5.8.0
/usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.1 .) at
/usr/bin/foomatic-configure line 14.
BEGIN failed--compilation aborted at /usr/bin/foomatic-configure line 14.

Comment 7 Tim Waugh 2004-01-09 17:25:16 UTC
Recompile it against the perl you're actually running. :-)

Comment 8 Gene Czarcinski 2004-01-09 18:37:03 UTC
When I grab something from rawhide/development, I "always" get the
src.rpm and rebuild so that it works with the libs, etc. I am running
... except this time.

OK, rebuilt the src rpm and installed ... print config now works.

BTW, it sure does take a lot of CPU to rebuild foomatic  ... I thought
I found another bug like the one I found in gcc where it looped with
gcc -O2.

Comment 9 Tim Waugh 2004-01-18 12:53:45 UTC
*** Bug 113794 has been marked as a duplicate of this bug. ***

Comment 10 Justin M. Forbes 2004-02-05 04:59:44 UTC
*** Bug 114975 has been marked as a duplicate of this bug. ***

Comment 11 Tim Waugh 2004-02-13 15:06:55 UTC
The bug is fixed in the foomatic update for Fedora Core 1, which you
can recompile the SRPM for.

Comment 12 Justin M. Forbes 2004-02-24 19:49:26 UTC
*** Bug 116728 has been marked as a duplicate of this bug. ***

Comment 13 Justin M. Forbes 2004-03-04 06:16:48 UTC
This seems to be working with the applied updates, which should ship
with FC1 release. Tested on multiple systems here, should we close
this one?

Comment 14 Gene Czarcinski 2004-03-04 12:34:24 UTC
yes, fixed in footmatic-3.0.0-21.3

I am closing as fixed in errata

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