Bug 485870

Summary:	Can't resize pop-up windows opened by widgets (eg KickOff, Calendar etc) under X11, works under Wayland
Product:	[Plasma] plasmashell	Reporter:	Eugene San <eugenesan>
Component:	Application Launcher (Kickoff) widget	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	eugenesan, mikel5764, nate, noahadvs
Priority:	NOR
Version:	git-stable-Plasma/5.27
Target Milestone:	1.0
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:	6.1.0
Sentry Crash Report:

Description Eugene San 2024-04-21 01:06:09 UTC

When opening Application Launcher window, mouse cursor changes to resize style but won't actually resize under X11.
The same works as expected under Wayland session.

Tested on: Ubuntu 23.10 - KDE 5.27.10, KF 5.112.0, QT 5.15.10
Also on Ubuntu 24.04 with also 5.27.11

Reproduction is simple.
Install Kubuntu 23.10 or 24.04, Open Application Launcher by clicking the button in in the panel. Move cursor to the edge of the applet window, try to resize. On X11 the cursor just leaves the window border and does nothing. On Wayland the cursor "grabs" the window edge and resizes it.

Comment 1 Nate Graham 2024-08-01 22:00:37 UTC

Does it affect every widget, or just Kickoff?

Any chance you can try to reproduce it in Plasma 6? I'm pretty sure it's fixed there.

Comment 2 Eugene San 2024-08-02 00:24:41 UTC

(In reply to Nate Graham from comment #1)
> Does it affect every widget, or just Kickoff?
Nice catch.
I didn't think about checking other pop-up windows but all pop-up windows opened by widgets (audio, battery, bluetooth, calendar etc) can't be resized.
Mouse cursor changes when reaching window edge but it doesn't react to clicking.
> 
> Any chance you can try to reproduce it in Plasma 6? I'm pretty sure it's
> fixed there.

I tested on Neon (Plasma 6.1.3) and all pop-up windows are resizable as expected.
Unfortunately, many Debian/Ubuntu users are stuck with 5.27 for a couple of years so fix for 5.27 would be greatly appreciated.

Comment 3 Nate Graham 2024-08-02 01:07:59 UTC

Thanks for the info. At this point I think we have to call this one fixed in 6.1. Regrettably, there just aren't development resources to backport bugfixes all the way back to 5.27 these days (assuming anyone could even find the exact thing that fixed it). Ideally the distros maintaining 5.27 for their users could put some resources into this.