virtualbox.org

On Mac OS 10.11.6 I upgraded to VirtualBox 5.2.2 from 4.something, upgraded to Fedora 27 from Fedora 21 and I was able to login and use Fedora (had the screen flashing problem, but was able to fix that by selecting Gnome with Xorg).

I then updated the Guest Additions to 5.2.2 by mounting the iso. A popup window with a name something with GA-5.2.2 asked permission to install, and the Guest Addition was rebuilt, I closed the terminal that was used, logged out, rebooted, and now I don't get a login window. I just get a screen with the Fedora logo at the bottom.

On the Devices->USB menu I see that the Apple Keyboard is available.

What do I need to do to get a login window again.

I attached a zipped VBox.log file. Ignore the "Fedora 20" in the name in the log file, that is just the directory name, I am running Fedora 27.

Thanks,
David.

Same problem for me:

Host:
kernel-4.14.4-300.fc27.x86_64
VirtualBox-5.2-5.2.2_119230_fedora26-1.x86_64

Guest:
kernel-4.13.16-302.fc27.x86_64
Guest Additions from VirtualBox-5.2-5.2.2_119230

Graphic card:
Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X]
xorg-x11-drv-ati-7.9.0-3.fc27.x86_64

Problem:
- With Guest Additions: no gdm loging prompt just Fedora logo
- With Guest Additions removed: normal gdm loging prompt

The 5.2.x series, coupled with the ever faster changing Linux distros, have introduced quite a few issues. As it is noted in the Downloads page:

Note: The Guest Additions image with the 5.2.2 release still has some known problems with certain Linux distributions when 3D acceleration is enabled. We hope to provide updated builds here when these are fixed.

Socratis,

Thanks to point 3D Acceleration issue, it's my problem:

- with 3D Disabled and GA I get gdm loging prompt
- with 3D Enabled and GA I get only Fedora logo

Host mesa:

mesa-dri-drivers-17.2.4-2.fc27.x86_64
mesa-filesystem-17.2.4-2.fc27.x86_64
mesa-libEGL-17.2.4-2.fc27.x86_64
mesa-libEGL-devel-17.2.4-2.fc27.x86_64
mesa-libgbm-17.2.4-2.fc27.x86_64
mesa-libGL-17.2.4-2.fc27.x86_64
mesa-libglapi-17.2.4-2.fc27.x86_64
mesa-libGL-devel-17.2.4-2.fc27.x86_64
mesa-libGLES-17.2.4-2.fc27.x86_64
mesa-libGLU-9.0.0-13.fc27.x86_64
mesa-libOpenCL-17.2.4-2.fc27.x86_64
mesa-libwayland-egl-17.2.4-2.fc27.x86_64
mesa-libwayland-egl-devel-17.2.4-2.fc27.x86_64
mesa-libxatracker-17.2.4-2.fc27.x86_64

Try the newly released Guest Additions from the Development Snapshots (at the bottom of the page). r 119522 as of this writing. As you can see they're actively working on the problem. Patience is a virtue...

VBoxGuestAdditions_5.2.97-119522.iso FIXES the problem with 3D enabled

You just gave a developer their wings...
Thanks for verifying. Marking as [Fixed].

sorry to say,
but fedora27 with plasma5 does still not run with 3D enabled
i tried both guest additions (119522 and 119577), but nothing works.
plasma is coming up, the background is ok, taskbar is visible for a short moment, then the network-notification popup comes up and that's it.
No reaction on mouse events whatsoever
(fc27 is running fine though, just not the gui)

I'm afraid that due to lack of developer time, this is not something which is likely to be fixed in the near future unless we get user contributions. Just investigating to find out what is going wrong will dramatically increase the chances of a fix.

Hi, I can help if you need it, then this is something pretty much simple to reproduce and debug: just install a Ubuntu or Fedora client and run Plasma5 desktop. You will easily find it runs BUT kwin. Single apps in other environments runs, do not crash. The problem is relevant just on Kwin probably compositor. It could be some missing Nvidia virtual extensions or something like that. I think - considering it is so easy to reproduce the problem - it could be more easy for developers to debug it on them development system. Just my two cents. And Plasma5 is relevant for people running Virtualbox, if you do not fix it, it will be around beouse I suppose many people need Plasma5 desktop.

Reproducing it is not what takes time; debugging it is what we do not have time for. If this were important enough to users I think that someone would take the time to do that (or users who do not have the skills would look for someone who does).