Bug 541302 – 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 541302 - 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-02 19:35 UTC by nethunter+gnome
Modified:	2008-07-02 20:39 UTC

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

Description nethunter+gnome 2008-07-02 19:35:31 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.25-NetHunt #19 SMP Sat Jun 14 15:09:38 IDT 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Aurora
Icon Theme: Discovery

Memory status: size: 744042496 vsize: 744042496 resident: 147980288 share: 36962304 rss: 147980288 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214932034 rtime: 11401 utime: 10293 stime: 1108 cutime:24639 cstime: 1464 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 0x7fcdefc62780 (LWP 4768)]
[New Thread 0x41183950 (LWP 29455)]
[New Thread 0x43244950 (LWP 5069)]
[New Thread 0x44246950 (LWP 4793)]
[New Thread 0x43a45950 (LWP 4792)]
[New Thread 0x42242950 (LWP 4770)]
(no debugging symbols found)
0x00007fcde819bedf in waitpid () from /lib/libpthread.so.0

+ Trace 201930

Thread 1 (Thread 0x7fcdefc62780 (LWP 4768))

#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_call
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 (83205 sec old) ---------------------
Cannot index Thunderbird contacts because a System.ArgumentNullException was thrown: Argument cannot be null.
Parameter name: path
** Message: Auto-retrying the connection
** Message: New connection device is 00:19:79:CE:88:7C (not changed)
** Message: New connection device is 00:19:79:CE:88:7C (not changed)
** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
** Message: Using serial channel -1 for device 00:19:79:CE:88:7C
** Message: Failed connection to device on 00:19:79:CE:88:7C
** Message: Exiting connect thread
** Message: Auto-retrying the connection
** Message: New connection device is 00:19:79:CE:88:7C (not changed)
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Reinout van Schouwen 2008-07-02 20:39:43 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 ***