Opened 7 years ago
Closed 7 years ago
#18021 closed defect (worksforme)
Full screen crash when opening Firefox ESR
Reported by: | AD1 | Owned by: | |
---|---|---|---|
Component: | guest additions/x11/graphics | Version: | VirtualBox 5.2.18 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Linux |
Description
Once opened Firefox ESR on the guest machine and switching to full screen mode with "CTRL+F", the screen becomes unusable (I attached an image that shows the problem).
I tested it on both Windows and Linux Hosts:
VIRTUALBOX: VirtualBOx Versione 5.2.18 r124319 (Qt5.6.1)
TEST 1:
GUEST: Linux GUEST 4.18.0-kali1-amd64 #1 SMP Debian 4.18.6-1kali1 (2018-09-10) x86_64 GNU/Linux
Tested with both iso GuestAdditions and virtualbox-guest-utils, virtualbox-guest-x11
FIREFOX: Firefox Quantum 60.2.0esr (64-bit)
HOST: Linux HOST 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
TEST 2:
GUEST: Linux GUEST 4.18.0-kali1-amd64 #1 SMP Debian 4.18.6-1kali1 (2018-09-10) x86_64 GNU/Linux
FIREFOX: Firefox Quantum 52.9.0 (64-bit)
HOST: Windows 10 Version 1803 build 17134.285
Attachments (2)
Change History (7)
by , 7 years ago
Attachment: | Dispaly.gif added |
---|
comment:1 by , 7 years ago
- Your setups (all of them) suffer from major configuration issues. For example for 3 of them that I looked at (5.1.30, 5.2.8, and 5.2.18) you have a Kali Linux guest, but you've declared it as a generic Linux 2.6 guest. There is a Debian (64) template that you should have chosen.
- On all of them, you have allocated 8 GB of RAM to the guest, very close to (and in one instance over) the available memory of you host.
- You do not have the Guest Additions installed. In one case (5.2.18) that you do, the GAs (5.2.0) are seriously outdated and not in sync.
- You do not have 3D acceleration in any of the VMs.
- In all of them you have 16 MB of VRAM. Not even close to being enough.
In summary, you have seriously misconfigured your guests. But, this is not the place for discussions about guest configuration, this is the place to file bugs only.
It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".
So, if you can, please open a new thread in the Linux Guests section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.
And please stick to the latest VirtualBox only. Anything else is seriously unsupported!
follow-up: 3 comment:2 by , 7 years ago
You're right, with the modified configuration it seems to work, but I reported it as a bug because even with my configuration and Kali everything worked fine unless FF ESR was opened. My configuration and Parrot OS with FF latest version = no problem, I though it was a bug because the problem comes out only with ESR version of FF.
comment:3 by , 7 years ago
Replying to AD1:
because the problem comes out only with ESR version of FF.
Maybe because it has higher "hardware" requirements? As I said, being underpowered is not a bug.
You're right, with the modified configuration it seems to work
So I take it that you agree with closing this ticket with a [WorksForMe] resolution.
And remember the forums next time... ;)
comment:4 by , 7 years ago
Yes, the ticket can be marked as solved. Thank you for the quick replies, and I'll keep in mind to use the forum before posting here.
comment:5 by , 7 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Screen