Lucid Lynx: /usr/bin/X: Segmentation fault at address (nil)

Bug #504254 reported by John Doe
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: xorg

I hope this time i filed the Bug in the right place. On Lucid (incl. updates from 07.01.10) X is aborting when GDM should load. I'm getting an "Ubuntu runs in low graphics mode" message. Continuing in low graphics mode works only when Ubuntu was started with the "nomodeset" Kernel Option.

When not using this, returning to the Console in Low Graphics Mode Options does not work, I only get a black screen.

Using "nomodeset", returning to the console and do a "startx", I get the following messages:

22: /usr/bin/X (0x8048000+0x1e931) [0x8066931]
Segmentation fault at address (nil)

Caught signal 11 (Segmentation fault). Server aborting

After trying two or three times, startx works sometimes, sometimes not.

ProblemType: Bug
Architecture: i386
Date: Thu Jan 7 14:54:36 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091221)
MachineType: ASUSTeK Computer INC. V6V
Package: xorg 1:7.5~3ubuntu4
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-9-generic root=UUID=6efc0a1a-f435-4f5a-88a0-15eab6fcf490 ro quiet radeon.modeset=0 rootflags=data=writeback
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-9.13-generic
RelatedPackageVersions:
 xserver-xorg 1:7.5~3ubuntu4
 libgl1-mesa-glx 7.6.1~rc3-1ubuntu1
 libdrm2 2.4.14-1ubuntu2
 xserver-xorg-video-intel 2:2.9.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20091125.0061c4db-0ubuntu1
SourcePackage: xorg
Tags: lucid
Uname: Linux 2.6.32-9-generic i686
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 10/12/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.name: V6V
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 2.00
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd10/12/2005:svnASUSTeKComputerINC.:pnV6V:pvr1.0:rvnASUSTeKComputerINC.:rnV6V:rvr2.00:cvnASUSTekComputerINC.:ct10:cvr1.0:
dmi.product.name: V6V
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer INC.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.32-9-generic

Related branches

Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :
Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

For the case that this bug is filed on the wrong place, some hints for me would be useful where should file this bug correct. I'm unsure with sending Bug-reports when I couldn't use apport.

Bryce Harrington (bryce)
affects: xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu)
Timo Aaltonen (tjaalton)
affects: xserver-xorg-video-ati (Ubuntu) → xserver-xorg-input-evdev (Ubuntu)
Timo Aaltonen (tjaalton)
affects: xserver-xorg-input-evdev (Ubuntu) → xorg-server (Ubuntu)
Changed in xorg-server (Ubuntu):
importance: Undecided → High
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg-server - 2:1.7.3.902-1ubuntu3

---------------
xorg-server (2:1.7.3.902-1ubuntu3) lucid; urgency=low

  [ Julien Cristau ]
  * Don't call config_init() until after InitInput() has initialized the event
    queue, so that devices don't get enabled too early (closes: #564256,
    #564324). (LP: #504254)
 -- Timo Aaltonen <email address hidden> Sat, 09 Jan 2010 19:34:30 +0200

Changed in xorg-server (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks Thorsten, this is a suitable place to file the crash bug. (xorg-server is also a suitable alternative)

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.