Bug 353745 – crash in Epiphany Web Bookmarks:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 353745 - crash in Epiphany Web Bookmarks:


Summary:	crash in Epiphany Web Bookmarks:


Status:	RESOLVED DUPLICATE of bug 354790

Product:	epiphany
Classification:	Core
Component:	General
Version:	2.15.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Epiphany Maintainers
QA Contact:	Marco Pesenti Gritti

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-31 21:42 UTC by Sven S.
Modified:	2006-09-30 20:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Sven S. 2006-08-31 21:42:18 UTC

Version: 2.15.91

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 136900608 vsize: 0 resident: 136900608 share: 0 rss: 64577536 rss_rlim: 0
CPU usage: start_time: 1157058912 rtime: 0 utime: 22137 stime: 0 cutime:20625 cstime: 0 timeout: 1512 it_real_value: 0 frequency: 796

Backtrace was generated from '/usr/bin/epiphany'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227696464 (LWP 23482)]
[New Thread -1269105760 (LWP 23494)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71334

Thread 1 (Thread -1227696464 (LWP 23482))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 gtk_moz_embed_get_title
from /usr/lib/firefox/libgtkembedmoz.so
#4 <signal handler called>
#5 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#6 NSGetModule
from /usr/lib/firefox/components/libgkplugin.so
#7 NSGetModule
from /usr/lib/firefox/components/libgkplugin.so
#8 ??
from /usr/lib/firefox/components/libgkplugin.so
#9 ??
#10 ??
from /usr/lib/firefox/components/libgklayout.so
#11 ??
#12 NSGetModule
from /usr/lib/firefox/components/libgklayout.so
#13 NSGetModule
from /usr/lib/firefox/components/libgklayout.so
#14 NSGetModule
from /usr/lib/firefox/components/libgklayout.so
#15 NSGetModule
from /usr/lib/firefox/components/libgkplugin.so
#16 NSGetModule
from /usr/lib/firefox/components/libgkplugin.so
#17 ??
from /usr/lib/firefox/components/libgkplugin.so
#18 ??
#19 ??
#20 ??
#21 ??
from /usr/lib/firefox/components/libpref.so
#22 ??
from /usr/lib/firefox/libxpcom_core.so
#23 ??
#24 ??
#25 NSGetModule
from /usr/lib/firefox/components/libgkplugin.so
#26 ??
from /usr/lib/firefox/components/libgkplugin.so
#27 ??
#28 ??
#29 ??
#30 ??
from /usr/lib/firefox/components/libgkplugin.so
#31 ??
#32 ??
#33 ??
#34 ??
from /usr/lib/firefox/components/libgkplugin.so
#35 ??
#36 ??
#37 ??
#0 __kernel_vsyscall

Comment 1 Reinout van Schouwen 2006-09-01 10:08:35 UTC

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.

Comment 2 Karsten Bräckelmann 2006-09-30 20:54:04 UTC

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 354790 ***