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 385171 - crash in Epiphany Web Bookmarks:
crash in Epiphany Web Bookmarks:
Status: RESOLVED DUPLICATE of bug 356632
Product: epiphany
Classification: Core
Component: General
2.17.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-12-12 19:44 UTC by alovell
Modified: 2006-12-13 17:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description alovell 2006-12-12 19:44:06 UTC 
Version: 2.17.2

What were you doing when the application crashed?



Distribution: Mandrakelinux release 10.2 (Limited Edition 2005) for i586
Gnome Release: 2.16.1 2006-10-08 (GNOME.Org)
BugBuddy Version: 2.16.0

Memory status: size: 139767808 vsize: 0 resident: 139767808 share: 0 rss: 55922688 rss_rlim: 0
CPU usage: start_time: 1165952177 rtime: 0 utime: 5208 stime: 0 cutime:4940 cstime: 0 timeout: 268 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228527952 (LWP 11817)]
[New Thread -1303753824 (LWP 11991)]
[Thread debugging using libthread_db enabled]
[New Thread -1228527952 (LWP 11817)]
[New Thread -1303753824 (LWP 11991)]
[Thread debugging using libthread_db enabled]
[New Thread -1228527952 (LWP 11817)]
[New Thread -1303753824 (LWP 11991)]
[New Thread -1260696672 (LWP 11847)]
[New Thread -1241404512 (LWP 11841)]
0xb7f1f410 in ?? ()

+ Trace 93624

Thread 4 (Thread -1241404512 (LWP 11841))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 loser_poll
    at ../sysdeps/unix/sysv/linux/poll.c line 48 






Comment 1


palfrey





          2006-12-13 17:56:47 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 356632 ***