Comment # 10 on bug 962246 from Ken Johnson

(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