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 383926 - crash in Epiphany Web Bookmarks: Launching Epiphany from ...
crash in Epiphany Web Bookmarks: Launching Epiphany from ...
Status: RESOLVED INVALID
Product: epiphany
Classification: Core
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-12-09 01:48 UTC by rsdundon
Modified: 2006-12-21 00:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description rsdundon 2006-12-09 01:48:09 UTC
Version: 2.16.2

What were you doing when the application crashed?
Launching Epiphany from the command line. Launching from a launcher generates this same error. Arch upgraded Epiphany & gnome-vfs on my system today.


Distribution: Unknown
Gnome Release: 2.16.2 2006-11-22 (Archlinux)
BugBuddy Version: 2.16.0

Memory status: size: 55857152 vsize: 0 resident: 55857152 share: 0 rss: 25149440 rss_rlim: 0
CPU usage: start_time: 1165628349 rtime: 0 utime: 634 stime: 0 cutime:570 cstime: 0 timeout: 64 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 -1240611120 (LWP 1243)]
[New Thread -1247323248 (LWP 1244)]
(no debugging symbols found)
0xb7f8b410 in ?? ()

Comment 1 Reinout van Schouwen 2006-12-09 10:47:45 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

(looks similar to bug 379223, but is it a duplicate?)
Comment 2 rsdundon 2006-12-20 17:17:46 UTC
An Arch dev told me to activate the debug symbols would require me to recompile a bunch a packages. Unfortunately this is beyond my knowledge base ATM.

The Arch devs have rebuilt Epiphany against a newer version of Python (now build against 2.4.4 vs. old of 2.4.3). This does not solve my issue. Epiphany works if epiphany-extensions is not installed. As soon as epiphany-extensions is installed, when I launch Epiphany I get the crash as noted above.

My comments in Arch bug tracker: http://bugs.archlinux.org/task/6029

My thread at the Arch forum: 

http://bbs.archlinux.org/viewtopic.php?t=27648&highlight=
Comment 3 rsdundon 2006-12-20 23:21:42 UTC
UPDATE:

Uninstalled epiphany-extensions, epiphany, and iso-codes. Deleted epiphany folder from within .gnome2. Deleted epiphany folder from .gconf folder. Reboot. Reinstalled epiphany (iso-codes brought back in as a dep). Reinstalled epiphany extensions.

Everything works now (?).

Every extension I have activated (including the java console and favicon fallback) work without crashing epiphany.

Something else I noticed...prior to my complete wipe of every thing epiphany related, when I would install epiphany-extensions the menu item 'Tools' was NOT being created. After my wipe and reinstall, the 'Tools" menu item is present.

I would guess I had some weird problem with my preferences, but I had renamed the .epiphany folder before to force a new, clean, folder to be created. This did not solve the problem.

Not sure what exactly I did, but hopefully this might provide some insight to the issue.

Bob
Comment 4 Reinout van Schouwen 2006-12-21 00:15:11 UTC
Sounds like it's not a problem on our part, then. Thanks! :)