Bug 348647

Summary:	Plasma 5 does not stretch a screen wallpaper when resizing a VirtualBox window
Product:	[Plasma] plasmashell	Reporter:	Aliaksei Herman <aliaksei.herman>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bshah, oliviervdtoorn, plasma-bugs-null, pleasefixwebkit
Priority:	NOR
Version First Reported In:	master
Target Milestone:	1.0
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Aliaksei Herman 2015-06-03 16:54:27 UTC

There is a problem with stretching a wallpaper/solid color area when resizing a VirtualBox window.
The wallpaper area must be changing the resolution to cover/fit the whole screen everytime we change resolution of the window.

I'm using Kubuntu 15.04 with Plasma 5 as a guest system on VirtualBox.

Configuration:
3D support enabled, 120MB of video memory, 2 cores, 4096MB RAM

Reproducible: Always

Steps to Reproduce:
1.Run Kubuntu 15.04 under VirtualBox
2.Install Guest Addidions (Settings - Drivers Section)
3.Boot with a small VirtualBox window and then maximize it.

Actual Results:  
I suppose the screenshot explains everything perfectly
http://i.imgur.com/vyAFtmO.png

Expected Results:  
The background wallpaper/solid color area should have been resized to fit new screen resolution, when resizing VirtualBox window.

Host system is Windows 8.1 64bit.

Comment 1 Olivier van der Toorn 2015-06-24 09:10:51 UTC

This happened under KVM too. For me the fix was to change to scaling option to something else. It would redraw the wallpaper, filling the entire screen.

Comment 2 steve 2015-06-24 09:38:26 UTC

+1 also happens with VMware Fusion.
low priority but an ugly UI glitch that indeed should be addressed. example of the bug in action:
https://youtu.be/gxhA7Vv_5ng?t=2m59s

Comment 3 steve 2015-06-24 09:39:40 UTC

Also with two independent users running into this bug, not sure why this is still on "unconfirmed" but I'm not familiar with the KDE QA policies.

Comment 4 Bhushan Shah 2015-06-25 07:27:21 UTC


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