Bug 322401 - Apper crashed on opening
Summary: Apper crashed on opening
Status: RESOLVED DUPLICATE of bug 270456
Alias: None
Product: apper
Classification: Applications
Component: general (show other bugs)
Version: 0.8.1
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-15 16:34 UTC by qub.box
Modified: 2013-07-29 23:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (4.06 KB, text/plain)
2013-07-25 12:42 UTC, Hebert
Details
New crash information added by DrKonqi (10.28 KB, text/plain)
2013-07-29 15:01 UTC, Matthew
Details

Note You need to log in before you can comment on or make changes to this bug.
Description qub.box 2013-07-15 16:34:46 UTC
Application: apper (0.8.1)
KDE Platform Version: 4.10.4
Qt Version: 4.8.4
Operating System: Linux 3.9.9-301.fc19.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:

I only run the Apper and it at once crashed. i try run this app again, but it does not happened

The crash does not seem to be reproducible.

-- Backtrace:
Application: Apper (apper), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x000000000060e840 in ?? ()
#7  0x000000308e017651 in parent (this=0x1155f30) at /usr/include/QtCore/qabstractitemmodel.h:393
#8  KCategorizedView::Private::categoryForIndex (this=0x1155ef0, index=...) at /usr/src/debug/kdelibs-4.10.4/kdeui/itemviews/kcategorizedview.cpp:396
#9  0x000000308e01ad5e in KCategorizedView::visualRect (this=0xfd9330, index=...) at /usr/src/debug/kdelibs-4.10.4/kdeui/itemviews/kcategorizedview.cpp:573
#10 0x000000308e01cb72 in KCategorizedView::leaveEvent (this=0xfd9330, event=<optimized out>) at /usr/src/debug/kdelibs-4.10.4/kdeui/itemviews/kcategorizedview.cpp:1072
#11 0x0000003089a1754d in QWidget::event (this=this@entry=0xfd9330, event=event@entry=0x7fffb51d72a0) at kernel/qwidget.cpp:8520
#12 0x0000003089db30fe in QFrame::event (this=this@entry=0xfd9330, e=e@entry=0x7fffb51d72a0) at widgets/qframe.cpp:557
#13 0x0000003089e2f22b in QAbstractScrollArea::event (this=this@entry=0xfd9330, e=e@entry=0x7fffb51d72a0) at widgets/qabstractscrollarea.cpp:996
#14 0x0000003089ec089b in QAbstractItemView::event (this=0xfd9330, event=0x7fffb51d72a0) at itemviews/qabstractitemview.cpp:1580
#15 0x00000030899c846c in QApplicationPrivate::notify_helper (this=0xf6fd50, receiver=0xfd9330, e=0x7fffb51d72a0) at kernel/qapplication.cpp:4562
#16 0x00000030899cea30 in QApplication::notify (this=this@entry=0x7fffb51d7cf0, receiver=receiver@entry=0xfd9330, e=e@entry=0x7fffb51d72a0) at kernel/qapplication.cpp:4348
#17 0x000000308e042f0a in KApplication::notify (this=0x7fffb51d7cf0, receiver=0xfd9330, event=0x7fffb51d72a0) at /usr/src/debug/kdelibs-4.10.4/kdeui/kernel/kapplication.cpp:311
#18 0x00000034e1779f7d in QCoreApplication::notifyInternal (this=0x7fffb51d7cf0, receiver=0xfd9330, event=0x7fffb51d72a0) at kernel/qcoreapplication.cpp:949
#19 0x00000030899cd925 in QApplicationPrivate::dispatchEnterLeave (enter=0x10ede60, leave=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:231
#20 0x00000030899ce2d9 in QApplicationPrivate::sendMouseEvent (receiver=0x10ede60, event=0x7fffb51d74a0, alienWidget=0x10ede60, nativeWidget=0x10e1db0, buttonDown=0x308a4a2258 <qt_button_down>, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3153
#21 0x0000003089a3f6bb in QETWidget::translateMouseEvent (this=0x10e1db0, event=<optimized out>) at kernel/qapplication_x11.cpp:4537
#22 0x0000003089a3e12c in QApplication::x11ProcessEvent (this=0x7fffb51d7cf0, event=event@entry=0x7fffb51d7810) at kernel/qapplication_x11.cpp:3660
#23 0x0000003089a64be4 in x11EventSourceDispatch (s=s@entry=0xf71000, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#24 0x00000034dae47e06 in g_main_dispatch (context=0xf6ff00) at gmain.c:3054
#25 g_main_context_dispatch (context=context@entry=0xf6ff00) at gmain.c:3630
#26 0x00000034dae48158 in g_main_context_iterate (context=context@entry=0xf6ff00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3701
#27 0x00000034dae481fc in g_main_context_iteration (context=0xf6ff00, may_block=1) at gmain.c:3762
#28 0x00000034e17a6cb5 in QEventDispatcherGlib::processEvents (this=0xf3c940, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#29 0x0000003089a64d56 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#30 0x00000034e1778bdf in QEventLoop::processEvents (this=this@entry=0x7fffb51d7bf0, flags=...) at kernel/qeventloop.cpp:149
#31 0x00000034e1778ed5 in QEventLoop::exec (this=this@entry=0x7fffb51d7bf0, flags=...) at kernel/qeventloop.cpp:204
#32 0x00000034e177dfbb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#33 0x00000030899c6c2c in QApplication::exec () at kernel/qapplication.cpp:3823
#34 0x0000000000406ae4 in main (argc=1, argv=0x7fffb51d7e38) at /usr/src/debug/apper-0.8.1/Apper/main.cpp:130

Possible duplicates by query: bug 316392, bug 316051, bug 311016, bug 306802, bug 305954.

Reported using DrKonqi
Comment 1 Hebert 2013-07-25 12:42:11 UTC
Created attachment 81335 [details]
New crash information added by DrKonqi

apper (0.8.1) on KDE Platform 4.10.5 using Qt 4.8.4

- Apper crashes as soon it starts up 
- Not always reproducible

-- Backtrace (Reduced):
#8  0x4a1824c5 in KCategorizedView::visualRect (this=0x8e2a7e0, index=...) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kcategorizedview.cpp:573
#9  0x4a18473e in KCategorizedView::leaveEvent (this=0x8e2a7e0, event=0xbfa316cc) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kcategorizedview.cpp:1072
#10 0x49424500 in QWidget::event (this=this@entry=0x8e2a7e0, event=event@entry=0xbfa316cc) at kernel/qwidget.cpp:8520
#11 0x4982f57d in QFrame::event (this=this@entry=0x8e2a7e0, e=0xbfa316cc) at widgets/qframe.cpp:557
#12 0x498bf52f in QAbstractScrollArea::event (this=this@entry=0x8e2a7e0, e=e@entry=0xbfa316cc) at widgets/qabstractscrollarea.cpp:996
Comment 2 Matthew 2013-07-29 15:01:57 UTC
Created attachment 81421 [details]
New crash information added by DrKonqi

apper (0.8.1) on KDE Platform 4.10.5 using Qt 4.8.4

- What I was doing when the application crashed: I opened apper and wanted to check the applications listed under the Applications category.  I double clicked the Applications category icon by mistake instead of a single click, then almost immediately Apper crashes and the bug report message appears.

This crash was reproducable by again opening Apper and again double clicking the Applications category icon.

I then tried each of the other category icons.  Double clicking on some of these other categories also cause Apper to crash. In particular double click on "Base System",  "Development", "Servers", or "Applications" all cause Apper to crash and then the bug report message.

Closer examination shows that It appears if you double click the top level categories show above, Apper begins to open the next window in sequence on the first mouse click and then the second click actually executes as the second window opens, then if the mouse happens to be resting on another icon in that second window as the second click actually executes. that then causes Apper to crash.

Would appear to be a timing issue, ie selecting category then sub category too fast causes the crash to happen.  Single clicks so far cause no issues in Apper for me.


- Unusual behavior I noticed:  System seems to be slow at picking up if there are any updates to be had, so far the auto update process hasn't notified me of updates, I instead have to manually open Apper and look for updates.
Some programs though installed are not showing as installed in Apper.  For example Blender is installed and functioning, but Apper doesn't show it as installed if I search for it.  It instead gives option to install.

Note I upgraded from 17 to 19 via Fedum, so perhaps the upgrade has partly failed?

-- Backtrace (Reduced):
#6  parent (this=0x25bd250) at /usr/include/QtCore/qabstractitemmodel.h:393
#7  KCategorizedView::Private::categoryForIndex (this=0x25bd210, index=...) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kcategorizedview.cpp:396
#8  0x0000003ace61940e in KCategorizedView::visualRect (this=0x25b8880, index=...) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kcategorizedview.cpp:573
#9  0x0000003ace61b222 in KCategorizedView::leaveEvent (this=0x25b8880, event=<optimized out>) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kcategorizedview.cpp:1072
#10 0x0000003acc81754d in QWidget::event (this=this@entry=0x25b8880, event=event@entry=0x7fff8877dd80) at kernel/qwidget.cpp:8520
Comment 3 Daniel Nicoletti 2013-07-29 23:07:33 UTC

*** This bug has been marked as a duplicate of bug 270456 ***