Opened 12 years ago
Closed 11 years ago
#11575 closed defect (fixed)
Fedora Guest aborts when changing from Full-screen to normal mode
| Reported by: | Quickbooks Office | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.2.8 |
| Keywords: | Cc: | quickbooks.office@… | |
| Guest type: | Linux | Host type: | Linux |
Description
Fedora Guest aborts when changing from Full-screen to normal mode.
During log-in screen press Ctrl+f to exit full screen mode caused Fedora Guest to crash.
Attachments (3)
Change History (12)
by , 12 years ago
| Attachment: | newFedoraV4-2013-03-10-01-38-13.log added |
|---|
comment:1 by , 12 years ago
comment:2 by , 12 years ago
I got the same issue on my F18 laptop, but only after upgrading to 4.2.12
My workaround is quite simple:
- Enable 3D Acceleration
- Disable 2D Video Acceleration
I tested with Fedora 18 (3.8.6-203.fc18.x86_64) and actual vbox 4.2.12 release. VMs: Windows 7 SP1, Fedora 18 with KDE, Fedora 18 with LXDE
comment:3 by , 12 years ago
I don't remember if this crash happened while the host was using Forced Fallback Mode of Gnome.
I had to switch to Cinnamon desktop environment because Forced Fallback Mode (2d desktop?) causes many problems with VirtualBox.
You cannot see the full log in screen in 4.2.12 when exiting full screen mode. There are scroll bars. I have attached log file.
by , 12 years ago
| Attachment: | not.autoresized.properly.Cinnamon.DesktopEnv.log added |
|---|
comment:4 by , 12 years ago
Can you see from newFedoraV4-2013-03-10-01-38-13.log whether I was using Forced Fallback mode of Gnome in the Host? Maybe adding Desktop Enviroment variables in the log files for Linux Hosts/Guest is a good idea for next release?
The latest log file:
Host: Cinnamon Desktop Env. using Fedora 18 64bit Guest: Forced Fallback Gnome using Fedora 18 64bit
follow-up: 6 comment:5 by , 12 years ago
Update: Using a different VBox file but same Virtual Machine image file (.vdi) as it is immutable, I was able to kind of crash the guest.
It did not abort this time.
I was still able to see the wall paper. But I could not do anything else.
I was NOT able to login by pressing Enter (and then my password).
Attaching the log file.
PS. Enable 3D Acceleration is still checked. Will do the testing (i.e. uncheck Enable 3D Acceleration box) soon.
by , 12 years ago
| Attachment: | can.only.see.wallpaper.log added |
|---|
comment:6 by , 12 years ago
Replying to quickbooks:
Update: Using a different VBox file but same Virtual Machine image file (.vdi) as it is immutable, I was able to kind of crash the guest.
It did not abort this time.
I was still able to see the wall paper. But I could not do anything else.
I was NOT able to login by pressing Enter (and then my password).
Attaching the log file.
PS. Enable 3D Acceleration is still checked. Will do the testing (i.e. uncheck Enable 3D Acceleration box) soon.
The way to reproduce this for me was to make sure the machine started in full screen mode. So in previous session you must shutdown in full screen mode. Then when you get to log in screen press ctrl+f.
comment:8 by , 12 years ago
coredump.CrashTicket11575.tar.gz
Successfully transferred /home/user/coredump.CrashTicket11575.tar.gz at 59.38 KB/s SITE CHMOD 664 /appsdev/incoming/coredump.CrashTicket11575.tar.gz
Please let me know if you get the files (core dump & log file). File(s) may contain sensitive information.
PS. This crash occured after logging in.
comment:9 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with VBox 4.3.10.
Does this still happen with VBox 4.2.12? Does this also happen if 3D is disabled for this VM?