Bug#284853: acknowledged by developer (Should now work)

2006-05-11 Thread Ronny Standtke
Thanks a lot, works now for me too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#365348: Kmail: IMAP-SSL borkage

2006-05-11 Thread Slaven
If your mail server uses imap4 protocol, you need to install kdepim-kio-plugins package, as well. I had a similar problem and installing this package fixed things for me. Good luck, Slaven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PR

Re: Bug#365348: Kmail: IMAP-SSL borkage

2006-05-11 Thread Alver
On Friday 12 May 2006 00:37, Slaven wrote: > If your mail server uses imap4 protocol, you need to install > kdepim-kio-plugins package, as well. I had a similar problem and > installing this package fixed things for me. Good luck, > Slaven I have the package installed - I actually have every packa

Bug#335929: kolf: now runs fine on powerpc

2006-05-11 Thread Frank Gevaerts
Package: kolf Version: 4:3.5.2-1+b2 Followup-For: Bug #335929 kolf now runs fine. The bug can probably be closed. Frank -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/s

Bug#365348: Kmail: IMAP-SSL borkage

2006-05-11 Thread Alver
According to the kdepim people, sasl *is* still used for imap-ssl in kmail; apparently libsasl2-modules should suffice. Currently installed sasl-related packages: ii libauthen-sasl-cyrus-perl 0.13-server-1 ii libauthen-sasl-perl 2.10-1 ii libgsasl7

Bug#191355: marked as done (text selection in kghostview just as in xpdf)

2006-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 May 2006 17:14:34 +0200 with message-id <[EMAIL PROTECTED]> and subject line text selection in kghostview just as in xpdf 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 i

Re: Bug#309765: acknowledged by developer (Re: no explanation)

2006-05-11 Thread Christopher Martin
On Thursday 11 May 2006 07:48, Guido Guenther wrote: > On Thu, May 11, 2006 at 03:33:14AM -0700, Debian Bug Tracking System wrote: > > On Thu, May 11, 2006 at 08:33:41AM +0200, Guido Guenther wrote: > > > Hi, > > > could you please explain, why you closed this bug? > > > Cheers, > > > -- Guido >

Bug#188295: marked as done (kmail: display of gpg key userid borken for unicode userids)

2006-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 May 2006 17:12:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line kmail: display of gpg key userid borken for unicode userids 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 no

Bug#185219: marked as done ((no subject))

2006-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 May 2006 17:07:54 +0200 with message-id <[EMAIL PROTECTED]> and subject line your mail 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 responsibility to reopen

Bug#184084: marked as done (libqt3-compat-headers as dependency)

2006-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 May 2006 17:06:01 +0200 with message-id <[EMAIL PROTECTED]> and subject line libqt3-compat-headers as dependency 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 you

Bug#184025: marked as done (kmail: Bin->Txt En/Decoding)

2006-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 May 2006 17:00:44 +0200 with message-id <[EMAIL PROTECTED]> and subject line kmail: Bin->Txt En/Decoding 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 respon

Bug#309765: acknowledged by developer (Re: no explanation)

2006-05-11 Thread Guido Guenther
On Thu, May 11, 2006 at 03:33:14AM -0700, Debian Bug Tracking System wrote: > On Thu, May 11, 2006 at 08:33:41AM +0200, Guido Guenther wrote: > > Hi, > > could you please explain, why you closed this bug? > > Cheers, > > -- Guido > > because devices:/ is deprecated (even does not exists anymore

Bug#309765: marked as done (kdebase-kio-plugins: devices:/ uri and labeled mounts)

2006-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 May 2006 12:13:52 +0200 with message-id <[EMAIL PROTECTED]> and subject line no explanation 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 responsibility to r

Bug#325292: status of this bug?

2006-05-11 Thread Florian Paul Schmidt
Hi, i wonder what's the status of this bugreport. It's from August last year, so has anybody just forgotten to close it? Regards, Flo -- Palimm Palimm! http://tapas.affenbande.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTE

Bug#364448: Additional info

2006-05-11 Thread Ulrich Eckhardt
1. On the console, I get the same three "call to deprecated.." messages. 2. The backtrace seems to be the same, too. 3. When I remove the folder ~/.kde/share/apps/kmail/imap I can start kmail. Then, I get the three messages above, embedded in a plethora of | kmail: WARNING: [void KMFolderImap::s

Bug#309765: no explanation

2006-05-11 Thread Guido Guenther
Hi, could you please explain, why you closed this bug? Cheers, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: reopening 309765

2006-05-11 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.19 > reopen 309765 Bug#309765: kdebase-kio-plugins: devices:/ uri and labeled mounts Bug reopened, originator not changed. > End of message, stopping processing here. Please contact me i