GNOME Bugzilla – Bug 146890
Galeon 1.3.15 crashes on x86_64 fc2
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: galeon Severity: blocker Version: GNOME2.6. 1.3.15 Gnome-Distributor: Red Hat, Inc Synopsis: Galeon 1.3.15 crashes on x86_64 fc2 Bugzilla-Product: galeon Bugzilla-Component: Mozilla interaction Bugzilla-Version: 1.3.15 BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: On start segfaults Steps to reproduce the crash: 1. Install the rpm galeon-1.3.15-1.1.fc2.dag of http://dag.wieers.com/apt/ 2. enter galeon in an xterm 3. Crash: galeon-bin[29672]: segfault at 0000003700000000 rip 00000037f03100da rsp 0000007fbfffef90 error 4 galeon-bin[7162]: segfault at 0000003700000000 rip 00000037f03100da rsp 0000007fbfffef90 error 4 galeon-bin[11447]: segfault at 0000003700000000 rip 00000037f03100da rsp 0000007fbfffef90 error 4 nautilus[13436]: segfault at 00000004fffffffe rip 00000037f232d22b rsp 0000007fbfffec60 error 4 galeon-bin[19009]: segfault at 0000003700000000 rip 00000037f03100da rsp 0000007fbffff060 error 4 galeon-bin[19220]: segfault at 0000003700000000 rip 00000037f03100da rsp 0000007fbfffee50 error 4 Expected Results: Should it work? How often does this happen? Always Additional Information: It is not possible to compile from source. Tried several configure options. /usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching for -lpthread /usr/bin/ld: skipping incompatible /usr/lib/libpthread.a when searching for -lpthread /usr/bin/ld: skipping incompatible /usr/lib/libz.so when searching for -lz /usr/bin/ld: skipping incompatible /usr/lib/libz.a when searching for -lz /usr/lib/libpopt.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [galeon-bin] Error 1 Debugging Information: Backtrace was generated from '/usr/bin/galeon-bin' (no debugging symbols found)...Using host libthread_db library "/lib64/tls/libthread_db.so.1". (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)...[Thread debugging using libthread_db enabled] [New Thread 182900987296 (LWP 19220)] [New Thread 1084225888 (LWP 19223)] [Thread debugging using libthread_db enabled] [New Thread 182900987296 (LWP 19220)] [New Thread 1084225888 (LWP 19223)] [Thread debugging using libthread_db enabled] [New Thread 182900987296 (LWP 19220)] [New Thread 1084225888 (LWP 19223)] (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)...(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)...(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)...0x00000037ee50be74 in waitpid () from /lib64/tls/libpthread.so.0
+ Trace 48245
Thread 1 (Thread 182900987296 (LWP 19220))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 08:25 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "galeon". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was ivololeribar@yahoo.it. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** This bug has been marked as a duplicate of 138997 ***