David Faure wrote:
> On Fri, Jul 21, 2000 at 01:01:57AM +0200, Udo Weber wrote:
> > Hi,
> > I know KDE2 is Beta but not far from the offical release.
> >
> > Here some experiences and bugs:
> > After the update from a current cooker-version, most things don't works.
> > Especialy dcopserver related bugs.
> >
> > Now I have done a complete new installation from the last mirror
> > snapshot on another partition.
> > I have now no error-messages relating dcop.
> > I think an update from the old KDE should not be recommended for the
> > moment!
> So... the old one works better than the new one ?
> Chris is trying to repackage a newer one (1.92, soon out).
>
> > Somtimes a application crashs (like kcontrol) but most things are stable
> > in the new installation.
> kcontrol ? On exit then, I guess ? This has been fixed.
>
> > There are some things which are should fixed in near future:
> > - the wellknown problem with the kdm (session select).
> Hopefully fixed, waiting for feedback (didn't have time to test yet)
>
> > - always at startup all desktop icons are in the upper left korner
> > arrange icons + safe desktop don't helps
> I fixed this one last Tuesday.
>
> > - where are the nice themes from the old release ? not compatible ?
> They are, with some compatibility code. Not sure what's the status
> of the kcontrol module for selecting them though.
>
> > - no xscreensaver in Screensaver-selection
> ? I thought there was ?
>
> > kpackage is a little bit confusing:
> Hmm, please report to the kpackage author (use the bug report dialog).
> Not many core developers put their hands in kpackage...
>
> --
> David FAURE
> [EMAIL PROTECTED], [EMAIL PROTECTED]
> http://home.clara.net/faure/, http://www.konqueror.org/
> KDE, Making The Future of Computing Available Today
Ok, I will wait for next (1.92) release.
But I found something what should explain my confusing about kpackage:
kpackage belongs now regular to kdeadmin and the old kpackage-rpm is still in
the distribution.
During a new installation, don't know why, but the old package overwrites (
--force ?) the new from KDE2.
This is the reason why I saw a different kapackage as after the update.
So I think this is at first a bug in cooker, that the old one is still there
and overwrites the newer one.
For the crashing new kpackage, I hope this will be fixed in the new release
because it starts and crashs, not possible to debug.
So please if you are consequent, remove the old kpackage, or put it in
contrib, change the install-destination or what ever.
Cu Udo