https://bugs.kde.org/show_bug.cgi?id=473351

Pedro V <voidpointertonull+bugskde...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |voidpointertonull+bugskdeor
                   |                            |g...@gmail.com

--- Comment #1 from Pedro V <voidpointertonull+bugskde...@gmail.com> ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to