Bug 425279 - kdeconnect crashes after resuming from hibernation
Summary: kdeconnect crashes after resuming from hibernation
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-08-13 05:45 UTC by Daniel Wohlers
Modified: 2022-10-27 05:16 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Wohlers 2020-08-13 05:45:38 UTC
Application: kdeconnectd (1.4.0)

Qt Version: 5.14.2
Frameworks Version: 5.72.0
Operating System: Linux 5.4.0-42-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.19

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

I usually do not poweroff my computer but use hibernation instead.
Yesterday I put it into hibernation mode and I woke it up today to see this error.

I think, according to the linked reports, this happens because the network stack is not fully operational, when kdeconnect tries to connect to my smart phone.

After I restart the deamon it works flawlessly.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDE-Connect-Dienst (kdeconnectd), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f4add673623 in QSslSocket::connectToHost (this=this@entry=0x7f4acc043db0, hostName=..., port=port@entry=1716, openMode=..., protocol=protocol@entry=QAbstractSocket::AnyIPProtocol) at ssl/qsslsocket.cpp:2039
#5  0x00007f4add6378c2 in QAbstractSocket::connectToHost (this=0x7f4acc043db0, address=..., port=<optimized out>, openMode=...) at socket/qabstractsocket.cpp:1782
#6  0x00007f4adf458df7 in LanLinkProvider::udpBroadcastReceived (this=0x55ae2e61b660) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:118
#7  0x00007f4added351e in QtPrivate::QSlotObjectBase::call (a=0x7ffcd69d8410, r=0x55ae2e61b660, this=0x55ae2e72ca30) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate<false> (sender=0x55ae2e61b678, signal_index=3, argv=0x7ffcd69d8410) at kernel/qobject.cpp:3870
#9  0x00007f4addecdaf7 in QMetaObject::activate (sender=sender@entry=0x55ae2e61b678, m=m@entry=0x7f4ade176360 <QIODevice::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3930
#10 0x00007f4adddd1884 in QIODevice::readyRead (this=this@entry=0x55ae2e61b678) at .moc/moc_qiodevice.cpp:190
#11 0x00007f4add638504 in QAbstractSocketPrivate::emitReadyRead (this=this@entry=0x55ae2e70af70, channel=channel@entry=0) at socket/qabstractsocket.cpp:1307
#12 0x00007f4add638599 in QAbstractSocketPrivate::canReadNotification (this=0x55ae2e70af70) at socket/qabstractsocket.cpp:734
#13 0x00007f4add64aa29 in QReadNotifier::event (this=<optimized out>, e=<optimized out>) at socket/qnativesocketengine.cpp:1274
#14 0x00007f4adea4bcc3 in QApplicationPrivate::notify_helper (this=this@entry=0x55ae2e48ae80, receiver=receiver@entry=0x55ae2e78e8d0, e=e@entry=0x7ffcd69d8720) at kernel/qapplication.cpp:3685
#15 0x00007f4adea54f40 in QApplication::notify (this=0x7ffcd69d89f0, receiver=0x55ae2e78e8d0, e=0x7ffcd69d8720) at kernel/qapplication.cpp:3431
#16 0x00007f4adde9d78a in QCoreApplication::notifyInternal2 (receiver=0x55ae2e78e8d0, event=0x7ffcd69d8720) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153
#17 0x00007f4addef6de5 in socketNotifierSourceDispatch (source=0x55ae2e4e7bd0) at kernel/qeventdispatcher_glib.cpp:107
#18 0x00007f4adc553fbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f4adc554240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f4adc5542e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f4addef61e2 in QEventDispatcherGlib::processEvents (this=0x55ae2e4f8950, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x00007f4adde9c24b in QEventLoop::exec (this=this@entry=0x7ffcd69d8930, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136
#23 0x00007f4addea4296 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118
#24 0x000055ae2dd14ed8 in main (argc=<optimized out>, argv=<optimized out>) at ./daemon/kdeconnectd.cpp:186
[Inferior 1 (process 2450) detached]

The reporter indicates this bug may be a duplicate of or related to bug 407962, bug 372745, bug 419349.

Possible duplicates by query: bug 419349, bug 407962, bug 372745.

Reported using DrKonqi
Comment 1 Justin Zobel 2022-10-12 03:50:16 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-10-27 05:04:43 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 3 Daniel Wohlers 2022-10-27 05:16:12 UTC
Hi KDE Team, 

I can no longer reproduce the issue.