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 341379 - Crash on startup
Crash on startup
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: General
2.14.x
Other All
: Normal critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-05-11 07:23 UTC by Dimitur Kirov
Modified: 2006-05-11 11:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
this should fix it (1.96 KB, patch)
2006-05-11 11:53 UTC, Christian Persch 		committed Details | Review

Description Dimitur Kirov 2006-05-11 07:23:01 UTC 
Steps to reproduce:
1. start epihany-2.14.1 on DLG
2. 
3. 


Stack trace:
(gdb) run
Starting program: /usr/bin/epiphany
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223977280 (LWP 11456)]
[New Thread -1233986640 (LWP 11461)]

** ERROR **: file ephy-bookmarks.c: line 909 (browse_cb): assertion failed:
(node != NULL)
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1223977280 (LWP 11456)]
0x452b4027 in raise () from /lib/tls/libc.so.6
(gdb) thread apply all bt

+ Trace 68161



Other information:
Comment 1 Dimitur Kirov 2006-05-11 07:29:14 UTC 
/apps/epiphany/lockdown/disable_bookmark_editing was false. When I set it to true epiphany starts normally.
Comment 2 Christian Persch 2006-05-11 11:53:37 UTC 
Created attachment 65233 [details] [review]
this should fix it
Comment 3 Christian Persch 2006-05-11 11:54:25 UTC 
Fixed in CVS. The fix will go into the next patch release. Thank you for your bug report.
Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.