Bug 438844 - KDE Daemon Connect crashes
Summary: KDE Daemon Connect crashes
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords: drkonqi
: 438857 438876 438922 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-06-18 06:57 UTC by Martin Mirchev
Modified: 2024-08-01 15:50 UTC (History)
8 users (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 Martin Mirchev 2021-06-18 06:57:36 UTC
Application: kdeconnectd (21.04.2)

Qt Version: 5.15.2
Frameworks Version: 5.82.0
Operating System: Linux 5.12.10-1-default x86_64
Windowing System: X11
Drkonqi Version: 5.22.0
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Started up the pc and a couple of seconds later it crashed again.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f73999a0340 (LWP 3114))]
[KCrash Handler]
#6  QCA::Certificate::Certificate (this=<optimized out>, opts=..., key=..., provider=..., this=<optimized out>, opts=..., key=..., provider=...) at /usr/src/debug/qca-qt5-2.3.3-1.1.x86_64/src/qca_cert.cpp:1466
#7  0x00007f739d751681 in KdeConnectConfig::generateCertificate (this=this@entry=0x7f739d76fdf0 <KdeConnectConfig::instance()::kcc>, certPath=...) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:347
#8  0x00007f739d751bfc in KdeConnectConfig::loadCertificate (this=this@entry=0x7f739d76fdf0 <KdeConnectConfig::instance()::kcc>) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:287
#9  0x00007f739d75201c in KdeConnectConfig::KdeConnectConfig (this=<optimized out>, this=<optimized out>) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:92
#10 0x00007f739d7521d5 in KdeConnectConfig::instance () at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:65
#11 KdeConnectConfig::instance () at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:65
#12 0x00007f739d7552b2 in Daemon::init (this=0x7ffd5282e0b0) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/daemon.cpp:89
#13 0x00007f739c1d709e in QObject::event (this=0x7ffd5282e0b0, e=0x561d34b66560) at kernel/qobject.cpp:1314
#14 0x00007f739cdfaa5f in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x7ffd5282e0b0, e=0x561d34b66560) at kernel/qapplication.cpp:3632
#15 0x00007f739c1aaaaa in QCoreApplication::notifyInternal2 (receiver=0x7ffd5282e0b0, event=0x561d34b66560) at kernel/qcoreapplication.cpp:1063
#16 0x00007f739c1adaf7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x561d34a55380) at kernel/qcoreapplication.cpp:1817
#17 0x00007f739c202a73 in postEventSourceDispatch (s=s@entry=0x561d34b2deb0) at kernel/qeventdispatcher_glib.cpp:277
#18 0x00007f739a74b80f in g_main_dispatch (context=0x7f7390005000) at ../glib/gmain.c:3337
#19 g_main_context_dispatch (context=0x7f7390005000) at ../glib/gmain.c:4055
#20 0x00007f739a74bb98 in g_main_context_iterate (context=context@entry=0x7f7390005000, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4131
#21 0x00007f739a74bc4f in g_main_context_iteration (context=0x7f7390005000, may_block=1) at ../glib/gmain.c:4196
#22 0x00007f739c2020f4 in QEventDispatcherGlib::processEvents (this=0x561d34b3b760, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#23 0x00007f739c1a94bb in QEventLoop::exec (this=this@entry=0x7ffd5282dfa0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#24 0x00007f739c1b1790 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#25 0x00007f739c6081fc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867
#26 0x00007f739cdfa9d5 in QApplication::exec () at kernel/qapplication.cpp:2824
#27 0x0000561d32f43a47 in main (argc=<optimized out>, argv=0x7ffd5282e050) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/daemon/kdeconnectd.cpp:174
[Inferior 1 (process 3114) detached]

Reported using DrKonqi
Comment 1 Nicolas Fella 2021-06-18 08:49:25 UTC
nico@localhost:~> /usr/lib64/libexec/kdeconnectd
Could not find support for RSA in your QCA installation
kdeconnect.daemon: "KDE Connect failed to start" : "Could not find support for RSA in your QCA installation. If your distribution provides separate packets for QCA-ossl and QCA-gnupg, make sure you have them installed and try again."
kdeconnect.core: Private key from "/home/nico/.config/kdeconnect/privateKey.pem" is not valid
kdeconnect.daemon: "KDE Connect" : "Could not store private key file: /home/nico/.config/kdeconnect/privateKey.pem"
KCrash: Application 'kdeconnectd' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi
Comment 2 Nicolas Fella 2021-06-18 08:51:13 UTC
I can reproduce this on OpenSUSE Tumbleweed.
Sounds like a downstream problem
Comment 3 Fabian Vogt 2021-06-18 08:54:39 UTC
Already fixed: https://bugzilla.opensuse.org/show_bug.cgi?id=1187457
Comment 4 Nicolas Fella 2021-06-18 08:57:39 UTC
Can confirm that installing qca-qt5 fixes it. Thanks Fabian and Christophe
Comment 5 Cristiano Guadagnino 2021-06-18 09:07:28 UTC
After installing qca-qt5 and restarting kdeconnectd I do not have anymore the message "Could not find support for RSA in your QCA installation", but I still have the "key not valid" message:

kdeconnect.core: Private key from "/home/cristiano/.config/kdeconnect/privateKey.pem" is not valid
kdeconnect.core: LanLinkProvider/newConnection: Host timed out without sending any identity. QHostAddress("::ffff:192.168.178.100")

Here is the situation with my qca-related installed packages:
~> LANG=C zypper se qca
Loading repository data...
Reading installed packages...

S  | Name               | Summary                                                   | Type
---+--------------------+-----------------------------------------------------------+--------
   | libqca-qt5         | Qt Cryptographic Architecture 2                           | package
i  | libqca-qt5-2       | QCA library                                               | package
   | libqca-qt5-devel   | Development files for the Qt Cryptographic Architecture 2 | package
   | libqca-qt5-plugins | Various plugins for the Qt Cryptographic Architecture 2   | package
   | libqca-qt6-2       | QCA library                                               | package
i+ | qca-qt5            | Qt Cryptographic Architecture 2                           | package
   | qca-qt5-devel      | Development files for the Qt Cryptographic Architecture 2 | package
i  | qca-qt5-plugins    | Various plugins for the Qt Cryptographic Architecture 2   | package
   | qca-qt6            | Qt Cryptographic Architecture 2                           | package
   | qca-qt6-devel      | Development files for the Qt Cryptographic Architecture 2 | package
   | qca-qt6-plugins    | Various plugins for the Qt Cryptographic Architecture 2   | package
Comment 6 Nicolas Fella 2021-06-18 12:02:23 UTC
*** Bug 438857 has been marked as a duplicate of this bug. ***
Comment 7 martin@piwany.com 2021-06-19 15:17:31 UTC
*** Bug 438876 has been marked as a duplicate of this bug. ***
Comment 8 Nicolas Fella 2021-06-20 11:05:11 UTC
*** Bug 438922 has been marked as a duplicate of this bug. ***
Comment 9 cwo 2024-08-01 15:50:24 UTC
No duplicates in three years, I think we can safely consider this actually fixed with that OpenSUSE change.