On Fri, Nov 21, 2003 at 05:30:25PM -0700, Thanasis Kinias wrote: > Greetings all, > > I don't know if this has to do with the Debian security situation, but > the three Sarge boxes I apt-get updated yesterday all now have broken > Galeons. Galeon refuses to execute, claiming that it can't find a gconf > schema. I followed the instructions in the Galeon FAQ, but there are no > gconfd processes running, nor any lockfiles to delete. It seems that > the gconf2 I pulled from testing yesterday broke Galeon. I couldn't get > any help on #debian, and I'm a bit surprised no one has yet commented on > this on d-u. Is this a problem that others have encountered? If not, > what might I do to troubleshoot this? > > (Note that this occurs both with $HOME on local disk and with > AFS-mounted $HOME...) > > It doesn't seem worthwhile to file a bug on this, since Sarge will have > Galeon 1.3 on release... >
I first noticed a problem with galeon in sarge several days *before* the security situation. It started showing up in aptitude under the category "Obsolete and Locally Created Packages". Since I know it is surely not locally created here, I take this to be part of an orderly transition to a newer version which is suppose is in progress. I did, at the time, research the versions of galeon on google. I found that there is/was a controversy about future direction of galeon within the galeon developer community. The new galeon may be substantially different in look and feel. And then again, I may be mistaken. HTH -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
