Bug 550852 - pstoraster fails on signal 6, can't print to HP PSC1610
Summary: pstoraster fails on signal 6, can't print to HP PSC1610
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ghostscript
Version: 12
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-27 19:00 UTC by Paul W. Frields
Modified: 2010-01-12 23:34 UTC (History)
2 users (show)

Fixed In Version: 8.70-2.fc11
Clone Of:
Environment:
Last Closed: 2010-01-12 23:27:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/cups/error_log (26.00 KB, text/plain)
2009-12-27 19:00 UTC, Paul W. Frields
no flags Details

Description Paul W. Frields 2009-12-27 19:00:00 UTC
Created attachment 380547 [details]
/var/log/cups/error_log

Description of problem:
Log file /var/log/cups/error_log attached to show problem. This error occurs each time I try to enable the USB-attached HP PSC1610 printer.

Version-Release number of selected component (if applicable):
cups-1.4.2-20.fc12.x86_64
hplip-3.9.8-25.fc12.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Open printer administration tool.
2. Right click printer and choose enable.
  
Actual results:
See attached log

Expected results:
Printer enabled on system startup per normal.

Additional info:
Problem occurred on current stable update for cups & hplip, and also in testing updates as of today.  Used 'service cups stop; rm -rf /var/cache/cups; service cups start' between updates to help ensure clean start each time.  Also did 'touch /.autorelabel ; reboot' -- no AVC errors are apparent but the SELinux audit.log shows:

type=ANOM_ABEND msg=audit(1261939726.547:33711): auid=501 uid=4 gid=7 ses=1 subj
=unconfined_u:system_r:cupsd_t:s0-s0:c0.c1023 pid=4121 comm="gs" sig=6

Comment 1 Tim Waugh 2010-01-05 12:08:41 UTC
Can you please try ghostscript-8.70-2.fc12 from koji?  I'd like to make sure whether that fixes it.

Comment 2 Paul W. Frields 2010-01-05 13:44:51 UTC
That ghostscript package does appear to fix the problem.  If you issue the new build(s) to updates-testing in support of this bug, I'll be happy to give the builds a +1 karma vote.

Comment 3 Fedora Update System 2010-01-05 14:04:07 UTC
ghostscript-8.70-2.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/ghostscript-8.70-2.fc11

Comment 4 Fedora Update System 2010-01-05 14:04:44 UTC
ghostscript-8.70-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/ghostscript-8.70-2.fc12

Comment 5 Fedora Update System 2010-01-08 19:56:59 UTC
ghostscript-8.70-2.fc12 has been pushed to the Fedora 12 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 ghostscript'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0327

Comment 6 Fedora Update System 2010-01-08 20:13:32 UTC
ghostscript-8.70-2.fc11 has been pushed to the Fedora 11 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 ghostscript'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-0350

Comment 7 Fedora Update System 2010-01-12 23:27:04 UTC
ghostscript-8.70-2.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2010-01-12 23:34:05 UTC
ghostscript-8.70-2.fc11 has been pushed to the Fedora 11 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.