Bug 314875

Summary: Apper hangs after update
Product: [Unmaintained] apper Reporter: Knut Hansen <knut.tr>
Component: generalAssignee: Daniel Nicoletti <dantti12>
Status: RESOLVED WORKSFORME    
Severity: crash CC: aguayro, andrew.crouthamel, fgm.cidacos, kennypb, luzemario, percycris, simon, vmoc777, y.shaladi
Priority: NOR    
Version First Reported In: 0.7.2   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi

Description Knut Hansen 2013-02-11 08:05:43 UTC 
Application: apper (0.7.2)
KDE Platform Version: 4.9.5
Qt Version: 4.8.4
Operating System: Linux 3.7.3-101.fc17.x86_64 x86_64
Distribution: "Fedora release 17 (Beefy Miracle)"

-- Information about the crash:
- What I was doing when the application crashed:
Apper notified about updates. Started update which finished complete. But Apper hangs afterwords while checking for more updates.

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  data (this=0x70002e0074007a) at ../../src/corelib/tools/qscopedpointer.h:135
#7  qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../src/corelib/global/qglobal.h:2455
#8  d_func (this=0x70002e00740072) at kernel/qstackedlayout.h:58
#9  QStackedLayout::setCurrentIndex (this=0x70002e00740072, index=0) at kernel/qstackedlayout.cpp:288
#10 0x00007f1f9f4011ce in ApperKCM::on_backTB_clicked (this=0xbe5cd0) at /usr/src/debug/apper-0.7.2/ApperKCM/ApperKCM.cpp:540
#11 0x00007f1f9f402bd7 in ApperKCM::qt_metacall (this=0xbe5cd0, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fff1e91e9f0) at /usr/src/debug/apper-0.7.2/x86_64-redhat-linux-gnu/ApperKCM/ApperKCM.moc:142
#12 0x0000003bb4b8cf83 in QMetaObject::activate (sender=0xdbe390, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff1e91e9f0) at kernel/qobject.cpp:3558
#13 0x0000003bb6a2ecb2 in QAbstractButton::clicked (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:219
#14 0x0000003bb678398e in QAbstractButtonPrivate::emitClicked (this=this@entry=0xdc22f0) at widgets/qabstractbutton.cpp:548
#15 0x0000003bb6783f90 in QAbstractButtonPrivate::click (this=this@entry=0xdc22f0) at widgets/qabstractbutton.cpp:541
#16 0x0000003bb67841fc in QAbstractButton::mouseReleaseEvent (this=0xdbe390, e=0x7fff1e91f2a0) at widgets/qabstractbutton.cpp:1123
#17 0x0000003bb683e47a in QToolButton::mouseReleaseEvent (this=<optimized out>, e=<optimized out>) at widgets/qtoolbutton.cpp:718
#18 0x0000003bb6419f29 in QWidget::event (this=0xdbe390, event=0x7fff1e91f2a0) at kernel/qwidget.cpp:8375
#19 0x0000003bb63ca5ac in QApplicationPrivate::notify_helper (this=this@entry=0xa70cb0, receiver=receiver@entry=0xdbe390, e=e@entry=0x7fff1e91f2a0) at kernel/qapplication.cpp:4562
#20 0x0000003bb63cf28b in QApplication::notify (this=<optimized out>, receiver=0xdbe390, e=0x7fff1e91f2a0) at kernel/qapplication.cpp:4105
#21 0x0000003bb7e468c6 in KApplication::notify (this=0x7fff1e920010, receiver=0xdbe390, event=0x7fff1e91f2a0) at /usr/src/debug/kdelibs-4.9.5/kdeui/kernel/kapplication.cpp:311
#22 0x0000003bb4b7799e in QCoreApplication::notifyInternal (this=0x7fff1e920010, receiver=0xdbe390, event=0x7fff1e91f2a0) at kernel/qcoreapplication.cpp:946
#23 0x0000003bb63cb3eb in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:231
#24 QApplicationPrivate::sendMouseEvent (receiver=0xdbe390, event=0x7fff1e91f2a0, alienWidget=0x0, nativeWidget=0xdbe390, buttonDown=0x3bb6e9e248, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3173
#25 0x0000003bb6445ac4 in QETWidget::translateMouseEvent (this=this@entry=0xdbe390, event=event@entry=0x7fff1e91fa10) at kernel/qapplication_x11.cpp:4537
#26 0x0000003bb6444851 in QApplication::x11ProcessEvent (this=0x7fff1e920010, event=0x7fff1e91fa10) at kernel/qapplication_x11.cpp:3660
#27 0x0000003bb646a90c in x11EventSourceDispatch (s=s@entry=0xa70100, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#28 0x00000039fb247825 in g_main_dispatch (context=0xa6fd20) at gmain.c:2539
#29 g_main_context_dispatch (context=context@entry=0xa6fd20) at gmain.c:3075
#30 0x00000039fb247b58 in g_main_context_iterate (context=context@entry=0xa6fd20, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3146
#31 0x00000039fb247c14 in g_main_context_iteration (context=0xa6fd20, may_block=1) at gmain.c:3207
#32 0x0000003bb4ba5fe6 in QEventDispatcherGlib::processEvents (this=0xa3da70, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#33 0x0000003bb646a5ee in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#34 0x0000003bb4b766ef in QEventLoop::processEvents (this=this@entry=0x7fff1e91fde0, flags=...) at kernel/qeventloop.cpp:149
#35 0x0000003bb4b76978 in QEventLoop::exec (this=0x7fff1e91fde0, flags=...) at kernel/qeventloop.cpp:204
#36 0x0000003bb4b7b768 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#37 0x00000000004064ef in main (argc=2, argv=0x7fff1e920158) at /usr/src/debug/apper-0.7.2/Apper/main.cpp:136

