GNOME Bugzilla – Bug 511604
crash in Galeon Web Browser: Trying to print a recipe...
Last modified: 2008-01-24 14:53:31 UTC
What were you doing when the application crashed? Trying to print a recipe in html from Gourmet Recipe manager Distribution: PCLinuxOS release 2007 (PCLinuxOS) for i586 Gnome Release: 2.21.2 2007-11-30 (%vendor) BugBuddy Version: 2.20.1 System: Linux 2.6.18.8.tex5 #1 SMP Thu May 10 11:36:58 WST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 122707968 vsize: 122707968 resident: 29999104 share: 21626880 rss: 29999104 rss_rlim: 4294967295 CPU usage: start_time: 1201115586 rtime: 331 utime: 306 stime: 25 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/i686/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1229912368 (LWP 15997)] [New Thread -1314071648 (LWP 16006)] [New Thread -1252369504 (LWP 16004)] [New Thread -1234539616 (LWP 16003)] (no debugging symbols found) 0xb7f49410 in __kernel_vsyscall ()
+ Trace 186525
Thread 4 (Thread -1234539616 (LWP 16003)): #-1 0xb7f49410 in __kernel_vsyscall () No symbol table info available. Thread 3 (Thread -1252369504 (LWP 16004)): #-1 0xb7f49410 in __kernel_vsyscall () No symbol table info available. Thread 2 (Thread -1314071648 (LWP 16006)): #-1 0xb7f49410 in __kernel_vsyscall () No symbol table info available. Thread 1 (Thread -1229912368 (LWP 15997)): #-1 0xb7f49410 in __kernel_vsyscall () No symbol table info available. ----------- .xsession-errors --------------------- Major opcode: 20 Minor opcode: 0 Resource id: 0x0 ** (galeon:15997): WARNING **: GConf error: Type mismatch: Expected `bool' got `int' for key /apps/galeon/Print/printon Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded --------------------------------------------------
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 460235 ***