Xorg crashed with SIGFPE

Bug #519125 reported by Alex Mauer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Trying to use switch user or guest session.

ProblemType: Crash
Architecture: amd64
Date: Mon Feb 8 20:37:17 2010
Disassembly: 0x7ff3facb6f21: Cannot access memory at address 0x7ff3facb6f21
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Shuttle Inc SN78S
NonfreeKernelModules: fglrx
Package: xserver-xorg-core 2:1.6.4-2ubuntu4.1
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-19-generic root=UUID=dbd06dad-db9f-4d08-899e-941a39ebca01 ro quiet splash
ProcCmdline: /usr/bin/X :1 -br -verbose -auth /var/run/gdm/auth-for-gdm-od9J4H/database -nolisten tcp
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu10
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel N/A
 xserver-xorg-video-ati N/A
Signal: 8
SourcePackage: xorg-server
Stacktrace:
 #0 0x00007ff3facb6f21 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff6b03fbc0
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (Thread 17295):
 #0 0x00007ff3facb6f21 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff6b03fbc0
Title: Xorg crashed with SIGFPE
Uname: Linux 2.6.31-19-generic x86_64
UserGroups: Domain Admins
dmi.bios.date: 11/06/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: FN78S
dmi.board.vendor: Shuttle Inc
dmi.board.version: V10
dmi.chassis.type: 3
dmi.chassis.vendor: Shuttle Inc
dmi.chassis.version: H7
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/06/2008:svnShuttleInc:pnSN78S:pvrV10:rvnShuttleInc:rnFN78S:rvrV10:cvnShuttleInc:ct3:cvrH7:
dmi.product.name: SN78S
dmi.product.version: V10
dmi.sys.vendor: Shuttle Inc
fglrx:

system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-19-generic

Revision history for this message
Alex Mauer (hawke) wrote :
Revision history for this message
Apport retracing service (apport) wrote : No launchpad retracing

Unsetting the need retracing tag, there is no retracer left running on that version of Ubuntu, the crash will need to be manually retraced

tags: removed: need-amd64-retrace
bugbot (bugbot)
tags: added: karmic
Timo Aaltonen (tjaalton)
visibility: private → public
affects: xorg-server (Ubuntu) → fglrx-installer (Ubuntu)
Revision history for this message
bugbot (bugbot) wrote :

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

Changed in fglrx-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in fglrx-installer (Ubuntu):
status: Incomplete → Expired
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.