MASTER: VirtualBox 2.0.4 through 2.2beta1 don't support xserver 1.6 in Jaunty

Bug #356264 reported by Mathias Menzer
134
This bug affects 2 people
Affects Status Importance Assigned to Milestone
virtualbox-ose (Ubuntu)
Fix Released
High
Unassigned
xorg-server (Ubuntu)
Invalid
High
Unassigned

Bug Description

[Problem]
VirtualBox 2.2beta2 was updated to work with the xserver 1.6 API, included in Jaunty. Prior versions of VirtualBox won't work with Jaunty's xserver and will lead to various problems due to the incompatibility.

Solution is to upgrade to VirtualBox 2.2beta2 or newer.

[Original Report]
Crashed on first Start in a Virtual Machine (VirtualBox) with Guest Additions installed.

Bug may also be associated with or cause higher resolutions to not be selectable.
It might be related to bug #301028 (VirtualBox OSE) or bug 335703 (similar trace)

Regression since Intrepid. Earliest apport report is bug 340305 on 3/9/09

ProblemType: Crash
Architecture: i386
Disassembly: 0x0:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/Xorg
Package: xserver-xorg-core 2:1.6.0-0ubuntu9
ProcAttrCurrent: unconfined
ProcCmdline: Xorg :99 -configure
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #40-Ubuntu SMP Fri Apr 3 17:39:51 UTC 2009
Signal: 11
SourcePackage: xorg-server
Title: Xorg crashed with SIGSEGV in InitOutput()
Uname: Linux 2.6.28-11-generic i686
Stacktrace:

Just this :«
~$ sudo /media/cdrom0/VBoxLinuxAdditions-x86.run
[sudo] password for jea:
Verifying archive integrity... All good.
Uncompressing VirtualBox 2.1.4 Guest Additions for Linux installation...........................................................................................................................................................................................................
VirtualBox 2.1.4 Guest Additions installation
Building the VirtualBox Guest Additions kernel module...
Building the shared folder support kernel module...
Installing the VirtualBox Guest Additions...

Warning: unknown version of the X Window System installed. Not installing
X Window System drivers.
Successfully installed the VirtualBox Guest Additions.
You must restart your guest system in order to complete the installation.
»

[backtrace]
Thread 1 (process 3361):
#0 0x00000000 in ?? ()
#1 0x080b02aa in InitOutput (pScreenInfo=0x81f6c20, argc=3, argv=0xbf8b2e64)
    at ../../../../hw/xfree86/common/xf86Init.c:797
 i = <value optimized out>
 j = <value optimized out>
 k = <value optimized out>
 scr_index = <value optimized out>
 modulelist = <value optimized out>
 optionlist = <value optimized out>
 layout = <value optimized out>
 screenpix24 = <value optimized out>
 pix24 = <value optimized out>
 pix24From = <value optimized out>
 autoconfig = 136208372
 configured_device = <value optimized out>
#2 0x08072141 in main (argc=3, argv=0xbf8b2e64, envp=0xbf8b2e74)
    at ../../dix/main.c:315
 i = <value optimized out>
 alwaysCheckForInput = {0, 1}

http://launchpadlibrarian.net/23694853/ThreadStacktrace.txt

[solution]

This was solved in the VirtualBox forums (http://forums.virtualbox.org/viewtopic.php?f=3&t=15512). Essentially what you have to do is edit the install script.

Step 1: run the regular export script with
     sudo ./VBoxLinuxAdditions-x86.run --target ~/tmp/
   where ~/tmp is any folder where you want to extract a bunch of files to.

Step 2: go to that folder (~/tmp/ in my case) and open the install.sh file. Go to line 415 and change
    15 1.5.99.* | 1.6 )
   to
    15 1.5.99.* | 1.6.0 )

Step 3: run install.sh
    sudo ./install.sh
  after this, just restart and everything should work properly.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02)
00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef]
     Subsystem: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] [1022:2000]

Revision history for this message
Mathias Menzer (mfm) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
InitOutput ()
main ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Bryce Harrington (bryce)
tags: added: crash
Changed in xorg-server (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
summary: - Xorg crashed with SIGSEGV in InitOutput()
+ Xorg crashed with SIGSEGV in InitOutput() - VirtualBox with Guest
+ Additions
Bryce Harrington (bryce)
description: updated
Bryce Harrington (bryce)
visibility: private → public
Bryce Harrington (bryce)
description: updated
Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Bryce Harrington (bryce)
description: updated
Bryce Harrington (bryce)
description: updated
summary: - Xorg crashed with SIGSEGV in InitOutput() - VirtualBox with Guest
- Additions
+ VirtualBox 2.0.4 through 2.2beta1 don't support xserver 1.6 in Jaunty
summary: - VirtualBox 2.0.4 through 2.2beta1 don't support xserver 1.6 in Jaunty
+ MASTER: VirtualBox 2.0.4 through 2.2beta1 don't support xserver 1.6 in
+ Jaunty
Changed in virtualbox-ose (Ubuntu):
importance: Undecided → High
status: New → Triaged
Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
status: Triaged → Invalid
Revision history for this message
mjhooker (mjhooker) wrote :

Bug 366773 has been linked against this bug (356264) as a duplicate.

This bug relates to xorg-server while 366773 relates to vbox0 network interfaces not being created, in fact they don't seem to be needed anymore.

I don't see the connection, could somebody justify the link.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

karmic has 3.0.2, and an update to jaunty is very unlikely, unless it's backported.

Changed in virtualbox-ose (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.