GNOME Bugzilla – Bug 356544
epiphany-browser crashes when attempt to print
Last modified: 2006-09-22 11:16:45 UTC
Distribution: Debian testing/unstable Package: epiphany Severity: Normal Version: GNOME2.14.3 unspecified Gnome-Distributor: Debian Synopsis: epiphany-browser crashes when attempt to print Bugzilla-Product: epiphany Bugzilla-Component: Printing Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: crashes when I attempt to print. Steps to reproduce the crash: 1. open any page 2. select printer 3. print .... crash Expected Results: How often does this happen? started after yesterdays upgrade. Additional Information: Debugging Information: Backtrace was generated from '/usr/libexec/epiphany-browser' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1508345344 (LWP 28758)] [New Thread -1555690576 (LWP 28783)] [New Thread -1547301968 (LWP 28782)] [New Thread -1538913360 (LWP 28775)] [New Thread -1530524752 (LWP 28774)] [New Thread -1521951824 (LWP 28773)] (no debugging symbols found) 0xa709d201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 72650
Thread 1 (Thread -1508345344 (LWP 28758))
------- Bug created by bug-buddy at 2006-09-18 14:25 -------
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Also, please try if the problem can be reproduced with the latest Epiphany (2.16) and Fontconfig versions.
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1508824576 (LWP 23109)] 0xa7264d17 in FcCharSetDestroy () from /usr/lib/libfontconfig.so.1 (gdb) thread apply all bt
+ Trace 72677
Thread 1 (Thread -1508824576 (LWP 23109))
*** Bug 357163 has been marked as a duplicate of this bug. ***
Rafal: the stack trace you posted in comment #2 doesn't contain debug symbols so unfortunately it's useless in tracking the source of the problem. Please see http://live.gnome.org/GettingTraces for info on getting good traces. Thanks!
Created attachment 73201 [details] Backtrace I installed all related debug packages I found I debian and here is backtrace.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 356632 ***