You are not logged in.

#1 2018-11-26 16:58:13

melwyrm
Member
Registered: 2018-11-26
Posts: 4

Random freeze of KDE - no response

Hello,
I experience this issue since some weeks and it's quite annoying. My system is Arch Linux with KDE as DE, all packages are up to date.
Completely random does my system freeze without any response - it's not even responding to SysRQ shortcuts (and yes, they are enabled). Nothing. I always have to do a hard reset by pressing the reset button. The issue is (that's at least my guess) application independet since I already experienced it in Firefox, QtCreator, Kate and some other applications.

journalctl tells me:

Nov 26 15:42:41 arch-linux systemd[926]: Started Accessibility services bus.
Nov 26 15:43:34 arch-linux systemd-coredump[2268]: Process 1123 (baloo_file) of user 1000 dumped core.
                                                   
                                                   Stack trace of thread 1334:
                                                   #0  0x00007ff37b42dd7f raise (libc.so.6)
                                                   #1  0x00007ff37bff96cf _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5)
                                                   #2  0x00007ff37b42de00 __restore_rt (libc.so.6)
                                                   #3  0x00007ff37a2955f4 mdb_midl_xmerge (liblmdb.so)
                                                   #4  0x00007ff37a28cc8f n/a (liblmdb.so)
                                                   #5  0x00007ff37a28eda4 n/a (liblmdb.so)
                                                   #6  0x00007ff37a28f1a9 n/a (liblmdb.so)
                                                   #7  0x00007ff37a2926e9 mdb_cursor_put (liblmdb.so)
                                                   #8  0x00007ff37a294adb mdb_put (liblmdb.so)
                                                   #9  0x00007ff37beddf80 _ZN5Baloo10PositionDB3putERK10QByteArrayRK7QVectorINS_12PositionInfoEE (libKF5BalooEngine.so.5)
                                                   #10 0x00007ff37bef1b40 _ZN5Baloo16WriteTransaction6commitEv (libKF5BalooEngine.so.5)
                                                   #11 0x00007ff37bee7ab3 _ZN5Baloo11Transaction6commitEv (libKF5BalooEngine.so.5)
                                                   #12 0x000055dc8f86290f n/a (baloo_file)
                                                   #13 0x00007ff37b989e11 n/a (libQt5Core.so.5)
                                                   #14 0x00007ff37b991f65 n/a (libQt5Core.so.5)
                                                   #15 0x00007ff37a4f7a9d start_thread (libpthread.so.0)
                                                   #16 0x00007ff37b4f1b23 __clone (libc.so.6)
                                                   
                                                   Stack trace of thread 1135:
                                                   #0  0x00007ff37b4e6c21 __poll (libc.so.6)
                                                   #1  0x00007ff3799cbee0 n/a (libglib-2.0.so.0)
                                                   #2  0x00007ff3799cbfce g_main_context_iteration (libglib-2.0.so.0)
                                                   #3  0x00007ff37bb92fe4 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
                                                   #4  0x00007ff37bb3e8cc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                                                   #5  0x00007ff37b987eb9 _ZN7QThread4execEv (libQt5Core.so.5)
                                                   #6  0x00007ff37bf11ba6 n/a (libQt5DBus.so.5)
                                                   #7  0x00007ff37b991f65 n/a (libQt5Core.so.5)
                                                   #8  0x00007ff37a4f7a9d start_thread (libpthread.so.0)
                                                   #9  0x00007ff37b4f1b23 __clone (libc.so.6)
                                                   
                                                   Stack trace of thread 1123:
                                                   #0  0x00007ff37b4e6c21 __poll (libc.so.6)
                                                   #1  0x00007ff3799cbee0 n/a (libglib-2.0.so.0)
                                                   #2  0x00007ff3799cbfce g_main_context_iteration (libglib-2.0.so.0)
                                                   #3  0x00007ff37bb92fe4 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
                                                   #4  0x00007ff37bb3e8cc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                                                   #5  0x00007ff37bb46bc6 _ZN16QCoreApplication4execEv (libQt5Core.so.5)
                                                   #6  0x000055dc8f8543f4 n/a (baloo_file)
                                                   #7  0x00007ff37b41a223 __libc_start_main (libc.so.6)
                                                   #8  0x000055dc8f85459e _start (baloo_file)
