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 407547 - crash in Epiphany Web Bookmarks: trying to start it
crash in Epiphany Web Bookmarks: trying to start it
Status: RESOLVED DUPLICATE of bug 404514
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-02-13 17:53 UTC by starcycle
Modified: 2007-02-14 11:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description starcycle 2007-02-13 17:53:26 UTC 
Version: 2.16.3

What were you doing when the application crashed?
trying to start it


Distribution: Unknown
Gnome Release: 2.16.3 2007-02-01 (Archlinux)
BugBuddy Version: 2.16.1

System: Linux 2.6.19-ARCH #1 SMP PREEMPT Thu Jan 11 20:08:17 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 54104064 vsize: 0 resident: 54104064 share: 0 rss: 23240704 rss_rlim: 0
CPU usage: start_time: 1171389188 rtime: 0 utime: 54 stime: 0 cutime:48 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/gnome/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 -1240725280 (LWP 21165)]
[New Thread -1247487088 (LWP 21170)]
(no debugging symbols found)
0xb7f84410 in ?? ()

+ Trace 110436







Comment 1


Reinout van Schouwen





          2007-02-13 23:10:24 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 404514 ***






Comment 2


starcycle





          2007-02-14 00:18:07 UTC
        



problem resolved for me with a restart of the dbus and hal systems and flushing of a stale /var/run/dbus.pid. 






Comment 3


Reinout van Schouwen





          2007-02-14 11:20:00 UTC
        



Please add additional comments to bug 404514, of which this bug is a duiplicate. Thanks!