Bug 546523 – crash in Epiphany Web Browser: Estaba descargando un fi...

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 546523 - crash in Epiphany Web Browser: Estaba descargando un fi...


Summary:	crash in Epiphany Web Browser: Estaba descargando un fi...


Status:	RESOLVED DUPLICATE of bug 536768

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-08-06 06:42 UTC by aneolf
Modified:	2008-08-06 08:04 UTC

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

Description aneolf 2008-08-06 06:42:09 UTC

Version: 2.22.3

What were you doing when the application crashed?
Estaba descargando un fichero .pdf


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 606416896 vsize: 606416896 resident: 101601280 share: 32186368 rss: 101601280 rss_rlim: 18446744073709551615
CPU usage: start_time: 1218003713 rtime: 7517 utime: 7066 stime: 451 cutime:10 cstime: 7 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 0x7fcdcf5d2780 (LWP 3732)]
[New Thread 0x43685950 (LWP 3741)]
[New Thread 0x42e84950 (LWP 3739)]
[New Thread 0x41e82950 (LWP 3738)]
[New Thread 0x42683950 (LWP 3737)]
[New Thread 0x41251950 (LWP 3733)]
(no debugging symbols found)
0x00007fcdc7b5fedf in waitpid () from /lib/libpthread.so.0

+ Trace 204689

Thread 1 (Thread 0x7fcdcf5d2780 (LWP 3732))

#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 ??
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#11 ??
from /usr/lib/libglib-2.0.so.0
#12 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#13 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#14 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (32 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)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
--------------------------------------------------

Comment 1 Reinout van Schouwen 2008-08-06 08:04:19 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 ***