[fglrx] aticonfig crashed with SIGSEGV (aticonfig --initial -f)

Bug #181405 reported by carseneau
76
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

can't run aticonfig --initial ... xorg.conf doesn't have the lines it needs?

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Jan 8 21:49:02 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/aticonfig
NonfreeKernelModules: cdrom
Package: xorg-driver-fglrx 1:7.1.0-7-11+2.6.24.4-3.10
PackageArchitecture: i386
ProcCmdline: aticonfig --initial -f
ProcCwd: /home/sarah
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
Signal: 11
SourcePackage: linux-restricted-modules-2.6.24
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: aticonfig crashed with SIGSEGV
Uname: Linux sarah-desktop 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Related branches

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

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Timo Aaltonen (tjaalton)
Changed in linux-restricted-modules-2.6.24:
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

Unfortunately, this crash dump doesn't contain a valid backtrace (probably because aticonfig is a proprietary binary), so this bug report does not have enough information to troubleshoot.

Are you able to get aticonfig --intial ... xorg.conf to reliably crash every time? If so, can you please provide the exact command line string used, a copy of all output printed at the console, your /etc/X11/xorg.conf, your /var/log/Xorg.0.log, and your ~/.xsession-errors from after running the command?

Alternately, if aticonfig does not crash reliably every time, can you outline what situations or procedures appear to lead to a crash with it?

Thanks ahead of time!

Revision history for this message
Emiliano (emiliano-perulli) wrote :

It seems the only way to avoid the crash is to manually configure xorg.conf.
In most of the cases I experienced, xorg.conf is configured as follows: (I'll report only the lines that should be modified)

Section "Monitor"
 Identifier "aticonfig-Monitor[0]"
 Option "VendorName" "ATI Proprietary Driver"
 Option "ModelName" "Generic Autodetecting Monitor"
 Option "DPMS" "true"
EndSection

Section "Device"
 Identifier "aticonfig-Device[0]"
 Driver "fglrx"
 Option "VideoOverlay" "on"
 Option "OpenGLOverlay" "off"
EndSection

Section "Screen"
 Identifier "aticonfig-Screen[0]"
 Device "aticonfig-Device[0]"
 Monitor "aticonfig-Monitor[0]"
 DefaultDepth 24
 SubSection "Display"
  Viewport 0 0
  Depth 24
 EndSubSection
EndSection

Im my experience, adding or modifying the appropriate lines manually as above, configures the card and avoids the crash.

Revision history for this message
Emiliano (emiliano-perulli) wrote :

I dont' know if some params depend by the card model or not..

Revision history for this message
Martin Kaufmann (martin.kaufmann) wrote :

Why does Hardy have such strange problems with Ati-Cards? Bulletproof X is nice, cause i can work, but in wrong Resolution and with no 3D-Support (Ati Mobility X1400)

Revision history for this message
harrydb (harrydeboer) wrote :

Because is is not finished... If you want a stable product try ubuntu gutsy gibbon.

Revision history for this message
Bryce Harrington (bryce) wrote :

Does it work if you omit the VideoOverlay and OpenGLOverlay option lines? (If so, then maybe this is just the DefaultDepth 24 bug for -fglrx).

Revision history for this message
harrydb (harrydeboer) wrote :

I don't think so, my config does not have them and it crashed for me too.

Revision history for this message
Thomas Novin (thomasn80) wrote :

This also makes it crash:

$ aticonfig --query-monitor
Data incomplete in file /etc/X11/xorg.conf
        Undefined Device "(null)" referenced by Screen "Default Screen".
aticonfig: Parsing the configuration file failed.
The above error messages are reported from XFree86 and may assist you in
diagnosing the problem with your configuration input file. Try use -f option
to generate a new configuration file.
$ aticonfig --query-monitor -f
Data incomplete in file /etc/X11/xorg.conf
        Undefined Device "(null)" referenced by Screen "Default Screen".
Segmentation fault (core dumped)

I have the default xorg.conf which was generated by installing fglrx.

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

I'll commit a fix to dexconf. Adding 'Device "foo"' to the Screen-section makes it work. Same applies to nvidia-settings.

Changed in linux-restricted-modules-2.6.24:
status: Confirmed → In Progress
Timo Aaltonen (tjaalton)
Changed in xorg:
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg - 1:7.3+10ubuntu5

---------------
xorg (1:7.3+10ubuntu5) hardy; urgency=low

  * dexconf: Bring Device back to the Screen-section, nvidia-settings
    and aticonfig need that. (LP: #181405)

 -- Timo Aaltonen <email address hidden> Tue, 19 Feb 2008 18:19:19 +0200

Changed in xorg:
status: In Progress → Fix Released
Revision history for this message
ryan (ryan8403) wrote :

This problem is still occurring in a fresh install of Hardy with the latest updates.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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