kdeconnect regression 22.12.3 to 24.12.0

[Albert Vaca Cintora]

Check the logs in case there's something suspicious there (like an error or
a warning). On the Android app there's a button in settings to export them.
On the desktop you can run `kdeconnectd --replace` to run the daemon
manually on a terminal and check the output. Best case there's an error
that tells us what the problem is. Worst case (if the devices really don't
see each other at all) you will see no trace about the other device.

On Sat, Apr 19, 2025 at 10:24 PM Rainer Dorsch <ml at bokomoko.de> wrote:

> Hi Albert,
>
> many thanks for the quick reply.
>
> I could delete the config on both sides, but I cannot pair again, since
> neither
> side finds the other side, both show empty lists.
>
> I assume the problem is on the Debian desktop side, since pairing with
> kdeconnect 24.12.3 running on a Manjaro system works flawless.
>
> Thanks
> Rainer
>
> Am Samstag, 19. April 2025, 02:01:31 Mitteleuropäische Sommerzeit
> schrieben
> Sie:
> > Can you try clearing the configuration on both sides and pairing again?
> On
> > Android you need to go to the app settings and click "clear data". On the
> > desktop it's located in ~/.config/kdeconnect.
> >
> > On Fri, Apr 18, 2025 at 12:09 PM Rainer Dorsch <ml at bokomoko.de> wrote:
> > > Hello,
> > >
> > > during a Debian x86 desktop upgrade, I upgraded from kdeconnect
> 22.12.3 to
> > > 24.12.0 on that machine . Unfortunately, after the upgrade kdeconnect
> does
> > > not
> > > connect to a moble running kdeconnect 1.33.2 from fdroid on LineageOS
> > > anymore.
> > >
> > > The app on LineageOS says that the connected (desktop) device is no
> > > reachable.
> > > The desktop application on Debian says no connected device is
> reachable.
> > >
> > > I can ping from the desktop the mobile device and from the mobile
> device
> > > the
> > > desktop device without any issues.
> > >
> > > I am aware that I use maybe two non-standard configurations
> > > 1) The desktop is connected to multiple vlans
> > > 2) The desktop uses /etc/network/interfaces and not network manager to
> > > configure the network on the desktop
> > >
> > > The mobile side should not be affected by these non-standard
> > > configurations
> > > though.
> > >
> > > Any hint or advice what could be the root cause of the issue is
> welcome.
> > >
> > > Many thanks
> > > Rainer
> > >
> > > --
> > > Rainer Dorsch
> > > http://bokomoko.de/
>
>
> --
> Rainer Dorsch
> http://bokomoko.de/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20250419/21ed9fa5/attachment.htm>