Custom Query (16363 matches)
Results (424 - 426 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4083 | obsolete | vesa driver crashes X when an application tries to use Composite with XRender | ||
| Description |
I use Slackware64-current in a VM. When I try to start up KDE-4.2.3 inside the VM, with the default configuration files, the xserver crashes. By default the vesa-driver is being used. KDE4 tries to enable Desktop Effects based on XRender if it finds the vesa-driver. This does work fine on a real machine, but crashes the xserver inside virtualbox. Tested version was VirtualBox 2.2.2, Xorg-server 1.4.2, xf86-video-vesa-1.3.0 |
|||
| #4094 | obsolete | VirtualBox and Desktops.exe (from sysinternals) | ||
| Description |
I am running Virtual Box on Windows 7 RC with Desktop. On first screen I have Windows stuff. On second I have started VirtualBox running XP and on the third screen I am trying to start another VirtualBox running Ubuntu. When I am trying to start virtual box (the main UI to fire ubuntu not actual VM) I get this error message. "Failed to create the VirtualBox COM Object" "The application will terminate now" Could not lock the setting file "C:\Users\robert\.virtualbox\VirtualBox.xml" (VERR_SHARING_VIOLATION) Result Code: E_FAIL (0x80004005) Component: VirtualBox Interface: IVirtualBox {779264f4-65ed-48ed-be39-518ca549e296} I just shutdown my Virtual Box and than exited (End Tree in task manager) Desktops.exe and I can start multiple VirtualBox just fine now. |
|||
| #4095 | obsolete | Debian package: please add "Provides: virtualbox-source" to debian/control | ||
| Description |
There's a problem if you do the following:
This leads to the following: In 2. virtualbox-ose-source appears to install its files into the symlink's target. In 3. /usr/src/share/virtualbox/src/vboxdrv gets removed and a dangling symlink is left behind I've tried to workaround this using "Conflicts", but (for some reason to clarify) we provide those names (virtualbox, virtualbox-2.0, virtualbox-2.1, virtualbox-2.2) ourselves. The solution to this problems appears to be if you would add "Provides: virtualbox-source" to your packages (after all, they provide/ship it), since the packages in Debian/Ubuntu already conflict/replace/provide "virtualbox-source". See https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/379878 for the bug in Launchpad. Keep in mind that this might be wrong of course, so maybe wait if there's any negative feedback from the Debian maintainers. |
|||

