Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 598280 - Crash at program startup
Summary: Crash at program startup
Status: CLOSED DUPLICATE of bug 577103
Alias: None
Product: Fedora
Classification: Fedora
Component: galeon
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Yanko Kaneti
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-01 01:22 UTC by wmccroskey
Modified: 2010-06-02 06:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-06-02 06:52:55 UTC

Attachments (Terms of Use)

Description wmccroskey 2010-06-01 01:22:03 UTC
Description of problem:

Version-Release number of selected component (if applicable):
Fedora 13 64-bit

How reproducible:
Start program

Steps to Reproduce:
1. run galeon
Actual results:
(galeon:4443): Gtk-WARNING **: Error loading theme icon 'stock_connect' for stock: Icon 'stock_connect' not present in theme

(galeon:4443): Gtk-WARNING **: Error loading theme icon 'stock_connect' for stock: Icon 'stock_connect' not present in theme
Segmentation fault (core dumped)

Expected results:
browser should have started

Additional info:

Comment 1 wmccroskey 2010-06-01 01:23:45 UTC
Don't see the directories for any of the stock_connect icons present on the machine.  Did something get missed on packaging?  All required packages appear to be installed and up to date.

Comment 2 Yanko Kaneti 2010-06-01 04:12:53 UTC
Please try removing ~/.galeon/mozilla/galeon/compreg.dat to work around the crash.

Comment 3 wmccroskey 2010-06-01 22:03:19 UTC
That fixed the crash, the program starts, but if you start it from the command line, you still get the Gtk-WARNING.

Thanks for the help!

Comment 4 Yanko Kaneti 2010-06-02 06:52:55 UTC
Thanks for the followup

*** This bug has been marked as a duplicate of bug 577103 ***

Note You need to log in before you can comment on or make changes to this bug.