Xorg crashed with SIGSEGV in FatalError()

Bug #509378 reported by xteejx
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
New
Medium
Unassigned

Bug Description

This happened after trying to start the nvidia-current drivers in Lucid, by following the instructions on the "Known Issues" section on the wiki page for Alpha 2.

"Jockey (Ubuntu's restricted driver manager) doesn't yet support the new alternatives system used by the nvidia driver packages, so in order to install nvidia drivers you will have to install them from the command line:

    *

      sudo apt-get install nvidia-current (or nvidia-173 or nvidia-96)
    * select the alternative that matches the driver that you have installed
          o

            (e.g. /usr/lib/nvidia-current/ld.so.conf for nvidia-current):

            sudo update-alternatives --config gl_conf
    * update the ld cache:
          o

            sudo ldconfig
    * then configure your xorg.conf with:
          o

            sudo nvidia-xconfig
    * And restart your computer. "

ld.so.conf was selected in ldconfig, it was option 0

ProblemType: Crash
Architecture: i386
CurrentDmesg:
 [ 10.988104] ppdev: user-space parallel port driver
 [ 20.832160] eth0: no IPv6 routers present
 [ 109.626834] __ratelimit: 15 callbacks suppressed
 [ 109.626840] Xorg[1702]: segfault at b ip 002f42b7 sp bf867454 error 4 in libc-2.11.1.so[27e000+14d000]
Date: Mon Jan 18 22:39:44 2010
Disassembly: 0x11: Cannot access memory at address 0x11
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/Xorg
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
MachineType: Hewlett-Packard Compaq Presario CQ50 Notebook PC
Package: xserver-xorg-core 2:1.7.3.902-1ubuntu8
ProcAttrCurrent: unconfined (enforce)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-10-generic root=UUID=a27ab297-9ed1-47a0-8f4a-3a8f6926b2ab ro quiet splash
ProcCmdline: /usr/bin/X :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-UrNbSm/database -nolisten tcp vt7
ProcEnviron:
 LANG=en_GB.UTF-8
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
RelatedPackageVersions:
 xserver-xorg 1:7.5+1ubuntu1
 libgl1-mesa-glx 7.7-0ubuntu6
 libdrm2 2.4.17-0ubuntu1
 xserver-xorg-video-intel 2:2.9.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20091125.0061c4db-0ubuntu2
SegvAnalysis:
 Segfault happened at: 0x11: Cannot access memory at address 0x11
 PC (0x00000011) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 ?? ()
 FatalError ()
 _start ()
Tags: lucid
Title: Xorg crashed with SIGSEGV in FatalError()
Uname: Linux 2.6.32-10-generic i686
UserGroups:

dmi.bios.date: 06/23/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.3E
dmi.board.name: 360A
dmi.board.vendor: Wistron
dmi.board.version: 08.60
dmi.chassis.type: 10
dmi.chassis.vendor: Wistron
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.3E:bd06/23/2009:svnHewlett-Packard:pnCompaqPresarioCQ50NotebookPC:pvrF.3E:rvnWistron:rn360A:rvr08.60:cvnWistron:ct10:cvrN/A:
dmi.product.name: Compaq Presario CQ50 Notebook PC
dmi.product.version: F.3E
dmi.sys.vendor: Hewlett-Packard
fglrx: Not loaded
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.32-10-generic

Revision history for this message
xteejx (xteejx) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 FatalError ()
 _start ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Timo Aaltonen (tjaalton)
affects: xorg-server (Ubuntu) → nvidia-graphics-drivers (Ubuntu)
visibility: private → public
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.