On 12/07/2024 11:56, Tomoaki AOKI wrote:
On Fri, 12 Jul 2024 10:20:19 +0200
Miroslav Lachman <000.f...@quip.cz> wrote:
[..]
Something similar happens to me, but when logging into KDE Plasma.
Sometimes it happens that desktop applications that start from a saved
session (Firefox, Thunderbird, Telegram, Signal...) start loading and
then everything crashes. The login screen reappears and when I log in
again, everything crashes again until I restart the machine. The machine
gets into this state randomly, about once a week.
Jul 5 12:24:52 xxx kernel: pid 1647 (packagekitd), jid 0, uid 0: exited
on signal 11 (core dumped)
Jul 5 12:25:28 xxx kernel: pid 1897 (kalarm), jid 0, uid 1001: exited
on signal 6 (core dumped)
Jul 5 12:25:36 xxx kernel: pid 1467 (Xorg), jid 0, uid 0: exited on
signal 6 (core dumped)
Jul 5 12:25:37 xxx kernel: pid 1772 (signal-desktop), jid 0, uid 1001:
exited on signal 5 (core dumped)
Jul 5 12:25:39 xxx pulseaudio[1630]: [] core-util.c: Failed to create
secure directory (/var/run/user/1001/pulse): No such file or directory
Jul 5 12:25:40 xxx kernel: pid 1776 (audacious), jid 0, uid 1001:
exited on signal 6 (core dumped)
Jul 5 12:25:41 xxx kernel: pid 1915 (drkonqi), jid 0, uid 1001: exited
on signal 6 (core dumped)
Jul 5 12:25:42 xxx kernel: pid 1914 (kwin_x11), jid 0, uid 1001: exited
on signal 6 (core dumped)
My system is 13.3-p3 amd64.
Kind regards
Miroslav Lachman
What comes in my mind is...
*Hardware problem
*Main memory (including memory slot)
*Dedicated grhaphics memories, if any
(seems that X-related processes are crashing)
*Power failures / instabilities
*Software problem
*Mis-alignments caused by ASLR or something
*Bitten by uncommon bugs in fundamental libraries like libc,
xcb, glib,...
*Not sure it's MFC'ed to 13.x or not, but missingly determined
instruction sets for SIMD libc or something alike.
I also thought about the memory modules (even though they are ECC), but
a few days ago I replaced them with 4 other modules from the server and
the problem persisted. Of course it could be anything else (graphic
card, power supply, etc.), but it's strange that it only happens after
booting when logging into KDE. When everything crashes and the login
screen reappears, I try to log in again, everything crashes again
(usually in the part where Signal Desktop starts, but I don't know if
it's related). I can repeat this 5 or 10 times, but until I reboot, KDE
doesn't fully start. When I reboot, the machine runs all day, even for
several days at a time.
It also happens that the screenlocker crashes
Jul 11 17:32:16 xxx kernel: pid 6487 (kscreenlocker_greet), jid 0, uid
1001: exited on signal 11
Jul 11 17:32:16 xxx kernel: pid 6489 (kscreenlocker_greet), jid 0, uid
1001: exited on signal 11
Then I have to log in as root via Ctrl+Alt+F2 and run: ck-unlock-session
Session1
Otherwise, when KDE is running, all applications work without crashing.
Translated with DeepL.com (free version)
Kind regards
Miroslav Lachman
