[Bug 279211] apper fails then segfault when window is closed

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=279211


Christoph Feck <christoph at maxiom.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |general
            Version|Git                         |unspecified
         AssignedTo|unassigned-bugs at kde.org     |dantti12 at gmail.com
            Product|kde                         |apper




--- Comment #1 from Christoph Feck <christoph maxiom de>  2011-08-02 22:03:14 ---
[Paste attachment from comment #0]

Application: apper (0.6.2)
KDE Platform Version: 4.7.00 (4.7.0)
Qt Version: 4.7.3
Operating System: Linux 2.6.37.6-0.5-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
When applying updates, Apper shows "simulating updates" for a while, then
"finishing" until the window is closed resulting in a crash. No update actually
takes place.

The crash can be reproduced every time.

-- Backtrace:
Application: Apper (apper), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f43ae57396f in QWidget::testAttribute_helper (this=0x7ae110,
attribute=Qt::WA_ForceDisabled) at kernel/qwidget.cpp:10870
#7  0x00007f43ae57cc35 in testAttribute (this=0x7ae110,
attribute=Qt::WA_ForceDisabled, on=false) at
../../src/gui/kernel/qwidget.h:1031
#8  QWidget::setAttribute (this=0x7ae110, attribute=Qt::WA_ForceDisabled,
on=false) at kernel/qwidget.cpp:10549
#9  0x00007f43ae584636 in QWidget::setEnabled (this=<value optimized out>,
enable=true) at kernel/qwidget.cpp:3285
#10 0x00007f43a3d01012 in ApperKCM::save (this=0x82d360) at
/usr/src/debug/apper-0.6.3.60git.1303203001/ApperKCM/ApperKCM.cpp:724
#11 0x00007f43af4fba67 in KCModuleProxy::save (this=<value optimized out>) at
/usr/src/debug/kdelibs-4.7.0/kutils/kcmoduleproxy.cpp:279
#12 0x00007f43af4f8af8 in KCMultiDialogPrivate::apply (this=<value optimized
out>) at /usr/src/debug/kdelibs-4.7.0/kutils/kcmultidialog.cpp:300
#13 0x00007f43af4f9c7c in KCMultiDialog::qt_metacall (this=0x732a40,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1b585760)
at /usr/src/debug/kdelibs-4.7.0/build/kutils/kcmultidialog.moc:95
#14 0x00007f43af892a5f in QMetaObject::activate (sender=0x732a40, m=<value
optimized out>, local_signal_index=<value optimized out>, argv=0x0) at
kernel/qobject.cpp:3278
#15 0x00007f43b020817e in KDialog::slotButtonClicked (this=0x732a40, button=8)
at /usr/src/debug/kdelibs-4.7.0/kdeui/dialogs/kdialog.cpp:887
#16 0x00007f43b0208682 in KDialog::qt_metacall (this=0x732a40,
_c=QMetaObject::InvokeMetaMethod, _id=33, _a=0x7fff1b585950) at
/usr/src/debug/kdelibs-4.7.0/build/kdeui/kdialog.moc:190
#17 0x00007f43b02dd7e0 in KPageDialog::qt_metacall (this=0x732a40,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1b585950)
at /usr/src/debug/kdelibs-4.7.0/build/kdeui/kpagedialog.moc:70
#18 0x00007f43af4f9b90 in KCMultiDialog::qt_metacall (this=0x732a40,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1b585950)
at /usr/src/debug/kdelibs-4.7.0/build/kutils/kcmultidialog.moc:86
#19 0x00007f43af892a5f in QMetaObject::activate (sender=0x711b80, m=<value
optimized out>, local_signal_index=<value optimized out>, argv=0x7fff1b585950)
at kernel/qobject.cpp:3278
#20 0x00007f43af89743e in QSignalMapper::mapped (this=<value optimized out>,
_t1=8) at .moc/release-shared/moc_qsignalmapper.cpp:101
#21 0x00007f43af897665 in QSignalMapper::map (this=0x711b80, sender=0x745570)
at kernel/qsignalmapper.cpp:266
#22 0x00007f43af897d20 in QSignalMapper::qt_metacall (this=0x711b80,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fff1b585ac0) at
.moc/release-shared/moc_qsignalmapper.cpp:87
#23 0x00007f43af892a5f in QMetaObject::activate (sender=0x745570, m=<value
optimized out>, local_signal_index=<value optimized out>, argv=0x7fff1b585ac0)
at kernel/qobject.cpp:3278

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.