[Akonadi] [Bug 353306] New: akonadi crash
https://bugs.kde.org/show_bug.cgi?id=353306 Bug ID: 353306 Summary: akonadi crash Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: nkuk...@lbsd.net CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.88.0) Qt Version: 5.4.2 Operating System: Linux 4.2.0-11-generic x86_64 Distribution: Ubuntu Wily Werewolf (development branch) -- Information about the crash: - What I was doing when the application crashed: I was in a different application. It seems to happen frequently, about 2-3 times a day. The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Resource (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7feedb692840 (LWP 2540))] Thread 4 (Thread 0x7feed8ba1700 (LWP 2554)): #0 0x7feeeafb08dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7feee679ebd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7feee67a074f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7feedb3389e9 in QXcbEventReader::run (this=0x15a5290) at qxcbconnection.cpp:1105 #4 0x7feeeb8b925e in QThreadPrivate::start (arg=0x15a5290) at thread/qthread_unix.cpp:337 #5 0x7feee69bd6aa in start_thread (arg=0x7feed8ba1700) at pthread_create.c:333 #6 0x7feeeafbbeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7feed1c46700 (LWP 21758)): #0 0x7ffc2f94fc4f in clock_gettime () #1 0x7feeeafca38d in __GI___clock_gettime (clock_id=, tp=tp@entry=0x7feed1c45af0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7feeeb96a346 in qt_clock_gettime (ts=0x7feed1c45af0, clock=) at tools/qelapsedtimer_unix.cpp:105 #3 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:161 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:170 #5 0x7feeebaed8a9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7feecc1c6060) at kernel/qtimerinfo_unix.cpp:84 #6 0x7feeebaede15 in QTimerInfoList::timerWait (this=0x7feecc1c6060, tm=...) at kernel/qtimerinfo_unix.cpp:379 #7 0x7feeebaef1fe in timerSourcePrepareHelper (timeout=0x7feed1c45bc4, src=) at kernel/qeventdispatcher_glib.cpp:127 #8 timerSourcePrepare (source=, timeout=0x7feed1c45bc4) at kernel/qeventdispatcher_glib.cpp:160 #9 0x7feee5e5f77d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7feee5e6011b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7feee5e602fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7feeebaefe1b in QEventDispatcherGlib::processEvents (this=0x7feecc0caf90, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #13 0x7feeeba962da in QEventLoop::exec (this=this@entry=0x7feed1c45d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #14 0x7feeeb8b4374 in QThread::exec (this=) at thread/qthread.cpp:503 #15 0x7feeeb8b925e in QThreadPrivate::start (arg=0x16d5300) at thread/qthread_unix.cpp:337 #16 0x7feee69bd6aa in start_thread (arg=0x7feed1c46700) at pthread_create.c:333 #17 0x7feeeafbbeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7feecb640700 (LWP 23701)): #0 0x7feee5ea48b4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7feee5e5f800 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7feee5e6011b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7feee5e602fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7feeebaefe1b in QEventDispatcherGlib::processEvents (this=0x7feec001bc60, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7feeeba962da in QEventLoop::exec (this=this@entry=0x7feecb63fd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7feeeb8b4374 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7feeeb8b925e in QThreadPrivate::start (arg=0x16d4020) at thread/qthread_unix.cpp:337 #8 0x7feee69bd6aa in start_thread (arg=0x7feecb640700) at pthread_create.c:333 #9 0x7feeeafbbeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7feedb692840 (LWP 2540)): [KCrash Handler] #6 0x7ff2aa3d in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () from /usr/lib/x86_64-linux-gnu/libKF5IMAP.so.5 #7 0x7ff3241b in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () from /usr/lib/x86_64-linux-gnu/libKF5IMAP.so.5 #8 0x7feeebaca1d1 in QObject::event (this=0x168b8c0, e=) at kernel/qobject.cpp:1245 #9 0x7feeec3e7b8c in
[kmail2] [Bug 353318] "Find messages" find only one mail
https://bugs.kde.org/show_bug.cgi?id=353318 --- Comment #1 from Ezio Vergine--- Is this bug the same as reported on 352472? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 353317] New: kMail 5.0: Wrong signature issuer shown for OpenPGP signed mails (SMIME not tested).
https://bugs.kde.org/show_bug.cgi?id=353317 Bug ID: 353317 Summary: kMail 5.0: Wrong signature issuer shown for OpenPGP signed mails (SMIME not tested). Product: kmail2 Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kdeb...@customcdrom.de Not sure if there might even be security implications: A friend of mine sends signed messages which are always * shown as having a valid signature (green display and everything) * but from a completely wrong sender (!) ** Die Nachricht enthält die Signatur von kl...@x.de (Schlüsselkennung: 0x9F8E2A98D1A4EDE5). Die Signatur ist gültig, und der Schlüssel ist vertrauenswürdig. ** (translation: The message contains the signature of kl...@x.de (Key-ID: 0x9F8E2A98D1A4EDE5). The signature is valid and the key is trusted. ** I have this public key in my keyring, but it has nothing to do with the mail that is displayed - if I extract its PGP signature into a separate file and use gpg to display information about it, the following is displayed: ** $ LANG= gpg --verify sigfile /dev/null gpg: Signature made Tue Sep 29 11:11:08 2015 CEST using RSA key ID 22B2951D gpg: WARNING: digest algorithm MD5 is deprecated gpg: please see https://gnupg.org/faq/weak-digest-algos.html for more information gpg: BAD signature from "Matthias XXX" ** Neither mail address nor key ID have anything to do with the wrong key that is picked up for display by kMail... I'm also not sure why the wrong key is displayed as "trusted" in the first place - it does not seem to be considered trusted by gpg: ** gpg: using classic trust model pub 2048R/D1A4EDE5 created: 2000-02-26 expires: never usage: SCE trust: undefined validity: unknown ** Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 353317] kMail 5.0: Wrong signature issuer shown for OpenPGP signed mails (SMIME not tested).
https://bugs.kde.org/show_bug.cgi?id=353317 --- Comment #1 from Gunter Ohrner--- (eMail addresses anonymized to avoid collection by spam bots.) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 353318] New: "Find messages" find only one mail
https://bugs.kde.org/show_bug.cgi?id=353318 Bug ID: 353318 Summary: "Find messages" find only one mail Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: search Assignee: kdepim-bugs@kde.org Reporter: virgo...@gmail.com CC: m...@vhanda.in "Find messages" find only one mail and don't consider any type of filter specified. I think the problem is related to the indexing system (baloo?). There are some a config file somewhere where I can say to kmail "reindex all emails"? Reproducible: Always Steps to Reproduce: 1. Open "Find message windows" 2. Search something 3. Actual Results: Always one mail is find (and doesn't respect the search criteria) Expected Results: All the mail that respect the search criteria) Kmail Version 5.0.1 KDE Frameworks 5.14.0 Qt 5.5.0 (built against 5.5.0) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 352512] 5.0.xx after a crash, the restore session pops up twice then akregator crashes
https://bugs.kde.org/show_bug.cgi?id=352512 S Clarkchanged: What|Removed |Added CC||smc+kdebugs@dogphilosophy.n ||et --- Comment #5 from S Clark --- If it helps, what seems to be happening is the feeds.opml file that akregator reads its feeds from gets truncated to 1 byte. Not sure what *exactly* is happening, but that's what I see every time this happens (about once every few weeks for the last couple of months). I have to remember to export my feedlist regularly so that I can replace/reimport after each crash. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately
https://bugs.kde.org/show_bug.cgi?id=350731 S Clarkchanged: What|Removed |Added CC||smc+kdebugs@dogphilosophy.n ||et --- Comment #4 from S Clark --- Also confirmed... This seems to specifically be a problem with the behavior around the "mark selected article read after..." advanced setting. I think this defaults to 0 seconds (i.e. immediately) which is what I used to have it set to. Previously, this just meant the article was marked "read" as soon as it was clicked, and if you had the unread filter set, it would then disappear from the list AFTER you clicked away from it to another article. Now the article is immediately removed from the list, causing the selection to automagically drop to the next, mark *it* unread, remove it, etc. You can watch it happen more slowly if you go to settings -> configure akregator -> advanced and set it to mark as read after, say, 5 seconds. Perhaps this bug should just read "Read articles should not be removed by the unread filter while the article is selected"? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kleopatra] [Bug 353252] Certification fails with "Allgemeiner Fehler" (Common Failure)
https://bugs.kde.org/show_bug.cgi?id=353252 --- Comment #1 from c.woll...@web.de --- In order to check Yubikey Neo I opened a ticket at Yubico: Ticket 00012836 When signing the key in command line with gpg --sign-key, the key was signed properly. I therefore assume that Yubikey Neo works properly. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #145 from j.d...@netcologne.de --- Dear, I've a case of a mail, which reproducibly and consistently creates duplicates, and a lot of them. When I try to remove duplicates ( *>), I get an error message. I've attached the screenshot of the error message and the mail file itself (after anonymising my mail address), maybe that helps for further analysis. This mail file resides here: ~/.local/share/akonadi_maildir_resource_0/inbox/new/ and the creation of duplicates ends only, when I manually delete this file. Am Freitag, 25. September 2015, 17:23:49 schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=283682 > > --- Comment #144 from Eike Sauer--- > > Am Donnerstag, 24. September 2015, 17:06:58 schrieben Sie: > > https://bugs.kde.org/show_bug.cgi?id=283682 > > > > --- Comment #142 from Hussam Al-Tayeb --- > > That breaks execution of other filters. I want it to still get filtered to > > Inbox/Bugs/KDE > > Obviously you need to deactivate "stop here if filter applies" on the > extended tab. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #146 from j.d...@netcologne.de --- Created attachment 94780 --> https://bugs.kde.org/attachment.cgi?id=94780=edit duplicateMailExample.png -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 352512] 5.0.xx after a crash, the restore session pops up twice then akregator crashes
https://bugs.kde.org/show_bug.cgi?id=352512 --- Comment #6 from Pavel--- (In reply to S Clark from comment #5) > I have to remember to export my feedlist regularly so that I can > replace/reimport after each crash. Why not automate the backup of feeds.opml? Use a cron job or systemd timer. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 350139] Akregator Crashes when open specific article
https://bugs.kde.org/show_bug.cgi?id=350139 --- Comment #6 from Graeme Hewson--- For the record, the image which crashes Akregator (and it crashes Konqueror, too) is https://i.guim.co.uk/img/media/622d43ad4fd15a12a95914826a16b3bc3253b261/34_85_1143_686/master/1143.jpg?w=620=85=format=10=b61ede16c18d228d687585f729de02d5 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 350139] Akregator Crashes when open specific article
https://bugs.kde.org/show_bug.cgi?id=350139 Graeme Hewsonchanged: What|Removed |Added CC||b...@wormhole.me.uk --- Comment #5 from Graeme Hewson --- Crashed for me too. Isn't there a more modern and maintained library for Akregator to use? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs