Custom Query (16363 matches)
Results (955 - 957 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15365 | obsolete | USB problem after upgrading to 5.0.18 | ||
| Description |
Hello, I have been in the community and request assistance since I could not find a solution in web. Here is the issue: I am running ubunty 14.04 LTS as the host system. Up to version 4.3.12 I have not had any issues with USB everything worked fine. Earlier I tried 4.3.16 and did not work. Now I have upgraded to 5.0.18. In summary 4.3.12 was the last version which works fine for me. Of course I could go back to 4.3.12 however I decided to to contact you for a deep dive and hopefully for support since I believe that I am not the only person in the world having this issue but maybe the first one to seriously willing to tackle it. I am added to vboxusers and have installed the right extpack. Everything seems to be fine according to the community moderator. But it is not. When I start vbox and try to add a USB filter device I got the greyed out <no device available> even though it is visible in Ubuntu. As stated the last working release for me was 4.3.12. Let me know what kind of information you need in order to investigate. Thanks |
|||
| #2702 | wontfix | QGtkStyle cannot be used together with the GTK_Qt engine. | ||
| Description |
I installed VirtualBox-2.0.6_39765_fedora9-1.i386.rpm on Fedora 10. I did not get any errors during the install but I did get SELinux errors. SELinux is now permanently disabled. I added the user to /etc/group: vboxusers:x:501:xyzuser When I run #VirtualBox I get the VirtualBox Personal use and Evaluation License (PUEL) box to pop up but the I Agree and I Disagree buttons are both grayed out. If I run VirtualBox as root the same problem with the PUEL box but I also get this message: Qt WARNING: QGtkStyle cannot be used together with the GTK_Qt engine. Qt WARNING: Qt: Session management error: None of the authentication protocols specified are supported I have no idea what this means. Can you help please? |
|||
| #11796 | obsolete | Mouse Integration Wacky on Dual Monitors | ||
| Description |
I hope this helps make vBox a better product. I searched, and didn't see this already submitted. When running Virtual Box in a Windows 8 host, and dual monitors: The mouse integration will be disabled correctly when the vBox VM is on the main monitor. If the vBox VM is on the secondary (or 3rd) monitor, the mouse integration is "wacky". It doesn't trully get disabled. Yet if the VM is moved to the main monitor, it works flawlessly. |
|||

