Custom Query (16363 matches)
Results (1567 - 1569 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19117 | obsolete | virtualbox service script references missing directory | ||
| Description |
If the directory "/usr/share/doc/virtualbox" does not exist, /etc/init.d/virtualbox script does not work. The script tests for the existence of the directory and if it does not exist, the script quits at that point. There is, however, a directory named "/usr/share/doc/virtualbox-6.0" and by soft linking that directory to "/usr/share/doc/virtualbox" I was able to get the script to run. This is obviously not a good solution since the next major release of virtualbox will like be named virtualbox-7.0, at which time I will need to replace the softlink. This is important because I am attempting to shut down my system gracefully rather than having all my VMs die a tragic death... this is particularly an issue upon a power failure. |
|||
| #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. |
|||
| #18494 | fixed | VBoxManage modifyvm --recording ... : Crash, Documentation wrong -> fixed after 6.0.4 | ||
| Description |
Hi, I'm running VBox 6.0.4 on Ubuntu 18.04 amd64. Recording video by using VBoxManage doesn't work for several reasons:
Maybe there are combinations of options that enable recording, but I couldn't find any. Thank you for your previous work on VirtualBox :-) Hauke |
|||

