Bug 539787 – crash in Epiphany Web Browser: navegando al abrir una i...

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 539787 - crash in Epiphany Web Browser: navegando al abrir una i...


Summary:	crash in Epiphany Web Browser: navegando al abrir una i...


Status:	RESOLVED DUPLICATE of bug 537495

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-23 17:26 UTC by josegd
Modified:	2008-06-23 20:00 UTC

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

Description josegd 2008-06-23 17:26:49 UTC

Version: 2.22.2

What were you doing when the application crashed?
navegando al abrir una imagen con el eiphany se colgo


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

System: Linux 2.6.25-2-amd64 #1 SMP Thu Jun 12 15:38:32 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: DebianRed
Icon Theme: Mist

Memory status: size: 529367040 vsize: 529367040 resident: 70463488 share: 29011968 rss: 70463488 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214241884 rtime: 312 utime: 298 stime: 14 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fc6873f1780 (LWP 29202)]
[New Thread 0x44578950 (LWP 29227)]
[New Thread 0x43d77950 (LWP 29211)]
[New Thread 0x43576950 (LWP 29210)]
[New Thread 0x42d75950 (LWP 29208)]
[New Thread 0x41d73950 (LWP 29207)]
[New Thread 0x42574950 (LWP 29206)]
[New Thread 0x41572950 (LWP 29203)]
(no debugging symbols found)
0x00007fc67fda95ef in waitpid () from /lib/libpthread.so.0

+ Trace 201179

Thread 1 (Thread 0x7fc6873f1780 (LWP 29202))

#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/xulrunner-1.9/libxul.so
#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/xulrunner-1.9/libxul.so
#15 ??
from /usr/lib/xulrunner-1.9/libxul.so
#16 ??
from /usr/lib/xulrunner-1.9/libxul.so
#17 ??
from /usr/lib/xulrunner-1.9/libxul.so
#18 ??
from /usr/lib/xulrunner-1.9/libxul.so
#19 ??
from /usr/lib/xulrunner-1.9/libxul.so
#20 ??
from /usr/lib/xulrunner-1.9/libxul.so
#21 ??
from /usr/lib/xulrunner-1.9/libxul.so
#22 ??
from /usr/lib/xulrunner-1.9/libxul.so
#23 ??
from /usr/lib/xulrunner-1.9/libxul.so
#24 ??
from /usr/lib/xulrunner-1.9/libxul.so
#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 (14974 sec old) ---------------------
(rhythmbox:4053): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:4053): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed
(rhythmbox:4053): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:4053): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed
(rhythmbox:4053): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:4053): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed
(rhythmbox:4053): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Susana 2008-06-23 20:00: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 537495 ***