Auto resize guest window size suddenly went to greyed out and doesn't work anymore

[VChris75]

I've been using Virtualbox 5.0 for several months, everything was fine until today. Auto resize of guest had been worked fine.
But today from one moment to the next Vbox suddenly crashed, and when I restarted it, auto resize didn't worked anymore. In the top menu of the VM window View/Auto resize... menu item is disabled (greyed out), and my VBox window is fixed sized, much smaller than my desktop.
My system's specifications:
Host: Fedora 23 Workstation
Guest: Win 8.1
I've removed my virtual machine, but keep the vdi file, and add the VM again with the same vdi. The issue is still present.
I've updated my Virtualbox to 5.1 hoping it will resolve my problem. But after upgrading to 5.1 the issue is still present.
Thereafter I've upgraded my Linux distro from Fedora 23 to Fedora 24 hoping it will resolve my problem, but the issue is still present.
I don't know what to do now
Could somebody help me, because my VM is unusable in 1024x768 for me. I need 1920x1080 resolution.
It had worked perfect for months, but from one moment to the next it doesn't work anymore, and I don't know why, and what happened
Hoping somebody can help me to resolve this issue. Thanks for any help!

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[VChris75]

Thanks for your quick reply, perryg.
I've attached the log file.

[VChris75]

In my previous post I've attached the log while the VM was turned off.
In this post I am attaching an other log file, which was saved while the WM is turned on.

[Perryg]

The log files do not show a reason for your issue. I would mention that giving all of the cores from your host to the guest can cause problems, although this probably would not be one.

I would remove the current version of VirtualBox and reboot the host to make sure it is all cleared and then install again. Then post the /var/log/vbox-install.log along with dmesg as an attachment.

[VChris75]

I've removed VirtualBox 5.1, then reboot. Then I've reisntalled Virtualbox, added the VM again, but the issue is still present.
I am attaching the two files.

[Perryg]

Strange thing it says it is removing 5.0.26 and then installs a slightly different version of 5.0.26 in the build log. For what ever reason the old version never truly was removed ( or so it seems )

Another thing I see in the logs is reference to SELinux having issues. This can happen sometimes and you can try to install by first disabling SELinux and rebooting. Edit the /etc/selinux/conf file and it tells you how to disable it. Re-enable it after the install.

[VChris75]

It is very strange, because I've installed 5.1 not 5.0. Previously 5.0 was installed on my system few days ago, but I've removed that version and then install 5.1

Could you tell me how can I remove fully every packages which wasn't removed fully?
Or how can I remove every VirtualBox related package with one command?

[Perryg]

The only way I was able was searching for the names I posted already and purging dkms. Here again I have no idea what Ubuntu calls these packages.

[VChris75]

Perryg, I am using Fedora, not Ubuntu

I've made a try.

1. set selinux to disabled
2. manually find all VirtualBox packages and remove them
3. delete ~/.config/virtualbox folder
4. remove VBox repo
5. reboot
6. reinstall VBox
7. add VM again

But the problem is the same...
I've attached log files again.
Would you like to see them?
Is it possible I have a graphic driver issue in my host?

[Perryg]

I am using Fedora, not Ubuntu

Yes I know but posted wrongly. Happens from reading too many posts at the same time. I looked at your logs and all looks like it should work. I can't explain why the install log is still picking up the 5.0.26 version to remove since it should be long gone and you said you deleted everything some time ago. I don't know what else to tell you at this point. You might try posting a ticket at bugtracker

[VChris75]

I am using Fedora, not Ubuntu

Yes I know but posted wrongly. Happens from reading too many posts at the same time.

No problem

As I mentioned above, there was a VBox crash or a Gnome Shell crash (?) when this issue had just begun.
Isn't it possible that it is related to a Gnome Shell crash and the problem is not related to VBox, but it is related to Gnome Shell or any other Fedora related module/driver (eg.: Xorg, or any other else)?

[Perryg]

Anything is always possible I guess but the core issue would be in the host side code. I don't think Gnome would be the cause but Xorg ...maybe. Host GPU drivers, absolutely.
I don't do a lot with rpm builds as I use debian builds exclusively, but I have heard that some of the rpm builds are pushing wayland and that might also be a reason. If this happened to me I would wonder what actually happened with the crash? What might have changed or become corrupt. You also might install another DT manager like cinnamon and see if that changes anything ( DTs can reside together ). I have also seen that lightdm has been causing issues lately as well.

[VChris75]

Thanks for the tips, I will try them. Hoping it will resolve my problem.

[VChris75]

Hi Perryg,
Finally I bought a new motherboard, a new i5 CPU and an SSD drive. My GPU, DDR3 is the same as erlier.

I made a clean Fedora 24 install to the new hardware. Formatting the SSD.
Install Virtualbox 5.1 (SE Linux alert happened during installation)
Create a new virtual machine. Installed Win 8.1 on it.
And the suprise came here... After installing Guest additions there is no window resize... It is greyed out, there is no desktop integration, no auto guest display resize, no full screen... Nothing works... My screen is fixed, 1024x768.
I am very confused. Who can help me in the next 1-2 day? I need both Linux as host and Win as guest for my work... I have to work with this system, as earlier, for months without problem. Why did it happened? And why did it happen on a new system again???
Please, somebody help me...