Hi,

I tried the new Slackware-13.1 under Virtualbox (3.2) and after quitting KDE the guest machine (Slack13.1) freezes. The Xorg.log file has at the end the followings rows:

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a1e6b]
1: /usr/bin/X (0x8048000+0x57b75) [0x809fb75]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
3: /usr/lib/xorg/modules/drivers/vboxvideo_drv.so (0xb72b3000+0xc7b7) [0xb72bf7b7]
4: /usr/bin/X (AddScreen+0x198) [0x807b978]
5: /usr/bin/X (InitOutput+0x820) [0x80afc00]
6: /usr/bin/X (0x8048000+0x1b200) [0x8063200]
7: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb73aab86]
8: /usr/bin/X (0x8048000+0x1afa1) [0x8062fa1]
Segmentation fault at address 0xc

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting

My questions is, that it is so only on Virtualbox?

Thanks for the replies.

Well, it doesn't happen on my machine, if that's what you're asking. What happens when you run without the vboxvideo_drv? The vbox driver seems the most likely culprit.

Ive had to change in /etc/kde/kdm/kdmrc the line for [X-:*-Core] TerminateServer=true now my vm doesnt hang, also fixes it for intel and ati/xorg/&fglrx.

Thanks for the answers, the problem is only under vbox, when I installed it on my system to harddisk, the problem doesn't exist anymore.

Confirmed.

If you run Slackware 13.1 under VBox and you want to use kdm (runlevel 4) you must set this option or it will crash on logout.

Also remember that running under run level 4 (VM or not) you need to add yourself to plugdev and friends groups or you will have limited use of the hardware (ie no sound).

Hi all,

What I experience, with my slack 13.1 virtual machine, is that X11 hangs completely at start up. I tried to set "TerminateServer=true" in kdmrc as suggested in this thread, but I've seen no improvements. In fact, the hang happens regardless the runlevel I choose to start. No problems if I start in runlevel 3, at least I can login at console and execute any command. When I launch "startx", the server starts but does not respond to keyboard neither mouse. The same thing happens when I start with kdm - I see the login screen but cannot enter anything.

The operating systems is still alive because it answers to ctrl-alt-canc signals sent from Virtualbox menu and reboots the machine. Apparently, it seems X can't read any input. I thought it was due to wrong Xorg.conf settings so I tried to copy it from another VM I have (OpenSuse 11.2) that works nicely but nothing changed.

My Virtualbox is a 3.1.8, the guest additions were successfully installed in VM. Is this happening to anybody out there?

I'll try to upgrade to 3.2.4 then let's see. It would be not so big deal, except for the annoyance to upgrade also the host additions on any VM I have (actually 6) so I would be happy to avoid that.

Thanks for your answers

I did the upgrade mentioned above. Still no news. The mouse arrow moves, passing above buttons, the buttons highlights but clicking the mouse they don't react. Absolutely nothing can be typed at keyboard