This bug may be a duplicate of or related to bug 289689.

Possible duplicates by query: bug 312085, bug 306433, bug 301921, bug 301919, bug 294203.

Reported using DrKonqi
Comment 1 Simon 2013-02-21 13:27:27 UTC 
Created attachment 77487 [details]
New crash information added by DrKonqi

apper (0.7.2) on KDE Platform 4.9.5 using Qt 4.8.4

- What I was doing when the application crashed:
just run an apper update ... apper completely freezes whilst waiting for yum to complete (this is NOT unusual & is the real issue & only unfreezes after logout or reboot)

- Unusual behavior I noticed:

switched to a root terminal .... checked messages, yum ... logs ok, etc.
ran:

yum check
yum check-update

both ran fine & quickly. switched back to apper window, closed it & this crash happened.
IMHO, this looks like some kind of lock wait issue.

-- Backtrace (Reduced):
#6  0x000000338fdca5ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQtGui.so.4
#7  0x000000338fdcea2a in QApplication::notify(QObject*, QEvent*) () from /lib64/libQtGui.so.4
#8  0x00000033910468c6 in KApplication::notify(QObject*, QEvent*) () from /lib64/libkdeui.so.5
#9  0x000000352b97799e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQtCore.so.4
#10 0x000000338fe1ce5b in QWidget::setParent(QWidget*, QFlags<Qt::WindowType>) () from /lib64/libQtGui.so.4
Comment 2 Jekyll Wu 2013-04-17 09:30:21 UTC 
*** Bug 318470 has been marked as a duplicate of this bug. ***
Comment 3 Jekyll Wu 2013-04-17 09:30:27 UTC 
*** Bug 289689 has been marked as a duplicate of this bug. ***
Comment 4 Jekyll Wu 2013-11-06 12:18:25 UTC 
*** Bug 327218 has been marked as a duplicate of this bug. ***
Comment 5 y.shaladi 2014-04-08 11:00:54 UTC 
Created attachment 86002 [details]
New crash information added by DrKonqi

apper (0.8.1) on KDE Platform 4.11.3 using Qt 4.8.5

- What I was doing when the application crashed:

Runnin Fedora in a VM, I was surfing a bit within Windows. However, the only application used in Windows was Mozilla (except VM). I was looking for the update but it got stocked at 10% for more than 10minute. After clicking on abort nothing happend and then the bug appeared.

-- Backtrace (Reduced):
#5  0x00000030975fe2a4 in QStackedLayout::setCurrentIndex(int) () from /lib64/libQtGui.so.4
#6  0x00007f27c85b5f8f in ApperKCM::on_backTB_clicked() () from /usr/lib64/kde4/kcm_apper.so
#8  0x00007f27c85b7863 in ApperKCM::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/kde4/kcm_apper.so
[...]
#10 0x0000003097c4bb92 in QAbstractButton::clicked(bool) () from /lib64/libQtGui.so.4
#11 0x000000309798ff83 in QAbstractButtonPrivate::emitClicked() () from /lib64/libQtGui.so.4
Comment 6 vmoc777 2015-11-10 23:48:18 UTC 
Apper crashed
Fedora KDE Platform Version 4.14.11
Linux (x86_64) release 4.1.10-100.fc21.x86_64

Apper crashed after updates installed.  Checked for new updates, the apper crashes.

reports: Activation of org.freedesktop.Packagekit timed out.

with crash, I am unable to update or check for applications.
Comment 7 vmoc777 2015-11-10 23:49:01 UTC 
Apper crashed
Fedora KDE Platform Version 4.14.11
Linux (x86_64) release 4.1.10-100.fc21.x86_64

Apper crashed after updates installed.  Checked for new updates, the apper crashes.

reports: Activation of org.freedesktop.Packagekit timed out.

with crash, I am unable to update or check for applications.
Comment 8 Andrew Crouthamel 2018-11-01 13:56:46 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Simon 2018-11-07 23:57:51 UTC 
Sorry, unable to retest since the machine in question died some years ago. Not installed apper since.
Comment 10 Andrew Crouthamel 2018-11-08 00:14:18 UTC 
Thanks for the update!