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 370798 - crash in Epiphany Web Browser: running a new browser
crash in Epiphany Web Browser: running a new browser
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-11-05 00:20 UTC by Kenneth Topp
Modified: 2006-11-17 16:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Kenneth Topp 2006-11-05 00:20:13 UTC
Version: 2.16.1

What were you doing when the application crashed?
running a new browser


Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.16.1 2006-10-21 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled
----------- .xsession-errors (6 sec old) ---------------------
  /lib/libdbus-1.so.3 [0x55d627]
  /lib/libdbus-1.so.3 [0x551ae6]
  /lib/libdbus-1.so.3(dbus_connection_close+0x1a1) [0x52f481]
  epiphany [0x808280d]
  epiphany [0x808288e]
  /lib/libgobject-2.0.so.0(g_object_unref+0x16c) [0x62a1ac]
  epiphany(_ephy_dbus_release+0x24) [0x8081d14]
  epiphany(main+0xbd9) [0x80819e9]
  /lib/libc.so.6(__libc_start_main+0xdc) [0x35be5c]
  epiphany [0x8080b01]
** (bug-buddy:19195): WARNING **: Couldn't load icon for Open Folder
Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &
Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &
Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &
--------------------------------------------------

Memory status: size: 28823552 vsize: 0 resident: 28823552 share: 0 rss: 8417280 rss_rlim: 0
CPU usage: start_time: 1162685993 rtime: 0 utime: 6 stime: 0 cutime:4 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

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

(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 -1208334080 (LWP 19322)]
(no debugging symbols found)
0x00a7f402 in __kernel_vsyscall ()

Thread 1 (Thread -1208334080 (LWP 19322))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 dbus_malloc
    from /lib/libdbus-1.so.3
  • #8 dbus_watch_set_data
    from /lib/libdbus-1.so.3
  • #9 dbus_connection_close
    from /lib/libdbus-1.so.3
  • #10 ephy_dbus_get_proxy
  • #11 ephy_dbus_get_proxy
  • #12 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #13 _ephy_dbus_release
  • #14 main
  • #0 __kernel_vsyscall

Comment 1 Diego Escalante Urrelo (not reading bugmail) 2006-11-07 00:46:14 UTC
Dbus fault?
Comment 2 Dimitur Kirov 2006-11-16 08:06:31 UTC
I have this too. It happens to me when I close epiphany, so it is not a big deal.

Without `dbus_connection_close` call everything is fine!

See http://www.j5live.com/?p=264
Comment 3 Dimitur Kirov 2006-11-17 10:45:49 UTC
Seems to be fixed in 2.17.2 . Is there any chance that we get a 2.16.X without this bug ?
Comment 4 Wouter Bolsterlee (uws) 2006-11-17 16:27:20 UTC
It should be backported to the stable branch.