Hide Forgot
abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 56832 bytes cmdline: /usr/lib64/openoffice.org3/program/soffice.bin webgis_wordpress_-_inschatting_webhosting.doc component: openoffice.org Attached file: coredump, 115568640 bytes crash_function: __libc_message executable: /usr/lib64/openoffice.org3/program/soffice.bin kernel: 2.6.35.11-83.fc14.x86_64 package: openoffice.org-brand-1:3.3.0-20.2.fc14 rating: 4 reason: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1299100298 uid: 500 How to reproduce ----- 1. I was trying to print a document. 2. 3.
Created attachment 481960 [details] File: backtrace
dtardon->twaugh: do you see any obvious problem on CUPS's side along this path?
Whoops! I just found out that I am unable to print anything. Even a test-page from 'system-config-printer' does not work. Cups generates quite some information in its error log. I will attach the information to this bug.
Created attachment 481995 [details] Cups error log (while trying to print test page)
Egon, please run bannertops like this /usr/lib/cups/filter/bannertops 1 egon '' 1 '' /usr/share/cups/data/testprint > testprint.ps What do you see ? Does the testprint.ps contain test page ? can you also attach output from printing troubleshooter ? thanks https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter
Created attachment 482263 [details] Printer troubleshooter -> error log
Hi Jiri, $ /usr/lib/cups/filter/bannertops 1 egon '' 1 '' /usr/share/cups/data/testprint > testprint.ps DEBUG: load_banner(filename="/usr/share/cups/data/testprint") DEBUG: PNG image: 128x128x8, color_type=6 (RGB+ALPHA) DEBUG: PNG image: 192x128x8, color_type=2 (RGB) # I viewed the result (testprint.ps), and it looks fine. I also ran the printing-troubleshooter. It showed some sort of "stack smashing"... ;) <see attachments> I hope this helps. kind regards, Egon
Created attachment 482264 [details] Printer troubleshooter -> diagnostics output
If there's still the /var/spool/cups/d00371-001 file, run it through /usr/lib/cups/filter/bannertops 1 egon '' 1 '' /var/spool/cups/d00371-001 > testprint.ps and if you see something strange attach the file to this bug report, thanks.
Hi Jiri, The file was not there anymore. So I tried to print a new test-page, which produced /var/spool/cups/d00372-001 Running that through bannertops did not produce anything strange. The output (viewed with gsview) shows a nice test-page. <see attachment> Egon
Created attachment 482285 [details] bannertops output (nice test-page)
Could you please attach the PPD you are using? It's this file: /etc/cups/ppd/almp0171.ppd
Created attachment 482850 [details] almp0171.ppd
Created attachment 482851 [details] Lexmark-C534dn.ppd
Hi Tim, I can not print to multiple printers. So I attached multiple PPD files. kind regards, Egon
*** Bug 689936 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping