GNOME Bugzilla – Bug 66578
Tried to start Galeon up , and got nothing but a 'crashed' notice...
Last modified: 2004-12-22 21:47:04 UTC
Package: galeon Severity: major Version: 0.11.0 Synopsis: Tried to start Galeon up , and got nothing but a 'crashed' notice... Bugzilla-Product: galeon Bugzilla-Component: general Description: Don't now, when I started Galeon, all I got was this ' the application has crashed' notice on my screen, seemingly due to a segmentation fault 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)... [New Thread 1024 (LWP 571)] [New Thread 2049 (LWP 579)] [New Thread 1026 (LWP 580)] [New Thread 2051 (LWP 581)] [New Thread 3076 (LWP 583)] 0x407e3689 in __wait4 () from /lib/libc.so.6
+ Trace 14839
------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-12-09 15:20 ------- The original reporter (han@linuxhan.bouwstr.home) 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 66373 ***