Bug#629123: libqca2-plugin-ossl

2011-07-07 Thread Jeffrey G Thomas
Hi! This seems to be a qca2-plugin-ossl bug and so I'm reassigning it. I think this bug has been solved already, so would you mind checking against the last version of qca2-plugin-ossl in the archive? Running the current version, I cannot connect with our Jabber server. Yes, it uses a

Bug#629123: Downgraded libqca2-plugin-ossl

2011-06-06 Thread Jeffrey G Thomas
I've downgraded the package libqca2-plugin-ossl with: $ apt-cache policy libqca2-plugin-ossl Version table: *** 2.0.0~beta3-1 0 0.1~20070904-4 0 $ sudo aptitude install libqca2-plugin-ossl=0.1~20070904-4 After a restart of Kopete, I can connect again. The bug may be in libqca2-plugin-ossl

Bug#629123: kopete: Kopete cannot connect to Jabber with TLS

2011-06-03 Thread Jeffrey G Thomas
Package: kopete Version: 4:4.6.3-1 Severity: important *** Please type your report below this line *** I have the package 'libqca2-plugin-ossl' installed but it doesn't help. I was able to connect to our local Jabber server (OpenFire) over port 5223 fine until I upgraded to Sid with KDE 4.6.3.

Bug#525441: Kontact keyboard selection

2009-04-29 Thread Jeffrey G Thomas
and if I use the keyboard to go to the [Do Not Sign] button and press [Enter] or [Spacebar], either way the pinentry-qt dialog pops up This isn't just the case with signing emails; if Kontact offers that I have the word 'attached' in an email and wants to know if I want to attach something,

Bug#525441: kontact: Keyboard selection of 'Do Not Sign' still pops up pinentry-qt dialog

2009-04-24 Thread Jeffrey G Thomas
Package: kontact Version: 4:4.2.2-1 Severity: normal I have GPG-signing set up in Kontact and with one of my contacts, I do not sign emails to that person. When Kontact pops up a message that reads, There are conflicting signing preferences for these recipients. Sign this message? and if I use

Bug#490981: kontact: Bug may be fixed, not crashing currently

2009-02-24 Thread Jeffrey G Thomas
Package: kontact Followup-For: Bug #490981 BUG: KMail crashes when printing to CUPS network printer I think that I am the original reporter for this bug; if not, I filed a very similar one. I've been able to print recently from within KMail without crashing. Thanks. -- System Information:

Bug#512662: kopete: Kopete cannot connect to OpenFire 3.6.2 Jabber

2009-01-22 Thread Jeffrey G Thomas
Package: kopete Version: 4:3.5.10-2 Severity: important I have Kopete for my desktop IM client at work, where we use OpenFire 3.5.2 for our Jabber server. We have another server running 3Openfire 3.6.2 and I cannot get Kopete to connect to this. Pidgin does connect but I don't want to use

Bug#512662: kopete: Invalid bug

2009-01-22 Thread Jeffrey G Thomas
Package: kopete Followup-For: Bug #512662 My mistake, I resolved this by using usern...@hostname.domain.com and changing the connection settings to the IP Address. This bug is invalid and should be closed. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500,

Bug#510872: KDEPIM-Wizard: scalixwizard improperly sets up Kalendar free/busy connection information

2009-01-05 Thread Jeffrey G Thomas
Package: kdepim-wizards Version: 4:3.5.9-5 Severity: normal We have a Scalix server for mail and shared calendars; when we set up Kontact with the scalixwizard it puts this into the Configure Kontact Calendar Free/Busy Server URL fields (for both Publish and Recieve): ###

Bug#490981: KMail crashes when printing to CUPS network printer

2008-07-15 Thread Jeffrey G Thomas
Package: KMail 1.9.9 (and Kontact 1.2.9 also, which integrates KMail) Version: 4:3.5.9-4 is how KPackage reports it; 1.9.9 is how the software reports it. When I click [Print], KMail crashes after opening a print dialog which never actually prints. I can print in other applications (KDE and