Crash accessing display and monitor settings kde/ktown 5_19.0
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I cannot access to gamma, compositor, or night light preferences. When I click on any of those options the system settings window crashes immediately. I can only access to display configuration (resolution and refresh rate)
This is the output in terminal:
Code:
[~]$ systemsettings5
Icon theme "gnome" not found.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
Icon theme "gnome" not found.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/SearchField.qml:47:9: QML Action: LayoutDirection attached property only works with Items and Windows
QQmlEngine::setContextForObject(): Object already has a QQmlContext
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")
Icon theme "gnome" not found.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
org.kde.kcoreaddons: Error loading plugin "kcm_kscreen" "The shared library was not found."
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136: TypeError: Value is undefined and could not be converted to an object
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136: TypeError: Value is undefined and could not be converted to an object
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136: TypeError: Value is undefined and could not be converted to an object
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136: TypeError: Value is undefined and could not be converted to an object
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136: TypeError: Value is undefined and could not be converted to an object
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings5 path = /usr/bin pid = 6377
KCrash: Arguments: /usr/bin/systemsettings5
KCrash: Attempting to start /usr/lib64/drkonqi from kdeinit
sock_file=/tmp/xdg-runtime-bakme/kdeinit5__0
[1]+ Stopped systemsettings5
This is the crash output error:
Code:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f02e14c97c0 (LWP 4268))]
Thread 6 (Thread 0x7f02c35ef700 (LWP 4447)):
#0 0x00007f02e5f6a86c in read () from /lib64/libc.so.6
#1 0x00007f02e251303f in ?? () from /usr/lib64/libglib-2.0.so.0
#2 0x00007f02e24cd81e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#3 0x00007f02e24cdc2a in ?? () from /usr/lib64/libglib-2.0.so.0
#4 0x00007f02e24cdd9f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#5 0x00007f02e666b28b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#6 0x00007f02e661681b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#7 0x00007f02e6450ce1 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8 0x00007f02e83abc25 in ?? () from /usr/lib64/libQt5Qml.so.5
#9 0x00007f02e6451d23 in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x00007f02e59c806b in start_thread () from /lib64/libpthread.so.0
#11 0x00007f02e5f7a72f in clone () from /lib64/libc.so.6
Thread 5 (Thread 0x7f02cbfff700 (LWP 4275)):
#0 0x00007f02e5f6a86c in read () from /lib64/libc.so.6
#1 0x00007f02e251303f in ?? () from /usr/lib64/libglib-2.0.so.0
#2 0x00007f02e24cd81e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#3 0x00007f02e24cdc2a in ?? () from /usr/lib64/libglib-2.0.so.0
#4 0x00007f02e24cdd9f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#5 0x00007f02e666b28b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#6 0x00007f02e661681b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#7 0x00007f02e6450ce1 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8 0x00007f02e83abc25 in ?? () from /usr/lib64/libQt5Qml.so.5
#9 0x00007f02e6451d23 in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x00007f02e59c806b in start_thread () from /lib64/libpthread.so.0
#11 0x00007f02e5f7a72f in clone () from /lib64/libc.so.6
Thread 4 (Thread 0x7f02d682f700 (LWP 4274)):
#0 0x00007f02e5f6ee9f in poll () from /lib64/libc.so.6
#1 0x00007f02e24cdc7e in ?? () from /usr/lib64/libglib-2.0.so.0
#2 0x00007f02e24cdd9f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3 0x00007f02e666b28b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4 0x00007f02e661681b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5 0x00007f02e6450ce1 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6 0x00007f02e83abc25 in ?? () from /usr/lib64/libQt5Qml.so.5
#7 0x00007f02e6451d23 in ?? () from /usr/lib64/libQt5Core.so.5
#8 0x00007f02e59c806b in start_thread () from /lib64/libpthread.so.0
#9 0x00007f02e5f7a72f in clone () from /lib64/libc.so.6
Thread 3 (Thread 0x7f02df7ba700 (LWP 4270)):
#0 0x00007f02e5f6ee9f in poll () from /lib64/libc.so.6
#1 0x00007f02e24cdc7e in ?? () from /usr/lib64/libglib-2.0.so.0
#2 0x00007f02e24cdd9f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3 0x00007f02e666b28b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4 0x00007f02e661681b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5 0x00007f02e6450ce1 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6 0x00007f02e68a7456 in ?? () from /usr/lib64/libQt5DBus.so.5
#7 0x00007f02e6451d23 in ?? () from /usr/lib64/libQt5Core.so.5
#8 0x00007f02e59c806b in start_thread () from /lib64/libpthread.so.0
#9 0x00007f02e5f7a72f in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x7f02e07a1700 (LWP 4269)):
#0 0x00007f02e5f6ee9f in poll () from /lib64/libc.so.6
#1 0x00007f02e489bd17 in ?? () from /usr/lib64/libxcb.so.1
#2 0x00007f02e489d80a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3 0x00007f02e135b3f0 in ?? () from /usr/lib64/qt5/plugins/platforms/../../../libQt5XcbQpa.so.5
#4 0x00007f02e6451d23 in ?? () from /usr/lib64/libQt5Core.so.5
#5 0x00007f02e59c806b in start_thread () from /lib64/libpthread.so.0
#6 0x00007f02e5f7a72f in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7f02e14c97c0 (LWP 4268)):
[KCrash Handler]
#6 0x00007f02e8760c40 in QQuickWindowPrivate::dirtyItem(QQuickItem*) () from /usr/lib64/libQt5Quick.so.5
#7 0x00007f02e87ab1b2 in QQuickText::setLinkColor(QColor const&) () from /usr/lib64/libQt5Quick.so.5
#8 0x00007f02e87b3593 in ?? () from /usr/lib64/libQt5Quick.so.5
#9 0x00007f02e87b39eb in QQuickText::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQt5Quick.so.5
#10 0x00007f02dfb7b6f6 in QQuickLabel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQt5QuickTemplates2.so.5
#11 0x00007f02e8389fae in QV4::QQmlValueTypeWrapper::write(QObject*, int) const () from /usr/lib64/libQt5Qml.so.5
#12 0x00007f02e83832fd in ?? () from /usr/lib64/libQt5Qml.so.5
#13 0x00007f02e838424c in ?? () from /usr/lib64/libQt5Qml.so.5
#14 0x00007f02e8380c24 in QQmlBinding::update(QFlags<QQmlPropertyData::WriteFlag>) () from /usr/lib64/libQt5Qml.so.5
#15 0x00007f02e835ea7d in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib64/libQt5Qml.so.5
#16 0x00007f02e83011ad in QQmlData::signalEmitted(QAbstractDeclarativeData*, QObject*, int, void**) () from /usr/lib64/libQt5Qml.so.5
#17 0x00007f02e664102c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5
#18 0x00007f02d6dfb8f0 in ?? () from /usr/lib64/libKF5Kirigami2.so.5
#19 0x00007f02e6642082 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#20 0x00007f02e70a7602 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#21 0x00007f02e70b06b0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#22 0x00007f02e6617b52 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#23 0x00007f02e661a658 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#24 0x00007f02e666bbd3 in ?? () from /usr/lib64/libQt5Core.so.5
#25 0x00007f02e24cdabd in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#26 0x00007f02e24cdd10 in ?? () from /usr/lib64/libglib-2.0.so.0
#27 0x00007f02e24cdd9f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#28 0x00007f02e666b271 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#29 0x00007f02e661681b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#30 0x00007f02e661dfee in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#31 0x000000000040c617 in ?? ()
#32 0x00007f02e5e87e5b in __libc_start_main () from /lib64/libc.so.6
#33 0x000000000040c68a in _start ()
[Inferior 1 (process 4268) detached]
org.kde.kcoreaddons: Error loading plugin "kcm_kscreen" "The shared library was not found."
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin")
That could be the actual business end of this problem.
Possibly the usual problem, packages out of sync? If not missing, the location of that plugin library may have changed or something. I don't know if it's applicable, but I remember one time when some kcm plugins were moved into the main qt5 plugins directory (i.e. older packages may not reflect that change)
Have all distro packages up to date
Have all ktown dependencies, and packages up to date for your distro version
Have Alien Bob's compat packages installed for libboost and libicu (not sure if that's applicable here, but if you're using his packages on -current you should)
org.kde.kcoreaddons: Error loading plugin "kcm_kscreen" "The shared library was not found."
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin")
That could be the actual business end of this problem.
I run a Slackware blog where I write about the stuff I release. Your issue is discussed in the https://alien.slackbook.org/blog/kde...tober-release/ article of a couple of days back - within the first couple of sentences.
I really wish people using my stuff would also subscribe to my blog . It would have saved you from writing this post.
org.kde.kcoreaddons: Error loading plugin "kcm_kscreen" "The shared library was not found."
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin")
That could be the actual business end of this problem.
Possibly the usual problem, packages out of sync? If not missing, the location of that plugin library may have changed or something. I don't know if it's applicable, but I remember one time when some kcm plugins were moved into the main qt5 plugins directory (i.e. older packages may not reflect that change)
Have all distro packages up to date
Have all ktown dependencies, and packages up to date for your distro version
Have Alien Bob's compat packages installed for libboost and libicu (not sure if that's applicable here, but if you're using his packages on -current you should)
Quote:
Originally Posted by Alien Bob
I run a Slackware blog where I write about the stuff I release. Your issue is discussed in the https://alien.slackbook.org/blog/kde...tober-release/ article of a couple of days back - within the first couple of sentences.
I really wish people using my stuff would also subscribe to my blog . It would have saved you from writing this post.
Thank you very much for the information. I didn't find any problem with libicu until I updated my slackware up to date. I fixed it after installing libicu and libboost from alien's packages. I'm going to check alien's blog first from now on when I got a problem with his packages One out of two problems solved.
ANYWAY the problem accessing compositor, gamma and night color is still there and I think I have found a very tricky bug which I will explain in my next comment in this post.
Global themes are the ones that crash different windows on plasma
I think I have found a very tricky bug and I will explain it.
Reproduce the bug:
* Open system settings
* Go to the global theme section
* Click on "Get New Global Themes"
I have installed the following themes to reproduce the bug but there could be more anyway, I will give two of them:
* Install Sweet KDE or KDE-Story themes to reproduce the bug
* After applying any of those two themes, open system settings again
* Go to: Hardware section
* Display and Monitor
Once you have got to the "display and monitor" section, go to the sub-sections such as compositor, gamma or night color and doing so will crash the system settings window.
If you change the theme to the default ones such as breeze or breeze-dark the bug WILL NOT happen.
Can somebody else reproduce this bug?
Last edited by slac; 10-18-2019 at 07:35 PM.
Reason: spell checking
Well, as far as I have been trying to find a workaround for this problem I think I have found something.
I have not checked this problem to access system gamma, night color, and compositor settings on other SO, so I do not know if this an exclusive problem for ktown/slackware.
Anyway. Possible causes for the problem:
- Global themes. The system settings window only crashes when using some global themes, ie: sweet.
- Some problem with the new GUI for the screen preferences section in the system settings window *
* I say this because Night Color preferences GUI doesn't work after applying custom settings, it just doesn't save the changes made because the button "Apply" (to save the changes) is never enabled. Please, don't get this wrong, the GUI works fine for some time when you just have installed Ktown but after some time (random time, I don't know exactly how much) the GUI stops working properly and just as I said you can't save changes for the night color settings.
The temporal fixes I found to these problems are the following (in case somebody else finds these problems):
System settings crashes:
- Avoid the system settings crash: Find a global theme that doesn't crash the system settings window, ie: Breeze or Breeze Dark, these themes are installed by default.
Night Color preferences can't be saved (GUI doesn't enable "apply" button):
+ Open a terminal and go open the file: ~/.config/kwinrc
+ Modify or delete this section:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Got one out of two
One out of two problems solved.
Global themes are the ones that crash different windows on plasma
Temporal solution
