Bug#394534: No data sync on kpilot 3.5.5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 16 November 2006 12:53, Sune Vuorela wrote: > Rumors say that these two packages (temporarily) solves the problem > > http://people.debian.org/~ana/394534/kpilot_3.5.5.dfsg.1-1~ana_i386.deb > http://people.debian.org/~ana/394534/libpisock8_

Bug#399025: kmail: SIGSEGV in KMMessage::fromDwString while reading mail

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: kmail Version: 4:3.5.5.dfsg.1-1 Severity: normal Hi! While reading mail I repeatedly - but not always on the same message - got the following crash (SEGV) from KMail: Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [

Bug#394534: lost syncing of calendar events and addressbook when upgrading to kpilot-3.5.5

This seems to be a longstanding bug in kpilot, see http://bugs.kde.org/show_bug.cgi?id=86879 Regards, David -- - hallo... wie gehts heute? - *hust* gut *rotz* *keuch* - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15

Bug#351029: kmail: crash still happens

Package: kmail Version: 4:3.5.2-1+b1 Followup-For: Bug #351029 Hi! The crash on startup still happens. Attached is are two backtrace with current kmail and -dbg symbols. The relevant piece seems to be: #5 0xb7cc970c in KMFolder::noContent (this=0x4) <<-- !! #6 0xb7d61dc4 in KMAcctImap::proc

Bug#356073: kopete: Jabber disconnects constantly with "unknown" error

On Monday 10 April 2006 04:54, Adam Porter wrote: > Well, I'd do that, except I think they are separate issues. In this beta, > the problem is that I can't connect at all. In the version currently in > Debian, the problem is that it connects for a while, but then disconnects > with "Unknown error

Bug#356073: kopete: Jabber disconnects constantly with "unknown" error

On Sunday 09 April 2006 06:12, you wrote: > On Saturday 08 April 2006 09:53, David Schmitt wrote: > > There is a new version of kopete unstable (3.5.2-1) available. Could you > > please test if your problem persists there? > > Well, I've actually compiled and installed t

Bug#361449: kopete: crashes in Devices Dialog

Package: kopete Version: 4:3.5.2-1 Severity: normal Tags: patch Hi! Current kopete crashes when entering the device configuration dialog. While I have lost the backtrace, I could figure out the crash site and make a crude patch. --- kdenetwork-3.5.2/kopete/kopete/config/avdevice/avdeviceconfig.

Bug#334465: kopete: '/me' expression seems to be passed as-is on AIM

found 334465 3.5.2-1 thanks Hi! This is also true with ICQ as of 3.5.2-1 Regards, David -- - hallo... wie gehts heute? - *hust* gut *rotz* *keuch* - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15

Bug#280777: kopete: Crashes with segfault in libcrypto

Hi! I noticed that freenode.net has an entry for brunner.freenode.net:993, where 993 is imaps in contrast to ircs which is 994. Both are not reachable anyways. Regards, David -- - hallo... wie gehts heute? - *hust* gut *rotz* *keuch* - gott sei dank kommunizieren wir über ein septisches mediu

Bug#336257: kopete: Kopete crash when I quit (SIGSEGV)

Hi Olivier! There is already a new version of kopete (3.5.1) in the archives available. Could you please test whether your problem still persists? If not, please close your bug report by sending a mail with a short notice to [EMAIL PROTECTED] Thank you for your cooperation! Regards, David

Bug#361366: kopete: irc: Unknown IRC numeric reply [..] 432 * DavidS/kop :Erroneous Nickname

Package: kopete Version: 4:3.5.2-1 Severity: normal Hi! kopete's IRC plugin cannot handle the "Erroneous Nickname" error message from oftc.net: kopete (irc): WARNING: Unknown IRC numeric reply for line::nobelium.oftc.net 432 * DavidS/kop :Erroneous Nickname Thank you for your time and work!

Bug#351029: kmail: crashes on startup

Indeed, I installed 3.5.1-1 from incoming and kmail works again. While I am aware, that KDE doesn't support partial upgrades, i would think that the obviousness and severeness of this crash warrant a Conflict or an appropriate Depends in kmail? Regards, David -- - hallo... wie gehts heute? -

Bug#351029: kmail: crashes on startup

Package: kmail Version: 4:3.5.0-5+b1 Severity: important Hi! It seems as if kmail 3.5.0 has problems with the 3.5.1 libraries and crashes on startup (see attached trace from kcrash). Before upgrading the libraries, kmail worked without a hitch. Perhaps this is related to http://bugs.kde.org/show

Bug#350561: ksysguard: changed order of sensors ignored

Package: ksysguard Version: 4:3.5.1-1 Severity: normal Hi! ksysguard ignores/reverts changing the order of sensors in the Signal Plotter Settings dialog. Steps to reproduce: * Start ksysguard * right click on one of the displays with multiple sensors (e.g. "Physical Memory") * choose "Propert

Bug#321441: artsd crashes

Package: arts Version: 1.4.2-5 Followup-For: Bug #321441 Hi there! This seems to be #312577 on alsa-lib. Regards, David -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh

Bug#319154: kdelibs' ftbfs: simple fix

Hello *! Including in kdeui/kactioncollection.h fixes this ftbfs, though I have not yet tried whether the new packages work and the build sports quite a few warnings. Regards, David -- - hallo... wie gehts heute? - *hust* gut *rotz* *keuch* - gott sei dank kommunizieren wir über ein septisc

Bug#317098: backtrace for kmail segfault

Package: kmail Version: 4:3.3.2-3 Followup-For: Bug #317098 Same problem here. Backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208117184 (LWP 2910)] 0x43fe11db in QString::QString () from /usr/lib/libqt-mt.so.3 (gdb) bt full #0 0x43fe11db in QString::QStrin