Custom Query (16612 matches)
Results (43 - 45 of 16612)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7797 | fixed | "Disable Remote Display" option seems ambigious (Usability) | ||
| Description |
(Defect observed in VirtualBox 3.2.10 r66523) After checking "Enable Remote Display" in the menu bar, and you once again click on it to disable it. Then the text says "Disable Remote Display", supported by a marked check box. This is pretty confusing, since the "checkbox" represents a state, while the label suggests an action. See the attached screenshot for details. |
|||
| #3911 | fixed | "Drive 1 is not ready, Press any Key." before OS/2-Bootmanager starts => Fixed in SVN | ||
| Description |
I have an annoying observation which exists since VBox 2.1.x (maybe already in last 2.0.x): I've got several VDI's with an installation of OS/2 using the IBM bootmanager. They all boot smoothly in VBox 1.6.6. But when booting same vdi's in VBox 2.1 or 2.2 boot process stops before bootmanager menu is displayed and I get a message at the bottom of the screen saying literaly: Drive 1 is not ready, Press any Key. When hitting return booting continues normal. This does not happen when OS/2 is installed on 1st primary partition without use of bootmanager! In this case boot proceeds normally. |
|||
| #14174 | obsolete | "Effective UID is not root (euid=XXXX egid=XXXX uid=XXXX gid=XXXX) (rc=-10)" | ||
| Description |
VirtualBox does not start in Fedora 22 unless run by root, otherwise it gives the following error:
I have tried reinstalled many times, running with a different user, as well as multiple versions (4.2, multiple variants of 4.3, and even the 5.0 beta), and all of them give the same error. Other people seem to have encountered this problem but none of their solutions (namely, reinstalling) seem to work. This makes VB completely unusable for non-root users. |
|||

