https://bugs.kde.org/show_bug.cgi?id=470627
Bug ID: 470627
Summary: Crash Upon Changing Page in SystemSettings if AMD
Drivers Installed
Classification: Applications
Product: systemsettings
Version: 5.24.6
Platform: Kubuntu
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: hicksc...@gmail.com
Target Milestone: ---
Good afternoon,
I've tried using Neon but unfortunately the AMD proprietary drivers won't
compile. So I've switched to Kubuntu LTS (Kernel is `5.19.0-43-generic`, distro
itself is `Ubuntu 22.04.2 LTS`).
I have a bunch of computers, and SystemSettings works great on all except one,
and after I install AMD proprietary GPU drivers. The rest seems to work OK.
Interestingly, uninstalling the AMD drivers immediatelly fixes the issue
without a reboot - so this might be useful. When using `amdgpu-uninstall` the
packages that are removed are:
```
The following packages will be REMOVED
amdgpu* amdgpu-core* amdgpu-dkms* amdgpu-dkms-firmware* amdgpu-lib*
amdgpu-lib32* amdgpu-pro* amdgpu-pro-core* amdgpu-pro-lib32* amdgpu-pro-oglp*
amdgpu-pro-oglp:i386* clinfo-amdgpu-pro* gst-omx-amdgpu*
libdrm-amdgpu-amdgpu1* libdrm-amdgpu-amdgpu1:i386* libdrm-amdgpu-common*
libdrm-amdgpu-radeon1*
libdrm-amdgpu-radeon1:i386* libdrm2-amdgpu* libdrm2-amdgpu:i386*
libegl1-amdgpu-mesa* libegl1-amdgpu-mesa:i386* libegl1-amdgpu-mesa-drivers*
libegl1-amdgpu-mesa-drivers:i386* libegl1-amdgpu-pro-oglp*
libegl1-amdgpu-pro-oglp:i386* libgbm1-amdgpu* libgbm1-amdgpu:i386*
libgl1-amdgpu-mesa-dri*
libgl1-amdgpu-mesa-dri:i386* libgl1-amdgpu-mesa-glx*
libgl1-amdgpu-mesa-glx:i386* libgl1-amdgpu-pro-oglp-dri*
libgl1-amdgpu-pro-oglp-dri:i386*
libgl1-amdgpu-pro-oglp-ext* libgl1-amdgpu-pro-oglp-gbm*
libgl1-amdgpu-pro-oglp-glx* libgl1-amdgpu-pro-oglp-glx:i386*
libglapi-amdgpu-mesa*
libglapi-amdgpu-mesa:i386* libgles1-amdgpu-pro-oglp*
libgles1-amdgpu-pro-oglp:i386* libgles2-amdgpu-pro-oglp*
libgles2-amdgpu-pro-oglp:i386*
libllvm15.0.50405-amdgpu* libllvm15.0.50405-amdgpu:i386*
libxatracker2-amdgpu* libxatracker2-amdgpu:i386* mesa-amdgpu-omx-drivers*
mesa-amdgpu-va-drivers*
mesa-amdgpu-va-drivers:i386* mesa-amdgpu-vdpau-drivers*
mesa-amdgpu-vdpau-drivers:i386* ocl-icd-libopencl1-amdgpu-pro*
opencl-legacy-amdgpu-pro-icd*
vulkan-amdgpu* xserver-xorg-amdgpu-video-amdgpu*
```
And of course DKMS kicks in and removes all the `ko` modules.
But as soon as the drivers are re-installed (Using `amdgpu-install
--usecase=workstation -y --vulkan=amdvlk --opencl=legacy`), SystemSettings
crashes as soon as I change page in it.
The interesting part is that if I open SystemSettings using `krunner` on a
specific page, that page loads fine. But as soon as I change page within
SystemSettings, it crashes immediately and with close to no information
(Nothing in `syslog`).
If I run `systemsettings` directly from my terminal, this is what the output
looks like at the time of the crash:
```
systemsettings
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 13. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:147:9:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 14. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:674:5:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 14. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:670:5:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 13. Use 'sequences: [ <key> ]' to bind to all of them.
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 13. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:147:9:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 14. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:674:5:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 14. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:670:5:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 13. Use 'sequences: [ <key> ]' to bind to all of them.
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 13. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:147:9:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 14. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:674:5:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 14. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:670:5:
QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated
with 13. Use 'sequences: [ <key> ]' to bind to all of them.
qml: The item SubCategoryPage_QMLTYPE_78(0x558989e1aa10) is already in the
PageRow
corrupted double-linked list
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings path = /usr/bin pid = 104369
KCrash: Arguments: /usr/bin/systemsettings
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
[1] 104369 alarm systemsettings
```
Again - I think the important hint here is that when using `amdgpu-install` and
`amdgpu-uninstall` without rebooting, the problem starts and stops - which
tells me that probably the `ko` modules themselves aren't the issue here (they
don't get unloaded / loaded until a reboot) but instead one of the libraries
that gets installed is the problem?
--
You are receiving this mail because:
You are watching all bug changes.
