virtualbox.org

Today, when I realised the new version of Virtualbox, I dowloaded it removed the older version from the system and intalled the new. After these steps I logged out and in and I started the Virtualbox from the Gnome menu but it didn't started rather the xorg made a restart like I press the control alt backspace keys. I saw the logfile of the xorg and I found this:

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x7e) [0x80c91ce]
1: [0xb7efb400]

Fatal server error:
Caught signal 11. Server aborting

I tried to reinstall Virtualbox recompile the vbox kernel module wich was wasting of time. Did anybody see similar problem with Virtualbox 3.0.2. ? Previous version of Virtualbox was working fine for me, but I think newer is better. Where could I make mistake?

I have the same problem on Debian 5.0 AMD64, nvidia graphic driver.
I'm using a custom 2.6.23.1 kernel.
Any idea?

i have no problem on debian lenny amd64, nvidia graphic driver

alte_frequenze wrote:I'm using a custom 2.6.23.1 kernel.
Any idea?

yes

My kernel is normal. I use to accept the latest version, when there is something new in the update manager. I installed again the 2.2.4 version of Virtualbox and I will use it for a little time. Last night I was thinking on to delete config files of Virtualbox in my home directory before the start of 3.0.2 version of Virtualbox. Probably it can help, if I rename the config directory instead of delete it. Unfortunately I don't have time to do it now.

ideiglenes wrote:My kernel is normal.

i dont know if its the custom kernel, just an idea to test with standard kernel

what graphic chip, xserver-xorg-video?


edit: compiz installed? (my box runs without compiz)

I changed the kernel to linux-image-2.6.30-bpo.1-amd64 from lenny backports
and now VirtualBox starts.

My problem is solved. I installed a new Nvidia driver for my videocard and my problem disappeard. The previous version was 96.43.07 and the newer is 96.43.13. So I'm using the 3.0.2 version of VirtualBox from this moment...