Bug 124940 - Error message when starting cups
Error message when starting cups
Status: CLOSED DUPLICATE of bug 124217
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2004-06-01 11:42 EDT by Daniel Malmgren
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:03:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Malmgren 2004-06-01 11:42:17 EDT
Description of problem:
I get the following when starting cups:
[~/empty#] service cups restart
Stoppar cups:                                     [     OK     ]
Startar cups: Traceback (most recent call last):
  File "/usr/sbin/printconf-backend", line 7, in ?
    import backend
  File "/usr/share/printconf/util/backend.py", line 54, in ?
    which = cups_import.which_spooler ()
  File "/usr/share/printconf/util/cups_import.py", line 195, in
    return which
UnboundLocalError: local variable 'which' referenced before assignment
                                                  [     OK     ]

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

How reproducible:

Steps to Reproduce:
Start cups service

Additional info:
All relevant packages are latest rawhide versions. I didn't get the
same error in previous version (think it was 1.1.20-6).
Comment 1 Daniel Malmgren 2004-06-01 11:43:12 EDT
Oh. I also get the same message when trying to start
Comment 2 Tim Waugh 2004-06-01 12:08:34 EDT
Does it work if you start it like 'LANG=C system-config-printer'?
Comment 3 Daniel Malmgren 2004-06-01 12:17:24 EDT
Yes it does.
Comment 4 Tim Waugh 2004-06-01 12:28:15 EDT

*** This bug has been marked as a duplicate of 124217 ***
Comment 5 Red Hat Bugzilla 2006-02-21 14:03:54 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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