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


Summary:	crash in Epiphany Web Bookmarks:


Status:	RESOLVED DUPLICATE of bug 509083

Product:	epiphany
Classification:	Core
Component:	[obsolete] BugBuddyBugs
Version:	2.22.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-08-04 19:12 UTC by X
Modified:	2010-08-04 20:28 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description X 2010-08-04 19:12:14 UTC

Version: 2.22.3

What were you doing when the application crashed?



Distribution: Debian squeeze/sid
Gnome Release: 2.30.2 2010-07-17 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-2-686 #1 SMP Mon Jun 21 05:58:44 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 121225216 vsize: 121225216 resident: 64352256 share: 23105536 rss: 64352256 rss_rlim: 4294967295
CPU usage: start_time: 1280948866 rtime: 4575 utime: 4291 stime: 284 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb61f0740 (LWP 15083)]
0xb7789424 in __kernel_vsyscall ()

+ Trace 223105

Thread 1 (Thread 0xb61f0740 (LWP 15083))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gspawn.c line 682
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 nsProfileLock::FatalSignalHandler
at nsProfileLock.cpp line 216
#7 <signal handler called>
#8 ??
#9 NS_HasPendingEvents_P
at nsThreadUtils.cpp line 194
#10 nsBaseAppShell::OnProcessNextEvent
at nsBaseAppShell.cpp line 288
#11 nsThread::ProcessNextEvent
at nsThread.cpp line 497
#12 NS_ProcessPendingEvents_P
at nsThreadUtils.cpp line 180
#13 nsBaseAppShell::NativeEventCallback
at nsBaseAppShell.cpp line 121
#14 nsAppShell::EventProcessorCallback
at nsAppShell.cpp line 69
#15 g_io_unix_dispatch
#16 IA__g_main_context_dispatch
at /build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c line 2012
#17 g_main_context_iterate
at /build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c line 2645
#18 IA__g_main_loop_run
at /build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c line 2853
#19 IA__gtk_main
at /build/buildd-gtk+2.0_2.12.12-1~lenny2-i386-2RfKoO/gtk+2.0-2.12.12/gtk/gtkmain.c line 1163
#20 main
at /build/buildd-epiphany-browser_2.22.3-9-i386-MLTyHU/epiphany-browser-2.22.3/src/ephy-main.c line 753
#0 __kernel_vsyscall



----------- .xsession-errors (54 sec old) ---------------------
** 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)
checking for valid crashreport now
warning: .dynamic section for "/usr/lib/libxcb-render-util.so.0" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------

Comment 1 Akhil Laddha 2010-08-04 20:28:47 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 bug 509083 ***