Bug 387856 - kdeconnectd 1.2 can't start on KDE Neon
Summary: kdeconnectd 1.2 can't start on KDE Neon
Status: RESOLVED NOT A BUG
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (other bugs)
Version First Reported In: 1.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-13 01:47 UTC by yihui.xiong
Modified: 2017-12-13 02:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description yihui.xiong 2017-12-13 01:47:43 UTC 
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
Comment 1 yihui.xiong 2017-12-13 02:10:08 UTC 
(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