Discover crashes shortly after launch

Project Discussion
1

Hello!

Am I the only one that has this problem?

$ plasma-discover
QObject::startTimer: Timers cannot have negative intervals
kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using Qt HiDPI scaling.
kf.newstuff.core: The ChecksumPolicy feature is defunct
kf.newstuff.core: The SignaturePolicy feature is defunct
kf.newstuff.core: The ChecksumPolicy feature is defunct
kf.newstuff.core: The SignaturePolicy feature is defunct
org.kde.plasma.libdiscover: Couldn’t find a category for “fwupd-backend”
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property “value”
KCrash: Application ‘plasma-discover’ crashing…
KCrash: Attempting to start /usr/libexec/drkonqi
amdgpu: The CS has been rejected, see dmesg for more information (-9).
amdgpu: Failed to allocate a buffer:
amdgpu: size : 2359296 bytes
amdgpu: alignment : 2097152 bytes
amdgpu: domains : 4
amdgpu: flags : 6
amdgpu: Failed to allocate a buffer:
amdgpu: size : 2359296 bytes
amdgpu: alignment : 2097152 bytes
amdgpu: domains : 4
amdgpu: flags : 6
amdgpu: The CS has been rejected, see dmesg for more information (-9).
org.kde.drkonqi: Unable to find an internal debugger that can work with the KCrash backend
The Wayland connection experienced a fatal error: Transport endpoint is not connected

2

Hello @v4k4qrnzszpo49 ,
Welcome to the discussion area, you may have found an issue. Perhaps report it to the KDE dev’s https://community.kde.org/Get_Involved/Issue_Reporting

3

Can you try with the latest release? What’s your rpm-ostree status?

1 Like
4

Hi Timothée,

I had work to get done, so I switched back to Manjaro. I’ll check out Kinoite again when it matures a bit.

5

Sure. Thanks!