GNOME Bugzilla – Bug 118008
Galeon crashes after changing popup setting
Last modified: 2004-12-22 21:47:04 UTC
Package: galeon Severity: major Version: GNOME2.2.2 2.2.104 os_details: Ximian, Inc. Synopsis: Galeon crashes after changing popup setting Bugzilla-Product: galeon Bugzilla-Component: User interface BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Popup setting was set to not allow from any site. I enabled popups for all sites so that I could receive a popup from a site that I needed to. I went to Web->Popups->Allow (or something like that). Upon clicking the selection, Galeon crashed. The same seems to be true of changing it back. Steps to reproduce the problem: 1. Click on Web 2. Click on Popups 3. Click on Allow from all (or something like that) Actual Results: Galeon crashed. Upon restarting Galeon, the change was indeed made though. Expected Results: Expected Galeon to allow popups and not crash. How often does this happen? Going to test more, but it's happened just about every time I've used the above function (perhaps every time). Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/bug-buddy' (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)...(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)... (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)...(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)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1085532320 (LWP 23099)] [New Thread 1098218800 (LWP 23100)] (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)... (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)...(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)... (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)...0xffffe002 in ?? ()
+ Trace 38918
Thread 1 (Thread 1085532320 (LWP 23099))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-21 14:24 ------- The original reporter (gus@gusalmighty.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, galeon-maint@bugzilla.gnome.org.
*** This bug has been marked as a duplicate of 112794 ***
The description is a duplicate of bug 112794, but the stack trace is a bug-buddy crash and it's a duplicate of bug 118028. I'll simply leave as it is, though.