Slackware - ARMThis forum is for the discussion of Slackware ARM.
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 have installed the latest image of Slackware ARM on my RPI4 with, of course, KDE5 !
Everything is working fine except ... the system configuration window !
When I click on "System configuration", a window appears with a black background and nothing visible inside ( see attachment )!
In spite of this, the window is active and when I move the mouse , I can see some of the various items and from time to time, the right part of the window displays the contents on a white background.
What is happening and how can I fix this problem ?
Hi all
When I click on "System configuration", a window appears with a black background and nothing visible inside ( see attachment )!
Good timing! I was just about to test the latest KDE build.
This may be a translation thing, but with the English language set, I cannot find a 'System configuration' in KDE; I'm assuming it's "System Settings".
Is what's in the attachment what you expected to see?
This is on a fresh installation of -current (which has a KDE upgrade) on the Orange Pi.
Keep an eye on the -current ChangeLog -- assuming the system integration tests pass, I'll push the updates out later today.
If it can help you, here is what I see when lauching systemsettings5 on a terminal
Code:
hermes-didier(5)% systemsettings5
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:158:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:148:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:73:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumHeight"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumHeight"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumHeight"
Quote:
Originally Posted by drmozes
Good timing! I was just about to test the latest KDE build.
This may be a translation thing, but with the English language set, I cannot find a 'System configuration' in KDE; I'm assuming it's "System Settings".
Is what's in the attachment what you expected to see?
This is on a fresh installation of -current (which has a KDE upgrade) on the Orange Pi.
Keep an eye on the -current ChangeLog -- assuming the system integration tests pass, I'll push the updates out later today.
The updates are making their way out now. Try grabbing them in a few hours now from the master ftp.arm.slackware.com
The updates may resolve it, since it certainly works on a fresh installation.
The updates are making their way out now. Try grabbing them in a few hours now from the master ftp.arm.slackware.com
The updates may resolve it, since it certainly works on a fresh installation.
Hi @drmozes
Full of hope seeing your Change.txt, I have pointed Slackpkg to my French mirror ( where I have checked they have got your changes )
- slackpkg update + install-new + upgrade-all
More than an hour of upgrade where I have seen all the components of KDE been upgraded that finishes without any errors and then ... reboot !
KDE starts normally and shows me the icon of System settings : I click on it and ....... a black window appears once again !
Like before the window is active and, when clicking randomly on the left side of the window, sometimes I got a useful right part ( see image )
I have also tried to launch systemsettings5 on a terminal and it shows the same errors as yesterday.
I have also tried to erase my .kde repository to let KDE build a new one but it has no effect.
I do not know what to do more now : is it a pb with the X driver but all the other windows are correct !
I do not know what to do more now : is it a pb with the X driver but all the other windows are correct !
A similar sounding and looking bug was reported here, where the report centres around the video driver.
I don't have an RPI so I can't help you I'm afraid. You could try reinstalling onto other storage if you can, to see if a fresh install fixes it in case it's being affected by something not in ~/.kde.
I have the same, or similar issue with my Pi 4 4GB. I haven't found the cause or fix, but I did find a "work-around".
If you can find it, in System Settings--> Configure, change Sidebar View to Icon View. Not a great solution, but at least you can see and access the settings.
It took a while to get back to you guys because I did a fresh installation. I do not have an exra monitor to plug into the Pi. I tested in a remote desktop session, with tigervnc, which techincally, should be more GPU intensive. I am using all stock settings and that includes window composites. I checked the log file for the vnc session and saw the same deprecation warnings.
By chance did either of you just change your global theme?
Sometimes KDE has a problem with this and you need to log out of KDE and log back into KDE with a new session.
Can each of you do a small test for me?
Create a new user, reboot, log into that user within KDE. Post back here to let me know if you have the same issue with the new user.
I won't be able to test a new account/user for a few hours, but yes, I did change the global theme, a couple of times. I'll try the new user test when time allows, and post results if it's still relevant.
I won't be able to test a new account/user for a few hours, but yes, I did change the global theme, a couple of times. I'll try the new user test when time allows, and post results if it's still relevant.
That is fine, what is the output of:
Code:
glxgears -info
As a test, I changed a bunch of settings, managed to crash vncviewer (unrelated), then reconnected, reverted to the default theme. I think the problem is in your user's configuration settings. Quite likely stale files in the home directory.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.