You are not logged in.
Pages: 1
KDE Connect app is keeps crashing...
here is the output of journalctl -p 3 -xb
Jul 07 17:41:32 hell systemd-coredump[1802]: Process 714 (kdeconnectd) of user 1000 dumped core.
Stack trace of thread 714:
#0 0x00007fae5639a97a _ZeqRK7QStringS1_ (libQt5Core.so.5)
#1 0x00007fae57dcbbbd _ZN13KNotification8setTitleERK7QString (libKF5Notifications.so.5)
#2 0x00007fae2d88a27e n/a (kdeconnect_notifications.so)
#3 0x00007fae2d891f46 n/a (kdeconnect_notifications.so)
#4 0x00007fae2d88db02 n/a (kdeconnect_notifications.so)
#5 0x00007fae5839f390 _ZN6Device21privateReceivedPacketERK13NetworkPacket (libkdeconnectcore.so.1)
#6 0x00007fae564fec50 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
#7 0x00007fae583a63c6 n/a (libkdeconnectcore.so.1)
#8 0x00007fae58376f03 _ZN13LanDeviceLink12dataReceivedEv (libkdeconnectcore.so.1)
#9 0x00007fae564fec50 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
#10 0x00007fae5837e871 _ZN16SocketLineReader12dataReceivedEv (libkdeconnectcore.so.1)
#11 0x00007fae564fec50 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
#12 0x00007fae558bb0ca n/a (libQt5Network.so.5)
#13 0x00007fae558a5131 n/a (libQt5Network.so.5)
#14 0x00007fae564feafc _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
#15 0x00007fae55865514 n/a (libQt5Network.so.5)
#16 0x00007fae558655a0 n/a (libQt5Network.so.5)
#17 0x00007fae55878202 n/a (libQt5Network.so.5)
#18 0x00007fae57248a74 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5)
#19 0x00007fae57250341 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5)
#20 0x00007fae564d4cb9 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
#21 0x00007fae56528cab n/a (libQt5Core.so.5)
#22 0x00007fae4fe06368 g_main_context_dispatch (libglib-2.0.so.0)
#23 0x00007fae4fe065b1 n/a (libglib-2.0.so.0)
#24 0x00007fae4fe0663e g_main_context_iteration (libglib-2.0.so.0)
#25 0x00007fae56528039 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.>
#26 0x00007fae48654722 n/a (libQt5XcbQpa.so.5)
#27 0x00007fae564d394c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#28 0x00007fae564dbc46 _ZN16QCoreApplication4execEv (libQt5Core.so.5)
#29 0x0000562dcde56daf n/a (kdeconnectd)
#30 0x00007fae55b4106b __libc_start_main (libc.so.6)
#31 0x0000562dcde56e1a _start (kdeconnectd)
Stack trace of thread 718:
#0 0x00007fae55c0bea9 __poll (libc.so.6)
#1 0x00007fae4e537180 n/a (libxcb.so.1)
#2 0x00007fae4e538e4b xcb_wait_for_event (libxcb.so.1)
#3 0x00007fae485bf22a n/a (libQt5XcbQpa.so.5)
#4 0x00007fae56326b45 n/a (libQt5Core.so.5)
#5 0x00007fae51deb075 start_thread (libpthread.so.0)
#6 0x00007fae55c1653f __clone (libc.so.6)
Stack trace of thread 721:
#0 0x00007fae55c0bea9 __poll (libc.so.6)
#1 0x00007fae4fe06523 n/a (libglib-2.0.so.0)
#2 0x00007fae4fe0663e g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fae56528039 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.>
#4 0x00007fae564d394c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5 0x00007fae5631ca99 _ZN7QThread4execEv (libQt5Core.so.5)
#6 0x00007fae54f54976 n/a (libQt5DBus.so.5)
#7 0x00007fae56326b45 n/a (libQt5Core.so.5)
#8 0x00007fae51deb075 start_thread (libpthread.so.0)
#9 0x00007fae55c1653f __clone (libc.so.6)
Stack trace of thread 729:
#0 0x00007fae55c0bea9 __poll (libc.so.6)
#0 0x00007fae55c0bea9 __poll (libc.so.6)
#1 0x00007fae4fe06523 n/a (libglib-2.0.so.0)
#2 0x00007fae4fe0663e g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fae56528039 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.>
#4 0x00007fae564d394c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5 0x00007fae5631ca99 _ZN7QThread4execEv (libQt5Core.so.5)
#6 0x00007fae56326b45 n/a (libQt5Core.so.5)
#7 0x00007fae51deb075 start_thread (libpthread.so.0)
#8 0x00007fae55c1653f __clone (libc.so.6)
-- Subject: Process 714 (kdeconnectd) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
--
-- Process 714 (kdeconnectd) crashed and dumped core.
--Offline
From my experience, I have found some versions of kdeconnect have problems with keeping a continuous connection. When kdeconnect is first installed it doesn't seem to have a problem, but over time it gets harder and harder to maintain a solid connection. Deleting the config folder in ~/.config/kdeconnect seems to help with connectivity temporarily, but the problem always seems to return. When it is not connecting properly it will cause constant coredumps that can quickly grow to a very large size. I eventually just ended up disabling coredumps because of this.
This has been a super annoying issue (depending on the version) with kdeconnect ever since I started using it several years ago. In all fairness I don't think its actually the computer side of things that causes the connectivity problems. I'm pretty sure its the Android app that causes the connection issues. I have side loaded older Android versions on my phone that I knew didn't have connection problems in the past. This would fix the connection problems, but then you wouldn't get the new features kdeconnect had introduced in recent versions.
Over time I have narrowed down what is causing the problem. I believe some of the plugins are what causes the " Segmentation fault (core dump)". If you disable the plugin(s) that seem problematic then hopefully the connection will remain stable. First you must determine which plugin options are causing your problems. Disable any plugins that seem to be causing problems until you can maintain a stable connection. Then you must lock the kdeconnect config file so that it can not be changed using the chattr command. This will lock the kdeconnect config file so that not even the root user can edit it.
You must edit the following command to reflect the correct path to your devices config file.
# chattr +i ~/.config/kdeconnect/3ff877f1e2e120e2/configIf you want to edit your plugin options again, you can unlock the config file using the following command:
# chattr -i ~/.config/kdeconnect/3ff877f1e2e120e2/configThis has resolved my connection issues and resultant coredumps.
Last edited by tbg (2018-07-14 03:57:20)
Offline
I have followed the hint of tbg. I found the plugin causing error is the "receive notifications".
I am using
plasma 5.13
kde framework 5.50
qt 5.11
kernel 4.14
kdeconnect 1.3.1-1
I would suggest to just disable that plugin from KDE connect GUI. It works fine for me.
I think the bug report is this one https://bugs.kde.org/show_bug.cgi?id=389518
Last edited by alx_03 (2018-10-10 12:09:48)
Offline
Pages: 1