[kmail2] [Bug 399768] Kmail uses 100% CPU in version 5.9.2
https://bugs.kde.org/show_bug.cgi?id=399768 Pieter David changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Pieter David --- It seems that the problem solved itself (CPU usage back to 0% when inactive) -- You are receiving this mail because: You are watching all bug changes.
[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-b...@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 watching all bug changes.
[Akonadi] [Bug 398191] akonadiserver crashes from time to time since upgrading to 18.08
https://bugs.kde.org/show_bug.cgi?id=398191 Pieter David changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Pieter David --- Indeed, after updating to 5.9.1 (applications 18.08.1) the crashes are gone. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 398191] New: akonadiserver crashes from time to time since upgrading to 18.08
https://bugs.kde.org/show_bug.cgi?id=398191 Bug ID: 398191 Summary: akonadiserver crashes from time to time since upgrading to 18.08 Product: Akonadi Version: 5.9.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: pieter.da...@gmail.com Target Milestone: --- Application: akonadiserver (5.9.0) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.18.5-arch1-1-ARCH x86_64 Distribution: "Arch Linux" (akonadi 18.08.0-1 package recompiled for debug symbols) -- Information about the crash: - What I was doing when the application crashed: It's hard to say what triggers the crash, other than "kmail activity" (mail sync, browsing email folders). The frequency goes down when I set my gmail account to "offline", but it still happens from time to time. - Custom settings of the application: I have several IMAP accounts, two of which (one gmail, one work-related which uses a microsoft exchange server) have quite a lot of messages. The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3b4c4a9e40 (LWP 22036))] Thread 44 (Thread 0x7f3ab77f6700 (LWP 22632)): #0 0x7f3b504f5ad4 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f3b504ae87a in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f3b504aee66 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f3b504aefee in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f3b5297b4c4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f3b52926dac in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x560db33a4383 in Akonadi::Server::Connection::handleIncomingData() () at /usr/include/qt/QtCore/qflags.h:120 #7 0x7f3b5295e137 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f3b529527eb in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #9 0x7f3b529280f7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #10 0x7f3b5297a87a in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #11 0x7f3b5297b102 in ?? () from /usr/lib/libQt5Core.so.5 #12 0x7f3b504aeca7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #13 0x7f3b504aef59 in ?? () from /usr/lib/libglib-2.0.so.0 #14 0x7f3b504aefee in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #15 0x7f3b5297b4a9 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #16 0x7f3b52926dac in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #17 0x7f3b5276ff59 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #18 0x7f3b5277a005 in ?? () from /usr/lib/libQt5Core.so.5 #19 0x7f3b51a0ba9d in start_thread () from /usr/lib/libpthread.so.0 #20 0x7f3b52444a43 in clone () from /usr/lib/libc.so.6 [many similar stacks for other threads left out for readability] Thread 9 (Thread 0x7f3b3bfff700 (LWP 22059)): [KCrash Handler] #6 QByteArray::QByteArray (a=..., this=this@entry=0x7f3b3bffd7e0) at /usr/include/qt/QtCore/qbytearray.h:498 #7 Akonadi::Server::Connection::sessionId (this=0x0) at /usr/src/debug/akonadi-18.08.0/src/server/connection.cpp:437 #8 0x560db33ca140 in Akonadi::Server::FetchHelper::isScopeLocal(Akonadi::Scope const&) () at /usr/src/debug/akonadi-18.08.0/src/server/handler/fetchhelper.cpp:268 #9 0x560db33cab78 in Akonadi::Server::FetchHelper::fetchItems(std::function&&) () at /usr/include/qt/QtCore/qflags.h:145 #10 0x560db34b47ac in Akonadi::Server::NotificationCollector::completeNotification(QSharedPointer const&) () at /usr/include/c++/8.2.0/new:169 #11 0x560db34b4cfb in Akonadi::Server::NotificationCollector::dispatchNotification(QSharedPointer const&) () at /usr/src/debug/akonadi-18.08.0/src/server/storage/notificationcollector.cpp:586 #12 0x560db34b8a1f in Akonadi::Server::NotificationCollector::itemNotification(Akonadi::Protocol::ItemChangeNotification::Operation, QVector const&, Akonadi::Server::Collection const&, Akonadi::Server::Collection const&, QByteArray const&, QSet const&, QSet const&, QSet const&, QSet const&, QSet const&, QVector const&, QVector const&) () at /usr/include/c++/8.2.0/bits/atomic_base.h:295 #13 0x560db34b9b52 in Akonadi::Server::NotificationCollector::itemsLinked(QVector const&, Akonadi::Server::Collection const&) () at /usr/include/qt/QtCore/qarraydata.h:255 #14 0x560db341695f in Akonadi::Server::SearchManager::searchUpdateResultsAvailable(QSet const&) () at /usr/src/debug/akonadi-18.08.0/src/server/search/searchmanager.cpp:451 #15 0x7f3b529520b0 in
[kmail2] [Bug 393489] Search folders are not updating in 18.04
https://bugs.kde.org/show_bug.cgi?id=393489 --- Comment #2 from Pieter David <pieter.da...@gmail.com> --- After running `akonadictl vacuum` and `akonadictl fsck` a few times, akonadi printed a message that the search database was corrupted (the search was crashing, at that point), so I removed it, triggered a re-indexing, recreated the search folder, and now it is working again. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393489] Search folders are not updating in 18.04
https://bugs.kde.org/show_bug.cgi?id=393489 --- Comment #1 from Pieter David <pieter.da...@gmail.com> --- The problem is also present in 5.8.1. Some more information: if I try to redo the search, I get a dialog asking about re-indexing folders (as in https://bugs.kde.org/show_bug.cgi?id=394071, but without crash). After `akonadictl restart` and re-opening kmail, I see messages like "unknown: Xapian error in indexer 0x5628475f8a70 : Attempted to delete or modify an entry in a non-existent posting list for example" and "unknown: We asked for UID but the server didn't give it back, resultingFlags not stored." being printed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393489] Search folders are not updating in 18.04
https://bugs.kde.org/show_bug.cgi?id=393489 Pieter David <pieter.da...@gmail.com> changed: What|Removed |Added Version|unspecified |5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393489] New: Search folders are not updating in 18.04
https://bugs.kde.org/show_bug.cgi?id=393489 Bug ID: 393489 Summary: Search folders are not updating in 18.04 Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: pieter.da...@gmail.com Target Milestone: --- Since I upgraded to the 18.04 applications release, search folders stopped updating automatically (I have one with the unread messages from different IMAP accounts, which contains none of the messages I received since the upgrade, while some of the messages from before are marked as read but still there). I tried to mark some messages as "unread" and then as "read" again, which has helped in the past, but that did not do the trick this time. Redoing the search through the dialog gives the same results. The quick filter for "unread" inside separate folders does seem to work fine. Please let me know if you need any more information. Thanks in advance! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389551] kwin_wayland crash when monitor is switched off (or input is changed)
https://bugs.kde.org/show_bug.cgi?id=389551 --- Comment #7 from Pieter David <pieter.da...@gmail.com> --- In my case one screen does stay connected at all time... but I just tried again, and it turns out that I can disable the external monitor without problem, I only get the crash when disabling the screen of my laptop. Maybe the problem is with disabling the "first" screen? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390234] kwin_wayland crash when disabling an output
https://bugs.kde.org/show_bug.cgi?id=390234 Pieter David <pieter.da...@gmail.com> changed: What|Removed |Added CC||pieter.da...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390234] kwin_wayland crash when disabling an output
https://bugs.kde.org/show_bug.cgi?id=390234 --- Comment #1 from Pieter David <pieter.da...@gmail.com> --- Created attachment 110515 --> https://bugs.kde.org/attachment.cgi?id=110515=edit output of qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390234] New: kwin_wayland crash when disabling an output
https://bugs.kde.org/show_bug.cgi?id=390234 Bug ID: 390234 Summary: kwin_wayland crash when disabling an output Product: kwin Version: 5.12.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pieter.da...@gmail.com Target Milestone: --- When I disable my laptop screen (with a VGA monitor attached, enabled, and set as primary output) through the kscreen kcm, the kwin_wayland process crashes with this stacktrace: Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib/startp'. Program terminated with signal SIGABRT, Aborted. #0 0x7f3df4ab3860 in raise () from /usr/lib/libc.so.6 [Current thread is 1 (Thread 0x7f3df7f226c0 (LWP 1294))] (gdb) bt #0 0x7f3df4ab3860 in raise () at /usr/lib/libc.so.6 #1 0x7f3df4ab4e48 in abort () at /usr/lib/libc.so.6 #2 0x7f3df4ec4d57 in __gnu_cxx::__verbose_terminate_handler() () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #3 0x7f3df4ec28c6 in __cxxabiv1::__terminate(void (*)()) (handler=) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47 #4 0x7f3df4ec179a in __cxa_call_terminate(_Unwind_Exception*) (ue_header=ue_header@entry=0x557fdfccfad0) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_call.cc:54 #5 0x7f3df4ec2189 in __cxxabiv1::__gxx_personality_v0(int, _Unwind_Action, _Unwind_Exception_Class, _Unwind_Exception*, _Unwind_Context*) (version=, actions=, exception_class=5138137972254386944, ue_header=0x557fdfccfad0, context=) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_personality.cc:676 #6 0x7f3ded5f2ca3 in _Unwind_RaiseException_Phase2 (exc=exc@entry=0x557fdfccfad0, context=context@entry=0x7ffef10008e0) at /build/gcc/src/gcc/libgcc/unwind.inc:62 #7 0x7f3ded5f34ce in _Unwind_Resume (exc=0x557fdfccfad0) at /build/gcc/src/gcc/libgcc/unwind.inc:230 #8 0x7f3df5685992 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #9 0x7f3df56dbe36 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7f3ddf5945de in QUnixEventDispatcherQPA::processEvents(QFlags) () at /usr/lib/qt/plugins/platforms/KWinQpaPlugin.so #11 0x7f3ddc9de31b in KWin::DrmBackend::~DrmBackend() (this=0x557fdfd0eb30, __in_chrg=) at /home/pieter/builds/kwin/src/kwin-5.12.0/plugins/platforms/drm/drm_backend.cpp:91 #12 0x7f3ddc9de67a in KWin::DrmBackend::~DrmBackend() (this=0x557fdfd0eb30, __in_chrg=) at /home/pieter/builds/kwin/src/kwin-5.12.0/plugins/platforms/drm/drm_backend.cpp:99 #13 0x7f3df56774f7 in () at /usr/lib/libQt5Core.so.5 #14 0x7f3df56799c6 in () at /usr/lib/libQt5Core.so.5 #15 0x7f3df4ab67b2 in __cxa_finalize () at /usr/lib/libc.so.6 #16 0x7f3df5465034 in () at /usr/lib/libQt5Core.so.5 #17 0x7ffef1001470 in () #18 0x7f3df7da7af3 in _dl_fini () at /lib64/ld-linux-x86-64.so.2 I am using kwin 5.12.0, rebuilt locally using the Arch PKGBUILD to add debug symbols (I can do the same with Qt if needed, I am using 5.10.0). Attached also the output of `qdbus org.kde.KWin /KWin supportInformation` - please let me know if you need any more information. Thanks in advance! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 377865] (De)Activating monitors on wayland does not work
https://bugs.kde.org/show_bug.cgi?id=377865 Pieter David <pieter.da...@gmail.com> changed: What|Removed |Added CC||pieter.da...@gmail.com --- Comment #6 from Pieter David <pieter.da...@gmail.com> --- I have the same issue, on Arch Linux (Plasma 5.10.3, frameworks 5.35.0, Qt 5.9.0): when disabling my laptop screen and making the external (VGA) screen the main output, the laptop screen does not turn off, but shows the same output as the external screen (for the part that is visible on the smaller screen). Please let me know if more information is needed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375081] Plasmashell crashes with plasmawayland session on startup
https://bugs.kde.org/show_bug.cgi?id=375081 Pieter David <pieter.da...@gmail.com> changed: What|Removed |Added CC||pieter.da...@gmail.com --- Comment #3 from Pieter David <pieter.da...@gmail.com> --- I am seeing something very similar (black screen with mouse pointer, sometimes some of my autostart programs (e.g. owncloud sync) start, if I close those, right-click or press the krunner keyboard shortcut krunner crashes and ~1min later plasmashell as well), so I think it's the same problem. I recompiled qt5-base, qt5-wayland (5.8 RC) and plasma-workspace (5.8.95) with debug symbols. For krunner I got this stacktrace from journalctl (demangled with c++filt): Stack trace of thread 1254: #0 0x7f61295a304f raise (libc.so.6) #1 0x7f612d8ba7d6 KCrash::defaultCrashHandler(int) (libKF5Crash.so.5) #2 0x7f61295a30b0 __restore_rt (libc.so.6) #3 0x7f6127f26289 wl_proxy_marshal (libwayland-client.so.0) #4 0x7f6119e3d259 QtWayland::wl_surface::destroy() (libQt5WaylandClient.so.5) #5 0x7f6119e23bfb QtWaylandClient::QWaylandWindow::reset() #6 0x7f6119e26ff8 QtWaylandClient::QWaylandWindow::setVisible(bool) #7 0x7f612a4756cc QWindow::setVisible(bool) (libQt5Gui.so.5) #8 0x00406baa main (krunner) #9 0x7f6129590291 __libc_start_main (libc.so.6) #10 0x00406cda _start (krunner) for plasmashell only this: Stack trace of thread 1256: #0 0x7f15fa16004f n/a (n/a) (libwayland-client is provided by the wayland 1.12.0-1 package) -- You are receiving this mail because: You are watching all bug changes.
