[akregator] [Bug 336417] Akregator crashes when being closed
https://bugs.kde.org/show_bug.cgi?id=336417 --- Comment #28 from diego.pigned...@gmail.com --- Created attachment 90614 -- https://bugs.kde.org/attachment.cgi?id=90614action=edit New crash information added by DrKonqi akregator (4.14.2) on KDE Platform 4.14.2 using Qt 4.8.6 - What I was doing when the application crashed: closin' it. nothing more else than closing it. Really, just closing it! (asks for more words, or I can't send the bug report :-)) -- Backtrace (Reduced): #6 0x7f139be89782 in Akregator::Frame::signalCompleted(Akregator::Frame*) () from /usr/lib/libakregatorprivate.so.4 #7 0x7f139be805b8 in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib/libakregatorprivate.so.4 #8 0x7f138133d1f7 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib/kde4/akregatorpart.so [...] #10 0x7f139be80039 in Akregator::FetchQueue::slotAbort() () from /usr/lib/libakregatorprivate.so.4 #11 0x7f139be800aa in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4 -- 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 336417] Akregator crashes when being closed
https://bugs.kde.org/show_bug.cgi?id=336417 diego.pigned...@gmail.com changed: What|Removed |Added CC||diego.pigned...@gmail.com -- 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 343086] Akregator annoying behaviour
https://bugs.kde.org/show_bug.cgi?id=343086 Christoph Feck cf...@kde.org changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO Severity|wishlist|crash CC||cf...@kde.org --- Comment #2 from Christoph Feck cf...@kde.org --- I guess it is bug 336417, which is fixed in version 4.14.3. If you are using that version, or a newer version, we need the backtrace to investigate the bug. For more information, please see https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports -- 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 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 alex jus...@gmx.de changed: What|Removed |Added CC||jus...@gmx.de --- Comment #11 from alex jus...@gmx.de --- Confirmed the bug still exists: Qt: 4.8.6 KDE: 4.14.3 KMail: 4.14.3 So switching from LOGIN to PLAIN worked for me. -- You are receiving this mail because: You are on the CC list for the bug. 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 342668] Kmail Crash on Close
https://bugs.kde.org/show_bug.cgi?id=342668 Laurent Montel mon...@kde.org changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kdep ||im/cb586e14cc6e2cbe695ccc6a ||f4acfb75b155d9b2 --- Comment #2 from Laurent Montel mon...@kde.org --- Git commit cb586e14cc6e2cbe695ccc6af4acfb75b155d9b2 by Montel Laurent. Committed on 23/01/2015 at 22:04. Pushed by mlaurent into branch 'master'. Fix Bug 342668 - Kmail Crash on Close M +1-0messageviewer/viewer/mimeparttreeview.cpp http://commits.kde.org/kdepim/cb586e14cc6e2cbe695ccc6af4acfb75b155d9b2 -- 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 343075] cannot start kleopatra because of an user rights error
https://bugs.kde.org/show_bug.cgi?id=343075 Christoph Feck cf...@kde.org changed: What|Removed |Added Severity|normal |grave -- 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 343186] New: Timeout trying to get lock on each start of kmail
https://bugs.kde.org/show_bug.cgi?id=343186 Bug ID: 343186 Summary: Timeout trying to get lock on each start of kmail Product: kmail2 Version: 4.14.2 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mar...@lichtvoll.de Before I only had it something on high load, but now after redoing Akonadi from scratch due to what seems to me a loss of the MySQL database, I get it everytime I start KMail. Even after Akonadi indexed the local maildir. Reproducible: Always Steps to Reproduce: I have no idea. Maybe have a large one million mail local maildir, wipe all of Akonadi and let it reindex it and then try? Actual Results: After only a few seconds, after starting KMail, and while I am able to see the folder list and mail lists just fine, I get the following dialog from KMail: The Email program encountered a fatal error and will terminate now. The error was: Timeout trying to get lock. I can only press Ok and then kmail finished. martin@merkaba:~ LANG=C kmail QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kmail2(3146) KDirWatch::removeDir: doesn't know /home/martin/.kde/share/apps/messageviewer/themes/ kmail2(3146) KDirWatch::removeDir: doesn't know /usr/share/kde4/apps/messageviewer/themes/ martin@merkaba:~ kmail2(3146)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout trying to get lock. Check who has acquired the name org.kde.pim.SpecialCollections on DBus, using qdbus or qdbusviewer. kmail2(3146)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get lock: Timeout trying to get lock. kmail2(3146) MailCommon::Kernel::emergencyExit: The Email program encountered a fatal error and will terminate now. The error was: Timeout trying to get lock. kmail2(3146)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout trying to get lock. Check who has acquired the name org.kde.pim.SpecialCollections on DBus, using qdbus or qdbusviewer. kmail2(3146)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get lock: Timeout trying to get lock. kmail2(3146) MailCommon::Kernel::emergencyExit: The Email program encountered a fatal error and will terminate now. The error was: Timeout trying to get lock. kmail2(3146)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout trying to get lock. Check who has acquired the name org.kde.pim.SpecialCollections on DBus, using qdbus or qdbusviewer. kmail2(3146)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get lock: Timeout trying to get lock. kmail2(3146) MailCommon::Kernel::emergencyExit: The Email program encountered a fatal error and will terminate now. The error was: Timeout trying to get lock. kmail2(3146)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout trying to get lock. Check who has acquired the name org.kde.pim.SpecialCollections on DBus, using qdbus or qdbusviewer. kmail2(3146)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get lock: Timeout trying to get lock. kmail2(3146) MailCommon::Kernel::emergencyExit: The Email program encountered a fatal error and will terminate now. The error was: Timeout trying to get lock. kmail2(3146)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout trying to get lock. Check who has acquired the name org.kde.pim.SpecialCollections on DBus, using qdbus or qdbusviewer. kmail2(3146)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get lock: Timeout trying to get lock. kmail2(3146) MailCommon::Kernel::emergencyExit: The Email program encountered a fatal error and will terminate now. The error was: Timeout trying to get lock. kmail2(3146)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout trying to get lock. Check who has acquired the name org.kde.pim.SpecialCollections on DBus, using qdbus or qdbusviewer. kmail2(3146)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get lock: Timeout trying to get lock. kmail2(3146) MailCommon::Kernel::emergencyExit: The Email program encountered a fatal error and will terminate now. The error was: Timeout trying to get lock. Expected Results: KMail just works. I think I will try these steps next: 1) Log out, make sure no user processes anymore, wipe out /tmp and /var/tmp KDE stuff, login, retry 2) Wipe KMail 2 configuration as well after I have wiped out and redone all of Akonadi due to the major breakage yesterday I reported in kde-pim-ml just a moment ago. I am using database optimized Akonagi 1.13 git master branch. This has not
[kmail2] [Bug 343186] Timeout trying to get lock on start of kmail
https://bugs.kde.org/show_bug.cgi?id=343186 Martin Steigerwald mar...@lichtvoll.de changed: What|Removed |Added Severity|grave |major Summary|Timeout trying to get lock |Timeout trying to get lock |on each start of kmail |on start of kmail --- Comment #1 from Martin Steigerwald mar...@lichtvoll.de --- Okay 1) Log out, make sure no user processes anymore, wipe out /tmp and /var/tmp KDE stuff, login, retry has helped. Now I recreate the filter rules from export of them and I configure POP3 account again. Reducing severity as it doesn't happen on each start anymore. KMail is now working again. -- 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 341909] Reply and Print time is in UTC, not in locale
https://bugs.kde.org/show_bug.cgi?id=341909 --- Comment #7 from Laurent Montel mon...@kde.org --- (In reply to rawi from comment #3) Created attachment 90580 [details] attempt to print the email in the first attachment Oh, and I forgot to say: If I need a hard copy of an email for archiving I get a print also with the time delay mentioned, which could become problematic until dangerous. See please this second attachment. What do you mean by I need a hard copy of an email for archiving ? -- 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 338402] File system cache is inneficient : too many file per directory
https://bugs.kde.org/show_bug.cgi?id=338402 --- Comment #9 from Martin Steigerwald mar...@lichtvoll.de --- With the SizeTreshold=32768 change I get a nice improvement for my work IMAP account on the laptop (the one I set to download all mails offline).ยน Before: ms@merkaba:~/.local/share/akonadi du -sch db_data/akonadi/* | sort -rh | head -10 2,8Ginsgesamt 2,6Gdb_data/akonadi/parttable.ibd 245Mdb_data/akonadi/pimitemtable.ibd 13M db_data/akonadi/pimitemflagrelation.ibd 248Kdb_data/akonadi/collectionattributetable.ibd 200Kdb_data/akonadi/collectiontable.ibd 136Kdb_data/akonadi/tagtable.ibd 120Kdb_data/akonadi/tagtypetable.ibd 120Kdb_data/akonadi/tagremoteidresourcerelationtable.ibd 120Kdb_data/akonadi/tagattributetable.ibd ms@merkaba:~/.local/share/akonadi find file_db_data | wc -l 524917 ms@merkaba:~/.local/share/akonadi#130 /usr/bin/time -v du -sch file_db_data 7,0Gfile_db_data 7,0Ginsgesamt Command being timed: du -sch file_db_data User time (seconds): 2.14 System time (seconds): 95.93 Percent of CPU this job got: 29% Elapsed (wall clock) time (h:mm:ss or m:ss): 5:35.47 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 33444 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 1 Minor (reclaiming a frame) page faults: 8079 Voluntary context switches: 667562 Involuntary context switches: 60715 Swaps: 0 File system inputs: 31509216 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0 After the change and akonadictl fsck: ms@merkaba:~/.local/share/akonadi find file_db_data | wc -l ; du -sch db_data/akonadi/* | sort -rh | head -10 27 7,5Ginsgesamt 7,3Gdb_data/akonadi/parttable.ibd 245Mdb_data/akonadi/pimitemtable.ibd 13M db_data/akonadi/pimitemflagrelation.ibd 248Kdb_data/akonadi/collectionattributetable.ibd 200Kdb_data/akonadi/collectiontable.ibd 136Kdb_data/akonadi/tagtable.ibd 120Kdb_data/akonadi/tagtypetable.ibd 120Kdb_data/akonadi/tagremoteidresourcerelationtable.ibd 120Kdb_data/akonadi/tagattributetable.ibd Yep, thats 27 files, instead of 50 (after just a week of the last fsck, which reduced to about 50 files, from 65+). After a nice vacuuming I even get: ms@merkaba:~/.local/share/akonadi find file_db_data | wc -l ; du -sch db_data/akonadi/* | sort -rh | head -10 27 6,5Ginsgesamt 6,2Gdb_data/akonadi/parttable.ibd 245Mdb_data/akonadi/pimitemtable.ibd 13M db_data/akonadi/pimitemflagrelation.ibd 248Kdb_data/akonadi/collectionattributetable.ibd 200Kdb_data/akonadi/collectiontable.ibd 136Kdb_data/akonadi/tagtable.ibd 120Kdb_data/akonadi/tagtypetable.ibd 120Kdb_data/akonadi/tagremoteidresourcerelationtable.ibd 120Kdb_data/akonadi/tagattributetable.ibd merkaba:/home/ms/.local/share/akonadi du -sh file_db_data 6,5Mfile_db_data I definitely prefer this over the original situation. Original was 2,8 GiB DB + 7 GiB file_db_local. Now is 6,5 GiB DB + 6,5 file_db_local and more than 524000 files less to consider for rsync and our enterprise backup software. Let's see whether it brings an performance enhancement, but for now I like this. [1] Re: Possible akonadi problem? From: Dmitry Smirnov Date: Fri, 23 Jan 2015 07:17:13 +1100 Message-id: 10777191.dsSRuLrDof@debstor https://lists.debian.org/debian-kde/2015/01/msg00055.html Thanks, Martin -- 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 341909] Reply and Print time is in UTC, not in locale
https://bugs.kde.org/show_bug.cgi?id=341909 --- Comment #8 from rawi only4...@web.de --- Sometimes one must keep an important Email also as printed on paper (in business to archive it, private a bill for taxes etc., to show to which moment he got an information) (I hope you could open that one mess of a PDF...) I printed your first message (comment 1) to PDF, as it reached my Kontact/Kmail, with the time 21:18:04. As you could see in the snapshot (1st. attachment) I got one hour earlier in the reference line of a replay (not sent). In the second attachment (PDF) I wanted to show, that I get the same time difference also in a print; that's more troublesome, if I intent to provide evidence of what time I got a certain information. -- 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
[nepomuk] [Bug 294320] kmail complains about the semantic destkop not running, when it is
https://bugs.kde.org/show_bug.cgi?id=294320 Vishesh Handa m...@vhanda.in changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|ASSIGNED|RESOLVED --- Comment #23 from Vishesh Handa m...@vhanda.in --- Thank you for taking the time to file a bug report. The Nepomuk project is no longer included in the KDE Software Compilation. With Plasma 5, we have replaced most of the underlying technology with Baloo and other components. Hopefully this will have addressed your concern. We encourage you to try out Plasma 5 (+Baloo) and let us know if your problem persists. -- 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
