Bug 429303 - KDEConnect, send sms not working and no error raised
Summary: KDEConnect, send sms not working and no error raised
Status: RESOLVED DUPLICATE of bug 429249
Alias: None
Product: kdeconnect
Classification: Applications
Component: messaging-application (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Simon Redman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-18 13:59 UTC by Unknown
Modified: 2020-11-19 03:58 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 Unknown 2020-11-18 13:59:12 UTC
SUMMARY
I can't send sms.

kdeconnect-cli --send-sms "testing sms" --destination +******** --device 361e2f1339ba2d2f

The command is executed, but no any error message and sms no sended.

From GUI, I wrote the message and click to send. The message is not sended and no error raised.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon
KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
I use device Samsung Galaxy S7 Edge.

KdeConnect version

 ✘ xarkam@HYKSOS  ~  apt-cache policy kdeconnect
kdeconnect:
  Installé : 20.08.3-0xneon+20.04+focal+build11
  Candidat : 20.08.3-0xneon+20.04+focal+build11
 Table de version :
 *** 20.08.3-0xneon+20.04+focal+build11 500
        500 http://archive.neon.kde.org/user focal/main amd64 Packages
        100 /var/lib/dpkg/status
     20.08.2-0xneon+20.04+focal+build10 500
        500 http://archive.neon.kde.org/user focal/main amd64 Packages
     20.08.2-0xneon+20.04+focal+build9 500
        500 http://archive.neon.kde.org/user focal/main amd64 Packages
     20.08.2-0xneon+20.04+focal+build8 500
        500 http://archive.neon.kde.org/user focal/main amd64 Packages
     1.4-0ubuntu5 500
        500 http://be.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
Comment 1 Simon Redman 2020-11-19 03:58:47 UTC

*** This bug has been marked as a duplicate of bug 429249 ***