On Thu, Aug 19, 2004 at 12:27:58AM +1000, Ben Burton wrote: > > Hi. > > This is quite probably related to the kontact 3.2 / kdelibs 3.3 mix. > If so, it should not block kontact 4:3.2.3-1 from staying in sarge > (since it is expected that kdelibs 4:3.2.3-x will stay in sarge also). > Though the bug presumably came with the kdelibs upgrade (not the kontact > upgrade), so I'm not sure what BTS tag is appropriate in such a scenario. Kontact 3.2.3 works fine here on top of kdelibs 3.3.0. I'm not sure what the problem would be unless KDE wasn't restarted after upgrading to KDE 3.3. Chris
Attachment:
signature.asc
Description: Digital signature