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

            Bug ID: 476422
           Summary: kdeconnectd does not start - "Could not store
                    certificate file"
    Classification: Applications
           Product: kdeconnect
           Version: 23.04.3
          Platform: RedHat Enterprise Linux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: common
          Assignee: albertv...@gmail.com
          Reporter: tdaw...@redhat.com
                CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

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.

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

Reply via email to