GNOME Bugzilla – Bug 331827
Crash when launching
Last modified: 2006-03-23 15:12:43 UTC
Distribution: Debian 3.1 (sarge) Package: epiphany Severity: Normal Version: GNOME2.12.2 unspecified Gnome-Distributor: Debian Synopsis: Crash when launching Bugzilla-Product: epiphany Bugzilla-Component: General Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.12.1) Description: Description of the crash: When launched by clicking a link on an email in Mozilla Thunderbird, Epiphany crashes before the browser window opens. How often does this happen? Always. If I launch epiphany myself, with the same command line parameters, there is no crash. Debugging Information: Backtrace was generated from '/usr/bin/x-www-browser' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227352384 (LWP 7010)] [New Thread -1244472400 (LWP 7014)] [New Thread -1232159824 (LWP 7011)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 66329
Thread 1 (Thread -1227352384 (LWP 7010))
3085156199, 3074202555, 3074271048, 142368704, 3085156199, 3215458136, 140969368, 142462824, 3085156199, 142462592, 3073697064, 141807512, 3085156176, 3215458184, 3073697064, 142368620, 3085156176, 3215458184, 3073298698, 3073698412, 3085156199, 3215458184, 3074271048, 142368620, 3071244324, 3215458216, 3074078349}}, sa_flags = 142368620, sa_restorer = 0xb7e3bf67 <pthread_mutex_lock+23>} pid = #0 0xffffe410 in __kernel_vsyscall () ------- Bug created by bug-buddy at 2006-02-19 23:37 -------
+ Trace 66330
library mismatch between mozilla and moz-thunderbird
Fantastic, I'll get the maintainer of the thunderbird package to clear LD_LIBRARY_PATH for spawned processes or something like that. Thanks!
Yeah, if a program alters LD_LIBRARY_PATH it should not leave it altered for spawned processes.
*** Bug 335542 has been marked as a duplicate of this bug. ***