Bug 426347 - Kde connect daemon crashes
Summary: Kde connect daemon crashes
Status: RESOLVED WORKSFORME
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-09-09 18:27 UTC by Nemanja Mucalovic
Modified: 2022-11-11 05:21 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nemanja Mucalovic 2020-09-09 18:27:17 UTC
Application: kdeconnectd (1.4.0)

Qt Version: 5.14.2
Frameworks Version: 5.72.0
Operating System: Linux 5.4.0-47-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:

Start Plasma session
Try to connect using Android App
After warning that .babel file is writbale or partition is running out of space 
Kde connect crashes

The crash can be reproduced every time.

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

[KCrash Handler]
#4  doActivate<false> (sender=0x560ec3818110, signal_index=4, argv=0x7ffd72180530) at kernel/qobject.cpp:3754
#5  0x00007fbc13967f92 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7fbc13dfd360 <QIODevice::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd72180530) at kernel/qobject.cpp:3930
#6  0x00007fbc1385c271 in QIODevice::channelReadyRead (this=<optimized out>, _t1=<optimized out>) at .moc/moc_qiodevice.cpp:197
#7  0x00007fbc1293b16c in QAbstractSocketPrivate::canReadNotification (this=0x560ec3818130) at socket/qabstractsocket.cpp:734
#8  0x00007fbc1294e781 in QReadNotifier::event (this=<optimized out>, e=<optimized out>) at socket/qnativesocketengine.cpp:1274
#9  0x00007fbc14ab69ac in QApplicationPrivate::notify_helper (this=this@entry=0x560ec3693090, receiver=receiver@entry=0x560ec3818340, e=e@entry=0x7ffd72180800) at kernel/qapplication.cpp:3685
#10 0x00007fbc14abdbb0 in QApplication::notify (this=0x7ffd72180ae0, receiver=0x560ec3818340, e=0x7ffd72180800) at kernel/qapplication.cpp:3431
#11 0x00007fbc139324a8 in QCoreApplication::notifyInternal2 (receiver=0x560ec3818340, event=0x7ffd72180800) at kernel/qcoreapplication.cpp:1075
#12 0x00007fbc1393267e in QCoreApplication::sendEvent (receiver=<optimized out>, event=event@entry=0x7ffd72180800) at kernel/qcoreapplication.cpp:1470
#13 0x00007fbc13992378 in socketNotifierSourceDispatch (source=0x560ec36fdc30) at kernel/qeventdispatcher_glib.cpp:107
#14 0x00007fbc0d354417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007fbc0d354650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007fbc0d3546dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007fbc139917cb in QEventDispatcherGlib::processEvents (this=0x560ec36fdca0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#18 0x00007fbc13930d2a in QEventLoop::exec (this=this@entry=0x7ffd72180a20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#19 0x00007fbc1393a4a0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1383
#20 0x0000560ec26f979d in main (argc=<optimized out>, argv=<optimized out>) at ./daemon/kdeconnectd.cpp:186

Possible duplicates by query: bug 426110, bug 426090, bug 426055, bug 425658, bug 425619.

Reported using DrKonqi
Comment 1 Nemanja Mucalovic 2020-09-09 18:31:04 UTC
Exact error reported previous to crash:
Unable to save bookmarks in /home/nemanja/.local/share/user-places.xbel. Reported error was: Existing file /home/nemanja/.local/share/user-places.xbel is not writable. This error message will only be shown once. The cause of the error needs to be fixed as quickly as possible, which is most likely a full hard drive.
Comment 2 Justin Zobel 2022-10-12 03:49:44 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 3 Bug Janitor Service 2022-10-27 05:05:01 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 Bug Janitor Service 2022-11-11 05:21:38 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!