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 377668 - crash in Epiphany Web Browser: epiphany -n process 1112...
crash in Epiphany Web Browser: epiphany -n process 1112...
Status: RESOLVED DUPLICATE of bug 358007
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-21 07:05 UTC by Baybal Ni
Modified: 2006-11-21 08:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Baybal Ni 2006-11-21 07:05:03 UTC
Version: 2.16.1

What were you doing when the application crashed?
epiphany -n
process 11122: Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application.
  D-Bus not built with -rdynamic so unable to print a backtrace


Distribution: Gentoo Base System version 1.13.0_alpha7
Gnome Release: 2.16.1 2006-11-10 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 23359488 vsize: 0 resident: 23359488 share: 0 rss: 8568832 rss_rlim: 0
CPU usage: start_time: 1162168051 rtime: 0 utime: 6 stime: 0 cutime:5 cstime: 0 timeout: 1 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)
`system-supplied DSO at 0xb7fca000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228031312 (LWP 11122)]
0xb7fca410 in __kernel_vsyscall ()

Thread 1 (Thread -1228031312 (LWP 11122))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_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 /usr/lib/libdbus-1.so.3
  • #8 dbus_watch_handle
    from /usr/lib/libdbus-1.so.3
  • #9 dbus_connection_close
    from /usr/lib/libdbus-1.so.3
  • #10 ephy_dbus_get_proxy
  • #11 ephy_dbus_get_proxy
  • #12 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #13 _ephy_dbus_release
  • #14 main
  • #0 __kernel_vsyscall

Comment 1 Baybal Ni 2006-11-21 07:42:23 UTC
dbus1
Comment 2 Diego Escalante Urrelo (not reading bugmail) 2006-11-21 07:45:49 UTC
Isn't this related/the same as the bug Wouter fixed some weeks ago (the dbus connection closing thing).
Comment 3 Baybal Ni 2006-11-21 07:56:06 UTC
link?
Comment 4 Diego Escalante Urrelo (not reading bugmail) 2006-11-21 08:10:37 UTC
See #358007
Comment 5 Baybal Ni 2006-11-21 08:42:27 UTC

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