Bug 510977

Summary:	Icons too small when having two rows
Product:	[Plasma] plasmashell	Reporter:	bd0
Component:	Quicklaunch widget	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	minor	CC:	kdedev
Priority:	NOR
Version First Reported In:	6.5.0
Target Milestone:	1.0
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description bd0 2025-10-23 20:31:27 UTC

SUMMARY
Since the update to Plasma 6.5.0, the Icons in a two-rowed Quicklaunch widget are much smaller because of unnecessarily large borders above and below the widget.

STEPS TO REPRODUCE
Panel height: 44
Quicklaunch settings: max 2 rows; no names; no popups

ADDITIONAL INFORMATION
I fixed this for myself by editing file
/usr/share/plasma/plasmoids/org.kde.plasma.quicklaunch/contents/ui/main.qml

After line
"Plasmoid.backgroundHints: ..."
insert a new line
"Plasmoid.constraintHints: Plasmoid.CanFillArea"

Test the modifications by restarting the panel:
$ systemctl restart --user plasma-plasmashell.service

Comment 1 TraceyC 2025-10-24 00:35:25 UTC

Thanks for the bug report. I'm not seeing a difference between the spacing in Plasma built from git-master vs Plasma 6.4.5 in Neon User Ed.
Can you share screenshots of the widget in the bugged state, and in the state after your changes? 

This may have been fixed in git-master already, but I want to verify what I see vs. what you see.

Thanks.

Comment 2 bd0 2025-10-24 16:50:33 UTC

I just found out that this is not a bug.

The increased margins on the top and bottom of the Quicklaunch widget were because of a misplaced Margins Separator widget on the left of the Quicklaunch widget. I guess I did the debian-unstable package upgrade when not all plasma related packages were available yet. This caused some problems with other widgets until I did another "apt upgrade" some hours later. I think I messed up the order of the widgets when restoring the Task Manager widget.

I just upgraded another computer from Plasma 6.3.6 to 6.5.0 (also Debian unstable), and everything worked fine there.

@TraceyC
Sorry for the inconvenience, and thanks for your efforts.

Comment 3 TraceyC 2025-10-24 17:34:42 UTC

(In reply to bd0 from comment #2)
> I just found out that this is not a bug.

Thanks for letting us know it's resolved for you. No worries about the report, things like this can happen :)