Mailinglist Archive: opensuse-bugs (4992 mails)

< Previous Next >
[Bug 498254] Printing does not work
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 11 May 2009 23:49:31 -0600 (MDT)
  • Message-id: <20090512054931.23EEF245393@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=498254

User jsmeix@xxxxxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=498254#c29


Johannes Meixner <jsmeix@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |sboyce@xxxxxxxxxxxxxxxx




--- Comment #29 from Johannes Meixner <jsmeix@xxxxxxxxxx> 2009-05-11 23:49:27
MDT ---
HPLIP in Factory is the same what works well in openSUSE 11.1
CUPS in Factory is the same what works well in openSUSE 11.1

Therefore the root cause it very likely neither in HPLIP
nor in CUPS but somewhere else.

The error message in comment #22 and comment #23
-------------------------------------------------------------------
.. (/usr/lib64/cups/filter/pstoraster) crashed on signal 11!
-------------------------------------------------------------------
indicates a Ghostscript issue.

Currently we have already bug #501711 and bug #502647
regarding Ghostscript.

Please provide a CUPS error_log for one single
failed printout as described here:
http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
--------------------------------------------------------------
1. Set the "LogLevel debug" in /etc/cups/cupsd.conf.
2. Stop cupsd.
3. Move /var/log/cups/error_log* to another location
(or delete it) in order to avoid having to search
through gigantic log files.
4. Start cupsd.
5. Retry the action leading to the problem.
6. Now /var/log/cups/error_log contains many messages
that are useful for troubleshooting.
--------------------------------------------------------------
Attach /var/log/cups/error_log to this bug after
one single printout had failed.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >