Skip to main content ↑ ↓
Topic: kdeconnect broke for good with the last update (Read 408 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

kdeconnect broke for good with the last update

I know the issue likely doesn't have do to with artix and it is upstream, but I'm posting it nonetheless as a warning:

I can't tell which package exactly has the issue, as I tried upgrading just one and that breaks kdeconnect in a different manner instead:





And yes I tested rebooting and still get the same qdbus error:



Re: kdeconnect broke for good with the last update

Reply #1 –
This issue is caused because kdeconnectd was moved from /usr/libexec to /usr/bin.

Normally it gets started by kdeconnect-cli automatically when it isn't running, but since it was moved it no longer works.

Somebody fucked up badly here, the same issue is also affecting voidlinux.

Re: kdeconnect broke for good with the last update

Reply #2 –
Quote from: Samueru – on
This issue is caused because kdeconnectd was moved from /usr/libexec to /usr/bin.
It appears you are sort of right.
But it's /usr/lib not  /usr/libexec

/usr/share/dbus-1/services/org.kde.kdeconnect.service contains
Code: [Select]
[D-BUS Service]
Name=org.kde.kdeconnect
Exec=/usr/lib/kdeconnectd
And /usr/lib/kdeconnectd does not exist,  /usr/bin/kdeconnectd does exist
In older package versions kdeconnectd was in /usr/lib/

It works here though. version kdeconnect 24.05.0-2
Even with this seeming discrepancy ?
Code: [Select]
kdeconnect-cli -a
- Galaxy S5: cfe1771a_2013_4e9e_913e_aa32f5e31034 (paired and reachable)
1 device found

I've never used the kdeconnect cli. I use the GUI for two things only. 'Find device' & writing long SMS texts on my PC.
I just tested both and both still work ?

As a workaround you could try a softlink from /usr/bin/kdeconnectd to /usr/lib/kdeconnectd

------------------------------

I've just looked a bit more wondering why it's working for me.
Also part of the package is /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop
Which (part) contains
Code: [Select]
[Desktop Entry]
Type=Application
Exec=/usr/bin/kdeconnectd

So on my system kdeconnectd is being started by an XDG autostart. If I manually kill kdeconnectd and then run kdeconnect-cli -a I get the same error as you
Symlinking actually made no difference to that error but manually running the symlink did start the deamon.

So there does seem to be issues with dbus starting kdeconnectd. But it should be started by the autostart anyway. Or at least is is for me.

Sorry for the slightly rambling post but I've been writing it while testing it.

Re: kdeconnect broke for good with the last update

Reply #3 –
Could it be the removal of this argument here? Is someone able to reproduce this error in Arch?

Re: kdeconnect broke for good with the last update

Reply #4 –
Quote from: gripped – on
Quote from: Samueru – on
This issue is caused because kdeconnectd was moved from /usr/libexec to /usr/bin.
It appears you are sort of right.
But it's /usr/lib not  /usr/libexec

/usr/share/dbus-1/services/org.kde.kdeconnect.service contains
Code: [Select]
[D-BUS Service]
Name=org.kde.kdeconnect
Exec=/usr/lib/kdeconnectd
And /usr/lib/kdeconnectd does not exist,  /usr/bin/kdeconnectd does exist
In older package versions kdeconnectd was in /usr/lib/

It works here though. version kdeconnect 24.05.0-2
Even with this seeming discrepancy ?
Code: [Select]
kdeconnect-cli -a
- Galaxy S5: cfe1771a_2013_4e9e_913e_aa32f5e31034 (paired and reachable)
1 device found

I've never used the kdeconnect cli. I use the GUI for two things only. 'Find device' & writing long SMS texts on my PC.
I just tested both and both still work ?

As a workaround you could try a softlink from /usr/bin/kdeconnectd to /usr/lib/kdeconnectd

------------------------------

I've just looked a bit more wondering why it's working for me.
Also part of the package is /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop
Which (part) contains
Code: [Select]
[Desktop Entry]
Type=Application
Exec=/usr/bin/kdeconnectd

So on my system kdeconnectd is being started by an XDG autostart. If I manually kill kdeconnectd and then run kdeconnect-cli -a I get the same error as you
Symlinking actually made no difference to that error but manually running the symlink did start the deamon.

So there does seem to be issues with dbus starting kdeconnectd. But it should be started by the autostart anyway. Or at least is is for me.

Sorry for the slightly rambling post but I've been writing it while testing it.



Yeah I also noticed that discrepancy with libexec, what's weird is that I had a line in my i3config that auto started /usr/libexec/kdeconnectd and if it failed it would have sent a notify-send with the error. That error and notification never happened somehow and kdeconnect worked like it should. I don't know how I managed to get kdeconnectd in libexec all this time.

Although I was using archlinux back then, this change happened very recently right after I switched to artix.

Eitherway as you can see in the original screenshot, kdeconnectd gets autostarted by something when I kill it, it no longer happens with the latest version.

I personally just added checks on my script that uses kdeconnect-cli to autotstart kdeconnectd trying its possible known paths from now on.