Summary: | Plasmashell randomly exits with wayland protocol error ("xdg_surface#157: error -1: invalid window geometry size (0x0)" after unlocking with multiple screens | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Robert David <robert.david.public> |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bugs.kde, haakon+kdebugs, kde, kdedev, kotversuchung, laurent.rineau, m.kurz, nate, niccolo.venerandi, nilskemail+kde, postix, tcope2112, xavier.forestier |
Priority: | VHI | Keywords: | multiscreen |
Version First Reported In: | 6.1.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=490813 https://bugs.kde.org/show_bug.cgi?id=491844 https://bugs.kde.org/show_bug.cgi?id=497204 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Robert David
2024-09-24 09:29:00 UTC
*** Bug 493374 has been marked as a duplicate of this bug. *** So far only see with AMD GPUs. See related NVIDIA bug 490813. And also Bug 491844, which also has the same error message with an AMD GPU. I observe similar issue on both of my systems. The second is older Lenovo T460 and when connected with HDMI it has a similar outcome as this bug. I need to clarify the error is the same, but probably is. None of these systems has a dedicated gpu. Both are wayland and Plasma 6.1.x.. I think I have also tested X11 on the older system, observing these random exits also. I will try to run the latest Neon on the older system to see if it is not a Void specific issue to sort that out. There may be something that a non-systemd system provides differently than the Plasma is expecting. And sorry for my initial description, that I forgot to erase the heading text. I'll be more careful next time. A possibly relevant merge request was started @ https://invent.kde.org/plasma/libplasma/-/merge_requests/1205 *** Bug 493036 has been marked as a duplicate of this bug. *** Git commit ee773fa669f91b34115a123c89055857bb52f04c by David Edmundson. Committed on 18/10/2024 at 13:55. Pushed by davidedmundson into branch 'master'. appletpopup: Guard against null sizes M +4 -1 src/plasmaquick/appletpopup.cpp M +3 -0 src/plasmaquick/dialog.cpp https://invent.kde.org/plasma/libplasma/-/commit/ee773fa669f91b34115a123c89055857bb52f04c Still have the issue, it's very simple to reproduce now : power down / up my screen crash plasmashell : ~ $ plasmashell KPackageStructure of KPluginMetaData(pluginId:"org.kde.graphsplasmoid", fileName: "/usr/share/plasma/plasmoids/org.kde.graphsplasmoid/metadata.json") does not match requested format "Plasma/Applet" KPackageStructure of KPluginMetaData(pluginId:"org.kde.plasma.kweather_1x4", fileName: "/usr/share/plasma/plasmoids/org.kde.plasma.kweather_1x4/metadata.json") does not match requested format "Plasma/Applet" KPackageStructure of KPluginMetaData(pluginId:"org.kde.plasma.kclock_1x2", fileName: "/usr/share/plasma/plasmoids/org.kde.plasma.kclock_1x2/metadata.json") does not match requested format "Plasma/Applet" kf.plasma.quick: Applet preload policy set to 1 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. org.kde.plasma.kicker: Entry is not valid "org.kde.kontact.desktop" 0x562fd54ac370 org.kde.plasma.kicker: Entry is not valid "org.kde.discover.desktop" 0x562fd54ac370 org.kde.plasma.kicker: Entry is not valid "org.kde.kontact.desktop" 0x562fd54ac370 org.kde.plasma.kicker: Entry is not valid "org.kde.discover.desktop" 0x562fd54ac370 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) : error getting max keyboard brightness via dbus QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/org/kde/Solid/PowerManagement/Actions/KeyboardBrightnessControl'") QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0d_00.6.iec958-stereo.monitor" kameleon supported false kameleon enabled true 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 qt.qpa.wayland: Creating a fake screen in order for Qt not to crash kf.plasma.quick: Exposed with no visual parent. Window positioning broken. qt.qpa.wayland: Creating a fake screen in order for Qt not to crash kf.plasma.quick: Exposed with no visual parent. Window positioning broken. kf.plasma.quick: Exposed with no visual parent. Window positioning broken. kf.plasma.quick: Exposed with no visual parent. Window positioning broken. org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0d_00.1.hdmi-stereo" org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0d_00.6.iec958-stereo.monitor" trying to show an empty dialog xdg_surface#113: error -1: invalid window geometry size (0x0) The Wayland connection experienced a fatal error: Erreur de protocole Can confirm this on Plasma 6.2.2 and Qt 6.8.0. My laptop is connected to an external monitor with HDMI, and the laptop lid is closed and its monitor disabled. When the external monitor is switched off (typically when the laptop sleeps) and comes back on, the plasmashell panel is still there but renders as a black/grey bar with nothing visible. No mouse clicks on it will trigger anything, but I can still open the launcher and the clock/calendar using keyboard shortcuts. The logs described in this issue are there, such as "kf.plasma.quick: Exposed with no visual parent. Window positioning broken." When I open the laptop lid so that the laptop display turns on, the plasmashell panel "wakes up" and renders correctly, and the problem is solved until next time. You might be interested in bug 497274 which may is caused by the same / similiar problem and which I can reproduce 100% each time. @David Edmundson You might be interested that your merge request https://invent.kde.org/plasma/libplasma/-/merge_requests/1205 _in theory_ fixed the problem, but the assertion still is not fulfilled. *** Bug 497274 has been marked as a duplicate of this bug. *** It looks like you're using Plasma 6.2.4, but the assert change only went into master. > It looks like you're using Plasma 6.2.4, but the assert change only went into master. Nate, like described in bug 497274 I cherry-picked the assert change from merge_requests 1205 (which went into the master branch only) on top of the Plasma/6.2 branch, because that merge request actually, in theory, fixes my problem, but only when removing the assert line. You might be interested in the conversation im I am having with someone over here https://invent.kde.org/plasma/libplasma/-/merge_requests/1205#note_1055423 *** Bug 498946 has been marked as a duplicate of this bug. *** |