Custom Query (16363 matches)
Results (805 - 807 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19132 | duplicate | Wrong Czech translation -> Duplicate of #4503 | ||
| Description |
when I clone VM, there is wrong time translation to Czech language --- dialog cloning machine --- time left: (zbývající čas:) x minutes (minutami), x seconds (vteřinami) correct is x minut (more than one) x vteřin (more than one) and when only one left, it's 1 minuta 1 vteřina --- hour x hodin 1 hodina --- days x dnů 1 den --- weeks x týdnů 1 týden --- months x měsíců 1 měsíc --- years x let 1 rok --- please correct it, thx |
|||
| #19130 | obsolete | screen resolution not restored at boot | ||
| Description |
Not sure if this is a vbox bug or artix bug, but maybe this can help determine which. After setting the screen resolution and rebooting, the screen comes up looking like
You can see the screen resolution really is set correctly:
The Guest Additions are up-to-date:
The firefox browser can be viewed by dragging it around into the viewable area, and you can see that I was able to snapshot the monitor configuration program as well as a terminal, so the system seems to be working correctly outside of the graphics.
Please note that I disabled 3D thinking that might help, but it didn't. Video has the full 128MB. There is enough memory I think: I admit this could be an issue with the particular configuration of this distro, which is artix, an arch-based distro without systemd. This is a recent issue that has only started NOTICING since the last GAs and/or the last repo updates -- I really don't know which might be contributing because I generally leave my VMs running for weeks at a time, unless there is some reason to restart them. I know I did not see this problem prior to this. Other VMs have experienced problems in the same period, but they are of a different nature. In one case, I had to switch display managers from slim to lightdm because slim was experiencing long delays; again, that could well be a different issue. Host is Devuan Ascii, with the latest updates applied. Thank you for your POLITE responses. Please let me know if you need more information. I also realize that a maintenance update will probably be along in the next few weeks or so. Perhaps those will clear up my current issue. |
|||
| #19127 | duplicate | Hard freeze on Centos Host system with Guest using Shared Folders | ||
| Description |
Running Centos 7.7 Host with a Windows 10 Guest using a Shared Folder. I have experienced issues in the past with Shared Folders, but in the past it only seemed to affect the Guest systems. This issue is hard to troubleshoot since the Host system freezes, I can only resolve it by unplugging the power. I have tried using the SysRq keys to no avail. In troubleshooting the issue, I have stopped all other host applications except VirtualBox and disconnected the Shared folder. For a week, I did not experience any freezing of the host the system. If I connect the Shared Folder I will randomly experience a hard freeze in a couple of hours or a couple of days. The host system has 16GB RAM and 4 cores. I am using 4GB and 2 cores for my Windows 10 1909 guest. I do not know how to troubleshoot this any further since the Host system hard freezes, I do not get any indications of problems in any of the host logs. It most likely freezes before documenting the problem. I welcome any tests or settings which you want me to implement in order to determine the problem or fixes. |
|||

