GNOME Bugzilla – Bug 112857
Gnumeric-1.1.16 crashes on printing
Last modified: 2009-08-15 18:40:50 UTC
Package: Gnumeric Severity: normal Version: 1.1.16 Synopsis: Gnumeric-1.1.16 crashes on printing Bugzilla-Product: Gnumeric Bugzilla-Component: Printing BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: I built my own gnumeric-1.1.16 on RH9, and created an RPM using checkinstall. When I try to print, I get an immediate crash (before the print dialog even comes up). The backtrace attached should give more details. Steps to reproduce the problem: 1. File->Print Reproducibility: Every time Debugging Information: Backtrace was generated from '/usr/local/bin/gnumeric' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1096266848 (LWP 6938)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...0xffffe002 in ?? ()
+ Trace 36809
Thread 1 (Thread 1096266848 (LWP 6938))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-12 15:02 ------- Reassigning to the default owner of the component, jody@gnome.org.
I don't believe that stack trace. Could you try making sure that debug information is on, both in gnumeric and in gnome-print?
Hmm, I re-built libgnomeprint-2.2 and libgnomeprintui-2.2, and re-built gal-1.99.4 (I had gal-2.0-0.0.7 built before), and then re-built gnumeric to work with these, and the problem went away. If there's not enough info in the stack trace, I can't re-duplicate it now anyway. Closing the bug report -- thanks.
May be a dup of bug 105745.
Entirely unrelated it appears to me. The part of the stack trace to compare is the part right below: #2 <signal handler called>