Bug 405843 - kdeconnectd crashes and looses connection with android client after replying to a message.
Summary: kdeconnectd crashes and looses connection with android client after replying ...
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 1.3.3
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-24 22:47 UTC by buggydroid
Modified: 2019-03-28 16:19 UTC (History)
1 user (show)

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

Attachments
Log of the crash and manually restored connection according to the 'steps to reproduce' (6.87 KB, text/plain)
2019-03-24 22:47 UTC, buggydroid 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description buggydroid 2019-03-24 22:47:36 UTC 
Created attachment 119013 [details]
Log of the crash and manually restored connection according to the 'steps to reproduce'

SUMMARY
If we reply to a message in an android phone through kde connect Arch linux desktop client, Looks like the desktop client crashes. This can happen randomly too but it's observed consistently while replying to a message. Error log below. 

STEPS TO REPRODUCE
1. Pair & Connect Android phone and Arch Linux PC using their respective clients
2. Reply to any SMS or WhatsApp message received on phone from the desktop which    
   crashes the connection.
3. Only way to restore the connection is to right click on kde connect widget on
   desktop > go into settings > Tap on refresh > Unlock phone > Open the app >
   Press back or force stop the app to reopen it.

OBSERVED RESULT
Crash

EXPECTED RESULT
Stable connection after a reply

SOFTWARE/OS VERSIONS
Linux: 5.0.4-arch1-1-ARCH
KDE Plasma Version: 5.15.3-1
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION (ATTACHED THE SAME LOG IF YOU FIND THIS CLUNKY IN DESCRIPTION) 

Error log when the crash happens: (When I receive the message)

Mar 25 04:02:50 humanb9 audit[14255]: ANOM_ABEND auid=1000 uid=1000 gid=985 ses=3 pid=14255 comm="kdeconnectd" exe="/usr/lib/kdeconnectd" sig=11 res=1
Mar 25 04:02:50 humanb9 kernel: kdeconnectd[14255]: segfault at c9 ip 00007f795663c498 sp 00007fffa93cac98 error 4 in libQt5Core.so.5.12.2[7f795641c000+2ca000]
Mar 25 04:02:50 humanb9 kernel: audit: type=1701 audit(1553466770.787:696): auid=1000 uid=1000 gid=985 ses=3 pid=14255 comm="kdeconnectd" exe="/usr/lib/kdeconnectd" sig=11 res=1
Mar 25 04:02:51 humanb9 systemd-coredump[14867]: Process 14255 (kdeconnectd) of user 1000 dumped core.
                                                 #4  0x00007f794cc1777e n/a (kdeconnect_notifications.so)
                                                 #5  0x00007f794cc1f446 n/a (kdeconnect_notifications.so)
                                                 #6  0x00007f794cc1b002 n/a (kdeconnect_notifications.so)
                                                 #7  0x00007f79577514a0 _ZN6Device21privateReceivedPacketERK13NetworkPacket (libkdeconnectcore.so.1)
                                                 #9  0x00007f79577584d6 n/a (libkdeconnectcore.so.1)
                                                 #10 0x00007f7957729013 _ZN13LanDeviceLink12dataReceivedEv (libkdeconnectcore.so.1)
                                                 #12 0x00007f7957730981 _ZN16SocketLineReader12dataReceivedEv (libkdeconnectcore.so.1)
                                                 #30 0x0000555b11f8112f n/a (kdeconnectd)
                                                 #32 0x0000555b11f8119e _start (kdeconnectd)

Log after restoring the connection - 

