Bug 180490 - printconf hangs when you click on new
printconf hangs when you click on new
Product: Fedora
Classification: Fedora
Component: system-config-printer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2006-02-08 11:30 EST by Kris Buytaert
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: FC5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-06-21 04:45:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screenshot of the error. (25.06 KB, image/png)
2006-02-08 11:31 EST, Kris Buytaert
no flags Details

  None (edit)
Description Kris Buytaert 2006-02-08 11:30:23 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060126 Fedora/1.5-5 Firefox/1.5

Description of problem:
With already 1 printer configured (not attached) I click on New printer 
It pops up a window    Loading Printer Information , Please Wait

Then i have to kill it.

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

How reproducible:

Steps to Reproduce:
1. start printconf
2. authenticate
3. click new printer

Actual Results:  popup and  nothing happens

Expected Results:  You'd expect either a working configuration gui or an error why something doesn't work.  Not a neverending popup.

Additional info:
Comment 1 Kris Buytaert 2006-02-08 11:31:07 EST
Created attachment 124387 [details]
screenshot of the error.
Comment 2 Tim Waugh 2006-06-20 09:52:36 EDT
When you started printconf from the command line, were there any error messages?

Also, you filed this against 'Fedora Core devel' -- did you mean to file it
against Fedora Core 5?
Comment 3 Kris Buytaert 2006-06-21 02:39:00 EDT
Hmm.. back in february I'm really not sure what I was running... proabely FC5 RC

I just tested again on my current distro with system-config-printer-gui-0.6.151-1
and system-config-printer-0.6.151-1  the problem seems to have dissapeared.

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