Bug 342120 - korgac crashes when clicking on taskber
Summary: korgac crashes when clicking on taskber
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korgac
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-12-22 10:45 UTC by Alin M Elena
Modified: 2018-02-01 09:45 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alin M Elena 2014-12-22 10:45:38 UTC
Application: korgac (4.72 pre)

Qt Version: 5.4.1
Operating System: Linux 3.18.1-1.gb68f510-desktop x86_64
Distribution: "openSUSE 20141219 (Tumbleweed) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I clicked on the taskbar. korgac crashes.. together with kmix.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KOrganizer Reminder Daemon (korgac), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa56af21800 (LWP 1588))]

Thread 2 (Thread 0x7fa551d47700 (LWP 1591)):
#0  0x00007fa564d694ad in poll () at /lib64/libc.so.6
#1  0x00007fa55e4e3322 in  () at /usr/lib64/libxcb.so.1
#2  0x00007fa55e4e4def in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x00007fa553c9dbb9 in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#4  0x00007fa56560494f in  () at /usr/lib64/libQt5Core.so.5
#5  0x00007fa55eb4d3a4 in start_thread () at /lib64/libpthread.so.0
#6  0x00007fa564d71a4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fa56af21800 (LWP 1588)):
[KCrash Handler]
#5  0x00007fa56580cd54 in QObject::thread() const () at /usr/lib64/libQt5Core.so.5
#6  0x00007fa5658170b8 in QObject::QObject(QObject*) () at /usr/lib64/libQt5Core.so.5
#7  0x00007fa55f8400de in DBusMenuExporter::DBusMenuExporter(QString const&, QMenu*, QDBusConnection const&) () at /usr/lib64/libdbusmenu-qt5.so.2
#8  0x00007fa568bd2508 in KStatusNotifierItem::setContextMenu(QMenu*) () at /usr/lib64/libKF5Notifications.so.5
#9  0x00007fa568bd2384 in KStatusNotifierItem::setContextMenu(QMenu*) () at /usr/lib64/libKF5Notifications.so.5
#10 0x00007fa568bd2c4a in  () at /usr/lib64/libKF5Notifications.so.5
#11 0x00007fa568bd3f8a in  () at /usr/lib64/libKF5Notifications.so.5
#12 0x00007fa568bd4211 in  () at /usr/lib64/libKF5Notifications.so.5
#13 0x00007fa56580e681 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#14 0x00007fa568be9953 in  () at /usr/lib64/libKF5Notifications.so.5
#15 0x00007fa568be9b5f in  () at /usr/lib64/libKF5Notifications.so.5
#16 0x00007fa567a9967f in  () at /usr/lib64/libQt5DBus.so.5
#17 0x00007fa56580f486 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#18 0x00007fa56649db1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#19 0x00007fa5664a2b80 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#20 0x00007fa5657dee05 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#21 0x00007fa5657e0c9f in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#22 0x00007fa565836d23 in  () at /usr/lib64/libQt5Core.so.5
#23 0x00007fa55ddc1a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#24 0x00007fa55ddc1c48 in  () at /usr/lib64/libglib-2.0.so.0
#25 0x00007fa55ddc1cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#26 0x00007fa56583619c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#27 0x00007fa5657dcd5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#28 0x00007fa5657e43e6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#29 0x0000000000419aa5 in main ()

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 20:02:40 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:45:41 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.