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 147289 - Galeon crashes when going into preferences
Galeon crashes when going into preferences
Status: RESOLVED DUPLICATE of bug 129741
Product: galeon
Classification: Deprecated
Component: User interface
1.3.15
Other other
: Normal normal
: ---
Assigned To: galeon-maint
galeon-maint
Depends on:
Blocks:
 
 
Reported: 2004-07-10 17:05 UTC by greve
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description greve 2004-07-10 17:05:52 UTC
Distribution: Debian testing/unstable
Package: galeon
Severity: normal
Version: GNOME2.6.1 1.3.15
Gnome-Distributor: Debian
Synopsis: Galeon crashes when going into preferences
Bugzilla-Product: galeon
Bugzilla-Component: User interface
Bugzilla-Version: 1.3.15
BugBuddy-GnomeVersion: 2.0 (2.6.1.1)
Description:
Description of the crash:

When selecting preferences, sometimes also while changing preferences,
Galeon crashes with "The Application 'galeon-bin' has quit
unexpectedly."

Steps to reproduce the crash:
1. Select preferences --OR-- edit preferences
2. 
3. 

Expected Results:


How often does this happen?

Does not happen every time, only every 5th time or so

Additional Information:




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-10 13:05 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "galeon".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was greve@gnuhh.org.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Yanko Kaneti 2004-07-10 17:48:53 UTC

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