Greetings,
I'm testing various Linux distribution to hopefully find a good Windows alternative, which brings me to the KDE Neon 5.22.4 Linux (version), installed neon-user 20210806-1520.
The OS was installed via VMware Player over WIN10.
To my surprise, even though it is a very recent version it does not give the possibility to adjust to a now common 4K (3840x2160) screen size.
In order to continue the evaluation process I opted for a suggested lower resolution, whereby I found that after selecting and accepting such, the screen would display it for about one second and immediately return to the default size.
Searching in the Forum I came across this link "https://forum.kde.org/viewtopic.php?t=157213". After implementing the given suggestion the screen stayed at any new selection I tried.
Success?
Not likely, after each restart of the VM machine the same System changes need to be made.
What is disappointing is that this issue as discussed in the above link was present in previous versions of the same OS.
I apologize for mentioning it directly to you, however after creating an account specifically for this reason, I could not locate the same thread to post there.
Well, it seems KDE Neon down, more to test.

Have you tried different VM software? Virtualbox comes to mind,

It is hard to troubleshoot something that is using visualized hardware, and complain that a 'fake' video card with virtual drivers can't output 4K video resolution. Did you install any vmware drivers inside the guest OS that might support this resolution in the guest better, and maybe fix things?

Did you try disabling kscreen2, as mentioned in the very last post in the thread? That would directly turn off the scree auto-resizing

Since you have moved on, it may be pointless to point out, but an OS that works perfectly well in a VM does not translate into one that will run well on real hardware. The reverse is true as well. Giving a USB live session would be a lot closer to the Real Thing, particularly in video related areas.


As to the OS version, KDE neon is Ubuntu 20.04 LTS, the version number you see is the Plasma (KDE) version, not the OS. The thread you reference is from when Neon was based on the previous Ubuntu 18.04 LTS

claydoh wrote:Have you tried different VM software? Virtualbox comes to mind,

It is hard to troubleshoot something that is using visualized hardware, and complain that a 'fake' video card with virtual drivers can't output 4K video resolution. Did you install any vmware drivers inside the guest OS that might support this resolution in the guest better, and maybe fix things?

Did you try disabling kscreen2, as mentioned in the very last post in the thread? That would directly turn off the scree auto-resizing

Since you have moved on, it may be pointless to point out, but an OS that works perfectly well in a VM does not translate into one that will run well on real hardware. The reverse is true as well. Giving a USB live session would be a lot closer to the Real Thing, particularly in video related areas.


As to the OS version, KDE neon is Ubuntu 20.04 LTS, the version number you see is the Plasma (KDE) version, not the OS. The thread you reference is from when Neon was based on the previous Ubuntu 18.04 LTS

Thank you for your Answer.
My answer In logical order,
Missing 4K resolution was not a complaint, but rather a disappointment. FYI 'Solus-4.3-Budgie' can display 3840x2160 via VMware on WIN 10.
All installations that I'm testing are as provided, with latest updates, no changes.
As mentioned in my first post above, I tried the disabling of 'kscreen2' and it worked for this one running of the VM. Subsequent starts of the VM require to repeat the same process each time. Not user friendly!
I have tried Linux as a VM using 'Hyper-V Manager, VirtualBox and VMware.
One distinct advantage for my purpose to use 'VMware player' is the selection of GPU memory, which is the limit of the installed GPU memory. VirtualBox absolute limit 256Mb.
My remaining question.
As you pointed out the mentioned thread was about the same issue occurring in Ubuntu 18.04 LTS, then WHY is it still occurring in Ubuntu 20.04 LTS?

Who knows? It is a virtual machine, they don't always act the same on different distros. Different kernels, luck of the draw? In this case, neon being Ubuntu 20.04 in terms of kernel and drivers would be the place to investigate any causes.

I imagine distros with similar kernel/drivers will probably act similarly.

All I am saying is don't discount something slightly minor (in relative terms, in a testing situation) in an environment that is heavily tied to non-physical hardware/emulation run in a VM to being something that will be happening in real life. Boot the iso from a USB, and see how it goes there. This goes for any distro, not Neon in particular.