[kontact] [Bug 472867] New: Crash While Removing IMAP Sending Accounts
https://bugs.kde.org/show_bug.cgi?id=472867 Bug ID: 472867 Summary: Crash While Removing IMAP Sending Accounts Classification: Applications Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: joh...@member.fsf.org Target Milestone: --- Application: kontact (5.23.3 (23.04.3)) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.4.6-200.fc38.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: I was removing old IMAP account for sending, so that only the new one I created would be there. A strange thing I did notice is that just prior to the crash, new IMAP entries started to appear. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7fdda5f33700 in MailTransport::TransportManagementWidgetPrivate::removeClicked() () from /usr/lib64/libKPim5MailTransport.so.5 #5 0x7fddf3ee8461 in void doActivate(QObject*, int, void**) () from /usr/lib64/libQt5Core.so.5 #6 0x7fddf4ca9c64 in QAbstractButton::clicked(bool) () from /usr/lib64/libQt5Widgets.so.5 #7 0x7fddf4ca9eef in QAbstractButtonPrivate::emitClicked() () from /usr/lib64/libQt5Widgets.so.5 #8 0x7fddf4cab850 in QAbstractButtonPrivate::click() () from /usr/lib64/libQt5Widgets.so.5 #9 0x7fddf4caba58 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #10 0x7fddf4bf3688 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #11 0x7fddf4baeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x7fddf4bb7456 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7fddf3eb4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #14 0x7fddf4bb56a4 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7fddf4c0d1a9 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7fddf4c1072f in QWidgetWindow::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7fddf4baeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7fddf3eb4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #19 0x7fddf436cc6b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #20 0x7fddf434acfc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib64/libQt5Gui.so.5 #21 0x7fddd811b4d6 in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQt5XcbQpa.so.5 #22 0x7fddea91348c in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #23 0x7fddea971648 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #24 0x7fddea910b13 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x7fddf3f06729 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #26 0x7fddf3eb2b4b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #27 0x7fddf3ebaddb in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #28 0x55b4840f3669 in main (argc=, argv=) at /usr/src/debug/kontact-23.04.3-2.fc38.x86_64/src/main.cpp:216 [Inferior 1 (process 6112) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kwin] [Bug 472827] Plasma crashed while Firefox and Telegram were open (kwin_screencast -> pipewire => crash)
https://bugs.kde.org/show_bug.cgi?id=472827 Nicolas Fella changed: What|Removed |Added Assignee|kdepim-bugs@kde.org |kwin-bugs-n...@kde.org Product|Akonadi |kwin CC||nicolas.fe...@gmx.de Component|server |wayland-generic --- Comment #11 from Nicolas Fella --- What you are seeing is kwin_wayland crashing. The crash report for Akonadi is misleading/not interesting. Could you please follow https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl to get a backtrace for kwin_wayland? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open (kwin_screencast -> pipewire => crash)
https://bugs.kde.org/show_bug.cgi?id=472827 --- Comment #10 from Ben P --- Re screencasts, I've just remembered that Firefox has been flaky with screensharing for a couple of days. Never had that problem before. Currently can't repo to get an exact error but the gist is "error: kwin_screencast can't create pipewire stream". Could be related..? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472861] Crash after click onto folders in Kmail
https://bugs.kde.org/show_bug.cgi?id=472861 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472861] Crash after click onto folders in Kmail
https://bugs.kde.org/show_bug.cgi?id=472861 --- Comment #1 from Piotr Mierzwinski --- Created attachment 160659 --> https://bugs.kde.org/attachment.cgi?id=160659&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472861] New: Crash after click onto folders in Kmail
https://bugs.kde.org/show_bug.cgi?id=472861 Bug ID: 472861 Summary: Crash after click onto folders in Kmail Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: piotr.mierzwin...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.24.40 (23.11.40)) Qt Version: 6.6.0 Frameworks Version: 5.240.0 Operating System: Linux 5.19.0-50-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.27.80 [CoredumpBackend] -- Information about the crash: I clicked onto folders in KMail. I have 2 email boxes. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140594462582336) at ./nptl/pthread_kill.c:44 #7 __pthread_kill_internal (signo=6, threadid=140594462582336) at ./nptl/pthread_kill.c:78 #8 __GI___pthread_kill (threadid=140594462582336, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #9 0x7fdebc842476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #10 0x7fdebc8287f3 in __GI_abort () at ./stdlib/abort.c:79 Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open (kwin_screencast -> pipewire => crash)
https://bugs.kde.org/show_bug.cgi?id=472827 --- Comment #9 from FreeLibre --- > when I tried to switch from Firefox to VSCode Same. A few seconds after I switched between Firefox to Telegram desktop. Plasma crashed and suddenly returned me to the desktop; all programs were closed, but no login was required. (Sorry for sending multiple messages in a row, I found no "edit message" button). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open (kwin_screencast -> pipewire => crash)
https://bugs.kde.org/show_bug.cgi?id=472827 FreeLibre changed: What|Removed |Added Summary|Plasma crashed while|Plasma crashed while |Firefox and Telegram were |Firefox and Telegram were |open|open (kwin_screencast -> ||pipewire => crash) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 --- Comment #8 from FreeLibre --- I've been able to reproduce this only using Firefox and Telegram desktop (and no audios were playing at the time). Seeing that the crash might be related to kwin_screencast, I assure you that there was no screencasting going on as far as I'm aware. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 --- Comment #7 from FreeLibre --- While the Akonadi report might not be useful, here's the logs from journalctl right around the crash, it seems Pipewire is also involved (it happens on 18:22:53): Jul 31 18:15:36 fedora pipewire[1442]: mod.client-node: 0x56053427c190: unknown peer 0x5605343d58d0 fd:101 Jul 31 18:16:13 fedora plasmashell[1569]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 31 18:16:13 fedora plasmashell[1569]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" Jul 31 18:18:12 fedora pipewire[1442]: mod.client-node: 0x5605348449d0: unknown peer 0x56053436cae0 fd:52 Jul 31 18:18:42 fedora plasmashell[1569]: kpipewire_logging: PipeWire remote error: -2 unknown resource 3 op:4 Jul 31 18:18:42 fedora plasmashell[1569]: kpipewire_logging: PipeWire remote error: -2 unknown resource 3 op:4 Jul 31 18:18:42 fedora plasmashell[1569]: kpipewire_logging: PipeWire remote error: -2 unknown resource 3 op:4 Jul 31 18:18:42 fedora plasmashell[1569]: kpipewire_logging: PipeWire remote error: -2 unknown resource 3 op:4 Jul 31 18:18:42 fedora plasmashell[1569]: kpipewire_logging: PipeWire remote error: -2 unknown resource 3 op:4 Jul 31 18:18:42 fedora plasmashell[1569]: kpipewire_logging: PipeWire remote error: -2 unknown resource 3 op:7 Jul 31 18:18:54 fedora pipewire[1442]: mod.client-node: 0x5605343d52b0: unknown peer 0x560534370140 fd:52 Jul 31 18:20:36 fedora pipewire[1442]: mod.client-node: 0x56053427c230: unknown peer 0x560534363170 fd:97 Jul 31 18:20:36 fedora pipewire[1442]: mod.client-node: 0x56053427c230: unknown peer 0x560534363170 fd:97 Jul 31 18:21:06 fedora pipewire[1442]: mod.client-node: 0x5605343d52b0: unknown peer 0x56053436cae0 fd:92 Jul 31 18:21:07 fedora kwin_wayland[1437]: kwin_screencast: Dropping a screencast frame because the compositor is slow Jul 31 18:21:37 fedora pipewire[1442]: mod.client-node: 0x560534843cb0: unknown peer 0x56053436cae0 fd:52 Jul 31 18:22:44 fedora kwin_wayland[1437]: kwin_screencast: Dropping a screencast frame because the compositor is slow Jul 31 18:22:45 fedora kwin_wayland[1437]: kwin_screencast: Dropping a screencast frame because the compositor is slow Jul 31 18:22:47 fedora pipewire[1442]: mod.client-node: 0x5605343655b0: unknown peer 0x56053436cae0 fd:52 Jul 31 18:22:47 fedora pipewire[1442]: mod.client-node: 0x5605343650f0: unknown peer 0x560534370140 fd:91 Jul 31 18:22:47 fedora kwin_wayland[1437]: kwin_screencast: Dropping a screencast frame because the compositor is slow Jul 31 18:22:48 fedora pipewire[1442]: mod.client-node: 0x560534371fd0: unknown peer 0x560534363170 fd:129 Jul 31 18:22:53 fedora kwin_wayland[1437]: kwin_screencast: Dropping a screencast frame because the compositor is slow Jul 31 18:22:53 fedora audit[1437]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1437 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 Jul 31 18:22:53 fedora kernel: kwin_wayland[1437]: segfault at 7ff373353284 ip 7ff3cbea10e1 sp 7fff60b277f0 error 6 in libpipewire-0.3.so.0.376.0[7ff3cbe4d000+63000] likely on CPU 0 (core 0, socket 0) Jul 31 18:22:53 fedora kernel: Code: ca 01 00 48 8d 15 f7 b5 01 00 e8 8a d5 fa ff 59 5e e9 74 ff ff ff 0f 1f 00 f3 0f 1e fa 53 48 8b 46 28 48 89 fb 48 85 c0 74 05 83 68 04 01 8b 46 24 a8 02 0f 85 07 01 00 00 8b 8b 18 10 00 00 Jul 31 18:22:53 fedora audit: BPF prog-id=82 op=LOAD Jul 31 18:22:53 fedora audit: BPF prog-id=83 op=LOAD Jul 31 18:22:53 fedora audit: BPF prog-id=84 op=LOAD Jul 31 18:22:53 fedora systemd[1]: Started systemd-coredump@1-12673-0.service - Process Core Dump (PID 12673/UID 0). ░░ Subject: A start job for unit systemd-coredump@1-12673-0.service has finished successfully -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 --- Comment #6 from Lubo Ivanovic --- Created attachment 160655 --> https://bugs.kde.org/attachment.cgi?id=160655&action=edit New crash information added by DrKonqi akonadiserver (5.22.3 (22.12.3)) using Qt 5.15.9 some terminator windows open (2 or 3? - not sure), 2 instances dolphin windows, vivaldi open; crash occured, when minimizing one of the dolphin instances; working on 4k screen connected using usb c; -- Backtrace (Reduced): #4 0x564e9291529b in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7ff853ac8264 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7ff853a9d5fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7ff853aa0984 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7ff853aeec27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 Lubo Ivanovic changed: What|Removed |Added CC||lubo...@googlemail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 460687] "Forward To" option missing from Filter Actions
https://bugs.kde.org/show_bug.cgi?id=460687 --- Comment #3 from Damian C --- (In reply to Laurent Montel from comment #2) > We have "redirect" action. > so what is missing ? I don't think Redirect is the same as Forward. If you look at the options presented here: https://docs.kde.org/stable5/en/kmail/kmail2/filters.html Forward and Redirect are two distinct options. Redirect: "This will redirect the message as-is to another email address.". I think it attempts to re route the message without re sending it as a message sent by you, but I'm not sure. While forward is the same as right clicking the message and re send it from your account as if right clicking and selecting forward - inline. Sending the messag efrom your account, adding the "Fwd:" prefix to the subject. So yeah, Forward To is literally missing. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 --- Comment #5 from wi...@posteo.net --- Created attachment 160651 --> https://bugs.kde.org/attachment.cgi?id=160651&action=edit New crash information added by DrKonqi akonadiserver (5.22.3 (22.12.3)) using Qt 5.15.9 Crashed for me when Firefox and VSCode opened when I tried to switch from Firefox to VSCode -- Backtrace (Reduced): #4 0x55b1ab5aa29b in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f7552ac8264 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f7552a9d5fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f7552aa0984 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f7552aeec27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 wi...@posteo.net changed: What|Removed |Added CC||wi...@posteo.net -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 472833] Akonadi tasks take up 25% CPU sitting idle
https://bugs.kde.org/show_bug.cgi?id=472833 tnem...@free.fr changed: What|Removed |Added Component|general |general Product|Akonadi |kmail2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472833] Akonadi tasks take up 25% CPU sitting idle
https://bugs.kde.org/show_bug.cgi?id=472833 --- Comment #7 from tnem...@free.fr --- Hum. In fine, it wasn't akonadi but KMail. Killing kmail stops the CPU hog while akonadi keeps working. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 --- Comment #4 from Ben P --- Similar versions to Alexia W, also running VS Code and Firefox, but didn't see that KWallet error on restart VSCode. Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.4.4-100.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.27.4 [KCrashBackend] -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 --- Comment #3 from Alexia W --- (In reply to Alexia W from comment #2) > In my case Telegram wasn't open. Firefox, Spotify, Thunderbird, and Proton > Mail Bridge were. I'd forgotten I was also running VSCode. Upon launching it after the crash, the following error was displayed: > You're running in a KDE environment but the OS keyring is not available for > encryption. Ensure you have kwallet running. Similar issues arose with Proton Mail Bridge and kwallet. Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.4.6-100.fc37.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 Alexia W changed: What|Removed |Added CC||ale...@duck.com --- Comment #2 from Alexia W --- In my case Telegram wasn't open. Firefox, Spotify, Thunderbird, and Proton Mail Bridge were. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472833] Akonadi tasks take up 25% CPU sitting idle
https://bugs.kde.org/show_bug.cgi?id=472833 --- Comment #6 from tnem...@free.fr --- Obviously, when I start KMail after, it asks to restart akonadi... And there it is again, taking up to 25% CPU... -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472833] Akonadi tasks take up 25% CPU sitting idle
https://bugs.kde.org/show_bug.cgi?id=472833 --- Comment #5 from tnem...@free.fr --- Created attachment 160647 --> https://bugs.kde.org/attachment.cgi?id=160647&action=edit Normal CPU load after killing akonadi. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472833] Akonadi tasks take up 25% CPU sitting idle
https://bugs.kde.org/show_bug.cgi?id=472833 --- Comment #4 from tnem...@free.fr --- Created attachment 160646 --> https://bugs.kde.org/attachment.cgi?id=160646&action=edit CPU load a few seconds after killing akonadi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472833] Akonadi tasks take up 25% CPU sitting idle
https://bugs.kde.org/show_bug.cgi?id=472833 --- Comment #3 from tnem...@free.fr --- Created attachment 160645 --> https://bugs.kde.org/attachment.cgi?id=160645&action=edit How I kill akonadi I just click on "Close an application" (in red). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472833] Akonadi tasks take up 25% CPU sitting idle
https://bugs.kde.org/show_bug.cgi?id=472833 --- Comment #2 from tnem...@free.fr --- Created attachment 160644 --> https://bugs.kde.org/attachment.cgi?id=160644&action=edit System monitor displaying akonadi It's in french... "Rappels d'agenda" means "Agenda Reminder" (something like that). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472833] Akonadi tasks take up 25% CPU sitting idle
https://bugs.kde.org/show_bug.cgi?id=472833 --- Comment #1 from tnem...@free.fr --- Created attachment 160643 --> https://bugs.kde.org/attachment.cgi?id=160643&action=edit List of akonadi processes before killing them -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472833] New: Akonadi tasks take up 25% CPU sitting idle
https://bugs.kde.org/show_bug.cgi?id=472833 Bug ID: 472833 Summary: Akonadi tasks take up 25% CPU sitting idle Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tnem...@free.fr CC: c...@carlschwan.eu Target Milestone: --- Created attachment 160642 --> https://bugs.kde.org/attachment.cgi?id=160642&action=edit CPU load before killing akonadi SUMMARY When running idle I've noticed that recently, after a few upgrades in QT/plasma packages, my CPU fan was blowing faster than before. The CPU monitor showed me that there was a permanent CPU load of 25% which wasn't there before. After investigating, I found the culprit : akonadi and all its tasks where busying my system, even after several hours, while all the processing of startup, mails reception, had already been done. File indexing is deactivated on my system. STEPS TO REPRODUCE 1. Log in a session that has kmail configured with a few accounts and wait a few minutes 2. Look at the CPU monitor OBSERVED RESULT The CPU load is way too high... EXPECTED RESULT The CPU load should be around 1 or 2 %... SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.4.0-1-amd64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-7567U CPU @ 3.50GHz Memory: 31.2 Gio of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics 650 Manufacturer: Intel Corporation Product Name: NUC7i7BNH System Version: J31153-308 ADDITIONAL INFORMATION I've taken a few screenshots and `ps aux` outputs... -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 --- Comment #1 from Ben P --- Created attachment 160639 --> https://bugs.kde.org/attachment.cgi?id=160639&action=edit New crash information added by DrKonqi akonadiserver (5.22.3 (22.12.3)) using Qt 5.15.9 Like OP, nothing unusual was happening. Only Firefox and VSCode windows were active. Nothing different from 90%+ of my KDE usage. -- Backtrace (Reduced): #4 0x557552b0429b in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f98d7cc8264 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f98d7c9d5fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f98d7ca0984 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f98d7ceec27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472827] Plasma crashed while Firefox and Telegram were open
https://bugs.kde.org/show_bug.cgi?id=472827 Ben P changed: What|Removed |Added CC||b...@bpulse.co.uk -- You are receiving this mail because: You are the assignee for the bug.
