Random logout in Buster/KDE

Everything about X, Gnome, KDE, ... and everything running on it

Random logout in Buster/KDE

Postby NFT5 » 2019-08-05 10:52

I recently installed a clean Buster and chose the Plasma desktop.

I've been experiencing random logouts, usually when I click something with the mouse. That it's logging out, not restarting, leads me to think that it's display server related, but I'm not sure and can't find any consistent errors that would point to a single problem.

Google returns a few instances of similar problems, usually on Mint (not that that's relevant, I think) but no consistent answers.

So, I'm looking for some ideas on where to look to solve the problem.

Code: Select all
chris@BOSSDESK:~$ inxi
CPU: 6-Core AMD FX-6300 (-MCP-) speed/min/max: 1405/1400/3500 MHz Kernel: 4.19.0-5-amd64 x86_64 Up: N/A
Mem: 929.4/7945.1 MiB (11.7%) Storage: 1.58 TiB (43.5% used) Procs: 242 Shell: bash 5.0.3 inxi: 3.0.32


These CPUs do run hot but I have a big cooler fitted and it usually sits around 59C. Weather is cool here and other sensor temperatures range 18-26C. System gets cleaned every few months. Pretty sure it isn't a hardware problem anyway. No problem on this machine running Debian 8 or 9, MATE and XFCE respectively.

Error messages:
Code: Select all
root@BOSSDESK:~# grep -i error /var/log/messages
Aug  4 10:07:53 BOSSDESK sddm-greeter[1002]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  4 10:07:53 BOSSDESK sddm-greeter[1002]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  4 10:18:39 BOSSDESK org.kde.KScreen[1395]: kscreen.xcb.helper: Event Error:  147
Aug  4 10:43:03 BOSSDESK org.kde.kuiserver[1395]: kuiserver: Fatal IO error: client killed
Aug  4 10:43:03 BOSSDESK org.kde.kaccessibleapp[1395]: kaccessibleapp: Fatal IO error: client killed
Aug  4 10:43:03 BOSSDESK org.kde.kglobalaccel[1395]: The X11 connection broke (error 1). Did the X11 server die?
Aug  4 10:43:03 BOSSDESK org.kde.ActivityManager[1395]: The X11 connection broke (error 1). Did the X11 server die?
Aug  4 10:43:03 BOSSDESK org.kde.KScreen[1395]: The X11 connection broke (error 1). Did the X11 server die?
Aug  4 10:43:05 BOSSDESK sddm-greeter[3027]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  4 10:43:05 BOSSDESK sddm-greeter[3027]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  4 10:43:22 BOSSDESK org.kde.KScreen[1395]: kscreen.xcb.helper: Event Error:  147
Aug  4 10:43:23 BOSSDESK kernel: [ 2170.932130] traps: blueman-applet[3229] trap int3 ip:7f84737c3c75 sp:7ffc4726c470 error:0 in libglib-2.0.so.0.5800.3[7f847378b000+7e000]
Aug  4 10:43:27 BOSSDESK org.kde.kaccessibleapp[1395]: X Error: RenderBadPicture (invalid Picture parameter) 143
Aug  4 10:43:27 BOSSDESK org.kde.kaccessibleapp[1395]: X Error: BadWindow (invalid Window parameter) 3
Aug  4 10:43:27 BOSSDESK org.kde.kaccessibleapp[1395]: X Error: BadWindow (invalid Window parameter) 3
Aug  4 12:26:45 BOSSDESK kernel: [ 8372.452874] konqueror[5290]: segfault at 2 ip 00007f962b04fdff sp 00007ffd70716470 error 4 in libgcc_s.so.1[7f962b043000+11000]
Aug  4 19:14:31 BOSSDESK kernel: [32840.093578] Chrome_~dThread[18828]: segfault at 0 ip 00007f12faf09d9f sp 00007f12f936ead0 error 6 in libxul.so[7f12faef6000+3a3c000]
Aug  4 19:14:31 BOSSDESK kernel: [32840.094069] Chrome_~dThread[8700]: segfault at 0 ip 00007fb759b69d9f sp 00007fb757fcead0 error 6 in libxul.so[7fb759b56000+3a3c000]
Aug  4 19:14:31 BOSSDESK kernel: [32840.094185] Chrome_~dThread[14358]: segfault at 0 ip 00007fbecca99d9f sp 00007fbecaefead0 error 6 in libxul.so[7fbecca86000+3a3c000]
Aug  4 19:21:48 BOSSDESK kernel: [    4.489836] EXT4-fs (sda8): re-mounted. Opts: errors=remount-ro
Aug  4 19:21:52 BOSSDESK sddm-greeter[955]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  4 19:21:52 BOSSDESK sddm-greeter[955]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  4 19:21:58 BOSSDESK org.kde.KScreen[1193]: kscreen.xcb.helper: Event Error:  147
Aug  5 03:11:31 BOSSDESK sddm[900]: Authentication error: "Process crashed"
Aug  5 03:11:31 BOSSDESK sddm[900]: Authentication error: "Process crashed"
Aug  5 03:11:31 BOSSDESK org.kde.kglobalaccel[1193]: The X11 connection broke (error 1). Did the X11 server die?
Aug  5 03:11:31 BOSSDESK org.kde.kdeconnect[1193]: The X11 connection broke (error 1). Did the X11 server die?
Aug  5 03:11:31 BOSSDESK org.kde.KScreen[1193]: The X11 connection broke (error 1). Did the X11 server die?
Aug  5 03:11:31 BOSSDESK org.kde.ActivityManager[1193]: The X11 connection broke (error 1). Did the X11 server die?
Aug  5 03:11:31 BOSSDESK org.kde.kuiserver[1193]: kuiserver: Fatal IO error: client killed
Aug  5 03:11:31 BOSSDESK org.kde.kaccessibleapp[1193]: kaccessibleapp: Fatal IO error: client killed
Aug  5 03:12:41 BOSSDESK kernel: [    4.760507] EXT4-fs (sda8): re-mounted. Opts: errors=remount-ro
Aug  5 03:12:44 BOSSDESK sddm-greeter[972]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  5 03:12:44 BOSSDESK sddm-greeter[972]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  5 03:12:52 BOSSDESK org.kde.KScreen[1158]: kscreen.xcb.helper: Event Error:  147
Aug  5 08:56:42 BOSSDESK org.freedesktop.FileManager1[1158]: org.kde.kcoreaddons: Error loading plugin "akregatorplugin" "The shared library was not found."
Aug  5 08:56:54 BOSSDESK org.freedesktop.FileManager1[1158]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2723, resource id: 25166358, major code: 40 (TranslateCoords), minor code: 0
Aug  5 12:40:55 BOSSDESK org.freedesktop.FileManager1[1158]: The X11 connection broke (error 1). Did the X11 server die?
Aug  5 12:40:55 BOSSDESK org.kde.kuiserver[1158]: kuiserver: Fatal IO error: client killed
Aug  5 12:40:55 BOSSDESK org.kde.kaccessibleapp[1158]: kaccessibleapp: Fatal IO error: client killed
Aug  5 12:40:55 BOSSDESK org.kde.ActivityManager[1158]: The X11 connection broke (error 1). Did the X11 server die?
Aug  5 12:40:55 BOSSDESK org.kde.KScreen[1158]: The X11 connection broke (error 1). Did the X11 server die?
Aug  5 12:40:55 BOSSDESK org.kde.kglobalaccel[1158]: The X11 connection broke (error 1). Did the X11 server die?
Aug  5 12:40:57 BOSSDESK sddm-greeter[7447]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  5 12:40:57 BOSSDESK sddm-greeter[7447]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  5 12:41:06 BOSSDESK org.kde.KScreen[1158]: kscreen.xcb.helper: Event Error:  147
Aug  5 20:56:09 BOSSDESK sddm[907]: Authentication error: "Process crashed"
Aug  5 20:56:09 BOSSDESK sddm[907]: Authentication error: "Process crashed"
Aug  5 21:01:19 BOSSDESK kernel: [    4.725677] EXT4-fs (sda8): re-mounted. Opts: errors=remount-ro
Aug  5 21:01:23 BOSSDESK sddm-greeter[967]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  5 21:01:23 BOSSDESK sddm-greeter[967]: file:///usr/share/sddm/themes/harmony-v.2/Main.qml:71: TypeError: Cannot read property 'text' of undefined
Aug  5 21:01:35 BOSSDESK org.kde.KScreen[1208]: kscreen.xcb.helper: Event Error:  147
Aug  5 21:01:35 BOSSDESK org.kde.kwalletd[1208]: Error message was:  "org.freedesktop.DBus.Error.UnknownInterface" : " "No such interface 'org.kde.KUniqueApplication' at object path '/MainApplication'" "


Any ideas?
Last edited by NFT5 on 2019-08-05 13:10, edited 1 time in total.
User avatar
NFT5
 
Posts: 317
Joined: 2014-10-10 11:38
Location: Canberra, Australia

Re: Random logout in Buster/KDE

Postby ruwolf » 2019-08-05 12:41

I am afraid, that you would find help in e.g. forum.KDE.org: Workspace with higher probability than in this forum, because it seems to be KDE specific to me...
User avatar
ruwolf
 
Posts: 391
Joined: 2008-02-18 05:04
Location: Slovakia, Banovce nad Bebravou, Matice slovenskej 1260/4-7

Re: Random logout in Buster/KDE

Postby NFT5 » 2019-08-05 13:08

Thanks ruwolf. I was hoping to avoid joining yet another forum, but we'll see what responses I get here. There are quite a few using the KDE desktop.
User avatar
NFT5
 
Posts: 317
Joined: 2014-10-10 11:38
Location: Canberra, Australia

Re: Random logout in Buster/KDE

Postby Head_on_a_Stick » 2019-08-05 14:53

Check the systemd journal for errors and perhaps install the systemd-coredump package and see if coredumpctl(1) can find anything left by the killed X server — the output probably won't be useful to you (or me) but the developers may be able to get something from it.
User avatar
Head_on_a_Stick
 
Posts: 10377
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Random logout in Buster/KDE

Postby NFT5 » 2019-08-05 21:10

systemd-coredump installed.

Now wait for the next crash.......
User avatar
NFT5
 
Posts: 317
Joined: 2014-10-10 11:38
Location: Canberra, Australia

Re: Random logout in Buster/KDE

Postby efrpcabo » 2019-08-30 08:33

NFT5 wrote:systemd-coredump installed.

Now wait for the next crash.......

Did you find out the cause?
I'm experiencing the same thing in Debian Buster 10 XFCE, like I posted in this thread:
viewtopic.php?f=10&t=143439
User avatar
efrpcabo
 
Posts: 91
Joined: 2013-08-08 06:36

Re: Random logout in Buster/KDE

Postby NFT5 » 2019-08-31 01:58

As per PM, no, I haven't definitively found the cause.

I've installed the firmware packages and amd microcode (I have an AMD CPU). I've also (for what it was worth) changed where various USB plugs were plugged in on the back of the computer. This was something that was suggested in one of the searches I did, on the basis that some peripheral may have been causing some conflict with the controller that it was plugged in to. Seems a bit random, but i figured it can't hurt.

Also installed the coredumpctl package. Not that this will fix the problem, but may help with diagnosis in the future. The reports mean absolutely nothing to me but I keep them each time the crash/logout happens in the hope that they may be useful to someone else, i.e. a dev.

in case it was hardware I increased the threshold temperatures in the BIOS. My CPU and system temperatures are typically quite low but the graphics chip seems to run much higher. Nothing in the reports to suggest that this is the problem but gave them all another 10C anyway. As above, it can't hurt.

Again i can't point to this as a definitive cause but I've changed the desktop theme as well. Back in the days of Jessie MATE some themes caused panel crashes and a change fixed that problem.

Since the installation is still new I'm still in the process of setting up, so lots of little tweaks here and there. Further, there have been a lot of updates for Buster in the past month and it's entirely possible that one or some of those may have helped.

In combination, all, some or one of the above seem to have reduced the incidence of the logouts. Still happen occasionally, but for now I can live with that, even though I don't think that i should have to. I'm not really happy that each new iteration of Debian seems to be less reliable and stable than its predecessor and takes ever increasing amounts of work to make work the way it should. I still have one notebook running Wheezy - it has been almost faultless since the original installation - just worked from day one.
User avatar
NFT5
 
Posts: 317
Joined: 2014-10-10 11:38
Location: Canberra, Australia

Re: Random logout in Buster/KDE

Postby efrpcabo » 2019-08-31 20:56

NFT5:
Thank you for your detailled answer!

NFT5 wrote:I'm not really happy that each new iteration of Debian seems to be less reliable and stable than its predecessor and takes ever increasing amounts of work to make work the way it should. I still have one notebook running Wheezy - it has been almost faultless since the original installation - just worked from day one.

I understand your feelings.
I use Debian because I like a stable system.
Before Debian, I used Ubuntu and Xubuntu, but I moved to Debian because of constant issues.
I used Debian 7 and Debian 8 for the past 5 or 6 years.
I just switched to Debian 10 because Debian 8 as reached end of life, because for me it was working without issues for the last 2 years.
But, since I installed Buster I have had much more issues than I expected.

For example, I use the XFCE version and I noticed that only a few weeks ago Debian 8, 9 and 10 all used XFCE version 4.12.
I believe that shouldn't happen because that 3 Debian versions share the "issues" that this version of XFCE has.

I think it would be nice to have even more stability in the stable version, even if that means sacrificing newer versions of programs, etc.

I really am grateful for Debian, please don't get me wrong.
User avatar
efrpcabo
 
Posts: 91
Joined: 2013-08-08 06:36

Re: Random logout in Buster/KDE

Postby phenest » 2019-08-31 21:08

@NFT5:

What about you video card and driver?
ASRock H77 Pro4-M i7 3770K - 32GB RAM - Pioneer BDR-209D
User avatar
phenest
 
Posts: 1703
Joined: 2010-03-09 09:38
Location: The Matrix

Re: Random logout in Buster/KDE

Postby NFT5 » 2019-08-31 22:50

Yes, I'm following that in the other thread.

Code: Select all
chris@BOSSDESK:~$ lspci -v -s 01:00.0
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) (prog-if 00 [VGA controller])
        Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210]
        Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0
        Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Memory at d0000000 (64-bit, prefetchable) [size=32M]
        I/O ports at e000 [size=128]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: nouveau
        Kernel modules: nouveau


