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 481162 - crash in Epiphany Web Browser: I've opened link in Epip...
crash in Epiphany Web Browser: I've opened link in Epip...
Status: RESOLVED DUPLICATE of bug 357564
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.20.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-28 05:01 UTC by Jakub 'Livio' Rusinek
Modified: 2007-09-28 11:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Jakub 'Livio' Rusinek 2007-09-28 05:01:10 UTC 
Version: 2.20.0

What were you doing when the application crashed?
I've opened link in Epiphany using Liferea (Epiphany wasn't yet running).

I have F7 with few Rawhide/Development (F8) packages.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Livious

Memory status: size: 87220224 vsize: 87220224 resident: 28012544 share: 16392192 rss: 28012544 rss_rlim: 4294967295
CPU usage: start_time: 1190955454 rtime: 230 utime: 193 stime: 37 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 -1208138016 (LWP 2424)]
[New Thread -1221272688 (LWP 2430)]
[New Thread -1210782832 (LWP 2429)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 166083

Thread 1 (Thread -1208138016 (LWP 2424))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
    from /usr/lib/firefox-2.0.0.6/libgtkembedmoz.so
  • #4 <signal handler called>
  • #5 __kernel_vsyscall
  • #6 raise
    from /lib/libc.so.6
  • #7 abort
    from /lib/libc.so.6
  • #8 g_logv
    from /lib/libglib-2.0.so.0
  • #9 g_log
    from /lib/libglib-2.0.so.0
  • #10 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #12 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #14 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #15 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #16 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /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





          2007-09-28 11:27:32 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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






Comment 2


Reinout van Schouwen





          2007-09-28 11:30:40 UTC
        



Hmm, this looks like a duplicate but the actual D-BUS bug should have been fixed long ago. Could you install debug symbols for d-bus, glib, gtk and epiphany so that you get a better backtrace next time this occurs?
See http://live.gnome.org/GettingTraces for more information on how to do so.