Red Hat Bugzilla – Bug 484960
system-config-printer useless in IceWM, modal popup steals focus from password entry
Last modified: 2009-02-24 17:12:04 EST
Created attachment 331471 [details]
Description of problem:
system-config-printer cannot be used to add a printer when IceWM is the window manager. A pop-up window with the message "Adding printer" appears and steals focus from the dialog asking for the root password. It's impossible to switch to the password entry with the mouse or with the keyboard. I had to run X without any window manager to add a printer.
Version-Release number of selected component (if applicable):
Always on one system, but not on another one.
Steps to Reproduce:
1. run system-config-printer as an ordinary users
2. Click on "New"
3. Select LPD/LPR, address 192.168.1.1, queue "FOO"
4. Select Alps MD-1000 (the first non-generic printer in the list)
5. In the "Describe Printer" dialog, leave "Location" empty, click on Apply
Two windows appears. One has "Please wait" in the window title, "Adding" in bold and "Adding printer" below. The other window has "Authentication" in the window title, "Password for root on localhost?" in bold and input entries "Username:" and "Password:". The first window has focus. The second window has no focus.
Only the second window appears. The first window seems useless to me, but I would not mind if it appears after I enter the root password.
I'm using icewm-1.2.35-4.fc10. The blame must be partly on IceWM. However, system-config-printer still has an interface problem. It should not be opening two windows at once. A window that requires input should not be obscured by an information window. Ideally, information windows should be replaced with the status bar in the main window.
system-config-printer-1.0.15-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
system-config-printer-1.0.15-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
I confirm that the bug is fixed. Thank you!