Bug 579957 - [abrt] crash in system-config-printer-1.1.18-2.fc12: timedops.py:150:collect_result:IPPError: (1030, 'client-error-not-found')
Summary: [abrt] crash in system-config-printer-1.1.18-2.fc12: timedops.py:150:collect_...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9015b701
Depends On:
Blocks: 583054
TreeView+ depends on / blocked
 
Reported: 2010-04-07 04:35 UTC by Doug Hutcheson
Modified: 2010-05-07 03:57 UTC (History)
2 users (show)

Fixed In Version: system-config-printer-1.2.1-1.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 583054 (view as bug list)
Environment:
Last Closed: 2010-05-07 03:57:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (612 bytes, text/plain)
2010-04-07 04:35 UTC, Doug Hutcheson
no flags Details
Output from printing troubleshooter (670.39 KB, text/plain)
2010-04-15 23:49 UTC, Doug Hutcheson
no flags Details

Description Doug Hutcheson 2010-04-07 04:35:02 UTC
abrt 1.0.8 detected a crash.

architecture: i686
cmdline: python /usr/share/system-config-printer/system-config-printer.py
comment: I am having constant problems with slow printing. system-config-printer/Server Settings/Advanced times out with a dialog "CUPS server error/There was an HTTP error: status 1000". No errors are being logged to /var/log/cups/error_log or /var/log/https/error_log. httpd and the CUPS scheduler service are both running (automatic at startup). The only printer is a locally connected BJC4100 driver name STP01419.PPD version 5.2.5. I have a LAN with 3 computers sharing the one printer. Printing worked under FC10 and I have only recently upgraded to FC12, with these problems starting right away.
component: system-config-printer
executable: /usr/share/system-config-printer/system-config-printer.py
kernel: 2.6.32.10-90.fc12.i686.PAE
package: system-config-printer-1.1.18-2.fc12
reason: timedops.py:150:collect_result:IPPError: (1030, 'client-error-not-found')
release: Fedora release 12 (Constantine)

backtrace
-----
timedops.py:150:collect_result:IPPError: (1030, 'client-error-not-found')

Traceback (most recent call last):
  File "/usr/share/system-config-printer/troubleshoot/PrintTestPage.py", line 471, in update_jobs_list
    notifications = self.op.run ()
  File "/usr/share/system-config-printer/timedops.py", line 197, in run
    return self.thread.collect_result ()
  File "/usr/share/system-config-printer/timedops.py", line 150, in collect_result
    raise self.exception
IPPError: (1030, 'client-error-not-found')

Local variables in innermost frame:
self: <OperationThread(Thread-26, stopped daemon -1285563536)>

How to reproduce
-----
1. Running print troubleshooter
2.
3.

Comment 1 Doug Hutcheson 2010-04-07 04:35:04 UTC
Created attachment 404833 [details]
File: backtrace

Comment 2 Jiri Popelka 2010-04-07 10:26:46 UTC
Are you able to somehow obtain the troubleshooter output ?
I see s-c-printer crashed when you tried to print test page in troubleshooter, but you write that "I am having constant problems with slow printing".
So you are able to print (and therefore obtain the troubleshooter output), right ?

Are you experiencing the same "slow printing" problems regardless whether you print from the locally connected machine or from some other computer on LAN ?
Or is it different ?

Comment 3 Tim Waugh 2010-04-08 13:55:46 UTC
I think commit 43089db (just pushed upstream) will fix the traceback, and some others like it.  It won't have any effect on the slow printing problem though.

Comment 4 Fedora Update System 2010-04-15 00:10:39 UTC
system-config-printer-1.2.1-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/system-config-printer-1.2.1-1.fc13

Comment 5 Doug Hutcheson 2010-04-15 23:49:30 UTC
Created attachment 406964 [details]
Output from printing troubleshooter

Requested by Jiri Popelka on 7 April 2010

Comment 6 Doug Hutcheson 2010-04-15 23:54:45 UTC
(In reply to comment #2)
> Are you able to somehow obtain the troubleshooter output ?
> I see s-c-printer crashed when you tried to print test page in troubleshooter,
> but you write that "I am having constant problems with slow printing".
> So you are able to print (and therefore obtain the troubleshooter output),
> right ?
> 
> Are you experiencing the same "slow printing" problems regardless whether you
> print from the locally connected machine or from some other computer on LAN ?
> Or is it different ?    

Jiri, I have been replying to this via gmail and did not realise I had to work here through Bugzilla - sorry for the delay this has caused. The content of my gmail posts is as follows:

Yes, I have been able to capture troubleshooter output - see attached. I also have the log file, which has timestamps, but it is +/-38Mb - is there any particular part of it you would like to see?.

The "slow printing" problem is this: any interaction with the CUPS server is taking one minute twenty five seconds to one minute forty five seconds, timed using my wrist watch. The document I printed to capture the trouble-shooter output was a page of random text (lorem ipsum) printed from OpenOffice. From the time I clicked Print to the time the printer started was 1:45. During the one-page print, the printer paused twice, each time for +/-1:25. Pointing Firefox to localhost:631 takes over a minute (not accurately timed yet). Connecting over my network takes well over a minute from the time I click 'Print...' until the printer dialog becomes available. It spends this time displaying the progress message "Getting printer information ...". A four-page pdf I printed over the network took over 11 minutes to complete.

Note that the output is correct and all documents have printed correctly, except for an inability to print a test page from the printer configuration/Troubleshooter dialogs.

Note also the same PC and printer did not have this problem under FC10.

Please let me know if there is anything more I can do to help.

I connected the printer to an old IBM T23 notebook (1.3Ghz CPU) and found the delays much shorter. Printing locally caused the same document to start on the printer after only 15 seconds and there was one delay of approx 10 seconds during the print. Printing from a networked notebook took approx 1 minute to start and there were two delays, one of aprox 45 seconds and the other of approx 15 seconds. I can live with these delays, so will set up the T23 as a printer server permanently on my network, but it does not solve the problem of the longer delays and crashes when the printer is connected to my desktop PC(2.8GHz CPU). As a wild idea from left field, has something changed in the parallel port driver in FC12? See also http://forums.fedoraforum.org/showthread.php?p=1351123#post1351123

Could not live with the delays after all, so booted the notebook into WinXP and shared the printer from there. Printing and getting printer properties from networked FC12 boxen is now immediate, so it does seem to be an issue with the FC12 CUPS server somewhere.

Cheers, Doug

Comment 7 Jiri Popelka 2010-04-16 14:44:25 UTC
I filled a separate bug #583054 report for this slow printing problem.

Comment 8 Fedora Update System 2010-04-16 23:49:07 UTC
system-config-printer-1.2.1-1.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update system-config-printer'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/system-config-printer-1.2.1-1.fc13

Comment 9 Fedora Update System 2010-05-07 03:57:00 UTC
system-config-printer-1.2.1-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.


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