Red Hat Bugzilla – Bug 152271
abnormally long waits for tasks inside the printer GUI
Last modified: 2007-12-28 14:24:58 EST
Description of problem: There is two long wait in system-config-printer-gui: "Loading printer information. Please wait..." -> ~55s "Applying changes. Please wait..." -> ~55s Version-Release number of selected component (if applicable): system-config-printer-gui-0.6.125-1 How reproducible: always Steps to Reproduce: 1. start system-config-printer-gui 2. Select printer (in my case, a SMB printer) 3. Action > Edit Queue 4. [WAIT] 5. Click on one of the tab and then click OK 6. Action > Apply changes 7. [WAIT] Actual results: -Excessive wait time, especially compared to kprinter or Windows. -Apply changes even if I didn't actually make any Expected results: -5-10s waits max. -No apply change possible if no actual change made... Additional info:
How many queues do you have? The first delay (loading printer information) should be better in rawhide since the information is now cached. It will still take a while the first time but subsequently should be quite fast.
I only have one queue... Will you be able to reduce the initial delay also?
Not for FC4, no.
Just for kicks, I tried doing the same task in Ubuntu Breezy Badger Colony 5 and it is painless and very quick (no delay at all). So I would suggest using whatever they are using (gnome-cups-manager) for future FC release.
Just tried FC5t2 system-config-printer-gui-0.6.148-1 and the initial delay is still there but after that it much faster as you've said. However: *the apply is still activated even if I haven't made a change *the "Please wait" box that pops up stays on top even when I ALT-TAB away from the application Will there be an effort on the printer GUI for FC5 release?
No. What is needed is a redesign of system-config-printer, or else a re-architecting of the client sides to make it irrelevant. Work is going into planning this.
In Fedora 8 system-config-printer is spiffier and although there is still a delay the first time when "Searching for drivers", it seems to be much snappier in subsequent instances. Thank you!