Bug 541336 – crash in Epiphany Web Browser:

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 541336 - crash in Epiphany Web Browser:


Summary:	crash in Epiphany Web Browser:


Status:	RESOLVED DUPLICATE of bug 537495

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-07-03 01:34 UTC by Jiun Shyong
Modified:	2008-07-04 07:57 UTC

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

Description Jiun Shyong 2008-07-03 01:34:44 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: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: MacUltimate_Leopard

Memory status: size: 554409984 vsize: 554409984 resident: 55144448 share: 29470720 rss: 55144448 rss_rlim: 18446744073709551615
CPU usage: start_time: 1215048605 rtime: 441 utime: 403 stime: 38 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 0x2ab7fedeede0 (LWP 4222)]
[New Thread 0x42804950 (LWP 4334)]
[New Thread 0x43005950 (LWP 4333)]
[New Thread 0x44808950 (LWP 4231)]
[New Thread 0x44007950 (LWP 4230)]
[New Thread 0x41001950 (LWP 4224)]
[New Thread 0x40800950 (LWP 4223)]
(no debugging symbols found)
0x00002ab7f8e5dedf in waitpid () from /lib/libpthread.so.0

+ Trace 201943

Thread 1 (Thread 0x2ab7fedeede0 (LWP 4222))

#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 PL_HandleEvent
from /usr/lib/libxul.so.0d
#20 PL_ProcessPendingEvents
from /usr/lib/libxul.so.0d
#21 ??
from /usr/lib/libxul.so.0d
#22 ??
from /usr/lib/libxul.so.0d
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#24 ??
from /usr/lib/libglib-2.0.so.0
#25 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (118 sec old) ---------------------
** 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)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Error: PDFDoc::writeTrailer original file's ID entry isn't an array. Trying to continue
Error: PDFDoc::writeTrailer original file's ID entry isn't an array. Trying to continue
--------------------------------------------------

Comment 1 Reinout van Schouwen 2008-07-04 07:57:14 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 537495 ***