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 592482 - crash in Epiphany Web Bookmarks: I've just closed Epiphan...
crash in Epiphany Web Bookmarks: I've just closed Epiphan...
Status: RESOLVED DUPLICATE of bug 509083
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.26.x
Other All
: Normal critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-08-20 17:15 UTC by v.merlin
Modified: 2009-08-22 03:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description v.merlin 2009-08-20 17:15:37 UTC 
Version: 2.26.1

What were you doing when the application crashed?
I've just closed Epiphany only


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.26.0

System: Linux 2.6.30-1-amd64 #1 SMP Mon Aug 3 12:28:22 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Litoral
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module, gail, atk-bridge

Memory status: size: 534933504 vsize: 534933504 resident: 60887040 share: 32690176 rss: 60887040 rss_rlim: 18446744073709551615
CPU usage: start_time: 1250788406 rtime: 608 utime: 537 stime: 71 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7fad04d037d0 (LWP 13778)]
0x00007fad013c928f in __libc_waitpid (pid=13788, stat_loc=0x7fffe031d990, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 217044

Thread 1 (Thread 0x7fad04d037d0 (LWP 13778))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.20.4/glib/gspawn.c line 382
  • #2 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.20.4/glib/gspawn.c line 694
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #5 <signal handler called>
  • #6 ??
  • #7 NS_HasPendingEvents_P
    at nsThreadUtils.cpp line 194
  • #8 nsBaseAppShell::OnProcessNextEvent
    at nsBaseAppShell.cpp line 288
  • #9 nsThread::ProcessNextEvent
    at nsThread.cpp line 497
  • #10 NS_ProcessPendingEvents_P
    at nsThreadUtils.cpp line 180
  • #11 nsBaseAppShell::NativeEventCallback
    at nsBaseAppShell.cpp line 121
  • #12 nsAppShell::EventProcessorCallback
    at nsAppShell.cpp line 69
  • #13 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.20.4/glib/gmain.c line 1824
  • #14 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.20.4/glib/gmain.c line 2455
  • #15 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.20.4/glib/gmain.c line 2663
  • #16 IA__gtk_main
    at /tmp/buildd/gtk+2.0-2.16.5/gtk/gtkmain.c line 1205
  • #17 main
    at /scratch/build-area/epiphany-browser-2.26.1/src/ephy-main.c line 751 


----------- .xsession-errors ---------------------
(operapluginwrapper-native:13545): Gdk-WARNING **: XID collision, trouble ahead
(operapluginwrapper-native:13545): Gdk-WARNING **: XID collision, trouble ahead
(operapluginwrapper-native:13545): Gdk-WARNING **: XID collision, trouble ahead
(operapluginwrapper-native:13545): Gdk-WARNING **: XID collision, trouble ahead
(operapluginwrapper-native:13545): Gdk-WARNING **: XID collision, trouble ahead
(operapluginwrapper-native:13545): Gdk-WARNING **: XID collision, trouble ahead
(operapluginwrapper-native:13545): Gdk-WARNING **: XID collision, trouble ahead
41	../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-08-22 03:23:45 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 bug 509083 ***