GNOME Bugzilla – Bug 69774
crash after editing pluggerrc to support fewer mime types
Last modified: 2004-12-22 21:47:04 UTC
Package: galeon Severity: normal Version: 1.1.2 Synopsis: crash after editing pluggerrc to support fewer mime types Bugzilla-Product: galeon Bugzilla-Component: general Description: I edited my /etc/pluggerrc to comment out support for the various audio/*mpeg*url types. After restarting Galeon, "about:plugins" still thinks plugger supports those types. Trying to open an object of one of those types crashes Galeon with the stack trace that Bug Buddy is hopefully attaching. I can't find where Galeon has cached this stale information. Even removing plugger.so, restarting Galeon, replacing it, and restarting Galeon again doesn't refresh the information. This is with galeon 1.1.2-1, mozilla 0.9.7-0, and plugger 3.3-4, all installed on a RH7.2 system from RPMs. (I couldn't get plugger 4.0 to install on my system, though I didn't spend a ton of time trying.) Debugging Information: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 1024 (LWP 13783)] [New Thread 2049 (LWP 13799)] [New Thread 1026 (LWP 13800)] [New Thread 2051 (LWP 13801)] [New Thread 9220 (LWP 13999)] 0x4084ec09 in __wait4 () from /lib/libc.so.6
+ Trace 16865
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-01-26 18:58 ------- Unknown version 1.1.x in product galeon. Setting version to the default, "unspecified". Reassigning to the default owner of the component, yaneti@declera.com.
any reason not to use the latest plugger release ?? *** This bug has been marked as a duplicate of 59361 ***
OK, the crash is plugger crashing; however, there is another bug in my report. (Though I suppose this one is probably a mozilla bug.) To repeat, if I change pluggerrc so that the plugin now supports fewer mime types than before, Galeon doesn't notice that and keeps thinking it supports the old types. Since I filed the bug, I found out that the way to fix this seems to be to delete ~/.mozilla/appreg. (Note that this file is not under ~/.galeon/mozilla as I would have expected, so it took a while to find it.) To answer your question about using the latest version of plugger, plugger 4.0 is a bit hard to install, though of course this is not galeon's fault at all. If I try to install the binary RPM on the plugger web page (which says it's for RH6.2) on RH7.2, rpm tells me it's for the wrong architecture (!). The source RPM won't rebuild because I don't have the Netscape plugin development kit. Fortunately installing by hand from the .tar.gz file works.
thanks for following up with this useful info