Bug 444970 - Crash when resuming by plugging into docking station
Summary: Crash when resuming by plugging into docking station
Status: RESOLVED BACKTRACE
Alias: None
Product: frameworks-knotifications
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.87.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-11-04 19:02 UTC by Ivan Murray-Smith
Modified: 2021-11-23 09:35 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Murray-Smith 2021-11-04 19:02:06 UTC 
Application: org_kde_powerdevil (2.0.0)

Qt Version: 5.12.7
Frameworks Version: 5.71.0
Operating System: Linux 5.3.18-lp152.95-default x86_64
Windowing system: X11
Distribution: "openSUSE Leap 15.2"

-- Information about the crash:
- What I was doing when the application crashed:
I had suspended my laptop and when I plugged it into the docking station, the power management app had crashed.

-- Backtrace:
Application: KDE Power Management System (org_kde_powerdevil), signal: Segmentation fault
[KCrash Handler]
#4  0x00007f38fda11d79 in KNotification::id() () from /usr/lib64/libKF5Notifications.so.5
#5  0x00007f38fda2e264 in ?? () from /usr/lib64/libKF5Notifications.so.5
#6  0x00007f38fda2e57f in ?? () from /usr/lib64/libKF5Notifications.so.5
#7  0x00007f38ffa91f4f in QtPrivate::QSlotObjectBase::call (a=0x7ffddc24edd0, r=0x55e3068da4a0, this=0x55e30691b180) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#8  QMetaObject::activate (sender=0x55e30691ae00, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffddc24edd0) at kernel/qobject.cpp:3784
#9  0x00007f38ffa92547 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f39001ad5c0 <QDBusPendingCallWatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffddc24edd0) at kernel/qobject.cpp:3657
#10 0x00007f38fff90d5f in QDBusPendingCallWatcher::finished (this=<optimized out>, _t1=<optimized out>) at .moc/moc_qdbuspendingcall.cpp:157
#11 0x00007f38ffa929e2 in QObject::event (this=0x55e30691ae00, e=<optimized out>) at kernel/qobject.cpp:1261
#12 0x00007f38ffa62328 in QCoreApplication::notifyInternal2 (receiver=0x55e30691ae00, event=0x55e30691a5e0) at kernel/qcoreapplication.cpp:1088
#13 0x00007f38ffa624fe in QCoreApplication::sendEvent (receiver=<optimized out>, event=event@entry=0x55e30691a5e0) at kernel/qcoreapplication.cpp:1476
#14 0x00007f38ffa64ee7 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55e3067b13c0) at kernel/qcoreapplication.cpp:1825
#15 0x00007f38ffa65488 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1679
#16 0x00007f38ffabfd93 in postEventSourceDispatch (s=0x55e306805960) at kernel/qeventdispatcher_glib.cpp:276
#17 0x00007f38f9fdc624 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#18 0x00007f38f9fdc9c0 in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x00007f38f9fdca4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f38ffabf3af in QEventDispatcherGlib::processEvents (this=0x55e3067bc8a0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#21 0x00007f38ffa6057a in QEventLoop::exec (this=this@entry=0x7ffddc24f180, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#22 0x00007f38ffa69780 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1389
#23 0x000055e3054d8b7f in ?? ()
#24 0x00007f38ff04834a in __libc_start_main () from /lib64/libc.so.6
#25 0x000055e3054d8bea in _start ()
[Inferior 1 (process 2938) detached]

Possible duplicates by query: bug 444534, bug 443954, bug 443784, bug 443771, bug 443586.

Reported using DrKonqi
Comment 1 Nate Graham 2021-11-08 20:07:28 UTC 
Unfortunately the backtrace is incomplete and missing debug symbols that we need to figure out exactly what's going wrong:


#4  0x00007f38fda11d79 in KNotification::id() () from /usr/lib64/libKF5Notifications.so.5
#5  0x00007f38fda2e264 in ?? () from /usr/lib64/libKF5Notifications.so.5
#6  0x00007f38fda2e57f in ?? () from /usr/lib64/libKF5Notifications.so.5


Could you please install debug symbols for the knotifications framework, reproduce it, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 2 Ivan Murray-Smith 2021-11-08 20:23:57 UTC 
I've installed the debug symbols, once I've managed to reproduce the issue I'll let you know. Annoyingly it's not happened again.
Comment 3 Bug Janitor Service 2021-11-23 04:38:37 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Ivan Murray-Smith 2021-11-23 09:35:11 UTC 
I have not been able to reproduce this crash.