GNOME Bugzilla – Bug 69187
Crash when closing final Galeon Window (clarification)
Last modified: 2004-12-22 21:47:04 UTC
Package: galeon Severity: normal Version: 0.11.3 Synopsis: Crash when closing final Galeon Window (clarification) Bugzilla-Product: galeon Bugzilla-Component: general Description: This is a clarification of a bug I reported a few minutes ago: Procedure to recreate bug is as follows: Start Galeon Click in 'body' part of window (where the web page would be) Press CTRL-W Crash Notes: - My Galeon is set to start on a blank page. - If you don't click on the window, it exits properly and doesn't crash - If you press CTRL-Q instead of CTRL-W, it exits properly and doesn't crash - If you select File/Close or File/Quit, it exits properly and doesn't crash - It is 100% consistent (on my machine - I don't have another rh7.2 installation to try it on) Debugging Information: (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 1024 (LWP 27145)] [New Thread 2049 (LWP 27156)] 0x40857669 in __wait4 () from /lib/i686/libc.so.6
+ Trace 16494
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-01-20 11:02 ------- The original reporter (steve@ellismansion.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, yaneti@declera.com.
*** This bug has been marked as a duplicate of 69186 ***