Nov 26 17:04:46 arch-linux dbus-daemon[964]: [session uid=1000 pid=964] Activating service name='org.kde.runners.baloo' requested by ':1.25' (uid=1000 pid=1127 comm="/usr/bin/plasmashell ")
Nov 26 17:04:46 arch-linux dbus-daemon[964]: [session uid=1000 pid=964] Successfully activated service 'org.kde.runners.baloo'
-- Reboot --

Does anyone have some kind of idea what may be the cause of my issue?
If you need more information, just ask.

Thanks!

Offline

#2 2018-11-26 17:21:47

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 1,096

Re: Random freeze of KDE - no response

While baloo_file is an annoying nuisance with KDE, I doubt it's possible to cripple your system like that, so this may have nothing to do with your system freezing. To eliminate it as a possibility, have you tried disabling baloo?

Offline

#3 2018-11-26 17:28:06

melwyrm
Member
Registered: 2018-11-26
Posts: 4

Re: Random freeze of KDE - no response

Not yet.
However, the freezes are completely random and I am unable to reproduce them. So there is the possibility that there won't be freezes for days although that's not the real issue.
But I'll give it a try.

Offline

#4 2018-12-22 22:38:50

melwyrm
Member
Registered: 2018-11-26
Posts: 4

Re: Random freeze of KDE - no response

Hi, I'm back, had another freeze today.
This time nothing, what could have caused the freeze, is in the log files. baloo is still disabled.
Kernel:  4.19.4 (I'm currently updating it). But since I have the issue for months, I don't think kernel 4.19.11 fixed it.
Does nobody else experience these freezes?

Offline

#5 2018-12-23 08:52:59

Caspian
Member
Registered: 2007-05-22
Posts: 263

Re: Random freeze of KDE - no response

I'm having this exact issue. krunner freezeing, graphic glitches, chromium regularly freezing. I've noticed that all of the freezing always occurs on my laptop monitor (I have a dual monitor setup, laptop monitor + external, both of them 4K panels. Using only integrated intel card and have nvidia disabled).
I had no issues on kernels prior to 4.19.x. I don't have issues with LTS kernel now as well, so it must be something kernel related. The problem is that 4.19 is the next LTS release if I'm not mistaking and once this propagates in Arch, my system will become completely unusable.
Logs don't show anything for me except baloo exception.

Offline

#6 2018-12-23 16:30:11

melwyrm
Member
Registered: 2018-11-26
Posts: 4

Re: Random freeze of KDE - no response

Another freeze with kernel 4.19.11. No log entries.
I have a setup with an AMD RX560 graphic card and two monitors.
For me, the issue also existed with kernel versions <4.19.

Offline

#7 2018-12-23 17:33:07

seth
Member
Registered: 2012-09-03
Posts: 50,924

Re: Random freeze of KDE - no response

@Caspian, I'm not sure whether you experience the same as OP, which sounds pretty much like a kernel panic while you seem to perceive userspace issues?
(Might still be related)

https://wiki.archlinux.org/index.php/Ge … nel_panics
You can try to run "dmesg -w" in a terminal emulator (probably w/o compositing) and wait for the panic, you *might* get some errors fired before that *could* provide leads for further investigation.
Other than that, kernel panics are a PITA to investigate :-(

Offline

#8 2018-12-23 20:27:21

Maniaxx
Member
Registered: 2014-05-14
Posts: 738

Re: Random freeze of KDE - no response

Set up a SSH daemon. The kernel might survive some crashes.


sys2064

Offline

Board footer

Powered by FluxBB