You are not logged in.
$journalctl -p 3 -xb
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
Pass -q to turn off this notice.
-- Logs begin at Thu 2020-04-09 17:49:45 EEST, end at Thu 2020-10-08 18:56:04 EEST. --
Oct 08 16:16:23 www.babaliaris systemd-coredump[861]: Process 639 (kmixctrl) of user 1000 dumped core.
Stack trace of thread 639:
#0 0x0000000000000000 n/a (n/a + 0x0)
░░ Subject: Process 639 (kmixctrl) dumped core
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ Documentation: man:core(5)
░░
░░ Process 639 (kmixctrl) crashed and dumped core.
░░
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.I'm not really sure about what kmixctrl is, but it seems to be a core functionality of systemd.
Should I do anything or ignore it? My system seems to work fine.
Last edited by babaliaris (2020-10-10 05:58:35)
Github Account: github.com/babaliaris
Arch General Guidelines![]()
Favourite Distro: archlinux.org
Arch Wiki![]()
Offline
coredumps are a core functionality of systemd but that doesn't have any relation to kmixctrl crashing.
In any case, the crash has no real world relevance, if you care about background information and how to prevent it from happening see https://bbs.archlinux.org/viewtopic.php?id=258412
Offline
In other words, something else causes this crash?
Github Account: github.com/babaliaris
Arch General Guidelines![]()
Favourite Distro: archlinux.org
Arch Wiki![]()
Offline
What "something else" ? kmix crashes, because of a bug in its sound restoration behaviour (kmixctrl is a audio mixer application for KDE, nothing to do with systemd). The restoration crash is irrelevant in so far that it wants to restore volumes, but if you use pulseaudio pulseaudio will do that anyway.
That systemd logs the fact that this crash happens and gives you the possibility to investigate why it happens is a functionality of systemd that it provides for every application that runs on your system. Systemd is fine, it's coredump handler is fine, kmix does have a crash but the fallout of it is irrelevant.
If you wonder what coredumps are, maybe reading https://wiki.archlinux.org/index.php/Core_dump will help you.
Edit: FWIW the bug I've had in my head that lead to a kmix crash should be fixed, so this might indeed be something new. But kmix is often not actively relevant anymore if you e.g. use plasma-pa anyway.
Last edited by V1del (2020-10-08 14:38:01)
Offline
I understand. Thank you for your answer! I'll read about core-dumps but I think I already getting it. Since systemd is the init process anything that crashes is being reported through it.
As the hint says: This is probably a programmatic bug and should be reported, and from what I read from the link that you gave me, it's actually a segmentation fault.
Probably not something I can do about it since it has to be fixed by the developers.
Last edited by babaliaris (2020-10-08 16:24:28)
Github Account: github.com/babaliaris
Arch General Guidelines![]()
Favourite Distro: archlinux.org
Arch Wiki![]()
Offline
I also got this crash on my new KDE install.
Process 812 (kmixctrl) of user 1000 dumped core.
Stack trace of thread 812:
#0 0x0000000000000000 n/a (n/a + 0x0)
░░ Subject: Process 812 (kmixctrl) dumped core
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/l … temd-devel
░░ Documentation: man:core(5)
░░
░░ Process 812 (kmixctrl) crashed and dumped core.
░░
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
So, apparently this should be ignored?
Last edited by maboleth (2020-11-06 14:52:50)
Offline