Bug 358467 - on session start mysqld goes into 100% CPU and is not killable
Summary: on session start mysqld goes into 100% CPU and is not killable
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 1.13.0
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-24 08:33 UTC by Matthias Apitz
Modified: 2026-01-28 21:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Apitz 2016-01-24 08:33:18 UTC
I have created a new user in FreeBSD, provided him a ~/.xinitrc which starts kde4 on 'startx'; the KDE environment is created fine and desktop comes up; but the isqld running for akonadi goes in 100% CPU loop and you can not kill it, not even with -9; a reboot ends up in PANIC because 1 vnode can not synced to disk;

The other (already existing account) works fine and does not show this problem;

Reproducible: Always

Steps to Reproduce:
1. create new user in FreeBSD system
2. create ~/.xinitrc as:
exec /usr/local/bin/startkde
3. login as this user and issue 'startx'
4. check mysql with 'ps ax | fgrep mysql'
5. try shutdwon, remains 1 unsync-able vnode
Comment 1 Justin Zobel 2021-03-09 05:47:06 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 2 aristsakas 2026-01-23 20:01:35 UTC
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Akonadi 25.12.0
Comment 3 cwo 2026-01-28 21:14:52 UTC
.