Bug#321102: data-loss still possible with kmail 3.5.2

On Tuesday 16 May 2006 11:03, Christopher Martin wrote: > Perhaps a better solution would be disable dimap support in the 3.5.3 > upload, and make sure that the fixed package makes Etch (which is > looming). Daniel, what do you feel about this? Given that upstream > appears to be unable to replicat

Processed: Fwd: Re: Catastrophe! - Print to File (PDF)

Processing commands for [EMAIL PROTECTED]: > tag 356138 - unreproducible moreinfo Bug#356138: Catastrophe! - Print to File (PDF) Tags were: moreinfo unreproducible Tags removed: unreproducible, moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug trac

Bug#356138: Catastrophe! - Print to File (PDF)

On Monday 15 May 2006 22:56, Pierre Habouzit wrote: > > Can you confirm you can print groklaw? > > yes I do, now I have a reproducible bug, I'll forward it upstream. Thanks, There seem to be some upstream bug reports along the same lines: http://bugs.kde.org/show_bug.cgi?id=114592 http://bugs.kd

Bug#302793: marked as done (konquest: typo in help)

Your message dated Tue, 16 May 2006 22:30:22 +0200 with message-id <[EMAIL PROTECTED]> and subject line konquest: typo in help has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibil

Processed: forward 302163

Processing commands for [EMAIL PROTECTED]: > package kshisen Ignoring bugs not assigned to: kshisen > retitle 302163 kshisen : hint displayed forever Bug#302163: shisen.app: When starting a new game, hint is still displayed, on new board Changed Bug title. > forwarded 302163 http://bugs.kde.org

Bug#367528: kdebase: System Crash on Start new Session

Package: kdebase Version: 4:3.5.2-2 Severity: normal Hi, I tried to start a new KDE-Session via K-Menu "Change User" (or what ever it reads in english) -> Start new Session. I expected to get a new login screen on VT10 (KDE is on 7 and console-log on 8 and 9) but what I got was a complete crash

Processed: Re: Bug#321102: data-loss still possible with kmail 3.5.2

Processing commands for [EMAIL PROTECTED]: > found 321102 4:3.5.2-1 Bug#321102: kmail looses mails Bug#332473: kmail: dangerous handling of dimap-folders Bug#350851: kmail: v1.9.1: Data loss w/disconnected IMAP (reported upstream) Bug marked as found in version 4:3.5.2-1. > found 332473 4:3.5.2-1

Bug#321102: data-loss still possible with kmail 3.5.2

found 321102 4:3.5.2-1 found 332473 4:3.5.2-1 found 350851 4:3.5.2-1 stop On Tuesday 16 May 2006 10:05, Bastian Venthur wrote: > So here it is, someone confirmed this bug with 3.5.2 on Debian: > > http://bugs.kde.org/show_bug.cgi?id=104956 > > Quote: > > "Bam! I had this bug right now. Using

Bug#357043: Attached valgrind report shows leaking

Package: korganizer Version: 4:3.3.2-3 Followup-For: Bug #357043 The attached valgrind report shows korgac -- System Information: Debian Release: 3.1 APT prefers stable APT policy: (500, 'stable'), (100, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Lin

Bug#365689: korganizer: Korganizer crash when adding new event.

Package: korganizer Version: 4:3.5.2-1+b2 Followup-For: Bug #365689 Same problem here. I attach the console output of Korganizer. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (100, 'unstable') Architecture: i386 (i686) Shell: /bin/

Bug#321102: data-loss still possible with kmail 3.5.2

So here it is, someone confirmed this bug with 3.5.2 on Debian: http://bugs.kde.org/show_bug.cgi?id=104956 Quote: "Bam! I had this bug right now. Using KDE 3.5.2 on Debian. Lost a whole folder of mails (thank god it was only a ML). Nevertheless this is totally uncool..." Whoever marked