[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#321102: Bug#350851 & Bug#321102: KMail data loss still not fixed



> close 350851 4:3.5.5-1
> thanks
>
> Hi Bastian,
>
> On Mon, Jan 08, 2007 at 10:12:17PM +0100, Bastian Venthur wrote:
> > reopen 350851
> > thanks
> >
> > Hi,
> >
> > I know this mail sucks (like this whole bug) but looking at the relevant
> > KDE bugreport, I really doubt that this bug is fixed.
> >
> >   http://bugs.kde.org/show_bug.cgi?id=104956
> >
> > I'm not using KMail anymore so I can't give any first hand information,
> > but I'm still following the relevant KDE bugreports and It simply looks
> > like this bug is not fixed.
> >
> > Why was it closed anyway? Looks like upstreams bugreport is still open
> > too.
>
> So, you do not use kmail anymore, go to the kde bugzilla and see people
> is still suffering this bug in kubuntu and decide to re-open this bug
> in the Debian BTS?
>
> The commit that should fix this bug was not committed before the kde3.5.5
> release, so only distributions that have hand-picked the fix from svn had
> it included.
> It is 'closed' in kde bugzilla. 'Verified' is the 'step' after 'fixed'
> in bugzilla wordings. Verified that it is fixed). Don't mix it with
> 'confirmed' which is a confirmation that the bug exists.
>
>
> Ana

Ana,

If you check the latest reports on KDE #104956, you'll see that Christian 
Maluck reports mail loss with the 1.9.5 version in Kubuntu, which checking 
the changelog reveals to have the patch that is merged upstream in 3.5.5, 
which means it has the same patch that Debian has.

Clearly, regardless of the upstream bug tracker's "status" field (which I and 
others would change but are unable to), this bug is not solved.  I just 
experienced it myself a short time ago, and others are also experiencing it.  
Why don't you just reopen this bug, rather than asking me to open an entirely 
new bug and throwing away the logs associated with this one?

This is a severely damaging bug resulting in mail loss both locally and on the 
server.  Please reopen it until it is truly fixed.

Adam Porter

Attachment: pgp_8QCueQvGU.pgp
Description: PGP signature


Reply to: