Siduction Forum

Siduction Forum => Installation - Support => Topic started by: tomsiduction on 2020/04/27, 19:59:18

Title: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/04/27, 19:59:18: Hello
My KDE-Systemsettings end up in crash.

Code: [Select]
systemsettings5 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/SearchField.qml:47:9: QML Action: LayoutDirection attached property only works with Items and Windows kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1", "Unable to execute statement", "no such column: rl.initiatingAgent") kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1", "Unable to execute statement", "no such column: rl.initiatingAgent") KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = systemsettings5 path = /usr/bin pid = 2776 KCrash: Arguments: /usr/bin/systemsettings5 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Angehalten systemsettings5A

kcmshell5 kcm_kscreen
ends up in crash too.

Code: [Select]
kcmshell5 kcm_kscreen org.kde.kcoreaddons: Error loading plugin "kcm_kscreen" "The shared library was not found." Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin") The environment variable QT_PLUGIN_PATH might be not correctly set file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136: TypeError: Value is undefined and could not be converted to an object file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136: TypeError: Value is undefined and could not be converted to an object file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136: TypeError: Value is undefined and could not be converted to an object file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136: TypeError: Value is undefined and could not be converted to an object file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136: TypeError: Value is undefined and could not be converted to an object KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kcmshell5 path = /usr/bin pid = 3566 KCrash: Arguments: /usr/bin/kcmshell5 kcm_kscreen KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0
Is there any kind of workaround ?

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: piper on 2020/04/28, 22:55:50: Your problem is kirigami, it was removed from debian 2 years ago, purge it and you should be fine
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/01, 13:31:43: Hello and thank you

Removing kirigami will remove other packages too.

Code: [Select]
apt remove qml-module-org-kde-kirigami2 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: libcolorcorrect5 libgps26 libibus-1.0-5 libkf5kirigami2-5 libnotificationmanager1 libqalculate20 libqalculate20-data libtaskmanager6abi1 plasma-workspace-data qml-module-qtwebengine Verwenden Sie »apt autoremove«, um sie zu entfernen. Die folgenden Pakete werden ENTFERNT: kde-plasma-desktop kinfocenter plasma-desktop plasma-integration plasma-mediacenter plasma-widgets-addons plasma-workspace qml-module-org-kde-kcm qml-module-org-kde-kirigami2 qml-module-org-kde-qqc2desktopstyle sddm-theme-breeze systemsettings
a lot of kde-plasma stuff.

Can I remove it without taking a risk to loose kde-plasma?

Regards

(just to explain: I removed "kirigami" and reinstalled
kde-plasma-desktop
kinfocenter
plasma-desktop
plasma-integration
qml-module-org-kde-kcm
qml-module-org-kde-qqc2desktopstyle
sddm-theme-breeze
systemsettings

but after starting I get only a (single) mouse-cursor on a black screen.)
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/01, 17:48:00: The best way to shot yourself in the foot!

So what you can try first, before reinstalling,

Code: [Select]
apt update; apt install --install-recommends plasma-workspace
good luck
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: piper on 2020/05/01, 18:38:23: Can I ask what your using kirigami2 for?
I build a lot of roms in android and other things, I have never used this, just curious.

danke hendrikL
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: piper on 2020/05/01, 18:45:48: From my little bit of research, this has been a problem with kirigami2 since 2019 with no answers

https://forum.manjaro.org/t/system-settings-are-crashing-when-i-choose-compositor-or-gamma-settings/110174

https://forum.kde.org/viewtopic.php?f=17&t=163459

http://forums.debian.net/viewtopic.php?f=6&t=146024
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/01, 19:11:43: Hello
and thank you to all of you for your help

Before doing the advised steps please allow me to answer the asked question.

I think I did never use kirigami2.

I am using siduction since several years and obviously kirigami was a part of my first installation - and I did update it until today.

May I mention that I managed the last update only by :
Code: [Select]
ln -s /usr/bin/startplasma-x11 /usr/bin/startkde
(Before that linking I had the same problem with the mouse-cursor in front of a black screen.)

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: der_bud on 2020/05/01, 19:48:30: Hi piper, FYI, never used kirigami or installed it on purpose, but it's part of my system and I cannot remove without badly hurting plasma ;)
Code: [Select]
ii libkf5kirigami2-5 5.62.0-2+b2 amd64 set of QtQuick components targeted for mobile use ii qml-module-org-kde-kirigami2 5.62.0-2+b2 amd64 set of QtQuick components targeted for mobile use

Code: [Select]
$ LANG=C aptitude why qml-module-org-kde-kirigami2 i systemsettings Depends qml-module-org-kde-kirigami2[code]
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/02, 13:26:35: Hello

I tried with
Code: [Select]
apt update; apt install --install-recommends plasma-workspace
but it ended in the same way as before.
After rebooting I get only a (single) mouse-cursor on a black screen.)

I am wondering if the behavior of KDE that I described does appear on other computers too?

Thank you
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: piper on 2020/05/02, 17:53:41: Were going to install this and try to destroy this install by removing it, and then install my latest build, just because.
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/02, 18:54:29: Quote from: tomsiduction on 2020/05/02, 13:26:35
Hello

I tried with
Code: [Select]
apt update; apt install --install-recommends plasma-workspace
but it ended in the same way as before.
After rebooting I get only a (single) mouse-cursor on a black screen.)

I am wondering if the behavior of KDE that I described does appear on other computers too?

So, you killed your kde/kf5/plasma installation.
This is not a behaviour of KDE!

Something is missing to bring up the xserver.
Read the log files, like xorg log, journalctl, dmesg....

Maybe kwin-x11 is missing?

Do you have a backup of your data’s?

What about an inxi -GSMx, please provid it.

My two cents, save your data's, get a new iso (https://isobuilds.siduction.org/) start a fresh installation.

This might be much faster, 10 min, then let us digging in the mud of your scrambled system.
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/02, 20:05:18: Hello and thank you

Here comes the system-Info:
Code: [Select]
System: Host: siduction Kernel: 5.6.7-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: KDE Plasma 5.17.5 Distro: siduction 17.1.0 Patience - kde - (201703051755) base: Debian GNU/Linux bullseye/sid Machine: Type: Laptop System: FUJITSU product: LIFEBOOK UEFI [Legacy]: FUJITSU // Insyde v: Version 1.19 date: 05/09/2017 Graphics: Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Fujitsu Limited. driver: i915 v: kernel bus ID: 00:02.0 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus ID: 1-10:5 Display: x11 server: X.Org 1.20.8 driver: intel resolution: 1600x900~60Hz OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 20.0.4 direct render: Yes
Kwin-X11 is installed.

I am testing only with a 1:1 copy of my (still) running system.

Just to explain: I have installed siduction several years ago - the only thing I did was a weekly/monthly upgrade resp. dirt-upgrade.

As it is a encrypted system I would like to avoid a reinstall.

The only error that I can seen in xorg.log
Code: [Select]
15.041] (EE) Failed to open authorization file "/var/run/sddm/{e7321542-832e-4463-8b92-4544509ef81c}": No such file or directory
journalctl gives me (looking not so good)
Code: [Select]
Logs begin at Sat 2020-05-02 06:04:47 CEST, end at Sat 2020-05-02 19:54:24 > Mai 02 06:04:47 siduction org.kde.KScreen[1610]: kscreen.xcb.helper: RRNotify_> Mai 02 06:04:47 siduction org.kde.KScreen[1610]: kscreen.xcb.helper: O> Mai 02 06:04:47 siduction org.kde.KScreen[1610]: kscreen.xcb.helper: P> Mai 02 06:04:47 siduction org.kde.KScreen[1610]: kscreen.xcb.helper: S>
and

Code: [Select]
Mai 02 06:04:47 siduction org.kde.KScreen[1610]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Mai 02 06:04:47 siduction org.kde.KScreen[1610]: kscreen.xcb.helper: Output: 67 Mai 02 06:04:47 siduction org.kde.KScreen[1610]: kscreen.xcb.helper: Property: Backlight Mai 02 06:04:47 siduction org.kde.KScreen[1610]: kscreen.xcb.helper: State (newValue, Deleted): 0
dmesg shows (looking not so good)
Code: [Select]
[25785.778982] QSGRenderThread[113873]: segfault at a0 ip 00007effa4e749d8 sp 00007eff92427d40 error 4 in iris_dri.so[7effa445b000+d2f000] [25785.778988] Code: 44 24 18 48 c7 44 24 10 00 00 00 00 48 c7 44 24 18 00 00 00 00 50 4c 8d 4c 24 18 e8 32 a1 b6 ff 48 8b 44 24 18 31 d2 48 89 ef <4c> 8b b0 a0 00 00 00 4c 89 f6 e8 f9 93 fd ff 48 8b bd 28 01 00 00 [27247.494241] QSGRenderThread[120005]: segfault at 24 ip 00007f0db329e336 sp 00007f0da5059d30 error 6 in iris_dri.so[7f0db2884000+d2f000] [27247.494248] Code: 7e 30 44 01 ff 81 ff ff ff 00 00 0f 87 ab 17 00 00 49 01 c7 4c 89 7e 38 48 85 c0 0f 84 2c 02 00 00 83 ea 01 81 ca 00 00 09 78 <89> 10 48 8d 50 04 45 85 ed 74 74 41 8d 75 ff 48 8d 74 f0 0c 66 0f [28062.146861] QSGRenderThread[123442]: segfault at 24 ip 00007fc751641336 sp 00007fc73ebfed30 error 6 in iris_dri.so[7fc750c27000+d2f000]

Thank you very much

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: piper on 2020/05/02, 22:40:31: Ok, this cannot be removed, that I know of at the moment, you can however purge

kirigami2-dev and libkf5kirigami2-doc if installed.

Kirigami in a QML based UI framework at the core of some KDE applications, which will become more and more central as more and more QML based applications are made.

Plasma 5.8 will depend from Kirigami 1.1, so if you are planning to write a Kirigami-based application, it will work by default and nicely integrate in the Plasma 5.8 desktop.

Plasma 5.8 also has a new big user for Kirigami 1.1, that is Discover: the application to search and install for new software, has a brand new user interface, based upon Kirigami.

But next time you have a problem with your system, please mention right away that you are using a encrypted system
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/03, 16:06:52: Hello and thank you

Do you think it is helpful to downgrade (for a while) to a earlier version of

qml-module-org-kde-kirigami

Or better wait for Plasma 5.18?

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: piper on 2020/05/03, 20:30:22: There is only qml-module-org-kde-kirigami in stretch (oldstable) (https://packages.debian.org/stretch/qml-module-org-kde-kirigami)
I don't recommend it
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/04, 07:22:28: Hello and thank you

You were right. I tested - and there was no improvement.

So I see my only chance - based on your help and http://forums.debian.net/viewtopic.php?f=6&t=146024 (http://forums.debian.net/viewtopic.php?f=6&t=146024) (you mentioned before) and the link at the end of the post https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_tracking_literal_testing_literal_with_some_packages_from_literal_unstable_literal

to edit my apt sources list - as described there - to

testing main contrib non-free
unstable main contrib non-free
testing-update main contrib

and hope that the following updates will heal my problem.

Or is there a easier way ?

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/04, 08:51:57: Sorry I have to change to german to ask a question I can't ask in english.

Ich muss gerade mal eine Verständnisfrage stellen.

Wir reden hier über ein Test System, welches eine 1 zu 1 Kopie des Hauptsystems ist?
Das ganze verschlüsselt.

Funktionieren tut in den Systemeinstellungen die Bildschirmeinstellungen nicht?
Wenn ja, was geht denn da nicht, was wird überhaupt versucht?
Dualmonitor setup?
Einstellung des zweiten Bildschirms?

Alles, was ich hier lese, ist für mich persönlich wirres Zeug!

Bitte kannst Du/ können Sie mir einfach mal beschreiben was da eigentlich versucht wird, außer unsere Zeit zu
verschwenden?

Was ich zu den systemsettings sagen kann ist, ja da sind ein paar Bugs drinnen , die zum Teil in neueren Versionen behoben sind, nicht alle.

Da könnte man ja auch mal die Suchmaschine seines Vertrauens befragen!

Was ich noch sagen muss ist, bitte immer lesen was apt tun möchte!

Wenn da steht, es werden soundso viel System relevante Programme entfernt, dann drückt Mensch auf die Bremse und sagt, nein das will ich nicht!

Das nächste ist, wenn ich lese, ich versuch das Problem mit brutalst möglichen Mitteln zu unterdrücken, bitte mach, aber erwarte keine Hilfe, es wird schiefgehen!

Wenn es wirklich um die Bildschirmeinstellung eines zweiten Monitors ginge/geht könnte auch randr zu Hilfe gezogen werden, wenn nicht sowieso alles zu spät ist und das System nur noch in einer Art Notfallmodus funktioniert/ vegetiert, weil alles wichtige weg, zerschossen und zerbröckelt ist.
Wenn Mensch gerne frickelt, sollte jener auch wissen wann Ende ist und alles zerfrickelt hat.

Da es sich um ein zweit/ bastel System handelt, warum nicht von vorne anfangen und es richtig machen, es gehen ja keine Daten verloren und Übung macht den Meister.

Verschlüsselung ist gut und schön, nur sollte man dies dann auch beherrschen, nur Verbrecher /Agenten/Abgeordnete/einige in der Wirtschaft, das Militär usw. brauchen ein voll verschlüsseltes System, bei den meisten reicht es die persönlichen Daten zu verschlüsseln, und die liegen, wenn möglich, auf einer extra Platte (hdd/ssd) bzw. extra Partition und ist von dem ganzen Quatsch getrennt!

Brauch man ein voll verschlüsseltes System, weil man z. B. Journalist ist, macht man solche Spielchen nicht und nimmt stable!

Ich würde neu installieren und gut ist, dies geht jetzt wirklich schneller, als das Vorhaben sein System endgültig zu schrotten.

Back to english, sorry that i couldn't write in englsh!
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/04, 09:47:49: Guten Morgen.

Viele Fragen tauchen auf - gerne gebe ich Antwort.

Zuerst einmal möchte ich mich für die bereits erwiesene Hilfe bedanken.
Ich arbeite gerne mit siduction - die Distribution ist eine sehr Gute.

Ich habe aus tatsächlichen Gründen auf Verschlüsselung gesetzt; nach dem Howto von siduction.
Dabei ist auch ein verschlüsseltes Betriebssystem herausgekommen.

Ich freue mich über ein funktionierendes System - vielleicht ist es zu perfektionistisch wenn ich die Systemsettings haben will, nur weil ich mit dem Touchpad ein Einstellungsproblem habe.

Aus gemachter Erfahrung führe ich ein "upgrade" bzw. "dist-upgrade" nur auf einer 1:1 Kopie der Festplatte durch - und nur wenn es läuft, wird auf dem Original die Maßnahme durchgeführt.
Klingt vielleicht umständlich - hilft aber gegen Stress.

So - jetzt darf ich mich nochmals bedanken (auch dafür, dass das Forum den Raum gibt sich verständlich zu machen).

Ich werde die Quellen ändern - so wie in dem vom piper verlinkten Artikel beschrieben - und hoffe das folgende Updates das System heilen.

Wenn das klappt, berichte ich gerne um ggf. auch anderen Betroffenen zu helfen.

So - jetzt darf ich mich nochmals bedanken (auch dafür, dass das Forum den Raum gibt sich verständlich zu machen).

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/04, 10:09:51: Well, one last thing,

start kcmshell with following option. (found somewhere in the net)
Code: [Select]
LANG=C kcmshell5 .........
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/04, 10:36:36: You run into a known bug,

https://bugs.kde.org/show_bug.cgi?id=417316

and it is fixed, so you have to wait till a more recent kde/plasma comes to debian sid/unstable.

https://phabricator.kde.org/D27442
https://cgit.kde.org/kscreen.git/commit/?id=357df7c5c48abd862fcd71e1d611f3f575c74be4

and what you can test
Code: [Select]
QT_QUICK_CONTROLS_STYLE=default systemsettings5
default or plasma or.... https://doc.qt.io/qt-5/qtquickcontrols2-styles.html

found here

https://github.com/NixOS/nixpkgs/issues/79713
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: der_bud on 2020/05/04, 10:57:46: Hint: we already had that, on the very same system ;) - https://forum.siduction.org/index.php?topic=7938.msg64393#msg64393
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/04, 11:11:13: :o
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/05, 06:24:38: Hello and thank you

It is good news to read that the bug is fixed and that it is only necessary to wait a bit.

Just to mention:
I tried to fix it by:

Code: [Select]
QT_QUICK_CONTROLS_STYLE=default systemsettings5
but systemsettings still do not work.

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/05, 06:56:19: And the error message?
The output of the console?

Try with "base"

Code: [Select]
QT_QUICK_CONTROLS_STYLE=base systemsettings5
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/05, 11:36:42: Hello and thank you

May I attach the error-code:
Code: [Select]
QT_QUICK_CONTROLS_STYLE=default systemsettings5 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/SearchField.qml:47:9: QML Action: LayoutDirection attached property only works with Items and Windows kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1", "Unable to execute statement", "no such column: rl.initiatingAgent") kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1", "Unable to execute statement", "no such column: rl.initiatingAgent") KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = systemsettings5 path = /usr/bin pid = 291264 KCrash: Arguments: /usr/bin/systemsettings5 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0

I did
Code: [Select]
QT_QUICK_CONTROLS_STYLE=base systemsettings5 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/SearchField.qml:47:9: QML Action: LayoutDirection attached property only works with Items and Windows kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1", "Unable to execute statement", "no such column: rl.initiatingAgent") kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1", "Unable to execute statement", "no such column: rl.initiatingAgent") KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = systemsettings5 path = /usr/bin pid = 371307 KCrash: Arguments: /usr/bin/systemsettings5 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Angehalten QT_QUICK_CONTROLS_STYLE=base systemsettings5
Thank you for your help

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/05, 14:40:51: Can you try

Code: [Select]
qdbus org.kde.KWin /Compositor suspend; QT_QUICK_CONTROLS_STYLE=base systemsettings5
to reactivate the effects use

Code: [Select]
qdbus org.kde.KWin /Compositor resume
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/05, 16:06:55: Hello and thank you very much

I tried it

Code: [Select]
qdbus org.kde.KWin /Compositor suspend; QT_QUICK_CONTROLS_STYLE=base systemsettings5 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/SearchField.qml:47:9: QML Action: LayoutDirection attached property only works with Items and Windows kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1", "Unable to execute statement", "no such column: rl.initiatingAgent") kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1", "Unable to execute statement", "no such column: rl.initiatingAgent") KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = systemsettings5 path = /usr/bin pid = 422600 KCrash: Arguments: /usr/bin/systemsettings5 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Angehalten QT_QUICK_CONTROLS_STYLE=base systemsettings5

Thank you

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/05, 16:46:34: Question:
Do you work with activities?

Can you test it with a test-user account and total new profile.
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: piper on 2020/05/05, 17:16:47: @hendrikL

+1

Thanks for asking this, I was going to ask the same, but you included activities, I was going to just suggest new profile, I didn't think of it because I don't use activities ;)
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/06, 10:52:04: Hello and thank you to all

What I did

1. adduser ...

2. when I log out from KDE "Abmelden" I end in a black screen with a single mouse cursor.

3. Killing "sddm" brings up a new KDE-Session without showing the SDDM-login

4. Killing the xserver : I end in a black screen with a single mouse-cursor.

5. Entering in a new console (and log in) as the new user is possible.
If I enter "startx" it will open only my "Backup" xfce.
If I enter "startplasma-x11" gives me

Code: [Select]
$DISPLAY is not set or cannot connect to the X server
Thank you for all your help

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/06, 10:57:22: I am clueless!
Sorry, all i can say is your system is totally messed.
sddm not starting? Even you restart the PC?
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/06, 11:00:27: Hello and thank you

In fact sddm does not start

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/06, 11:17:51: Code: [Select]
apt update; apt install --reinstall --install-recommends sdm sddm-theme-breeze && reboot
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/06, 18:11:18: Hello and thank you very much

I did as suggested

Code: [Select]
apt update; apt install --reinstall --install-recommends sddm sddm-theme-breeze && reboot
but unfortunately sddm is still not visible.

Code: [Select]
kcmshell5 kcm_sddm
crashes too

Code: [Select]
kcmshell5 kcm_sddm QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object libpng warning: iCCP: known incorrect sRGB profile KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kcmshell5 path = /usr/bin pid = 3579 KCrash: Arguments: /usr/bin/kcmshell5 kcm_sddm KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Angehalten kcmshell5 kcm_sddm

Thank you again

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/06, 21:36:17: mh, really no clue what you done with your system.

take a look to the log files, like xorg.log
and
systemctl status sddm

journalctl -b | grep sddm

apt policy
inxi -r

what you can try is, all in getty/tty (ctrl+alt+Fn) as root

Code: [Select]
systemctl stop sddm.service then systemctl start sddm.service
or/and
Code: [Select]
systemctl isolate multi-user.target then systemctl isolate graphical.target
<german>
Aber wie gesagt, da ist etwas gewaltig faul und so wie es scheint kann nur ein Wunder oder eine Neuinstallation das System retten
</german>

Ich streiche die Segel, sorry!
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/07, 14:37:57: Hello and thank you

I have found the reason but I can not explain.

Inside a different computer everything is going fine.

Same disk!

Sddm ist working there and systemsettings too.

Is there a way to reinstall the whole system of the grafic-card?

I tried a X -config but that did not bring the right result.

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/07, 14:42:14: What kind of gpu?
Code: [Select]
inxi -GMSx
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/07, 16:30:34: Hello and thank you very much for your help

Code: [Select]
System: Host: siduction Kernel: 5.6.7-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: KDE Plasma 5.17.5 Distro: siduction 17.1.0 Patience - kde - (201703051755) base: Debian GNU/Linux bullseye/sid Machine: Type: Laptop System: FUJITSU product: LIFEBOOK E756 v: 10601736746 serial: <superuser/root required> Mobo: FUJITSU model: FJNB292 v: N4 serial: <superuser/root required> UEFI [Legacy]: FUJITSU // Insyde v: Version 1.19 date: 05/09/2017 Graphics: Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Fujitsu Limited. driver: i915 v: kernel bus ID: 00:02.0 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus ID: 1-10:5 Display: x11 server: X.Org 1.20.8 driver: intel resolution: 1600x900~60Hz OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 20.0.6 direct render: Yes

Regards
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: hendrikL on 2020/05/07, 17:06:40: mh, maybe you can use the modestting driver by renaming the xorg.conf to xorg.conf~ or the 20-intel.conf to 20-intel.conf~
you have to look what you have, both con be found in /etc/X11 or /etc/X11/xorg.conf.d/, after renaming restart the laptop.

Then it should look like that
inxi -Gx
Code: [Select]
Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1440x900~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.0.6 direct render: Yes
If it doesn't work, rename them again and restart the system.
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: towo on 2020/05/07, 17:46:23: The 1st thing, i would try, is intel_iommu=off as bootparameter.
Title: Re: KDE-Systemsettings ends up in crash, kcmshell5 kcm_kscreen too
Post by: tomsiduction on 2020/05/08, 11:05:23: Hello and thank you

Everything ist fixed.

What I did:

I started siduction from a usb-stick and looked for the settings of Xorg in
/etc/X11/xorg.conf.d/ and /usr/share/X11/xorg.conf.d/ while siduction was booted from the stick.
I examined /etc/X11/xorg.conf.d/ and /usr/share/X11/xorg.conf.d/ while the system was running from the stick.
I saw that there was neither in /etc/X11/xorg.conf.d/ or /usr/share/X11/xorg.conf.d/ a file named 20-intel.conf.

So I rebooted from the disk and deleted in /usr/share/X11/xorg.conf.d/ the file
20-intel.conf

(in /etc/X11/xorg.conf.d/ the file 20-intel.conf did not exist)

(@ thank you very much hendrikL for the hint)
and rebooted.

Everything is working again:

SDDM
Systemsettings
vlc

and so on.

Thank you very much to all of you for your great help.

Regards