Bug 539523 – crash in Epiphany Web Browser: a downloaded pdf had jus...

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 539523 - crash in Epiphany Web Browser: a downloaded pdf had jus...


Summary:	crash in Epiphany Web Browser: a downloaded pdf had jus...


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-06-21 21:24 UTC by ralough
Modified:	2008-06-22 12:28 UTC

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

Description ralough 2008-06-21 21:24:13 UTC

Version: 2.22.1.1

What were you doing when the application crashed?
a downloaded pdf had just completed


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

System: Linux 2.6.23-ver.1.0 #1 SMP Sun Jan 27 13:18:45 GMT 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 680878080 vsize: 680878080 resident: 140771328 share: 31236096 rss: 140771328 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214027929 rtime: 44536 utime: 38616 stime: 5920 cutime:0 cstime: 4 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 0x2b8dff329200 (LWP 8311)]
[New Thread 0x43005950 (LWP 19121)]
[New Thread 0x42003950 (LWP 8455)]
[New Thread 0x42804950 (LWP 8454)]
[New Thread 0x41001950 (LWP 8313)]
[New Thread 0x40800950 (LWP 8312)]
(no debugging symbols found)
0x00002b8df98e0edf in waitpid () from /lib/libpthread.so.0

+ Trace 201041

Thread 1 (Thread 0x2b8dff329200 (LWP 8311))

#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 (437442 sec old) ---------------------
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: N
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Susana 2008-06-22 12:28:24 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 ***