Bug 562492 – 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 562492 - crash in Epiphany Web Bookmarks:


Summary:	crash in Epiphany Web Bookmarks:


Status:	RESOLVED DUPLICATE of bug 536768

Product:	epiphany
Classification:	Core
Component:	[obsolete] BugBuddyBugs
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-11-27 20:19 UTC by hipho
Modified:	2008-11-28 08:38 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description hipho 2008-11-27 20:19:29 UTC

Version: 2.22.1.1

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Wasp
Icon Theme: Amaranth

Memory status: size: 590069760 vsize: 590069760 resident: 149618688 share: 31322112 rss: 149618688 rss_rlim: 18446744073709551615
CPU usage: start_time: 1227808786 rtime: 44501 utime: 41879 stime: 2622 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b856e0cbea0 (LWP 2988)]
[New Thread 0x45009950 (LWP 3251)]
[New Thread 0x41802950 (LWP 3250)]
[New Thread 0x44808950 (LWP 3001)]
[New Thread 0x44007950 (LWP 3000)]
[New Thread 0x41001950 (LWP 2992)]
[New Thread 0x40800950 (LWP 2989)]
(no debugging symbols found)
0x00002b8567d2eedf in waitpid () from /lib/libpthread.so.0

+ Trace 210287

Thread 1 (Thread 0x2b856e0cbea0 (LWP 2988))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 ??
from /usr/lib/libgtkembedmoz.so.0d
#5 <signal handler called>
#6 dbus_g_proxy_connect_signal
from /usr/lib/libdbus-glib-1.so.2
#7 notify_notification_show
from /usr/lib/libnotify.so.1
#8 ??
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 ??
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#13 ??
#14 ??
from /usr/lib/libxul.so.0d
#15 ??
from /usr/lib/libxul.so.0d
#16 ??
from /usr/lib/libxul.so.0d
#17 ??
from /usr/lib/libxul.so.0d
#18 ??
from /usr/lib/libxul.so.0d
#19 ??
from /usr/lib/libxul.so.0d
#20 ??
from /usr/lib/libxul.so.0d
#21 PL_HandleEvent
from /usr/lib/libxul.so.0d
#22 PL_ProcessPendingEvents
from /usr/lib/libxul.so.0d
#23 ??
from /usr/lib/libxul.so.0d
#24 ??
from /usr/lib/libxul.so.0d
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 ??
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-11-28 08:38:03 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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