| Summary: | kdeconnectd 1.2 can't start on KDE Neon | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | yihui.xiong |
| Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | 1.2 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
(In reply to yihui.xiong from comment #0) > OS: KDE neon User Edition 5.11 > APP: kdeconnect/xenial,now 1.2-0neon+16.04+xenial+build28 amd64 > > $ kdeconnect-cli --refresh > error activating kdeconnectd: QDBusError("", "") > error: Process org.kde.kdeconnect received signal 6 > > $ /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd > kdeconnect.core: KdeConnect daemon starting > pure virtual method called > terminate called without an active exception > Aborted > > > It seems kdeconnectd can't start after upgrading to KDE Frameworks 5.41.0. > kdeconnect worked well before that after remove its configuration, it can start rm -rf .config/kdeconnect |
OS: KDE neon User Edition 5.11 APP: kdeconnect/xenial,now 1.2-0neon+16.04+xenial+build28 amd64 $ kdeconnect-cli --refresh error activating kdeconnectd: QDBusError("", "") error: Process org.kde.kdeconnect received signal 6 $ /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd kdeconnect.core: KdeConnect daemon starting pure virtual method called terminate called without an active exception Aborted It seems kdeconnectd can't start after upgrading to KDE Frameworks 5.41.0. kdeconnect worked well before that