Bug 476422 - kdeconnectd does not start - "Could not store certificate file"
Summary: kdeconnectd does not start - "Could not store certificate file"
Status: REPORTED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (other bugs)
Version First Reported In: 23.04.3
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-01 16:23 UTC by Troy Dawson
Modified: 2025-05-10 07:56 UTC (History)
2 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 Troy Dawson 2023-11-01 16:23:39 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  On a RHEL 9 or CentOS Stream 9 system, log in with kde-connect installed.

or manually
1.  #kill all kdeconnect processes
2.  rm -rf $HOME/.config/kdeconnect/
3. /usr/libexec/kdeconnectd

OBSERVED RESULT
Normal Login:
-  A crash with normal KDE crash icons and popups

Manual start:
libEGL warning: failed to get driver name for fd 0
libEGL warning: MESA-LOADER: failed to retrieve device information
libEGL warning: failed to get driver name for fd 0
kdeconnect.core: Certificate from "/home/quake/.config/kdeconnect/certificate.pem" is not valid
kdeconnect.daemon: "KDE Connect" : "Could not store certificate file: /home/quake/.config/kdeconnect/certificate.pem"

$ ls -lh $HOME/.config/kdeconnect/
total 8.0K
-rw-------. 1 quake quake    0 Oct 31 15:07 certificate.pem
-rw-r--r--. 1 quake quake   24 Oct 31 15:07 config
-rw-------. 1 quake quake 1.7K Oct 31 15:07 privateKey.pem

EXPECTED RESULT
Login:
It should just start and not be seen
Manual:
It just starts with no output, and stays running in that console.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.4
KDE Frameworks Version:  108 / 23.04.3
Qt Version: 5.15.9-7

ADDITIONAL INFORMATION
This has been happening for a long time, not just these latest versions.
Comment 1 Troy Dawson 2023-11-01 16:24:19 UTC
Crash Report:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault

[KCrash Handler]
#4  std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/11/bits/atomic_base.h:486
#5  QAtomicOps<int>::loadRelaxed<int> (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239
#6  QBasicAtomicInteger<int>::loadRelaxed (this=0x0) at /usr/include/qt5/QtCore/qbasicatomic.h:107
#7  QtPrivate::RefCount::ref (this=0x0) at /usr/include/qt5/QtCore/qrefcount.h:55
#8  QString::QString (other=..., this=<optimized out>, this=<optimized out>, other=...) at /usr/include/qt5/QtCore/qstring.h:1094
#9  KdeConnectConfig::deviceId (this=<optimized out>) at /usr/src/debug/kde-connect-23.04.3-2.el9.next.x86_64/core/kdeconnectconfig.cpp:131
#10 0x00007f204c1adeb7 in NetworkPacket::createIdentityPacket (np=0x7fffe5b525d0) at /usr/src/debug/kde-connect-23.04.3-2.el9.next.x86_64/core/networkpacket.cpp:50
#11 0x00007f204c19a4c0 in LanLinkProvider::broadcastToNetwork (this=0x55b2bd9d7540) at /usr/src/debug/kde-connect-23.04.3-2.el9.next.x86_64/core/backends/lan/lanlinkprovider.cpp:138
#12 LanLinkProvider::broadcastToNetwork (this=0x55b2bd9d7540) at /usr/src/debug/kde-connect-23.04.3-2.el9.next.x86_64/core/backends/lan/lanlinkprovider.cpp:124
#13 0x00007f204a8dbca9 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#14 0x00007f204a8def2e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5
#15 0x00007f204a8d2ccf in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#16 0x00007f204b5af533 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#17 0x00007f204a8a7998 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#18 0x00007f204a8f8b13 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5
#19 0x00007f204a8f940c in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#20 0x00007f2048fc8e2f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#21 0x00007f204901e108 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#22 0x00007f2048fc65f3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#23 0x00007f204a8f9818 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#24 0x00007f204a8a63a2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#25 0x00007f204a8ae8d4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#26 0x000055b2bbb360ae in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kde-connect-23.04.3-2.el9.next.x86_64/daemon/kdeconnectd.cpp:185
[Inferior 1 (process 2674) detached]
Comment 2 Troy Dawson 2023-11-01 16:26:49 UTC
Although this sounds similar to the Suse Tumbleweed bugs, we have already checked that both qca-qt5 and qca-qt5-ossl are installed.  We eventually installed all the qca packages, with no changes.

We have also turned off selinux to see if that was the problem.  It wasn't.
Comment 3 cwo 2025-05-10 07:56:39 UTC
*** Bug 502287 has been marked as a duplicate of this bug. ***