*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY STEPS TO REPRODUCE 1. start plasmashell 2. see errors 3. sometimes monitor is turned off or switched to alternate source OBSERVED RESULT crash EXPECTED RESULT does not crash kinfo Operating System: KDE neon 6.2 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.8.0-49-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 partial trace from two sessions: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.hdmi-stereo" file:///usr/share/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:91: TypeError: Cannot read property 'description' of undefined org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.hdmi-stereo" org.kde.pulseaudio: No object for name "@DEFAULT_SINK@" org.kde.pulseaudio: No object for name "@DEFAULT_SINK@" qt.qpa.wayland: Creating a fake screen in order for Qt not to crash kde.plasmashell: requesting unexisting screen available rect -1 kde.plasmashell: requesting unexisting screen available rect -1 kde.plasmashell: requesting unexisting screen available rect -1 kde.plasmashell: requesting unexisting screen available rect -1 The Wayland connection broke. Did the Wayland compositor die? user@dell:~$ plasmashell kf.plasma.quick: Applet preload policy set to 1 qml: false file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth": file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9 Toolbox not loading, toolbox package is either invalid or disabled. file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel" file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel" qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString, QString, uint, QString, bool) : QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. kpipewire_logging: PipeWire remote error: -2 target not found kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:4 kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce.
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the `coredumpctl` command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks!
Hey Nate, thanks for responding. I actually ran into additional difficulties trying to fix the issue and crashed the system. I had tried switching to using X11 to see if the issue still existed and could no longer login to the system, as Kwin always crashed and then pretty much froze the system. I could not get to the point to switch back to Wayland so after many frustrating hours I gave up and just installed a new instance of Neon. I may still try to resurrect the old system at some point and if I manage to do it I will send you the backtrace/debug info as requested. Until then thanks for your help and hope you enjoy the holidays. ~ Neil On 2024-12-16 13:28, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=497473 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |nate@kde.org > Resolution|--- |BACKTRACE > Status|REPORTED |NEEDSINFO > > --- Comment #1 from Nate Graham <nate@kde.org> --- > If something crashed, we need a backtrace of it so we can figure out what's > going on. Can you please attach a backtrace of the crash using the > `coredumpctl` command-line program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? > > Thanks! >
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.