| Summary: | After boot KDE connect always crush | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Daiver <daiver> |
| Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | andrew.g.r.holmes, cwo.kde, dylan, eevans, voidpointertonull+bugskdeorg |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 22.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Daiver
2023-08-14 03:54:27 UTC
Did you start encountering the issue after an update, or is this the first run of the program? You should check ~/.config/kdeconnect/ where privateKey.pem and certificate.pem should be two "reasonable looking" text files starting with "-----BEGIN [...]-----" and ending with "-----END [...]-----" . Hard to guess wisely without being familiar with the code, but I'd consider the following problems: - The files just don't exist which is likely the least likely option, at least on its own - The files exist, but they are empty or have garbage data in them. Seems like there's some protection against this case too, but temporarily moving the whole directory out of the way would let you see if that's the problem. Advising moving and not deleting, so you don't lose your data for a test, but you may be okay with reconfiguring from scratch - The files may or may not exist, but there are permission (or generic I/O) errors somewhere which really shouldn't happen, but I'm not convinced these errors are handled too well, so they can cause unexpected problems later in the process You may need to adjust the path depending on where your kdeconnectd binary is, but you can get more useful output by running the following command: QT_LOGGING_RULES="*.debug=true; qt.*.debug=false" /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd --replace Looking back to the code, there were quite significant related changes somewhat recently, and it seems like there are quite a few error checks you likely don't have in your version. That still doesn't change my suspicion that you likely have a broken environment, so the bug is likely not bailing out in time before an issue causes a crash later. Created attachment 163256 [details]
New crash information added by DrKonqi
kdeconnectd (23.04.3) using Qt 5.15.9
Occurs after a standard install of Plasma on CentOS 9
Certificate file in .config is empty
-- Backtrace (Reduced):
#4 0x00007f4caebfe3d6 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.23
#5 0x00007f4caec02eb7 in NetworkPacket::createIdentityPacket(NetworkPacket*) () from /lib64/libkdeconnectcore.so.23
#6 0x00007f4caebef4c0 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.23
#7 0x00007f4cad2dbca9 in QtPrivate::QSlotObjectBase::call (a=0x7fff02723750, r=<optimized out>, this=0x562e3cc2f7c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8 doActivate<false> (sender=0x562e3cadba38, signal_index=3, argv=0x7fff02723750) at kernel/qobject.cpp:3923
Created attachment 163320 [details]
New crash information added by DrKonqi
kdeconnectd (23.04.3) using Qt 5.15.9
CentOS Stream 9
KDE Plama Workspaces
Dell Precision 5250 Laptop
SELinux is disabled and firewall is off.
If you need any more information please let me know.
Every boot the kdeconnectd fails. Once I connect to bluetooth it seems to subside untill I go into ssettings and choose kdeconnect then I get the app failure essage again,
-- Backtrace (Reduced):
#4 0x00007ffb7b0d63d6 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.23
#5 0x00007ffb7b0daeb7 in NetworkPacket::createIdentityPacket(NetworkPacket*) () from /lib64/libkdeconnectcore.so.23
#6 0x00007ffb7b0c74c0 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.23
#7 0x00007ffb798dbca9 in QtPrivate::QSlotObjectBase::call (a=0x7ffca7a493b0, r=<optimized out>, this=0x5555b5b65fb0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8 doActivate<false> (sender=0x5555b5bd3ba8, signal_index=3, argv=0x7ffca7a493b0) at kernel/qobject.cpp:3923
Created attachment 163343 [details]
New crash information added by DrKonqi
kdeconnectd (23.04.3) using Qt 5.15.9
CentOS STream 9 with KDE Plasma Woekspaces. Installed through epel and epel-next.
Anytime I try to usse kdeconnect, it crashes. I'm still researching.
-- Backtrace (Reduced):
#4 0x00007f5651d793d6 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.23
#5 0x00007f5651d7deb7 in NetworkPacket::createIdentityPacket(NetworkPacket*) () from /lib64/libkdeconnectcore.so.23
#6 0x00007f5651d6a4c0 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.23
#7 0x00007f56504dbca9 in QtPrivate::QSlotObjectBase::call (a=0x7ffc1d878f50, r=<optimized out>, this=0x562b8c9f08e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8 doActivate<false> (sender=0x562b8ca356d8, signal_index=3, argv=0x7ffc1d878f50) at kernel/qobject.cpp:3923
*** This bug has been marked as a duplicate of bug 453875 *** |