Bug 335510

Summary:	after changing screen resolutions, icon sizes are unusably large in kickoff
Product:	[Plasma] plasmashell	Reporter:	mu3en <mu3en>
Component:	Application Launcher (Kickoff) widget	Assignee:	Sebastian Kügler <sebas>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bhush94, kde, notmart, spaced.wombat
Priority:	NOR
Version:	master
Target Milestone:	1.0
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	image of the above described scaling bug second inage of the scaling bug neon5-201406200837.iso before dpi setting neon5-201406200837.iso at 125 dpi scaling

Description mu3en 2014-05-29 09:59:23 UTC

After resizing screen setup via xrandr or via kscreen in project neon, the kmenu icons become oversized and alignment makes them invisible. Same/similar dpi/scaling effect is seen with other elements (burger menu on panel, burger/ex-cashew on desktop activity).

Reproducible: Always

Steps to Reproduce:
1. switch resolutions and/or screen arrangements using xrandr or kscreen
Actual Results:  
brief high cpu activity, plasma crashes, konsole/system settings crashes, plasma reloads with the new settings, but with the scaling issues described above. cpu activity is consistently high on interaction with plasma elements such as the kmenu thereafter.

Expected Results:  
nothing crashes. resized/rearranged screens/desktops and rescaled/dpi adjusted for various desktop and panel elements/widgets.

kubuntu 1404 project-neon only minimal system UEFI booted on core i7 all intel system76 Gazelle Pro P8

Comment 1 Marco Martin 2014-05-29 10:02:28 UTC

what is kmenu?
and please, for graphical bugs, please provide a screenshot

Comment 2 mu3en 2014-05-29 20:35:11 UTC

Created attachment 86909 [details]
image of the above described scaling bug

took these using the full testing ISO provided, rather than the custom ubuntu install.

Comment 3 mu3en 2014-05-29 20:36:09 UTC

Created attachment 86910 [details]
second inage of the scaling bug

same as above

Comment 4 mu3en 2014-05-29 20:40:09 UTC

i don't think i made up the "K-menu" thing by the way, pretty sure it was called that long before any of this plasma business... seems to be somewhat generically called "Application Launcher" now.

Comment 5 mu3en 2014-05-29 20:43:29 UTC

so the second comment is before resizing/rescaling/rearranging the screens
the third one is after

[it would also be nice to edit the comments to correct typos or add info instead of just adding endless new ones].

Comment 6 mu3en 2014-05-29 23:21:22 UTC

in the initial screenshot, i've just run 'xrandr --output LVDS1 --off --output HDMI1 --mode 1920x1200' (LVDS1 is 1920x1080)
the weird black artifacts in the background are (i assume) the desktop not having redrawn yet, which i probably a bug in itself, although unrelated. if i switch desktops or whatever, the background redraws as expected.

Comment 7 mu3en 2014-05-29 23:27:05 UTC

also, on the live cd version, there is no crash related to this change in resolution, just the strange scaling - which changes the severity i guess.
(the large scaled plasma elements/icons are not in themselves bad,  by the way, but the panel and application launcher elements need some sort of dynamic resizing to cope, or the icons should scale differently.)

Comment 8 Marco Martin 2014-06-24 10:53:44 UTC

is the "force fonts dpi" checkbox set in the fonts kcm?

Comment 9 mu3en 2014-06-25 19:32:53 UTC

hey,
so, basing this off neon5-201406200837.iso

see screenshots above for the difference without dpi scaling and with 125dpi scaling (which looks good under KDE4.x on this screen/resolution)

Comment 10 mu3en 2014-06-25 19:34:06 UTC

Created attachment 87403 [details]
neon5-201406200837.iso before dpi setting

Comment 11 mu3en 2014-06-25 19:34:57 UTC

Created attachment 87404 [details]
neon5-201406200837.iso at 125 dpi scaling

Comment 12 Adi Stadi 2014-08-21 20:30:11 UTC

Screenshots looks same as bug 338308.
xrandr output? Monitor dimension correct? May be a edid problem.

Comment 13 David Edmundson 2014-08-23 18:54:15 UTC


*** This bug has been marked as a duplicate of bug 338308 ***