Bug#766349: Kmail: Some times sign with S/MIME failed
Hi, Am Samstag, 1. November 2014, 00:22:43 schrieb Scott Kitterman: > Is there a pattern about when it fails and when it doesn't? No, only that I can sign 3 or 4 mail and then all other failed without any errormessage. For me I think is a memory hole... > > When you filed this bug, you filed it at severity critical. In Debian, > critical is defined as: > > critical > makes unrelated software on the system (or the whole system) break, or > causes serious data loss, or introduces a security hole on systems where you > install the package. > I think that a not or wrong encrypted or signed mail is already a security issue. > This does not seem to fit that criteria, so I'm going to adjust the > severity. > > Scott K CU Jörg -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema-ID: SYR8SJXB IRC: j_...@freenode.net, j_...@oftc.net signature.asc Description: This is a digitally signed message part.
Processed: severity of 766349 is normal
Processing commands for cont...@bugs.debian.org: > severity 766349 normal Bug #766349 [kmail] Kmail: Some times sign with S/MIME failed Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 766349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.14148157824960.transcr...@bugs.debian.org
Bug#735261: kmail2 randomly marks read messages as unread
On Tue, 14 Jan 2014 10:40:48 +0200 Shai Berger wrote: > Package: kmail > Version: 4:4.11.3-1 > Severity: grave > Justification: causes non-serious data loss > > Dear Maintainer, > > KMail randomly marks single messages as unread. This makes my > normal workflow, where I leave messages unread for later, deeper > consideration, tedious and bordering on impossible. > > KMail also randomly creates new duplicates of old messages, which > are (of course) also marked unread. Is this still an issue with the current kmail (4.14) or akonadi (1.13)? Scott K signature.asc Description: This is a digitally signed message part.
Bug#766349: Kmail: Some times sign with S/MIME failed
Is there a pattern about when it fails and when it doesn't? When you filed this bug, you filed it at severity critical. In Debian, critical is defined as: critical makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. This does not seem to fit that criteria, so I'm going to adjust the severity. Scott K signature.asc Description: This is a digitally signed message part.
Processed: tagging 767459
Processing commands for cont...@bugs.debian.org: > tags 767459 +pending Bug #767459 [qbs] qbs: FTBFS on mips64/mips64el: endian problem Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 767459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.141475654732244.transcr...@bugs.debian.org
Bug#767459: qbs: FTBFS on mips64/mips64el: endian problem
Package: qbs Version: 1.3.2+dfsg-1 Users: debian-m...@lists.debian.org Usertags: mips-port mips-patch Please add mips64/mips64el/mipsn32/mipsn32el in endianness.diff In these 4 archs, mips64 and mipsn32 are big endian and mips64el and mipsn32el are little endian. -- YunQiang Su -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cakcpw6vvebxkfg-uqengvocubhvpjju8hgvoh0hvjrpxf-j...@mail.gmail.com
