Public bug reported:

I'm used to being able to print from Abiword over to my server.
Client and server computers are running Gutsy.
Printer is HP D7460 attached to server by USB.
I just upgraded both client and server computers this morning.

Error reported in error_log is:
D [22/Feb/2008:09:48:35 -0500] [Job 617] Unrecoverable error: 
configurationerror in setpagedevice
D [22/Feb/2008:09:48:35 -0500] [Job 617] Operand stack:
D [22/Feb/2008:09:48:35 -0500] [Job 617] true  --nostringval--
D [22/Feb/2008:09:48:35 -0500] [Job 617] renderer return value: 255
D [22/Feb/2008:09:48:35 -0500] [Job 617] renderer received signal: 255
D [22/Feb/2008:09:48:35 -0500] [Job 617] Process dying with "The renderer 
command line returned an unrecognized error code 255.", exit stat: 1
D [22/Feb/2008:09:48:35 -0500] [Job 617] error: Illegal seek (29)
D [22/Feb/2008:09:48:35 -0500] [Job 617] tail process done writing data to 
STDOUT
D [22/Feb/2008:09:48:35 -0500] [Job 617] KID4 finished
D [22/Feb/2008:09:48:35 -0500] [Job 617] Found: %%PageResources: procset 
gnome-print-procs-2.18.2
D [22/Feb/2008:09:48:35 -0500] [Job 617] --> Continue DSC parsing now.
D [22/Feb/2008:09:48:35 -0500] [Job 617] 
D [22/Feb/2008:09:48:35 -0500] [Job 617] Found: %%Trailer
D [22/Feb/2008:09:48:35 -0500] [Job 617] --> Continue DSC parsing now.
D [22/Feb/2008:09:48:35 -0500] [Job 617] 
D [22/Feb/2008:09:48:35 -0500] [Job 617] Found: %%Pages: 1
D [22/Feb/2008:09:48:35 -0500] [Job 617] --> Continue DSC parsing now.
D [22/Feb/2008:09:48:35 -0500] [Job 617] 
D [22/Feb/2008:09:48:35 -0500] [Job 617] Found: %%BoundingBox: 0 0 612 792
D [22/Feb/2008:09:48:35 -0500] [Job 617] --> Continue DSC parsing now.
D [22/Feb/2008:09:48:35 -0500] [Job 617] 
D [22/Feb/2008:09:48:35 -0500] [Job 617] Found: %%EOF
D [22/Feb/2008:09:48:35 -0500] [Job 617] --> Continue DSC parsing now.
D [22/Feb/2008:09:48:35 -0500] [Job 617] 
D [22/Feb/2008:09:48:35 -0500] [Job 617] 
D [22/Feb/2008:09:48:35 -0500] [Job 617] Closing renderer
D [22/Feb/2008:09:48:35 -0500] [Job 617] KID3 exited with status 1
D [22/Feb/2008:09:48:35 -0500] [Job 617] Renderer exit stat: 1
D [22/Feb/2008:09:48:35 -0500] [Job 617] The renderer command line returned an 
unrecognized error code 255.
D [22/Feb/2008:09:48:35 -0500] [Job 617] Renderer process finished
D [22/Feb/2008:09:48:35 -0500] [Job 617] Killing process 3304 (KID3)

I don't know if it is relevant, but the apt log on the server:
Log started: 2008-02-22  08:37:54
(Reading database ... 272879 files and directories currently installed.)
Preparing to replace libpcre3 7.4-0ubuntu0.7.10.1 (using 
.../libpcre3_7.4-0ubuntu0.7.10.2_i386.deb) ...
Unpacking replacement libpcre3 ...
Preparing to replace libpcrecpp0 7.4-0ubuntu0.7.10.1 (using 
.../libpcrecpp0_7.4-0ubuntu0.7.10.2_i386.deb) ...
Unpacking replacement libpcrecpp0 ...
Preparing to replace scribus 1.3.3.9.dfsg-1ubuntu1 (using 
.../scribus_1.3.3.11.dfsg-1ubuntu3~gutsy1_i386.deb) ...
Unpacking replacement scribus ...
Setting up libpcre3 (7.4-0ubuntu0.7.10.2) ...
Setting up libpcrecpp0 (7.4-0ubuntu0.7.10.2) ...
Setting up scribus (1.3.3.11.dfsg-1ubuntu3~gutsy1) ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Log ended: 2008-02-22  08:38:04

This morning I first printed out one Abiword document that I had laying around.
A new Abiword document failed.  I tried repeatedly.  They all failed.  I tried 
restarting in cups admin and they all stopped.
I tried quiting all of my Abiword instances, then restarting Abiword, opening 
up the problem doc and trying to print that again.  Failed again.
I printed off to PDF, opened up that document in evince and printed that off 
successfully (from client sys evince to server HP printer).
Hence I do not know if the issue is in Abiword, cups, or the regular expression 
parser that was picked up by the update.

** Affects: abiword (Ubuntu)
     Importance: Undecided
         Status: New

-- 
cups not printing from abiword
https://bugs.launchpad.net/bugs/194384
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to