[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #18 from Martin Gräßlin--- All right that might explain it. I only tested with Cirrus so far as I had some bug reports regarding Cirrus to fix as well. Will try again with QXL. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #17 from OlafLostViking--- You did check the setting in the menu mentioned in comment #14? I just tried all the GPUs available in KVM/virt-manager in Neon: * QXL: see above * Virtio: won't work with Neon, but in other distributions it behaves like QXL * Cirrus: does not report the true window resolution "to xrandr" * VGA: offers 800x600 as the only resolution available, no matter the host window size * VMVGA: lots of funny effects/flickering, locks up(!) after ksplash * Xen: doesn't come up at all To summarize: I'd say that for now QXL and in the long run Virtio are the two relevant GPUs for a Linux/KDE desktop in a KVM VM. The others are probably not that important for KWin (just my personal opinion!)? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #16 from Martin Gräßlin--- no dice, also with X11 it doesn't do any changes to xrandr. Does one need to do anything else? Specific GPU in kvm, or something like that? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #15 from Martin Gräßlin--- I have now started spice-vdagent inside the VM (that was missing) and checked the auto resize option. But I still don't get any changes regarding the xrandr output - might be related to me running Wayland. Looks like virt-manager overall is not Wayland ready. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #14 from OlafLostViking--- Oh, and it seems you have to select `View -> Scale Display -> Auto resize VM with window` in the virt-manager window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #13 from OlafLostViking--- Are you using spice in the virt-manager and ran spice-vdagent inside of the VM? The spice protocol is the one responsible for the integration of host and guest. In Neon it is in universe/x11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #12 from Martin Gräßlin--- I now have a VM running through virtmanager. But I don't understand how I can resize the VM window. If I resize the window it does not affect xrandr at all. There are no changes. Any ideas what I do wrongly? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #11 from Martin Gräßlin--- Not the result I expected, but also helps. It looks like the resolution changes, but our software stack does not react on it. That must be an XRandR event we don't handle yet. Well I need to create a VM for another bug anyway, so can investigate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #10 from OlafLostViking--- > Could you run xrandr before and after resizing the VM window and diff the > change? Sure thing (using Neon): # after booting in a VM window with 1280x720, internal resolution 1280x720 after login $ xrandr > xrandr.before $ qdbus org.kde.KWin /KWin supportInformation > qdbus.before # increasing VM window size, no touching internal settings $ xrandr > xrandr.bigger $ qdbus org.kde.KWin /KWin supportInformation > qdbus.bigger # decreasing VM window size, no touching internal settings $ xrandr > xrandr.smaller $ qdbus org.kde.KWin /KWin supportInformation > qdbus.smaller $ diff xrandr.before xrandr.bigger 3c3 <1280x720 59.86*+ --- >1512x893 59.84 + 13a14 >1280x720 59.86* $ diff xrandr.before xrandr.smaller 3c3 <1280x720 59.86*+ --- >1064x664 59.86 + 13a14 >1280x720 59.86* $ diff qdbus.before qdbus.bigger $ diff qdbus.before qdbus.smaller -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #9 from Martin Gräßlin--- > Changing the size of the outer VM window does _not_ alter the output of the qdbus query This is very interesting. This means that we don't get an xrandr update when the window changes. Which would explain everything here. Could you (no need to do on multiple distributions) run xrandr before and after resizing the VM window and diff the change? My assumption is that the Screen 0 changes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #8 from OlafLostViking--- === Setup === The following steps have been tried on these installations within a libvirt/KVM VM: - Neon (user): Qt 5.7.0, KWin/Plasma 5.7.0, kf5 5.24, QXL (Virtio doesn't even reach X11/SDDM) - Archlinux (kf5-only): Qt 5.7.0, KWin/Plasma 5.7.0, kf5 5.23, QXL as well as Virtio - Manjaro (KDE): Qt 5.7.0, KWin/Plasma 5.6.5, kf5 5.23, QXL - openSUSE (Tumbleweed): Qt 5.6.1, KWin/Plasma 5.6.4, kf5 5.23, QXL as well as Virtio All were updated to use the repository packages of today (2016-07-11) and rebooted while having 1280x720 set as desktop resolution. === Booting === They boot into a default sized (1024x768) SDDM, which doesn't react on VM window changes (unlike f.ex. GDM that I tested before in another VM, see comment #2). After logging in, Plasma/KSplash adjusts to the resolution of the last session. (At least most of the times... I finally gave up for now finding a pattern - I guess using xrandr vs kscreen makes a difference... But that's probably for another bug report one day ;-) ) === QDbus === Output of the qdbus command after login: ```[olaflostviking@valhalla ~]$ qdbus org.kde.KWin /KWin supportInformation | grep -A7 Screens ```Screens ```=== ```Multi-Head: no ```Active screen follows mouse: yes ```Number of Screens: 1 ``` ```Screen 0: ```- ```Name: Virtual-1 ### index depends on distribution ```Geometry: 0,0,1280x720 ```Refresh Rate: 60 ### exact frequency differs on distributions Changing the size of the outer VM window does _not_ alter the output of the qdbus query (`diff`ed the whole output). Using kscreen to change the resolution works as mentioned before. The output of the qdbus query changes at the "Geometry" entry only. === xrandr === With `xrandr --output Virtual-1 --mode 1280x720` I can switch to the desired resolution, too. This is correctly shown by a following `xrandr` (including * and +) as well as in the `qbus...` query on KWin (just to make it clear: the outer window size of the VM is correctly reflected by `xrandr` only but not the `qdbus` output). Thanks for having a look! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 Martin Gräßlinchanged: What|Removed |Added CC||mgraess...@kde.org --- Comment #7 from Martin Gräßlin --- two questions: 1) Can you check with qdbus org.kde.KWin /KWin supportInformation Whether KWin gets the resolution change correctly 2) Can you try changing the resolution through xrandr manually to see whether that gets applied correctly? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 OlafLostVikingchanged: What|Removed |Added Version|5.6.0 |master Platform|Archlinux Packages |Neon Packages --- Comment #6 from OlafLostViking --- Now that KDE is offering the "official" NEON packages I thought I should give them a try to rule out distribution/packaging problems. So I installed the NEON git stable image of today via ubiquity, updated it with an "apt-get update"/"apt-get upgrade" and added "spice-vdagent" to it: * neon-desktop (4+p16.04+git20160415.1334) * kwin (4:5.6.2+p16.04+git20160415.0003-0) * plasma-framework (5.21.0+p16.04+git20160416.0014-0) * sddm (0.13.0-1ubuntu5) This bug report is also valid for this installation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #5 from Mike Goodwin--- This affects me on Fedora 23 host/guest scenario with a F23 KDE Plasma 5 guest. GNOME guest of the same type works correctly. I can essentially confirm what @OlafLostViking has written. I am particularly interested in this because I use virt-manager/kvm/libvirt as a replacement for VMware/VirtualBox and I consider it a basic guest functionality. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 Mike Goodwinchanged: What|Removed |Added CC||m...@mgoodwin.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 OlafLostVikingchanged: What|Removed |Added Version|5.5.1 |5.6.0 --- Comment #4 from OlafLostViking --- Still valid for 5.6.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 Aleix Polchanged: What|Removed |Added Component|general |Multi-screen support Assignee|k...@davidedmundson.co.uk|aleix...@kde.org CC||aleix...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #3 from OlafLostViking--- Can I provide any more details of should I try out other things? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 David Edmundsonchanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from David Edmundson --- If you type "xrandr -q" does that show the updated size? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 OlafLostVikingchanged: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #2 from OlafLostViking --- Yes, it does. In the example down below I manually set the resolution in kscreen to 1280x720) and resized the window - the new resolution seems to be always the value appearing first in the list. In "virt-manager" the check box "View->Scale Display->Auto resize VM with window" is active. When I open the kscreen config now, 1024x768 is preselected in the dropdown and the "strange" resolution of my VM window is not selectable/shown in the list. Just to be very sure it's not a driver problem in my KDE VM, I just installed the "plasma" package group in my dedicated (working) GNOME VM (so everything is up-to-date [SDDM 0.13.0, Plasma 5.5.1, Frameworks 5.17.0 and Apps 15.12.0] without any old KDE libs/config etc.) and tried logging into Plasma via GDM as well as SDDM. The results are the same: * GDM adapts, Plasma starts in the "correct" resolution set by GDM but doesn't adapt anymore. * When booting with SDDM as display manager, it's already starting in a wrong resolution. A started GNOME session corrects the resolution and adapts, a Plasma session stays "wrong" and won't adapt either. [olaflostviking@kessel ~]$ xrandr -q Screen 0: minimum 320 x 200, current 1280 x 720, maximum 8192 x 8192 Virtual-0 connected primary 1280x720+0+0 0mm x 0mm 1216x591 59.72 + 1920x1200 59.88 1920x1080 59.96 1600x1200 59.87 1680x1050 59.95 1400x1050 59.98 1280x1024 59.89 1440x900 59.89 1280x960 59.94 1280x854 59.89 1280x800 59.81 1280x720 59.86* 1152x768 59.78 1024x768 59.92 800x600 59.86 848x480 59.66 720x480 59.71 640x480 59.38 Virtual-1 disconnected Virtual-2 disconnected Virtual-3 disconnected [olaflostviking@kessel ~]$ -- You are receiving this mail because: You are watching all bug changes.