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 549656 - crash in Epiphany Web Bookmarks: closing epiphany
crash in Epiphany Web Bookmarks: closing epiphany
Status: RESOLVED DUPLICATE of bug 509083
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.22.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-28 00:01 UTC by secretagentbo-bug
Modified: 2008-08-28 12:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description secretagentbo-bug 2008-08-28 00:01:38 UTC
Version: 2.22.3

What were you doing when the application crashed?
closing epiphany


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-custom #1 Tue Jul 22 02:49:26 CEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Moomex
Icon Theme: black-white_2-Gloss

Memory status: size: 95772672 vsize: 95772672 resident: 39153664 share: 22589440 rss: 39153664 rss_rlim: 4294967295
CPU usage: start_time: 1219881122 rtime: 722 utime: 638 stime: 84 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6a46700 (LWP 26202)]
0xb7f0c424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6a46700 (LWP 26202))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.4/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.4/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #6 <signal handler called>
  • #7 NS_HasPendingEvents_P
    at nsThreadUtils.cpp line 209
  • #8 nsBaseAppShell::OnProcessNextEvent
    at nsBaseAppShell.cpp line 288
  • #9 nsThread::ProcessNextEvent
    at nsThread.cpp line 497
  • #10 NS_ProcessPendingEvents_P
    at nsThreadUtils.cpp line 181
  • #11 nsBaseAppShell::NativeEventCallback
    at nsBaseAppShell.cpp line 121
  • #12 nsAppShell::EventProcessorCallback
    at nsAppShell.cpp line 69
  • #13 g_io_unix_dispatch
  • #14 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.4/glib/gmain.c line 2012
  • #15 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.4/glib/gmain.c line 2645
  • #16 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.4/glib/gmain.c line 2853
  • #17 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.11/gtk/gtkmain.c line 1163
  • #18 main
    at /build/buildd/epiphany-browser-2.22.3/src/ephy-main.c line 744
  • #0 __kernel_vsyscall


----------- .xsession-errors (184699 sec old) ---------------------
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
Network timeout occured. Cancel active operations.
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Reinout van Schouwen 2008-08-28 12:11:07 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 509083 ***