Bug 479066 - Changing Panel thickness while Widget Explorer is also open immediately closes Panel edit mode dialog
Summary: Changing Panel thickness while Widget Explorer is also open immediately close...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.91.0
Platform: Other Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
: 477933 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-12-27 06:57 UTC by Enrico
Modified: 2024-06-26 21:34 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.1.1


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enrico 2023-12-27 06:57:27 UTC
SUMMARY
***
Hello,
the panel's EDIT MODE seems to crash when changing height after adding a widget. I've tested it on both KaOS and Neon Unstable.
I found this bug trying to reproduce https://bugs.kde.org/show_bug.cgi?id=477933
***


STEPS TO REPRODUCE
1. Right click on the panel -> Add Widget
2. Add a Widget to the panel, for example the Bluetooth
3. Keep the left widget bar opened
4. Right click on the panel > Enter Edit mode
5. Press the "+" button to increase panel height

OBSERVED RESULT
The dialog to increase/decrease panel height seems to crash as it's closed immediately. Moreover, if you hover the mouse on the system tray icons you can see  that you're not in Edit mode.
If you right click again in the panel, you see "Exit edit mode". If you click on Exit edit mode you actually ENTER edit mode again (hovering the system tray icons you see "remove" and others edit commands)

EXPECTED RESULT
Changing height should not cause this problem

SOFTWARE/OS VERSIONS
Operating System: KaOS (2023) 
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.6.1
Kernel Version: 6.5.11-1 (64-bit)
Graphics Platform: Wayland
Comment 1 Tom Max 2023-12-27 11:45:48 UTC
reproducing the bug on Neon unstable, you can see that the file /var/log/syslog contains a lot of QML lines, both plasmashell and kwin_wayland are complaining about missing function on the plugin, maybe it needs a review? 
The clock plugin has  a very similar behavior

Dec 27 12:26:30 tom-neon kwin_wayland[1096]: kwin_wayland_drm: EglGbmLayerSurface::importWithCpu: failed to get a target dumb buffer
Dec 27 12:26:31 tom-neon plasmashell[1189]: file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/main.qml:364:9: QML ListModel: remove: indices [-1 - 0] out of range [0 - 11]
Dec 27 12:26:31 tom-neon plasmashell[1189]: message repeated 5 times: [ file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/main.qml:364:9: QML ListModel: remove: indices [-1 - 0] out of range [0 - 11]]
Dec 27 12:26:31 tom-neon kwin_wayland[1096]: kwin_core: drmPrimeHandleToFD() failed: No such file or directory
Dec 27 12:26:31 tom-neon kwin_wayland[1096]: kwin_scene_qpainter: Failed to allocate a qpainter swapchain graphics buffer
Dec 27 12:26:31 tom-neon kwin_wayland[1096]: kwin_wayland_drm: EglGbmLayerSurface::importWithCpu: failed to get a target dumb buffer
Dec 27 12:26:31 tom-neon plasmashell[1189]: Arrived mimeData QList() QList("text/x-plasmoidservicename") at 475 ,  19

adding the plugin

Dec 27 12:26:31 tom-neon plasmashell[1189]: adding "org.kde.plasma.bluetooth"
Dec 27 12:26:31 tom-neon plasmashell[1189]: This plugin does not support setting window opacity
Dec 27 12:26:31 tom-neon kwin_wayland[1096]: kwin_core: drmPrimeHandleToFD() failed: No such file or directory
Dec 27 12:26:31 tom-neon kwin_wayland[1096]: kwin_scene_qpainter: Failed to allocate a qpainter swapchain graphics buffer
Dec 27 12:26:31 tom-neon kwin_wayland[1096]: kwin_wayland_drm: EglGbmLayerSurface::importWithCpu: failed to get a target dumb buffer
Dec 27 12:26:33 tom-neon plasmashell[1189]: KPackageStructure of KPluginMetaData(pluginId:"org.kde.kdeconnect", fileName: "/usr/share/plasma/plasmoids/org.kde.kdeconnect/metadata.json") does not match requested format "Plasma/Applet"
Dec 27 12:26:36 tom-neon plasmashell[1189]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/PanelConfiguration.qml:512:9: QML SpinBox: Binding loop detected for property "implicitWidth"
Dec 27 12:26:36 tom-neon plasmashell[1189]: file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/ConfigOverlay.qml:326:17: QML SpinBox: Binding loop detected for property "implicitWidth"
Dec 27 12:26:36 tom-neon plasmashell[1189]: file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/ConfigOverlay.qml:288: TypeError: Cannot read property 'applet' of null
Dec 27 12:26:37 tom-neon plasmashell[1189]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Dec 27 12:26:37 tom-neon plasmashell[1189]: KPackageStructure of KPluginMetaData(pluginId:"org.kde.kdeconnect", fileName: "/usr/share/plasma/plasmoids/org.kde.kdeconnect/metadata.json") does not match requested format "Plasma/Applet"
Dec 27 12:26:39 tom-neon plasmashell[1189]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Dec 27 12:26:42 tom-neon kwin_wayland[1096]: This plugin does not support raise()
Comment 2 Nate Graham 2024-01-10 17:29:48 UTC
Possible Bug 477933. But 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!
Comment 3 Enrico 2024-01-10 20:19:58 UTC
Hello,
I did the coredumpctl --reverse, but nothing is shown there.
I'm not sure that something really crashes, it's probably a misbehavior, not a crash.

This issue seems very similar to the bug you linked, but plasmashell doesn't crash (or at least Dr Konqi doesn't report it) and it's still usable.
Comment 4 Nate Graham 2024-01-11 15:53:28 UTC
Ok, so if nothing crashed, then what happened was simply that Edit Mode exited. I can reproduce the issue.
Comment 5 Akseli Lahtinen 2024-06-06 13:41:10 UTC
*** Bug 477933 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2024-06-26 21:34:25 UTC
In Plasma 6.1.1, the issue is no longer possible.