I ran the Nvidia driver on this machine back in Wheezy and had constant ongoing problems. From Jessie on I stayed with the nouveau driver and it was problem free. For this reason I'm reluctant to change.

However, I'm pretty sure that I have another of these graphics cards somewhere, brand new, bought for a machine I didn't use it in. I'll dig it out and swap it over. If it is hardware then that should fix it. Just about due to give this box a service anyway - it lives in a pretty harsh environment in the shop.
User avatar
NFT5
 
Posts: 317
Joined: 2014-10-10 11:38
Location: Canberra, Australia

Re: Random logout in Buster/KDE

Postby efrpcabo » 2019-09-02 00:20

Hi,

I don't know it this helps to solve your case, but I got the solution to mine and described everything here:
viewtopic.php?f=10&t=143439&start=30#p707209
User avatar
efrpcabo
 
Posts: 91
Joined: 2013-08-08 06:36

Re: Random logout in Buster/KDE

Postby NFT5 » 2019-09-03 00:18

So, exploring the hardware possibility......

Gave the computer a service. Wow, dust storm worthy of the Sahara and then half a can of contact cleaner followed by a hit with a blowgun at about 60psi.

Replaced the graphics card and noted that the old one came out a little too easily - maybe not seated in the slot properly?

Reconnected, pressed the big power button and...............random colour patterns all over screen. Diagnosis - dead card. Disconnected it all again, removed card and lobbed to bin.

Replaced with brand new MSI GT710 with 2GB DDR3 that I'd been intending to put in my desktop at home.

Reconnected, fired up and.................it works! Better than the old one? Really hard to say but certainly no screen tearing which I did experience occasionally with the GT610.

Code: Select all
chris@BOSSDESK:~$ lspci -v -s 01:00.0
01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 710B] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710]
        Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0
        Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
        Memory at d0000000 (64-bit, prefetchable) [size=128M]
        Memory at d8000000 (64-bit, prefetchable) [size=32M]
        I/O ports at e000 [size=128]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: nouveau
        Kernel modules: nouveau


Now we'll see what happens.

Update coming in a week or so.
User avatar
NFT5
 
Posts: 317
Joined: 2014-10-10 11:38
Location: Canberra, Australia


Return to Desktop & Multimedia

Who is online

Users browsing this forum: No registered users and 8 guests

fashionable