Mar 25 04:03:56 humanb9 dbus-daemon[906]: [session uid=1000 pid=906] Activating service name='org.kde.kdeconnect' requested by ':1.168' (uid=1000 pid=14945 comm="/usr/bin/kcmshell5 kcm_kdeconnect ")
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: kdeconnect.core: KdeConnect daemon starting
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: kdeconnect.core: onStart
Mar 25 04:03:56 humanb9 dbus-daemon[906]: [session uid=1000 pid=906] Successfully activated service 'org.kde.kdeconnect'
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: kdeconnect.core: KdeConnect daemon started
Mar 25 04:03:56 humanb9 plasmashell[986]: kdeconnect.interfaces: dbus interface not valid
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Type= "fixed" line for icon theme:  "/usr/share/icons/macOS/places/symbolic/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/8x8/legacy/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/16x16/legacy/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/16x16/ui/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/22x22/legacy/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/24x24/legacy/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/24x24/ui/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/32x32/legacy/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/32x32/ui/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/48x48/legacy/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/48x48/ui/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/256x256/legacy/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/512x512/legacy/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/scalable/ui/"
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: kdeconnect.core: Broadcasting identity packet
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: kdeconnect.core: Sending onNetworkChange to  1  LinkProviders
Mar 25 04:03:56 humanb9 kdeconnectd[14951]: kdeconnect.core: Broadcasting identity packet
Mar 25 04:04:00 humanb9 kdeconnectd[14951]: kdeconnect.core: TCP connection done (i'm the existing device)
Mar 25 04:04:00 humanb9 kdeconnectd[14951]: kdeconnect.core: Starting server ssl (I'm the client TCP socket)
Mar 25 04:04:00 humanb9 kdeconnectd[14951]: kdeconnect.core: Socket succesfully stablished an SSL connection
Mar 25 04:04:00 humanb9 kdeconnectd[14951]: kdeconnect.core: It is a known device "Xiaomi"
Mar 25 04:04:00 humanb9 kdeconnectd[14951]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Mar 25 04:04:00 humanb9 kdeconnectd[14951]: kdeconnect.plugin.sftp: add to dolphin
Mar 25 04:04:00 humanb9 kdeconnectd[14951]: kdeconnect.plugin.sftp: Created device: "Xiaomi"
Mar 25 04:04:00 humanb9 plasmashell[986]: kdeconnect.interfaces: Adding missing or previously removed device "0b8728edee56c7b1"

Error log of the second crash after replying to the message post restore - 

Mar 25 04:04:11 humanb9 audit[14951]: ANOM_ABEND auid=1000 uid=1000 gid=985 ses=3 pid=14951 comm="kdeconnectd" exe="/usr/lib/kdeconnectd" sig=11 res=1
Mar 25 04:04:11 humanb9 kernel: kdeconnectd[14951]: segfault at 30 ip 00007fa4520fa523 sp 00007ffed68f6df8 error 4 in libQt5Core.so.5.12.2[7fa45203f000+2ca000]
Mar 25 04:04:11 humanb9 kernel: audit: type=1701 audit(1553466851.798:703): auid=1000 uid=1000 gid=985 ses=3 pid=14951 comm="kdeconnectd" exe="/usr/lib/kdeconnectd" sig=11 res=1
Mar 25 04:04:12 humanb9 systemd-coredump[14974]: Process 14951 (kdeconnectd) of user 1000 dumped core.
                                                 #2  0x00007fa44878977e n/a (kdeconnect_notifications.so)
                                                 #3  0x00007fa448791446 n/a (kdeconnect_notifications.so)
                                                 #4  0x00007fa44878d002 n/a (kdeconnect_notifications.so)
                                                 #5  0x00007fa4533744a0 _ZN6Device21privateReceivedPacketERK13NetworkPacket (libkdeconnectcore.so.1)
                                                 #7  0x00007fa45337b4d6 n/a (libkdeconnectcore.so.1)
                                                 #8  0x00007fa45334c013 _ZN13LanDeviceLink12dataReceivedEv (libkdeconnectcore.so.1)
                                                 #10 0x00007fa453353981 _ZN16SocketLineReader12dataReceivedEv (libkdeconnectcore.so.1)
                                                 #28 0x0000557a8d71b12f n/a (kdeconnectd)
                                                 #30 0x0000557a8d71b19e _start (kdeconnectd)
Comment 1 Simon Redman 2019-03-25 18:39:42 UTC 
Sorry you are having this issue!

Could you install debug symbols for (at least) kdeconnectd, then capture a backtrace of the crash? The current backtraces don't give enough information for me to see where the crash is happening.
Comment 2 buggydroid 2019-03-28 11:44:09 UTC 
(In reply to Simon from comment #1)
> Sorry you are having this issue!
> 
> Could you install debug symbols for (at least) kdeconnectd, then capture a
> backtrace of the crash? The current backtraces don't give enough information
> for me to see where the crash is happening.

Sorry for replying late as I wanted to report after completely testing it. 
I compiled it from source for a good backtrace but to my surprise, It was actually working fine and very stable after compiling it from sources with Cmake. Looks like the bug was in the arch community package or just a broken installation and not really in the KDE connect. Thanks for your time.
Comment 3 Simon Redman 2019-03-28 16:19:02 UTC 
Glad to hear it! It's not a crash I've seen before, so hopefully this was a one-off.