Custom Query (16363 matches)
Results (2482 - 2484 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4597 | fixed | Windows 7 Ubuntu 9.04 alt tab GUI freeze | ||
| Description |
Host: Windows 7 Beta 64bit Guest: Ubuntu 9.04 32bit When installing Ubuntu, pushing alt+tab when any progress bar is shown results in the entire terminal freezing. VirtualBox remains responsive and Ubuntu continues processing up until user interaction is required. I am able to alt+f4 to the debug console to view progress but the first graphical console never unfreezes. At one point, the first console became visually corrupt while the other terminals remained fine. |
|||
| #4598 | fixed | OpenGL accel seems to work, but some things cause asserts -> Fixed in SVN/3.1.6 | ||
| Description |
I'm getting this error on an OSX host with an Ubuntu Jaunty VM. Using 3.0.2 and 3.0.2 additions. OpenGL Error: Assertion failed: !context->pOwnWindow, file /mnt/tinderbox/add-3.0/src/VBox/Additions/common/crOpenGL/context.c, line 894 #0 0xb7fb4430 in __kernel_vsyscall () #1 0xb7cf44b0 in raise () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7537261 in crError () from /usr/lib/VBoxOGLcrutil.so #3 0xb7596b88 in stubMakeCurrent () from /usr/lib/dri/vboxvideo_dri.so #4 0xb75ab01c in vboxstub_glXMakeCurrent () from /usr/lib/dri/vboxvideo_dri.so #5 0xb7f6f190 in ?? () from /usr/lib/libclutter-glx-0.8.so.0 #6 0xb7f3c960 in ?? () from /usr/lib/libclutter-glx-0.8.so.0 #7 0xb7f6413e in clutter_stage_ensure_current () from /usr/lib/libclutter-glx-0.8.so.0 This is code using clutter 0.8 and works on unvirtualised ubuntu. Apologies for the heavy clutter references that follow... This problem occurs if we use clutter_stage_new(), but not with clutter_stage_get_default(). Here's the test case: #include <clutter/clutter.h>
#include <stdlib.h>
int main (int argc, char ** argv) {
ClutterActor* stage;
clutter_init (&argc, &argv);
//stage = (ClutterActor *)clutter_stage_get_default ();
stage = (ClutterActor *)clutter_stage_new();
clutter_actor_set_size (stage, 800, 200);
clutter_actor_show (stage);
clutter_main ();
return 0;
}
gcc -Wall -g test.c -o test |
|||
| #4601 | fixed | when creating multiple vboxnetX configuration is always replaced with the first one | ||
| Description |
when creating more than one host-only network (vboxnet1, vboxnet2, etc.) the configuration (ip address, netmask, etc.) is always replaced with the configuration of the first interface (vboxnet0). you can reconfigure them by hand (ifconfig/ip addr) or using vbox ui but when starting the guest vm they get misconfigured again. from the guest vm using any of the internal interfaces (no matter if they are connected to vboxnet1 or vboxnet2) you can always ping vboxnet0 ip address. vbox 2.2.4 only supports one host-only network so deploying a not so complex network scenario is currently not possible in virtualbox. |
|||

