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 421343 - crash in Epiphany Web Bookmarks: trying to connect ti a j...
crash in Epiphany Web Bookmarks: trying to connect ti a j...
Status: RESOLVED DUPLICATE of bug 349051
Product: epiphany
Classification: Core
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2007-03-22 04:48 UTC by Gerard
Modified: 2007-03-22 23:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Gerard 2007-03-22 04:48:00 UTC 
Version: 2.16.1

What were you doing when the application crashed?
trying to connect ti a jberry site


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: -2004975616 vsize: -2004975616 resident: 62930944 share: 31768576 rss: 62930944 rss_rlim: -1
CPU usage: start_time: 1174538645 rtime: 432 utime: 387 stime: 45 cutime:0 cstime: 1 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 47467788922032 (LWP 7037)]
[New Thread 1149274448 (LWP 7103)]
[New Thread 1140881744 (LWP 7102)]
[New Thread 1132489040 (LWP 7082)]
[New Thread 1098918224 (LWP 7081)]
[New Thread 1124096336 (LWP 7078)]
[New Thread 1115703632 (LWP 7077)]
[New Thread 1090525520 (LWP 7041)]
[New Thread 1082132816 (LWP 7040)]
(no debugging symbols found)
0x00002b2beeb395cf in waitpid () from /lib/libc.so.6

+ Trace 121018







Comment 1


Reinout van Schouwen





          2007-03-22 23:23:39 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 349051 ***