Comment # 11 on bug 962246 from Eduardo Reyes

(In reply to Ken Johnson from comment #10)
> (In reply to Eduardo Reyes from comment #7)
> > (In reply to Dominique Leuenberger from comment #6)
> > > (In reply to Larry Finger from comment #5)
> > > > Dominique,
> > > > 
> > > > If you are not taking care of VMware, please reassign as appropriate.
> > > 
> > > I'm taking care of open-vm-tools (together with Mike)...
> > > 
> > > but not even having a crash dump or anything makes it close to impossible to
> > > guess what crashes and why.
> > > 
> > > Eduardo: can you please provide a coredump / backtrace? coredumpctl is
> > > hopefully logging something for you.
> > 
> > Dominique: you can easily reproduce the situation by performing the
> > following actions:
> > 
> > - Create a Tumbleweed VM on VMware ESXi
> > - Open a console window on VMware client
> > - Logging into the VM using Plasma 5 GUI
> > - Change the resolution of the VM display (Applications
> > Menu/Settings/Configure Desktop/Display and Monitor)
> 
> Eduardo,
> 
> I have VMware ESXi system, version 6.0.0 build 3380124, that I'm using to
> try and reproduce this crash. I'm unable to reproduce the issue as
> documented.
> 
> I created a new guest and did a network install of openSUSE tumbleweed
> (20160404). the default desktop resolution was 1024x768 and I've
> successfully switched it to 1280x800 and 1440x900 without a crash.
> 
> Please update to the latest tumbleweed snapshot and then provide a coredump
> / backtrace as requested by Dominique. You might also want to play around
> with the amount of video memory you have configured for the video card.
> 
> Guest Configuration:
>  - VM Version 11
>  - 4 GB Memory
>  - 2 CPUs
>  - 16 MB Video Memory
>  - 20 GB Thick provisioned HDD
> 
> Regards,
> Ken


My virtualized environment is built on top of VMware ESXi 6.0.0 build 3568940
and the Guest Configuration is:

 - VM Version 11
 - 4 GB Memory
 - 2 CPUs
 - 20 GB Thin provisioned HDD
 - 4 MB Video Memory which should be enough for a resolution of 1024x768 as per
VMware Video Memory Calculator

I have performed some additional tests and I may have found the cause of the
issue.

I created a new guest and did a network install of openSUSE Tumbleweed
(20160404). The default desktop resolution was 800x600 and the first time I
tried to switch it to 1024x768 the display resolution got automatically reset
to 800x600. After rebooting the VM, every time I tried to change the resolution
to 1024x768 the session got locked though without a black screen.

All this hinted a non-suficient video memory so I changed the VM video memory
to 5MB and the issue disappeared. 

Taking into account that the issue is not present at all on a similar guest
running Leap, it seems like if the memory requirements for changing the display
resolution have changed a bit.

Hope this will be helpful to solve the issue and make the display resolution
changes to work as in Leap.