amdcccle crashed with SIGSEGV

Bug #647802 reported by Steven
880
This bug affects 114 people
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Invalid
Medium
Alberto Milone

Bug Description

Using XBMC in Ubuntu 10.10. Stopping the movie cause this crash

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: fglrx-amdcccle 2:8.780-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sat Sep 25 22:02:27 2010
DkmsStatus: fglrx, 8.780, 2.6.35-22-generic, x86_64: installed
ExecutablePath: /usr/lib/fglrx/bin/amdcccle
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=714a9fbd-98a8-48e1-bd74-df85154d1492 ro quiet splash
ProcCmdline: amdcccle
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x57858c: cmp 0x10(%rbx),%r12d
 PC (0x0057858c) ok
 source "0x10(%rbx)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: fglrx-installer
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: amdcccle crashed with SIGSEGV
UserGroups:

dmi.bios.date: 04/15/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2005
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A785TD-V EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2005:bd04/15/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-22-generic

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

StacktraceTop:
 CXDriver::UpdateRandrConfig2 ()
 CDisplayRule2::saveConfig ()
 CDisplayRule2::SetDriverData ()
 CDisplayRule2::SetData ()
 CDisplayPage2::SetApplyData ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in fglrx-installer (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
Changed in fglrx-installer (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
visibility: private → public
Revision history for this message
CirclingTheSun (circlingthesun) wrote :

Great, I can see the bug!

I'm running a AMD Radeon HD 5770 with 3 screens attached to it on Ubuntu 11.10. When I go into the catalyst control center and adjust the monitor over scan settings it crashes when I hit apply. The settings do get applied though. Then when I want to change the refresh rate it happens again but still saves the settings. When I try to group monitors into a single desktop, it crashes and does not change any settings when I hit apply.

I'm currently running the open source AMD drivers which do not crash.

On a side note, I have 3 identical monitors but 2 of them are detected as having a refresh rate of 30hz instead of 60hz. This never happened in Ubuntu prior to 10.10. In what package do I need to report this?

Revision history for this message
rumpl (rumplstielz) wrote :

trying to configure 2 monitors with Radeon HD5770 and no setting gets saved. The ccc just disappears. Please tell what traces/logs/dumps you need for analyzing?!

Revision history for this message
rumpl (rumplstielz) wrote :

btw: using 11.10

Revision history for this message
Adrian (supercluster00) wrote :

Just updated to the latest version 2:8.902-0ubuntu1. Problem still persists.

Revision history for this message
mwolfe38 (mwolfe38) wrote :

I have this same issue in ubuntu 11.10. I have an amd 5770 card and the proprietary driver installed.

Revision history for this message
tibord (tibord) wrote : Re: [Bug 647802] Re: amdcccle crashed with SIGSEGV
Download full text (3.4 KiB)

I found a way around this issue on my system. Sorry but I am not on my Linux
box right noe so am trying to remember details; essentially the AMD Control
Center - admin version you start from the desktop DOES NOT make changes
permanently. I suspect there are permission issues when it tries to write to
configuration files.

My workaround was to launch the application from the terminal "sudo amdccle" I
think is the command. This launches the same program but the configuration
change are now saved as you would expect.

Hope this helps.

Tibord

Quoting mwolfe38 <email address hidden>:

> I have this same issue in ubuntu 11.10. I have an amd 5770 card and the
> proprietary driver installed.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (870453).
> https://bugs.launchpad.net/bugs/647802
>
> Title:
> amdcccle crashed with SIGSEGV
>
> Status in “fglrx-installer” package in Ubuntu:
> Confirmed
>
> Bug description:
> Using XBMC in Ubuntu 10.10. Stopping the movie cause this crash
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.10
> Package: fglrx-amdcccle 2:8.780-0ubuntu2
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
> Uname: Linux 2.6.35-22-generic x86_64
> NonfreeKernelModules: fglrx
> Architecture: amd64
> Date: Sat Sep 25 22:02:27 2010
> DkmsStatus: fglrx, 8.780, 2.6.35-22-generic, x86_64: installed
> ExecutablePath: /usr/lib/fglrx/bin/amdcccle
> InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
> (20100816.1)
> MachineType: System manufacturer System Product Name
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic
> root=UUID=714a9fbd-98a8-48e1-bd74-df85154d1492 ro quiet splash
> ProcCmdline: amdcccle
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_GB.utf8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x57858c: cmp 0x10(%rbx),%r12d
> PC (0x0057858c) ok
> source "0x10(%rbx)" (0x00000010) not located in a known VMA region (needed
> readable region)!
> destination "%r12d" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: fglrx-installer
> StacktraceTop:
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> Title: amdcccle crashed with SIGSEGV
> UserGroups:
>
> dmi.bios.date: 04/15/2010
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 2005
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: M4A785TD-V EVO
> dmi.board.vendor: ASUSTeK Computer INC.
> dmi.board.version: Rev X.0x
> dmi.chassis.asset.tag: Asset-1234567890
> dmi.chassis.type: 3
> dmi.chassis.vendor: Chassis Manufacture
> dmi.chassis.version: Chassis Version
> dmi.modalias:
>
dmi:bvnAmericanMegatrendsInc.:bvr2005:bd04/15/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
> dmi.product.name: System Product Name
> dmi.product.version: System Version
> dmi.sys.vendor: System manufacturer
> system:
> distro: Ubuntu
> codename: maverick
> architecture: x86_64
> kernel: 2.6.3...

Read more...

Revision history for this message
mwolfe38 (mwolfe38) wrote :

No that definitely isn't the issue.. I always run it with sudo as it will warn you about it..

Revision history for this message
celle (legrrr) wrote :

Even so, I've got it to work that way in one distro, don't remember which
one atm. In another it worked with gksu amdcccle in the alt+f2 box. A third
one I had to copy the srandr file from an old distro, and hey presto. It's
never boring :)

On Fri, Dec 16, 2011 at 12:06 AM, mwolfe38 <email address hidden> wrote:

> No that definitely isn't the issue.. I always run it with sudo as it
> will warn you about it..
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (857457).
> https://bugs.launchpad.net/bugs/647802
>
> Title:
> amdcccle crashed with SIGSEGV
>
> Status in “fglrx-installer” package in Ubuntu:
> Confirmed
>
> Bug description:
> Using XBMC in Ubuntu 10.10. Stopping the movie cause this crash
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.10
> Package: fglrx-amdcccle 2:8.780-0ubuntu2
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
> Uname: Linux 2.6.35-22-generic x86_64
> NonfreeKernelModules: fglrx
> Architecture: amd64
> Date: Sat Sep 25 22:02:27 2010
> DkmsStatus: fglrx, 8.780, 2.6.35-22-generic, x86_64: installed
> ExecutablePath: /usr/lib/fglrx/bin/amdcccle
> InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
> (20100816.1)
> MachineType: System manufacturer System Product Name
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic
> root=UUID=714a9fbd-98a8-48e1-bd74-df85154d1492 ro quiet splash
> ProcCmdline: amdcccle
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_GB.utf8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x57858c: cmp 0x10(%rbx),%r12d
> PC (0x0057858c) ok
> source "0x10(%rbx)" (0x00000010) not located in a known VMA region
> (needed readable region)!
> destination "%r12d" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: fglrx-installer
> StacktraceTop:
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> Title: amdcccle crashed with SIGSEGV
> UserGroups:
>
> dmi.bios.date: 04/15/2010
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 2005
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: M4A785TD-V EVO
> dmi.board.vendor: ASUSTeK Computer INC.
> dmi.board.version: Rev X.0x
> dmi.chassis.asset.tag: Asset-1234567890
> dmi.chassis.type: 3
> dmi.chassis.vendor: Chassis Manufacture
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr2005:bd04/15/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
> dmi.product.name: System Product Name
> dmi.product.version: System Version
> dmi.sys.vendor: System manufacturer
> system:
> distro: Ubuntu
> codename: maverick
> architecture: x86_64
> kernel: 2.6.35-22-generic
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/647802/+subscriptions
>

Revision history for this message
multipass (jhsnowboard) wrote :

I've been experiencing this same problem.
The program crashes when I am trying to setup dual monitors and press Apply.
There is no output when you run amdcccle in console. Ive also tried attaching the process to a watcher, and nothing is reported.

Revision history for this message
Joost Van Durme (joostvandurme) wrote :

Hi, I'm experiencing the same issue with latest update of 12.04.

STEPS:

1. Launch AMD Catalyst control center (admin mode) from Dash
2. Change resolution and click "Apply"

OBSERVED RESULT:

New resolution is set but Catalyst Control Center closes immediately. There is no crash report.

EXPECTED RESULT

New resolution is set and Catalyst Control Center remains open

When I start the control center via the terminal with "sudo amdcccle" I do not have this behaviour and the window remains open.

System Info:

Ubuntu 12.04
All packages up to date
fglrx-amdcccle 2:8.911-0ubuntu1

Revision history for this message
Joost Van Durme (joostvandurme) wrote :

Oh yeah, it also crashed (with crash report) when I hadn't opened it yet. Now that's strange!

Revision history for this message
bash321 (bash321) wrote :

Ubuntu 12.04 alpha 2 crashed after setting resolution of screen. the resolution also does not stay the same if you shutdown your computer. it goes back to the highest resolution that can be set on my screen which is not what i want because i cannot read anything as all the text is too small. Ati HD 4250 Graphics card AMD 955 Processor 64BIT Ubuntu.

Revision history for this message
bash321 (bash321) wrote :

also it does not crash when i use sudo amdcccle from terminal.

Revision history for this message
wag9 (wag9) wrote :

I am having the same issue with a Radeon 5770 and XUbuntu 11.10, using the command 'sudo amdcccle'. I ran 'sudo gdb amdcccle', followed by the run command to run the executable, duplicated the error, and got a backtrace with 'bt'. I'm not sure how helpful this is because there are a lot of unnamed functions here.

#0 0x00000000005b5614 in ?? ()
#1 0x0000000000499709 in ?? ()
#2 0x000000000049d3b5 in ?? ()
#3 0x00000000004a127f in ?? ()
#4 0x00000000004b60b7 in ?? ()
#5 0x0000000000424761 in ?? ()
#6 0x000000000059a0dc in ?? ()
#7 0x00007ffff6bd4eba in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8 0x00007ffff7763642 in QAbstractButton::clicked(bool) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9 0x00007ffff74a91fe in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x00007ffff74aa53b in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x00007ffff74aa7ac in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007ffff7142cea in QWidget::event(QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007ffff70f2474 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x00007ffff70f7cbb in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#15 0x00007ffff6bc1afc in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#16 0x00007ffff70f3442 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#17 0x00007ffff71729d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#18 0x00007ffff717194e in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#19 0x00007ffff719a4a2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x00007ffff3985a5d in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007ffff3986258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007ffff3986429 in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007ffff6beced6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x00007ffff719a10e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#25 0x00007ffff6bc0cf2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x00007ffff6bc0ef7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x00007ffff6bc5789 in QCoreApplication::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#28 0x000000000041e925 in ?? ()
#29 0x00007ffff407530d in __libc_start_main ()
#30 0x000000000041c3ea in ?? ()
#31 0x00007fffffffe738 in ?? ()
#32 0x000000000000001c in ?? ()
#33 0x0000000000000001 in ?? ()
#34 0x00007fffffffe95f in ?? ()
#35 0x0000000000000000 in ?? ()

Revision history for this message
ex0a (ex0a) wrote :
Download full text (3.3 KiB)

Program received signal SIGSEGV, Segmentation fault.
0x00000000005ba1e4 in CXDriver::UpdateRandrConfig2(int, int, int, short, char const*, int, int, unsigned short, bool, bool)
    ()
(gdb) bt
#0 0x00000000005ba1e4 in CXDriver::UpdateRandrConfig2(int, int, int, short, char const*, int, int, unsigned short, bool, bool) ()
#1 0x000000000049a1d9 in CDisplayRule2::saveConfig(int, char const*, int, char const*, int, int, short, int, int, unsigned short, bool, bool) ()
#2 0x000000000049dc9e in CDisplayRule2::SetDriverData(CDisplayData2&, bool*, int*) ()
#3 0x00000000004a20ef in CDisplayRule2::SetData(CDisplayData2*, bool, bool*) ()
#4 0x00000000004b7a27 in CDisplayPage2::SetApplyData(bool, bool*) ()
#5 0x00000000004252a1 in CLDCDialog::clickApply() ()
#6 0x000000000059ecac in CLDCDialog::qt_metacall(QMetaObject::Call, int, void**) ()
#7 0x00007ffff6e57291 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/share/ati/lib64/libQtCore.so.4
#8 0x00007ffff6e575e9 in QMetaObject::activate(QObject*, QMetaObject const*, int, int, void**) ()
   from /usr/share/ati/lib64/libQtCore.so.4
#9 0x00007ffff78b8657 in QAbstractButton::clicked(bool) () from /usr/share/ati/lib64/libQtGui.so.4
#10 0x00007ffff76354a6 in QAbstractButtonPrivate::emitClicked() () from /usr/share/ati/lib64/libQtGui.so.4
#11 0x00007ffff763695c in QAbstractButtonPrivate::click() () from /usr/share/ati/lib64/libQtGui.so.4
#12 0x00007ffff7636b4d in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/share/ati/lib64/libQtGui.so.4
#13 0x00007ffff7318a4c in QWidget::event(QEvent*) () from /usr/share/ati/lib64/libQtGui.so.4
#14 0x00007ffff7635b0a in QAbstractButton::event(QEvent*) () from /usr/share/ati/lib64/libQtGui.so.4
#15 0x00007ffff76c9eee in QPushButton::event(QEvent*) () from /usr/share/ati/lib64/libQtGui.so.4
#16 0x00007ffff72ce60d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/share/ati/lib64/libQtGui.so.4
#17 0x00007ffff72d288a in QApplication::notify(QObject*, QEvent*) () from /usr/share/ati/lib64/libQtGui.so.4
#18 0x00007ffff6e435eb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/share/ati/lib64/libQtCore.so.4
#19 0x00007ffff72d4071 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/share/ati/lib64/libQtGui.so.4
#20 0x00007ffff7332583 in QETWidget::translateMouseEvent(_XEvent const*) () from /usr/share/ati/lib64/libQtGui.so.4
#21 0x00007ffff7330890 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/share/ati/lib64/libQtGui.so.4
#22 0x00007ffff7356979 in QEventDispatcherX11::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/share/ati/lib64/libQtGui.so.4
#23 0x00007ffff6e42a71 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/share/ati/lib64/libQtCore.so.4
#24 0x00007ffff6e42cc8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/share/ati/lib64/libQtCore.so.4
#25 0x00007ffff6e44628 in QCoreApplication::exec() () from /usr/share/ati/lib64/libQtCore.so.4
#26 0x00007ffff72ce1cc in QApplication::exec() () from /usr/share/ati/lib64/libQtGui.so.4
#27 0x000000000041f...

Read more...

Revision history for this message
Todd Howe (tehowe) wrote :

I got this while trying to set up my multidesktops after installing Precise Beta 1

Revision history for this message
pnatte (pnatte) wrote :

This occurred after upgrading to Precise Beta 1 on an Acer Aspire One 722

Revision history for this message
Alexx (ag-cdo) wrote :

I've got the same as comment #16. 12.4 beta with dual monitors. Computer starts with cloned displays and when I try to chance amdcccle crashes, but applies changes. Changes are lost on restart though and so have to go through whole process again. The interesting thing is that the displays are not cloned on the login screen, so wondering if logging in over-writes something.

Revision history for this message
Mark Fernandes (typist) wrote :

I had this problem when I booted my laptop into single display (basicially just the laptop screen) mode after having configured it earlier in multiple display (extended desktop) mode.

Worked fine when it was configured in single display and later connected an external monitor (in that situation only mirrored desktops worked)

Revision history for this message
Jim Rorie (jfrorie) wrote :

This is still present in Precise Beta2

Revision history for this message
linfidel (linfidel) wrote :

I have a ATI Radeon HD 5450, and a newly installed, fully updated xubuntu 11.10. I cannot get dual monitors to work after installing the proprietary driver. I've tried running the amdcccle program
1. From the menu, administrative mode: nothing happens at all (non-admin mode does run).
2. From the terminal, using both sudo and gksu: after any change at all, hitting "apply" causes program to disappear, with no output.
3. From Alt-F2, using gksu: same as from terminal. Using sudo, nothing happens, as expected since it can't prompt for the password.

I had the same problems with lubuntu, if I remember correctly. I do think it worked with Ubuntu, but I stopped using the driver because it caused shutdown failures 90% of the time. It seemed to be OK in the 12.04 beta, though, with my limited experience so far.

Revision history for this message
wilbur.harvey (wilbur-harvey) wrote :

The driver that comes with Ubuntu, 11.10 or 12.04 doesn't seem to work very
well and is outdated.
Completely remove the Ubuntu supplied driver and install the v12.3
(3/28/2012) driver from
http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx?type=2.4.1&product=2.4.1.3.42&lang=English
It doesn't work perfectly, but it is much better, I actually have triple
monitors working with this driver.

On Wed, Apr 11, 2012 at 9:10 AM, linfidel <email address hidden> wrote:

> I have a ATI Radeon HD 5450, and a newly installed, fully updated xubuntu
> 11.10. I cannot get dual monitors to work after installing the proprietary
> driver. I've tried running the amdcccle program
> 1. From the menu, administrative mode: nothing happens at all (non-admin
> mode does run).
> 2. From the terminal, using both sudo and gksu: after any change at all,
> hitting "apply" causes program to disappear, with no output.
> 3. From Alt-F2, using gksu: same as from terminal. Using sudo, nothing
> happens, as expected since it can't prompt for the password.
>
> I had the same problems with lubuntu, if I remember correctly. I do
> think it worked with Ubuntu, but I stopped using the driver because it
> caused shutdown failures 90% of the time. It seemed to be OK in the
> 12.04 beta, though, with my limited experience so far.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/647802
>
> Title:
> amdcccle crashed with SIGSEGV
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/647802/+subscriptions
>

Revision history for this message
Joost Van Durme (joostvandurme) wrote :

I can confirm that even with the 12.3 driver, settings applied in amdcccle are not saved on next reboot (for dual head setups).

Revision history for this message
Joost Van Durme (joostvandurme) wrote :

Oh sorry, the thing was that the 12.3 driver didn't want to install, raised an error. Settings were not saved with the shipped fglrx driver.

Revision history for this message
Chris Knight (cknight725) wrote :

Same issue here:

Radeon HD 5450 1GB, 2 Monitors, different sizes. Changing res, attempting to setup dual monitors causes a crash.

Catalyst 8.96.7-120312a-135598C-ATI

Even tried swiping an xorg.conf from a 5870 equipped system with the desired config, no joy with duals and amdcccle still crashes:

Output of 'sudo gdm amdcccle' <RUN:

sudo gdb amdcccle
GNU gdb (Ubuntu/Linaro 7.4-2012.02-0ubuntu2) 7.4-2012.02
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/amdcccle...(no debugging symbols found)...done.
(gdb)
(gdb) amdcccle
Undefined command: "amdcccle". Try "help".
(gdb) ^CQuit
(gdb) ^CQuit
(gdb) exit
Undefined command: "exit". Try "help".
(gdb) quit
cknight@office-myth:~$ sudo gdb amdcccle
GNU gdb (Ubuntu/Linaro 7.4-2012.02-0ubuntu2) 7.4-2012.02
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/amdcccle...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/amdcccle
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffef3ef700 (LWP 5622)]
[New Thread 0x7fffe2aed700 (LWP 5626)]
[Thread 0x7fffe2aed700 (LWP 5626) exited]

(process:5617): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.1/./gobject/gtype.c:2722: You forgot to call g_type_init()

(process:5617): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(process:5617): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.1/./gobject/gtype.c:2722: You forgot to call g_type_init()

(process:5617): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(process:5617): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe1657961 in gdk_display_open ()
   from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0

tags: added: precise
Revision history for this message
Alberto Milone (albertomilone) wrote :

I'm closing this bug report. If you can still reproduce the issue in recent Ubuntu releases, feel free to reopen this report.

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