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 562118 - crash in Epiphany Web Bookmarks: Habe zweimal auf einen L...
crash in Epiphany Web Bookmarks: Habe zweimal auf einen L...
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-11-24 13:16 UTC by oliver
Modified: 2008-11-24 20:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description oliver 2008-11-24 13:16:49 UTC 
Version: 2.22.3

What were you doing when the application crashed?
Habe zweimal auf einen Link, der auf dem Desktop lag, gecklickt.
Dann das oberste Dokument angeschaut und ein bischen runter gescrollt, dann mit STRG-W das erste und danach auch das zweite Dokument geschlossen.

Der Fehler ist bei mir reproduzierbar... hatte erst keinen Fehlerbericht geschickt (Bug-Buddy beendet) und dann nochmal das gleiche Vorgehen getätigt und es wurde erneut dieser Fehlerbericht-Bug-Buddy gestartet.



Inhalt des Links mit vim angeschaut:

===================================================
[Desktop Entry]
Version=1.0
Encoding=UTF-8
Name=Verknüpfung mit IT-Management: Die 14 häufigsten Projektfehler vermeiden - computerwoche.de
Type=Link
URL=http://www.computerwoche.de/knowledge_center/it_strategie/1869524/?otc-gulp
Icon=gnome-fs-bookmark
===================================================



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

System: Linux 2.6.26-1-amd64 #1 SMP Sat Nov 8 18:25:23 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 459603968 vsize: 459603968 resident: 60338176 share: 27324416 rss: 60338176 rss_rlim: 18446744073709551615
CPU usage: start_time: 1227532231 rtime: 338 utime: 314 stime: 24 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 0x7feac94ee780 (LWP 4041)]
[New Thread 0x44cac950 (LWP 4052)]
0x00007feac229e5ef in waitpid () from /lib/libpthread.so.0

+ Trace 210179

Thread 1 (Thread 0x7feac94ee780 (LWP 4041))

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


----------- .xsession-errors (11 sec old) ---------------------
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
--------------------------------------------------
Comment 1 palfrey 2008-11-24 20:01:43 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 ***