Bug 362954 – crash in Epiphany Web Bookmarks: logging out

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 362954 - crash in Epiphany Web Bookmarks: logging out


Summary:	crash in Epiphany Web Bookmarks: logging out


Status:	RESOLVED DUPLICATE of bug 350663

Product:	epiphany
Classification:	Core
Component:	General
Version:	2.16.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-10-17 20:04 UTC by george
Modified:	2006-10-17 23:09 UTC

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

Description george 2006-10-17 20:04:03 UTC

Version: 2.16.1

What were you doing when the application crashed?
logging out


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 189366272 vsize: 0 resident: 189366272 share: 0 rss: 75616256 rss_rlim: 0
CPU usage: start_time: 1161111660 rtime: 0 utime: 231640 stime: 0 cutime:130000 cstime: 0 timeout: 101640 it_real_value: 0 frequency: 8

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 -1228646736 (LWP 28088)]
[New Thread -1343423584 (LWP 28990)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 76852

Thread 1 (Thread -1228646736 (LWP 28088))

#0 __kernel_vsyscall
#1 waitpid
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 ??
#6 ??
from /usr/lib/libglib-2.0.so.0
#7 pthread_mutex_lock
from /lib/tls/i686/cmov/libc.so.6
#8 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_iteration
from /usr/lib/libglib-2.0.so.0
#12 gtk_main_iteration
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
#14 ??
from /usr/lib/libglib-2.0.so.0
#15 pthread_mutex_lock
from /lib/tls/i686/cmov/libc.so.6
#16 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_iteration
from /usr/lib/libglib-2.0.so.0
#20 gtk_main_iteration
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
#22 ??
from /usr/lib/libglib-2.0.so.0
#23 pthread_mutex_lock
from /lib/tls/i686/cmov/libc.so.6
#24 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_iteration
from /usr/lib/libglib-2.0.so.0
#28 gtk_main_iteration
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
#30 ??
from /usr/lib/libglib-2.0.so.0
#31 pthread_mutex_lock
from /lib/tls/i686/cmov/libc.so.6
#32 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#35 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 main
#0 __kernel_vsyscall

Comment 1 Reinout van Schouwen 2006-10-17 23:09:07 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 350663 ***