[konsole] [Bug 388181] As Yet Unknown Cause

[bugzilla_noreply at kde.org]

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

--- Comment #1 from gerald.david at gmx.com ---
Created attachment 109494
  --> https://bugs.kde.org/attachment.cgi?id=109494&action=edit
New crash information added by DrKonqi

konsole (16.12.3) using Qt 5.6.2

- What I was doing when the application crashed:
Fillling out the previous bug report "As Yet Unknown Cause".  The main
difference between this & the last report is:

Thread 2 (Thread 0x7f38c913c700 (LWP 11908)):
#0  0x00007f38dc42a959 in g_mutex_lock () from /lib64/libglib-2.0.so.0

If I keep getting conitinous crash reports with only slight differences between
them I can see it being a waiste of resources re time spent reading by
developers/bug triage folks. If I save the diff's from each report and build a
"trail" of sorts, then this would address that difficulty; on the other hand,
if the reports are that serious in nature & my box is comprimised then overkill
also has it's merrits. 

I would appreciate some direction if I am to be of any use here and not
waisting peoples valuable time. Seeking the opportunity to contribute & learn
:)

-- Backtrace (Reduced):
#4  0x00007f38dfa161a9 in KNotification::id() () from
/lib64/libKF5Notifications.so.5
#5  0x00007f38dfa187c9 in
KNotificationManager::notifyPluginFinished(KNotification*) () from
/lib64/libKF5Notifications.so.5
#6  0x00007f38dfa18bdc in KNotificationManager::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libKF5Notifications.so.5
[...]
#8  0x00007f38dfa4249f in KNotificationPlugin::finished(KNotification*) () from
/lib64/libKF5Notifications.so.5
#9  0x00007f38dfa2a51c in NotifyByPopup::onPassivePopupDestroyed() () from
/lib64/libKF5Notifications.so.5

-- 
You are receiving this mail because:
You are the assignee for the bug.