Hey, > I've been quite surprised to find that this bug report was first filled > in 2016 because I've only began experiencing it for about a week. Using > testing I waited for a week to see if a fix would come. Now's the time > for the BR.
well this is a bug, that needs to be solved by upstream, so please file a bugreport at https://bugs.kde.org > It's also sad that we can't strace which system call causes the crash > nor use gdb (even without debugging information). > > ------8<------8<------8<------8<------8<------8<------8<------8<------ > ~$ LC_ALL=C strace /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd > strace: test_ptrace_get_syscall_info: PTRACE_TRACEME: Operation not > permitted strace: ptrace(PTRACE_TRACEME, ...): Operation not permitted > +++ exited with 1 +++ > ~$ gdb /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd > [...] > (No debugging symbols found in > /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd) (gdb) run > Starting program: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd > warning: Could not trace the inferior process. > warning: ptrace: Operation not permitted > During startup program exited with code 127. > ------8<------8<------8<------8<------8<------8<------8<------8<------ Your user needs to have the ptrace permission in order to use gdb successfully [1]. And you need to install the symbols files: kdeconnect-dbgsym from the repo: deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main hefee [1] https://wiki.ubuntu.com/SecurityTeam/Roadmap/ KernelHardening#ptrace_Protection
signature.asc
Description: This is a digitally signed message part.
