After upgrading from Mageia 4 to current Cauldron, the maximum resolution has changed from 1176x885 to 1360x768, resulting in a loss in vertical screen space. Also, when X is running, rebooting or powering off the system (either through the KDE menu or reboot/poweroff commands in a terminal) causes the system to freeze. Reproducible: Steps to Reproduce:
The screen size issue logically would seem to be an issue in x11-driver-video-vmware. The freezing issue may not be. I have a server test VM and a desktop test VM. The server VM doesn't run X by default, but I can put it into graphical.target. Both VMs use KDM for login, but the server one uses IceWM for the desktop and it reboots or poweroffs fine. The desktop one uses KDE and has the problem. Another difference is the desktop one is using the Default-kde4-config and the server one is using the vanilla-kde4-config. A physical machine with KDE is working fine though.
CC: (none) => lmenut
Indeed the shutdown/reboot freezing issue is a KDE issue. It works fine from IceWM on that same desktop VM. I see some log messages that may give clues, but I'll split that issue into another bug.
Blocks: (none) => 14992
This bug is now just about the loss of vertical screen size.
Blocks: 14992 => (none)Summary: screen size and rebooting issues with graphical desktop VMWare VM => loss of vertical screen size with graphical desktop VMWare VM
CC: lmenut => (none)
Unfortunately the screen size issue isn't fixed with the latest update. Strangely, the poweroff/reboot issue is fixed though.
Source RPM: x11-driver-video-vmware-13.0.2-8.mga5.src.rpm => x11-driver-video-vmware-13.1.0-1.mga5.src.rpm
After using drakx11 to change the Monitor setting from 1024x768 generic to Plug'n'play or 1280x1024, some more resolutions become available, like 1152x864 (just a bit smaller than what I had before), and some larger ones like 1280x960 and 1440x900. drakx11 can also put a PreferredMode line in xorg.conf for 1152x864 that does work in KDM. I guess kscreen is getting its settings from randr, which gets them from the driver, which is somewhat dependent on the monitor setting, so I guess this all makes sense. It's a bit strange that I can't get back 1176x885, but maybe they decided to drop that from the driver.
It's a bummer to lose that resolution, since it was kind of a perfect size, but this is probably not so much a "bug" as a migration issue because of changes in the driver. We should probably have an errata entry for it in the Mageia 5 documentation, that people that want to use resolutions above 1024x768 in VMWare will need to reconfigure their video settings.
Well, maybe it's still a bug that it doesn't let you make full use of your capabilities. I had forgotten for a second that I had increased the video memory to 5 MB. Once back down to 4 MB, the 1152x864 is still working, but the "max" is 1360x768 again, so 864 is the largest vertical size you can get.
Whiteboard: (none) => FOR_ERRATA
David, could you write the Errata entry if you still think it's needed?
Whiteboard: FOR_ERRATA => MGA5TOO FOR_ERRATA
How's this sound? Due to changes in the VMWare Xorg module, Mageia 5 VMs may not be able to use the same screen resolution settings that older versions were able to. First, the Monitor setting now must not be set to lower than the desired resolution. Second, a resolution that makes full usage of the VM's video memory is no longer an option. Only a fixed set of standard resolutions are allowed. (mga#14974)
Looks fine.
Whiteboard: MGA5TOO FOR_ERRATA => MGA5TOO