amdcccle crashed with SIGSEGV in QPersistentModelIndex::~QPersistentModelIndex()

[Allen]

using amdcccle and changing the configuration for dual monitors

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: fglrx-amdcccle 2:8.840-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
NonfreeKernelModules: fglrx
Architecture: i386
CrashCounter: 1
Date: Mon Apr 11 09:47:11 2011
DistUpgraded: Log time: 2011-04-05 19:07:52.240719
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/lib/fglrx/bin/amdcccle
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: amdcccle
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6bdb270 <_ZN21QPersistentModelIndexD2Ev+16>: lock decl 0x10(%eax)
 PC (0xb6bdb270) ok
 source "0x10(%eax)" (0xb778c758) ok
 SP (0xbfb8c860) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: fglrx-installer
StacktraceTop:
 QPersistentModelIndex::~QPersistentModelIndex() () from /usr/lib/libQtCore.so.4
 ?? () from /usr/lib/libQtGui.so.4
 QItemSelectionModel::select(QItemSelection const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /usr/lib/libQtGui.so.4
 QItemSelectionModel::select(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /usr/lib/libQtGui.so.4
 QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /usr/lib/libQtGui.so.4
Title: amdcccle crashed with SIGSEGV in QPersistentModelIndex::~QPersistentModelIndex()
UpgradeStatus: Upgraded to natty on 2011-04-06 (5 days ago)
UserGroups: pkcs11
version.compiz: compiz 1:0.9.4+bzr20110407-0ubuntu2
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu1
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

[Apport retracing service (apport)]

StacktraceTop:
 deref (this=0x92405f0, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:132
 QPersistentModelIndex::~QPersistentModelIndex (this=0x92405f0, __in_chrg=<value optimized out>) at kernel/qabstractitemmodel.cpp:154
 ~QItemSelectionRange (this=0xbfb8c918, __in_chrg=<value optimized out>) at ../../include/QtGui/../../src/gui/itemviews/qitemselectionmodel.h:59
 node_destruct (this=0xbfb8c918, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qlist.h:418
 free (this=0xbfb8c918, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qlist.h:742

[Bryce Harrington (bryce)]

Possibly related to bug 747246 in that it seems to be crashing during object destruction, but the stack trace is completely different so not marking it as a dupe.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bryce Harrington (bryce)]

Hey allen-lau,

You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.

If it's solved in the new release and you think it's worth backporting
the fix, please indicate that. Or if having the fix in the new release
is good enough, feel free to close out the bug (or let us know and we'll
close it.)

If it's not solved, leave the bug report open. I can't promise we'll
get to it (we get way more bugs filed than we can usually get to), but
your testing and feedback can help out if and when we do.

[bugbot (bugbot)]

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.