Now that I am running 5.1.95, I can now maximize the VMware Player window without crashing plasma. However, the wallpaper stays small (in the upper right). Also, I cannot move the hamburger (used to be a cashew) off the bounds of the wallpaper. However, I can move konversation, KInfocenter, and Firefox (URL to imgur above, and I will attach a ksnapshot) outside the wallpaper. Reproducible: Always
Created attachment 90484 [details] Screenshot
(In reply to marco_parillo from comment #0) He means the Desktop view is stuck at the previous resolution, and not updated. Kwin gets the new resolution, but Plasma fails to update every component. The panel get's the new resolution, but not the Desktop. He ends up with a big dark unusable space (from Plasma's point of view, not Kwin's)
Steps to reproduce: Install VMware Player 6.0.4 on Win7 Install Kubuntu Vivid (15.04) in VMware Player sudo apt update sudo apt install open-vm-tools-desktop sudo apt upgrade sudo apt dist-upgrade maximize the VMware Window System Settings > Display and Monitor > Display Configuration reports 2560x1600 Open windows using either <alt F1> or <alt F2> can be created outside the wallpaper and moved inside and outside the wallpaper, but the wallpaper itself does not grow to the entire panel, nor can the hamburger / cashew be moved outside the wallpaper area.
Sounds like bug in Desktop containment/view
is the right mouse button menu working on areas outside the wallpaper? also, is it possible to move applets outside the wallpaper area? i think is the desktop window that is not resizing (as opposed to window contents) probably for KScreen not emitting proper signals?
(In reply to Marco Martin from comment #5) > is the right mouse button menu working on areas outside the wallpaper? > also, is it possible to move applets outside the wallpaper area? When this happens to me when this happens due to a second monitor being plugged in, I cannot bring the context menu in the black area, and also I cannot move any widgets to that area. > i think is the desktop window that is not resizing (as opposed to window > contents) probably for KScreen not emitting proper signals? Probably, I don't know exactly how that part is working.
(In reply to Marco Martin from comment #5) > is the right mouse button menu working on areas outside the wallpaper? No, inside the wallpaper, i get: Run Command... Add Widgets... Add Panel Activities Lock Widges Lock Screen Leave... Desktop Settings Outside the wallpaper, I get nothing > also, is it possible to move applets outside the wallpaper area? No, I created an Analog clock and can move and resize it within the wallpaper area, but I cannot move it outside the area. But, an application like Dolphin (not an applet) can be maximized, or entirely within the wallpaper area, entirely outside the area, orhalf in and half outside the area.
The right mouse button does work outside the wallpaper area if it is inside an application window. So when I RMB on the Dolphin Title Bar, I get Dolphin actions: Minimze Maximize More Actions > Close
I have the same issue, with VMware too. It seems kscreen always reports 800x600 screen size. It also fails to report output size (and setting the resolution doesn't work) when it uses a custom mode (ie when the VMware window has been resized by the host). After setting a standard mode with xrandr tool, kscreen works but still reports 800x600 screen. But it doesn't have any effect on the wallpaper issue.
(In reply to Loïc Yhuel from comment #9) > I have the same issue, with VMware too. > > It seems kscreen always reports 800x600 screen size. > It also fails to report output size (and setting the resolution doesn't > work) when it uses a custom mode (ie when the VMware window has been resized > by the host). > After setting a standard mode with xrandr tool, kscreen works but still > reports 800x600 screen. > But it doesn't have any effect on the wallpaper issue. Thank you for the pointer. Mine seems to be 800x600 if I am reading it correctly. mparillo@mparillo-Kubuntu-Daily:~/.local/share/kscreen$ cat 6cb97a8b7135b10da1b3a378322e99d7 [ { "enabled": true, "id": "Virtual1", "metadata": { "name": "Virtual1" }, "mode": { "refresh": 60, "size": { "height": 600, "width": 800 } }, "pos": { "x": 0, "y": 0 }, "primary": true, "rotation": 1 } ]
experiencing similar issue: two screens (using open ATI/AMD driver), Upper screen (HDMI-0) is 1920x1080, lower screen (VGA-0) is 1440x900. Hamburger/Cashew on VGA-0, when placed in a corner, rapidly switches appearance from corner hamburger to "tab" hamburger (with text beside it). Hamburger/Cashew on top screen works without issue. If this should be a new bug, please advise.
I experienced this same issue withing VMware. After changing from 800x600 to 1680x1050 and the desktop background did not resize, and right click menu unavailable beyond the confines of the previous desktop size. While playing around with these settings, the gui crashed and restarted. After this occurred, the desktop background is now properly resized, but I had to reboot to get rid of several unresponsive and minimized X-windows.
*** Bug 348647 has been marked as a duplicate of this bug. ***
This is fixed in Kubuntu Wily Daily Builds.
Great news! Can't wait to see this in a Kubuntu update.
I haven't experienced this with Plasma 5 at all. I'm using Vivid currently.
Will this be ported upstream, so that non-kubuntu users can enjoy these benefits?
(In reply to Jason Oliveira from comment #17) > Will this be ported upstream, so that non-kubuntu users can enjoy these > benefits? When I wrote, "This is fixed in Kubuntu Wily Daily Builds", I was not asserting that it was fixed by the Kubuntu team down-stream. I assume that applying updates to Plasma and/or the open-vm-tools-desktop package have resulted in this being fixed.
Resolved - Fixed. But when will the fix be in Kubuntu? What's the process for that to happen?
Kubuntu has many different releases. In Vivid, it probably won't. It might have a chance with backports, but not sure about that. It might be in Wily. But you can always experiment with the CI.
(In reply to steve from comment #19) > Resolved - Fixed. But when will the fix be in Kubuntu? What's the process > for that to happen? At least for me, it is already in the Wily (soon to be 15.10) daily builds. If you can test it yourself to confirm, that would be great.
Installed 15.10 beta as described here: https://wiki.ubuntu.com/WilyWerewolf/Beta1/Kubuntu Confirming the fix. Not sure who here has editing power, but this bug should probably be "Confirmed Fixed".
Closing due to popular confirmation.