Bug 351151 – crash on Navigateur Web Epiphany

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 351151 - crash on Navigateur Web Epiphany


Summary:	crash on Navigateur Web Epiphany


Status:	RESOLVED DUPLICATE of bug 357564

Product:	epiphany
Classification:	Core
Component:	General
Version:	2.15.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-13 12:03 UTC by Jean Privat
Modified:	2006-09-26 22:16 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Jean Privat 2006-08-13 12:03:48 UTC

What were you doing when the application crashed?
Just start epiphany form the gnome pannel.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.91 2006-08-08 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 63750144 vsize: 0 resident: 63750144 share: 0 rss: 29421568 rss_rlim: 0
CPU usage: start_time: 1155470700 rtime: 0 utime: 220 stime: 0 cutime:198 cstime: 0 timeout: 22 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227622736 (LWP 15859)]
[New Thread -1246954592 (LWP 15864)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 70359

Thread 1 (Thread -1227622736 (LWP 15859))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 gtk_moz_embed_get_title
from /usr/lib/firefox/libgtkembedmoz.so
#4 <signal handler called>
#5 __kernel_vsyscall
#6 *__GI_raise
from /lib/tls/i686/cmov/libc.so.6
#7 *__GI_abort
from /lib/tls/i686/cmov/libc.so.6
#8 g_logv
from /usr/lib/libglib-2.0.so.0
#9 g_log
from /usr/lib/libglib-2.0.so.0
#10 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#11 dbus_g_proxy_new_for_name
from /usr/lib/libdbus-glib-1.so.2
#12 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#13 dbus_g_proxy_set_interface
from /usr/lib/libdbus-glib-1.so.2
#14 dbus_connection_dispatch
from /usr/lib/libdbus-1.so.2
#15 dbus_server_setup_with_g_main
from /usr/lib/libdbus-glib-1.so.2
#16 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#18 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#19 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#20 main
#0 __kernel_vsyscall

Comment 1 Reinout van Schouwen 2006-08-13 15:36:05 UTC

This might be a dbus problem?

Comment 2 Christian Persch 2006-09-07 11:40:27 UTC


*** This bug has been marked as a duplicate of 348421 ***

Comment 3 Karsten Bräckelmann 2006-09-26 22:16:36 UTC

Actually this is not the same as bug 348421, but as bug 357564. Correcting, so other duplicates won't be closed wrong. Sorry for the noise.


*** This bug has been marked as a duplicate of 357564 ***