[kmail2] [Bug 399768] New: Kmail uses 100% CPU in version 5.9.2
https://bugs.kde.org/show_bug.cgi?id=399768 Bug ID: 399768 Summary: Kmail uses 100% CPU in version 5.9.2 Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: pieter.da...@gmail.com Target Milestone: --- Since I upgraded to version 5.9.2 yesterday (applications 18.08.2) the kmail (or kontact) process always uses 100% CPU, also when I'm not using it (this did not happen with 5.9.1). The application works fine otherwise and stays responsive, but my laptop battery is not so happy. I am happy to provide more information or test things, but is it safe to downgrade to the previous version in the mean time? SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.0 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION I am using kmail with three IMAP accounts and search folders. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar
https://bugs.kde.org/show_bug.cgi?id=393059 --- Comment #13 from Wolfgang Bauer --- (In reply to Denis Kurz from comment #12) > it is fixed in 18.04.0, which > should be... 5.8.0, I guess? Yes, that's indeed 5.8.0. Actually the fix was pushed to the 17.12 branch as well, but that was after 17.12.3/5.7.3 so it didn't make it into any 17.12 (or 5.7.x) release. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar
https://bugs.kde.org/show_bug.cgi?id=393059 Denis Kurz changed: What|Removed |Added Resolution|--- |FIXED CC||kde...@posteo.de Version Fixed In||5.8.0 Latest Commit||https://cgit.kde.org/eventv ||iews.git/commit/?h=Applicat ||ions/17.12=a3a66bb10020e ||6fbdd354b4ecc6c0fee6741c467 Version|unspecified |5.7.3 Status|REPORTED|RESOLVED --- Comment #12 from Denis Kurz --- I think Wolfgang is right about this. According to https://phabricator.kde.org/source/eventviews/tags/master/;a3a66bb10020e6fbdd354b4ecc6c0fee6741c467 it is fixed in 18.04.0, which should be... 5.8.0, I guess? I still hate this superfluous pim extra versioning scheme... -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 397314] korganizer segfaults on exit
https://bugs.kde.org/show_bug.cgi?id=397314 Denis Kurz changed: What|Removed |Added Status|REPORTED|RESOLVED CC||kde...@posteo.de Resolution|--- |DUPLICATE --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 393059 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar
https://bugs.kde.org/show_bug.cgi?id=393059 Denis Kurz changed: What|Removed |Added CC||onkekabo...@hotmail.com --- Comment #11 from Denis Kurz --- *** Bug 397314 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 399752] kontact crash while using akregator
https://bugs.kde.org/show_bug.cgi?id=399752 --- Comment #1 from Christoph Feck --- Crash is in libQt5WebEngineCore. If this is reproducible, please install debug symbols for QtWebEngine and report this issue directly to Qt developers via https://bugreports.qt.io/ -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 399752] New: kontact crash while using akregator
https://bugs.kde.org/show_bug.cgi?id=399752 Bug ID: 399752 Summary: kontact crash while using akregator Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.9.2) Qt Version: 5.11.2 Frameworks Version: 5.50.0 Operating System: Linux 4.12.14-lp150.12.19-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: Looking at blog posts using akregator, specifically https://akashasternberg.wordpress.com/2018/10/13/news-and-updates-that-hopefully-will-not-scare-you-silly/ fetched from the RSS feed at http://iheartsl.com/ -- Backtrace: Application: Kontact (kontact), signal: Bus error Using host libthread_db library "/lib64/libthread_db.so.1". 184 return currentThreadData; [Current thread is 1 (Thread 0x7f3c911ec900 (LWP 26404))] Thread 45 (Thread 0x7f3ad6494700 (LWP 2933)): #0 0x7f3c89a99bcb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c7ecd25f7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3c7ecd3b57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3c7ecd3c42 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3c7ecd8cc1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3c7ecda05f in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3c7ece4c61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3c89a93559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3c8db4982f in clone () at /lib64/libc.so.6 Thread 44 (Thread 0x7f3ad6c95700 (LWP 2928)): #0 0x7f3c89a99bcb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c7ecd25f7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3c7ecd3b57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3c7ecd3c42 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3c7ecd8cc1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3c7ecda05f in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3c7ece4c61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3c89a93559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3c8db4982f in clone () at /lib64/libc.so.6 Thread 43 (Thread 0x7f3adcb5d700 (LWP 2927)): #0 0x7f3c89a99bcb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c7ecd25f7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3c7ecd3b57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3c7ecd3c42 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3c7ecd8cc1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3c7ecda249 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3c7ece4c61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3c89a93559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3c8db4982f in clone () at /lib64/libc.so.6 Thread 42 (Thread 0x7f3b2e115700 (LWP 2926)): #0 0x7f3c89a99bcb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c7ecd25f7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3c7ecd3b57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3c7ecd3c42 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3c7ecd8cc1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3c7ecda249 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3c7ece4c61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3c89a93559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3c8db4982f in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7f3adf3e3700 (LWP 2910)): #0 0x7f3c89a99bcb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c7ecd25f7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3c7ecd3b57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3c7ecd3c42 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3c7ecd8cc1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3c7ecda249 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3c7ece4c61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3c89a93559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3c8db4982f in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7f3c3dffb700 (LWP 2296)): [KCrash Handler] #6 0x7f3c8dbab49e in __memmove_avx_unaligned_erms () at /lib64/libc.so.6 #7 0x7f3c7fa11ae5 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f3c7fa4f704 in () at /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f3c7fa4ff6d in () at /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f3c7fa77004 in () at /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f3c7fa7c980 in
[akregator] [Bug 130951] aKregator should default to the feed-specified check interval
https://bugs.kde.org/show_bug.cgi?id=130951 Stephan Sokolow changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Stephan Sokolow --- Woops. Forgot to set the status. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 130951] aKregator should default to the feed-specified check interval
https://bugs.kde.org/show_bug.cgi?id=130951 --- Comment #4 from Stephan Sokolow --- Sorry for the delay. It appears to still be a problem under Akregator 4.13.3. If you want me to test under KDE 5, let me know and I'll try to get access to a machine running something newer than Kubuntu 14.04 LTS. You can use http://feeds.ssokolow.com/ssokolow_blog?format=xml for testing. It's handled by FeedBurner and provides the following RSS 1.0 elements: hourly 1 (Where xmlns:sy="http://purl.org/rss/1.0/modules/syndication/; ) If you also need something to test against which uses RSS 2.0's `ttl` element, let me know and I'll dig something up or craft a test case. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 399346] Can not start Akonadi
https://bugs.kde.org/show_bug.cgi?id=399346 Rik Mills changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Rik Mills --- Now also reported in Debian (Cheers Ian) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910902 -- You are receiving this mail because: You are the assignee for the bug.
