4)printerdrake today refused to see remote printers (though it worked 
fine with this late last week on up-to-date cooker)

Same probleme for me :/

Le jeu 18/09/2003 � 01:00, [EMAIL PROTECTED] a �crit :
> >> On Wed, 2003-09-17 at 21:54, [EMAIL PROTECTED] wrote:
> >> > > Hi
> >> > >
> >> > if you ask cooker , i think the answer is "We need a RC3"
> >> > but Mandrakesoft ?
> >>
> >> You think? I see no need for one.
> >
> > me thinks, as i said :-)
> 
> Instead of telling we need one, how about telling us why?
> 
> >
> > but obviously (me thinks wrong)
> > and there are people who belive MDK-9.2 is ready :)
> >
> 
> On the hardware I have been using, rc2 plus updates from cooker (including
> the latest kernel which fixed the problem rebooting with a pcmcia NIC for
> me) is pretty solid.
> 
> But, there are some minor problems I have still:
> 
> 1)drakconnect kills connections via PCMCIA NICs when "restarting"
> 2)konqueror in double-click and detailed view still doesn't respect the
> double-click setting (but the file-open dialog does as does icon view in
> konqueror)
> 3)recently discussed mdkkdm issue with missing boot options needs to be fixed
> 4)printerdrake today refused to see remote printers (though it worked fine
> with this late last week on up-to-date cooker)
> 5)winbind in install seems broken still
> 6)pcmcia needs an update (and I would personally like to see the patch I
> provided applied - and I think we are going to see breakage from more
> ne2000 compatible pcmcia NICs)
> 7)lisa needs to be updated with the init script in bugzilla
> 8)drakauth needs to set nscd to start for NIS and LDAP (to fix missing
> kdesktop)
> 9)setsysfont segfaulting
> 
> Maybe we should have a summary of the really important (non-hardware) bugs
> (preferably with bug numbers) to see if we can have a final stab at fixing
> them?
> 
> Regards,
> Buchan
> 
> 
> *****************************************************************
> Please click on http://www.cae.co.za/disclaimer.htm to read our
> e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
> *****************************************************************
> 


Reply via email to