GNOME Bugzilla – Bug 501713
crash in Galeon Web Browser: Print
Last modified: 2007-12-19 12:40:22 UTC
What were you doing when the application crashed? Print Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 117940224 vsize: 117940224 resident: 47476736 share: 27013120 rss: 47476736 rss_rlim: 4294967295 CPU usage: start_time: 1196851117 rtime: 2526 utime: 2364 stime: 162 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/galeon' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb61736c0 (LWP 6747)] [New Thread 0xb312db90 (LWP 9057)] [New Thread 0xb5275b90 (LWP 6761)] [New Thread 0xb5d83b90 (LWP 6754)] (no debugging symbols found) 0xb7ecbbf1 in waitpid () from /lib/libpthread.so.0
+ Trace 180805
----------- .xsession-errors (1734654 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Ctrl + P or menu Print, any web site $ gdb galeon GNU gdb 6.6.90.20070912-debian Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/galeon (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) [Thread debugging using libthread_db enabled] (no debugging symbols found) (no debugging symbols found) [New Thread 0xb603e6c0 (LWP 5336)] [New Thread 0xb5c0bb90 (LWP 5341)] [New Thread 0xb50fdb90 (LWP 5345)] [New Thread 0xb48fdb90 (LWP 5346)] [New Thread 0xb402bb90 (LWP 5354)] [Thread 0xb402bb90 (LWP 5354) exited] [New Thread 0xb382bb90 (LWP 5355)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb603e6c0 (LWP 5336)] 0x080b7448 in print_printer_combo_cb () (gdb) Quit (gdb) thread apply all bt
+ Trace 181861
Thread 1 (Thread 0xb603e6c0 (LWP 5336))
Thanks for the follow up. The information on where exactly the crash was happening (print_printer_combo_cb) was missing from the original trace. This is a bug thats fixed in cvs (see the dup). It would be nice if the debian maintainer is made aware of it so that he can update galeon with the fix, we get way to many reports from Debian lenny/sid about printing crashes with no useful information in the report. From now on I plan to mark all of those as dups to the original. *** This bug has been marked as a duplicate of 460235 ***
Is this the same Bug reported in Debian, or it is another: Debian Bug report logs - #444196 SIGSEGV when opening print dialog http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444196&archived=False&mbox=no Notes below - just for reference, if we need to report it. :-) #dpkg --list galeon ||/ Navn Versjon Beskrivelse +++-==============-==============-============================================ ii galeon 2.0.2-4 GNOME web browser for advanced users How to report a bug in Debian using reportbug http://www.debian.org/Bugs/Reporting
I think its the same one, and fixed with the upgrade to 2.0.4-1 as noted in the report. Please reopen here if you still see this with 2.0.4. Thanks