Application: apper (0.7.2) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.2 Operating System: Linux 3.4.0-1.fc17.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: After completing the most recent update, apper just sits their with the spinning "wait" icon indefinitely. The "Notifications" applet shows a spinning job which is completely blank. This also persists indefinitely. This occurs on both my home machine (which is a Fedora 17 install with various additional repositories), and my work machine (which is a plain Fedora 17 install with no additional repositories). This did not occur after the initial installation and first few updates of Fedora 17, but it happens now, every time. PS: I was required to download 1G (4.7G unpacked) of debuginfo packages before the crash reporting assistant would listen to my bug report. I typically resist using the word "insane," but it does seem to apply in this case. The crash can be reproduced every time. -- Backtrace: Application: Apper (apper), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #6 0x0000003a9501d174 in QStackedWidget::setCurrentIndex (this=0x1808600, index=0) at widgets/qstackedwidget.cpp:258 #7 0x00007f804e1991ce in ApperKCM::on_backTB_clicked (this=0x1706580) at /usr/src/debug/apper-0.7.2/ApperKCM/ApperKCM.cpp:540 #8 0x00007f804e19abd7 in ApperKCM::qt_metacall (this=0x1706580, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fff753eac50) at /usr/src/debug/apper-0.7.2/x86_64-redhat-linux-gnu/ApperKCM/ApperKCM.moc:142 #9 0x0000003a91f8cd63 in QMetaObject::activate (sender=0x180d1d0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff753eac50) at kernel/qobject.cpp:3566 #10 0x0000003a9522ece2 in QAbstractButton::clicked (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:219 #11 0x0000003a94f82fde in QAbstractButtonPrivate::emitClicked (this=this@entry=0x181d450) at widgets/qabstractbutton.cpp:548 #12 0x0000003a94f835e0 in QAbstractButtonPrivate::click (this=this@entry=0x181d450) at widgets/qabstractbutton.cpp:541 #13 0x0000003a94f8384c in QAbstractButton::mouseReleaseEvent (this=0x180d1d0, e=0x7fff753eb500) at widgets/qabstractbutton.cpp:1123 #14 0x0000003a9503d80a in QToolButton::mouseReleaseEvent (this=<optimized out>, e=<optimized out>) at widgets/qtoolbutton.cpp:718 #15 0x0000003a94c19b50 in QWidget::event (this=0x180d1d0, event=0x7fff753eb500) at kernel/qwidget.cpp:8371 #16 0x0000003a94bca37c in QApplicationPrivate::notify_helper (this=this@entry=0x1558390, receiver=receiver@entry=0x180d1d0, e=e@entry=0x7fff753eb500) at kernel/qapplication.cpp:4551 #17 0x0000003a94bcf05b in QApplication::notify (this=<optimized out>, receiver=0x180d1d0, e=0x7fff753eb500) at kernel/qapplication.cpp:4094 #18 0x0000003a97645a56 in KApplication::notify (this=0x7fff753ec270, receiver=0x180d1d0, event=0x7fff753eb500) at /usr/src/debug/kdelibs-4.8.3/kdeui/kernel/kapplication.cpp:311 #19 0x0000003a91f763ee in QCoreApplication::notifyInternal (this=0x7fff753ec270, receiver=0x180d1d0, event=0x7fff753eb500) at kernel/qcoreapplication.cpp:915 #20 0x0000003a94bcb1bb in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:231 #21 QApplicationPrivate::sendMouseEvent (receiver=0x180d1d0, event=0x7fff753eb500, alienWidget=0x0, nativeWidget=0x180d1d0, buttonDown=0x3a9569dd68, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3162 #22 0x0000003a94c45894 in QETWidget::translateMouseEvent (this=this@entry=0x180d1d0, event=event@entry=0x7fff753ebc70) at kernel/qapplication_x11.cpp:4523 #23 0x0000003a94c44621 in QApplication::x11ProcessEvent (this=0x7fff753ec270, event=0x7fff753ebc70) at kernel/qapplication_x11.cpp:3646 #24 0x0000003a94c6a60c in x11EventSourceDispatch (s=s@entry=0x1556960, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148 #25 0x0000003a866476e5 in g_main_dispatch (context=0x1556800) at gmain.c:2539 #26 g_main_context_dispatch (context=context@entry=0x1556800) at gmain.c:3075 #27 0x0000003a86647a18 in g_main_context_iterate (context=context@entry=0x1556800, block=block@entry=1, dispatch=dispatch@entry=1, self=<error reading variable: Unhandled dwarf expression opcode 0xfa>) at gmain.c:3146 #28 0x0000003a86647ad4 in g_main_context_iteration (context=0x1556800, may_block=1) at gmain.c:3207 #29 0x0000003a91fa44e6 in QEventDispatcherGlib::processEvents (this=0x152d990, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #30 0x0000003a94c6a2ee in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #31 0x0000003a91f7513f in QEventLoop::processEvents (this=this@entry=0x7fff753ec040, flags=...) at kernel/qeventloop.cpp:149 #32 0x0000003a91f753c8 in QEventLoop::exec (this=0x7fff753ec040, flags=...) at kernel/qeventloop.cpp:204 #33 0x0000003a91f7a1b8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #34 0x00000000004064ef in main (argc=2, argv=0x7fff753ec3b8) at /usr/src/debug/apper-0.7.2/Apper/main.cpp:136 Possible duplicates by query: bug 294203, bug 289899, bug 289712, bug 289689, bug 286403. Reported using DrKonqi
*** Bug 301921 has been marked as a duplicate of this bug. ***
Created attachment 73519 [details] New crash information added by DrKonqi apper (0.7.2) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.2 - What I was doing when the application crashed: I've updated some packages related, then as usual Apper remained in a waiting state (checking for more updates after the ones I've done). I've hit "Cancel" then closed the application. It crashed right after I've closed. Note: I've not updated all the proposed packages, I've discarded some of them. -- Backtrace (Reduced): #6 0x000000383481d174 in QStackedWidget::setCurrentIndex (this=0x14546d0, index=0) at widgets/qstackedwidget.cpp:258 #7 0x00007f0de93461ce in ApperKCM::on_backTB_clicked (this=0x1298200) at /usr/src/debug/apper-0.7.2/ApperKCM/ApperKCM.cpp:540 #8 0x00007f0de9347bd7 in ApperKCM::qt_metacall (this=0x1298200, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7ffff856db00) at /usr/src/debug/apper-0.7.2/x86_64-redhat-linux-gnu/ApperKCM/ApperKCM.moc:142 [...] #10 0x0000003834a2ece2 in QAbstractButton::clicked (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:219 #11 0x0000003834782fde in QAbstractButtonPrivate::emitClicked (this=this@entry=0x1462700) at widgets/qabstractbutton.cpp:548
Created attachment 73727 [details] New crash information added by DrKonqi apper (0.7.2) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.2 - What I was doing when the application crashed: Before It installed the updates, it was running but didn't fishish. When I close it, crashed -- Backtrace (Reduced): #7 0x4220ccff in QStackedWidget::setCurrentIndex (this=0x9454238, index=0) at widgets/qstackedwidget.cpp:258 #8 0xb58c23f3 in ApperKCM::on_backTB_clicked (this=0x9609160) at /usr/src/debug/apper-0.7.2/ApperKCM/ApperKCM.cpp:540 #9 0xb58c4374 in ApperKCM::qt_metacall (this=0x9609160, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbff151e8) at /usr/src/debug/apper-0.7.2/i686-redhat-linux-gnu/ApperKCM/ApperKCM.moc:142 #10 0x4159a326 in metacall (argv=0xbff151e8, idx=44, cl=QMetaObject::InvokeMetaMethod, object=0x1) at kernel/qmetaobject.cpp:245 [...] #13 0x4245c7be in QAbstractButton::clicked (this=0x9316730, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:219
Created attachment 73728 [details] New crash information added by DrKonqi apper (0.7.2) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.2 - What I was doing when the application crashed: Before It installed the updates, it was running but didn't fishish. When I close it, crashed -- Backtrace (Reduced): #7 0x4220ccff in QStackedWidget::setCurrentIndex (this=0x9454238, index=0) at widgets/qstackedwidget.cpp:258 #8 0xb58c23f3 in ApperKCM::on_backTB_clicked (this=0x9609160) at /usr/src/debug/apper-0.7.2/ApperKCM/ApperKCM.cpp:540 #9 0xb58c4374 in ApperKCM::qt_metacall (this=0x9609160, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbff151e8) at /usr/src/debug/apper-0.7.2/i686-redhat-linux-gnu/ApperKCM/ApperKCM.moc:142 #10 0x4159a326 in metacall (argv=0xbff151e8, idx=44, cl=QMetaObject::InvokeMetaMethod, object=0x1) at kernel/qmetaobject.cpp:245 [...] #13 0x4245c7be in QAbstractButton::clicked (this=0x9316730, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:219
Created attachment 73729 [details] New crash information added by DrKonqi apper (0.7.2) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.2 - What I was doing when the application crashed: Before It installed the updates, it was running but didn't fishish. When I close it, crashed -- Backtrace (Reduced): #7 0x4220ccff in QStackedWidget::setCurrentIndex (this=0x9454238, index=0) at widgets/qstackedwidget.cpp:258 #8 0xb58c23f3 in ApperKCM::on_backTB_clicked (this=0x9609160) at /usr/src/debug/apper-0.7.2/ApperKCM/ApperKCM.cpp:540 #9 0xb58c4374 in ApperKCM::qt_metacall (this=0x9609160, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbff151e8) at /usr/src/debug/apper-0.7.2/i686-redhat-linux-gnu/ApperKCM/ApperKCM.moc:142 #10 0x4159a326 in metacall (argv=0xbff151e8, idx=44, cl=QMetaObject::InvokeMetaMethod, object=0x1) at kernel/qmetaobject.cpp:245 [...] #13 0x4245c7be in QAbstractButton::clicked (this=0x9316730, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:219
*** Bug 306433 has been marked as a duplicate of this bug. ***
*** Bug 312085 has been marked as a duplicate of this bug. ***
Did you close the window while it was there "waiting for something"?
*** This bug has been marked as a duplicate of bug 289689 ***
Yes I did, but after a long time (some minutes). ________________________________ From: Daniel Nicoletti <dantti12@gmail.com> To: bonomi4@yahoo.com Sent: Wednesday, January 9, 2013 6:34 PM Subject: [apper] [Bug 301919] Apper doesn't complete after updating https://bugs.kde.org/show_bug.cgi?id=301919 --- Comment #8 from Daniel Nicoletti <dantti12@gmail.com> --- Did you close the window while it was there "waiting for something"?