atieventsd crashed with SIGSEGV in _XSend()

Bug #212026 reported by Michael Sebastian
196
This bug affects 4 people
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Installed the latest updates, rebooted, and got this crash report.

ProblemType: Crash
Architecture: amd64
Date: Fri Apr 4 16:40:33 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/sbin/atieventsd
NonfreeKernelModules: fglrx
Package: xorg-driver-fglrx 1:7.1.0-8-3+2.6.24.12-15.33
PackageArchitecture: amd64
ProcCmdline: /usr/sbin/atieventsd
ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: linux-restricted-modules-2.6.24
StacktraceTop:
 _XSend () from /usr/lib/libX11.so.6
 XQueryExtension () from /usr/lib/libX11.so.6
 XInitExtension () from /usr/lib/libX11.so.6
 XextAddDisplay () from /usr/lib/libXext.so.6
 ?? ()
Title: atieventsd crashed with SIGSEGV in _XSend()
Uname: Linux 2.6.24-15-generic x86_64
UserGroups:

Revision history for this message
Michael Sebastian (msebast2) wrote :
Revision history for this message
Michael Sebastian (msebast2) wrote :

Ran sudo /etc/init.d/atieventsd restart
and it crashed again.

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:XQueryExtension (dpy=0x538300, name=0x422726 "ATIFGLEXTENSION",
XInitExtension (dpy=0x538300, name=0x422726 "ATIFGLEXTENSION")
XextAddDisplay (extinfo=0x533990, dpy=0x538300,
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi msebast2,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in linux-restricted-modules-2.6.24:
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for fglrx bugs, which now includes a process for upstreaming bugs to AMD.

  http://bugs.launchpad.net/ubuntu/+source/fglrx-installer

To transition your bug into the new fglrx-package, we need your help. Please do the following:

 a. Verify the bug occurs in Intrepid.
     (Intrepid ISOs: http://cdimage.ubuntu.com)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Click 'Also affects distribution'
 d. Set 'Source Package Name' to 'fglrx-installer'
 e. Click Continue

Thank you. This will assist us in reviewing and upstreaming your fglrx bug, as appropriate.

[We'll expire the fglrx bugs in l-r-m-* in a month or so.]

Changed in linux-restricted-modules-2.6.24:
importance: Undecided → Medium
status: Incomplete → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

I've posted a new version of the -fglrx driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get fglrx 8.620 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

Changed in fglrx-installer (Ubuntu):
status: Confirmed → New
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) 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 → Invalid
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.