Re: Configure phone call application in kaddressbook

Rainer Dorsch <[email protected]> Fri, 18 Jul 2025 23:08:23 +0200
Newsgroups gmane.comp.kde.users.pim
Organization @home
Message-ID <8601406.NyiUUSuA9g@h370>
--nextPart2035334.usQuhbGJ8B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Rainer Dorsch <[email protected]>
To: [email protected]
Subject: Re: Configure phone call application in kaddressbook
Date: Fri, 18 Jul 2025 23:08:23 +0200
Message-ID: <8601406.NyiUUSuA9g@h370>
Organization: @home
In-Reply-To: <3297583.5fSG56mABF@h370>
MIME-Version: 1.0

=2E..if I remove the lines with

x-scheme-handler/
tel=3Dorg.kde.kdeconnect.app.desktop;org.kde.kdeconnect.sms.desktop;arglogg=
er.desktop;org.kde.kdeconnect.handler.desktop;
x-scheme-handler/tel=3Dorg.kde.kdeconnect.app.desktop;

from ~/.config/mimeapps.list with an editior, KDE connect gets called again.

Rainer


Am Freitag, 18. Juli 2025, 23:02:19 Mitteleurop=C3=A4ische Sommerzeit schri=
eb=20
Rainer Dorsch:
> Hi Jan,
>=20
> thanks for following up.
>=20
> System Settings is a good hint. I just click on the phone number. After I
> changed the System Settings for the phone standard app, I get the same er=
ror
> message as you though. Even if I change the app back to kde connect. Not
> sure how I can revert this setting :-/
>=20
> Other then setting the app, the phone number needs to be handed over. I
> previous verisons of kaddressbook, it was sufficient to tell kaddressbook=
 to
> call
>=20
> Linphone-6.0.0-CallEdition-x86_64.AppImage call %N
>=20
> I am running Debian trixie.
>=20
> Thanks
> Rainer
>=20
>=20
> Am Freitag, 18. Juli 2025, 15:02:10 Mitteleurop=C3=A4ische Sommerzeit sch=
rieb Jan
> Neuh=C3=A4u=C3=9Fer:
> > Hello Rainer,
> >=20
> > never thought about, there could be such a fuctionality (initiating a
> > phone
> > call, out of kaddressbook), but that sounds very interesting for me.
> >=20
> > So I started investigating:
> >=20
> > Am Donnerstag, 17. Juli 2025, 19:12:10 Mitteleurop=C3=A4ische Sommerzeit
> > schrieb
>=20
> Rainer Dorsch:
> > > Hello,
> > >=20
> > > can somebody tell if it is in kaddressbook version 6.3.3 (24.12.3) st=
ill
> > > possible to configure which application is used to do a phone call?
> > >=20
> > > I would like to use linphone, but on my system it seems it tries to u=
se
> > > the
> > > phones which are connected to kde-connect.
> >=20
> > In an opensuse forum I found the following thread, the question there w=
as
> > how to change from skype to kdeconnect, very similar to your problem:
> >=20
> > https://forums.opensuse.org/t/kdeconnect-as-default-app-in-kaddressbook=
=2Dfo
> > r-> phone-call/146469[1]
> >=20
> > The proposed solution is to change settings in ~/.config/mimeapps.list.
> >=20
> > As an example the output of a grep command is given:
> >=20
> > <snip>
> >=20
> > >$ grep -P '(skype|kdeconnect)' ~/.config/mimeapps.list
> >=20
> > x-scheme-handler/callto=3D**skype**forlinux.desktop
> > x-scheme-handler/**skype**=3D**skype**forlinux.desktop
> > x-scheme-handler/tel=3Dorg.kde.**kdeconnect**.handler.desktop
> >=20
> > </snip>
> > I think the important entry is the one for the tel-protocol
> >=20
> > But perhaps changing the standard app for phone number in system settin=
gs
> > already solves your problem.
> >=20
> > > Many thanks
> > > Rainer
> >=20
> > An additional question to Rainer:
> >=20
> > Im using the same version of kaddressbook as you: 6.3.3 (24.12.3).
> >=20
> > How do you start a phone call? When I click on a phone number I get an
> > error message from KIOexec, saying "unknown protocol 'tel'". And indeed,
> > there seem to be no KIO-module for this protocol, at least on my
> > notebook.
> >=20
> >=20
> > Kind regards,
> > Jan
> >=20
> >=20
> > --------
> > [1]
> > https://forums.opensuse.org/t/kdeconnect-as-default-app-in-kaddressbook=
=2Dfo
> > r
> > -phone-call/146469


=2D-=20
Rainer Dorsch
http://bokomoko.de/
--nextPart2035334.usQuhbGJ8B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQGzBAABCgAdFiEEvxDOxJgXzxfm1YjWzE1Dd9lwMVMFAmh6t8cACgkQzE1Dd9lw
MVNTeQwAi35tZm3eyClUFYIEFvnp1lmZ1QNcUzJHs5FVb8z9Ud2yUM1Ba+crmZCX
XQq3UUbsQSxPFwZTyjQG84noFYiXDow2hJ3xt67uotK3bh5FprS3ocjGGU+x4DMp
jMcuII2+gQMOwYNDrRAnnluhl8NsD+vxusaIF96QujW8PMZWmRwW/wiudNjqfYJm
r4SYTdqXAqblc7iCHM63YJwxpNg6P3JKlAp8qDbMAVcjQuaBnHaYhS0FCieSrfgR
qqvwNXg2DgHAkb7n+7PNZEIih0V3o+2C1j8EwzYRPHjYEteWpUdMIDJZEMimu2Os
EgDYgLjroeHKkbVBnwJNMOVGfOeaYwLh08/s2n+dsXsHDx8a3xIhJcpmkISrxTfa
a70oMIHzcBuUl/ruUMUoDS2xFvRDfLy0OwX3/FGMBEm/1DD8uxWm9QEcAT/UKOZu
Syx35gyQw7EiE22HGbUsdAVst/UVx7Nb+Nw43sY+UpOIy3IE+dhXmHdjxqUuuR9K
De3uLh3e
=ljV8
-----END PGP SIGNATURE-----

--nextPart2035334.usQuhbGJ8B--