Der avahi zeroconf Browser zeigt ja nichts an.
Über das Terminal funktioniert es.
Kann es sein das für KDE Abhängigkeiten fehlen ?
Wenn ich mir avahi anschaue sieht das so aus
kio-zeroconf ?
Das war es leider nicht.
Ich versuche es nochmal genauer zu erklären.
avahi-browse -art ✔
+ eno2 IPv4 dreambox _sftp-ssh._tcp local
+ eno2 IPv4 dreambox HTTPS _https._tcp local
+ eno2 IPv4 dreambox HTTP _http._tcp local
+ eno2 IPv4 dreambox FTP _ftp._tcp local
+ eno2 IPv4 dreambox _ssh._tcp local
+ eno2 IPv4 Block CR-20 002261715c68 _spotify-connect._tcp local
+ eno2 IPv4 KEF LSX_024441 _spotify-connect._tcp local
+ eno2 IPv4 841715024441@KEF LSX _raop._tcp local
+ eno2 IPv4 DREAMBOX _smb._tcp local
+ eno2 IPv4 dreambox SMB _smb._tcp local
+ eno2 IPv4 192-168-0-1 _smb._tcp local
+ eno2 IPv4 192-168-0-1 _fbox._tcp local
+ eno2 IPv4 192-168-0-1 _l2tpv3._tcp local
+ eno2 IPv4 192-168-0-1 _igd2._tcp local
+ eno2 IPv4 192-168-0-1 _igd._tcp local
+ eno2 IPv4 192-168-0-1 _libmediasrv._tcp local
+ eno2 IPv4 KEF LSX _airplay._tcp local
+ eno2 IPv4 [LG] webOS TV LR60006LA _airplay._tcp local
= eno2 IPv4 [LG] webOS TV LR60006LA _airplay._tcp local
hostname = [LGwebOSTV.local]
address = [192.168.0.27]
port = [7000]
txt = ["pk=c51f0e14a9586601c96d227bf4871ef59382eb487fb75988e8af740378f461aa" "gcgl=0" "gid=00000000-0000-0000-0000-3D0CCA12C3D3" "psi=00000000-0000-0000-0000-3D0CCA12C3D3" "pi=3D:0C:CA:12:C3:D3" "srcvers=377.40.00" "protovers=1.1" "serialNumber=502TAJD00572_74:c1:7e:b8:82:63" "manufacturer=LG" "integrator=LG Electronics" "model=32LR60006LA" "flags=0x244" "at=0x1" "fv=p20.13.43.25" "rsf=0x3" "fex=0Ip/AEbPiwNACA" "features=0x7F8AD0,0x38BCF46" "deviceid=3D:0C:CA:12:C3:D3" "acl=0"]
= eno2 IPv4 192-168-0-1 _libmediasrv._tcp local
hostname = [fritz.box]
address = [fd48:44a5:12d1:0:b6fc:7dff:fe8c:899b]
port = [49000]
txt = ["path=http://fritz.box:49000/MediaServerDevDesc.xml"]
= eno2 IPv4 192-168-0-1 _igd._tcp local
hostname = [fritz.box]
address = [fd48:44a5:12d1:0:b6fc:7dff:fe8c:899b]
port = [49000]
txt = ["path=http://fritz.box:49000/igddesc.xml"]
= eno2 IPv4 192-168-0-1 _igd2._tcp local
hostname = [fritz.box]
address = [fd48:44a5:12d1:0:b6fc:7dff:fe8c:899b]
port = [49000]
txt = ["path=http://fritz.box:49000/igd2desc.xml"]
= eno2 IPv4 192-168-0-1 _l2tpv3._tcp local
hostname = [fritz.box]
address = [fd48:44a5:12d1:0:b6fc:7dff:fe8c:899b]
port = [49000]
txt = ["path=http://fritz.box:49000/l2tpv3.xml"]
= eno2 IPv4 192-168-0-1 _fbox._tcp local
hostname = [fritz.box]
address = [fd48:44a5:12d1:0:b6fc:7dff:fe8c:899b]
port = [49000]
txt = ["path=http://fritz.box:49000/fboxdesc.xml"]
= eno2 IPv4 192-168-0-1 _smb._tcp local
hostname = [fritz.box]
address = [fd48:44a5:12d1:0:b6fc:7dff:fe8c:899b]
port = [445]
txt = []
= eno2 IPv4 KEF LSX _airplay._tcp local
hostname = [KEF-LSX.local]
address = [192.168.0.22]
port = [7000]
txt = ["pk=52c32b5f94374ecb364e0d2203fad12fb4f63a1091d0a20a51825325c1cc6dd4" "gcgl=0" "gid=970f0973-4f28-4764-9dd7-1e6fe5fd5170" "pi=970f0973-4f28-4764-9dd7-1e6fe5fd5170" "srcvers=366.0" "protovers=1.1" "serialNumber=84:17:15:02:44:41" "manufacturer=KEF" "model=LSX" "flags=0x4" "fv=p20.5202205110.105243422" "rsf=0x0" "features=0x445D0A00,0x1C340" "deviceid=84:17:15:02:44:41" "acl=0"]
= eno2 IPv4 841715024441@KEF LSX _raop._tcp local
hostname = [KEF-LSX.local]
address = [192.168.0.22]
port = [7000]
txt = ["pk=52c32b5f94374ecb364e0d2203fad12fb4f63a1091d0a20a51825325c1cc6dd4" "vs=366.0" "vn=65537" "tp=UDP" "sf=0x4" "am=LSX" "md=2" "fv=p20.5202205110.105243422" "ft=0x445D0A00,0x1C340" "et=0,4" "da=true" "cn=0,1"]
= eno2 IPv4 KEF LSX_024441 _spotify-connect._tcp local
hostname = [KEF-LSX.local]
address = [192.168.0.22]
port = [80]
txt = ["CPath=/goform/spotifyConfig" "VERSION=1.0"]
= eno2 IPv4 Block CR-20 002261715c68 _spotify-connect._tcp local
hostname = [Block-CR-20-002261715c68.local]
address = [192.168.0.21]
port = [80]
txt = ["VERSION=1.0" "CPath=/goform/spotifyConfig"]
= eno2 IPv4 dreambox HTTPS _https._tcp local
hostname = [dreambox.local]
address = [192.168.0.24]
port = [443]
txt = []
= eno2 IPv4 dreambox _sftp-ssh._tcp local
hostname = [dreambox.local]
address = [192.168.0.24]
port = [22]
txt = []
= eno2 IPv4 dreambox SMB _smb._tcp local
hostname = [dreambox.local]
address = [192.168.0.24]
port = [139]
txt = []
= eno2 IPv4 DREAMBOX _smb._tcp local
hostname = [dreambox.local]
address = [192.168.0.24]
port = [445]
txt = []
= eno2 IPv4 dreambox _ssh._tcp local
hostname = [dreambox.local]
address = [192.168.0.24]
port = [22]
txt = []
= eno2 IPv4 dreambox FTP _ftp._tcp local
hostname = [dreambox.local]
address = [192.168.0.24]
port = [21]
txt = []
= eno2 IPv4 dreambox HTTP _http._tcp local
hostname = [dreambox.local]
address = [192.168.0.24]
port = [80]
txt = []
Diese Terminalausgabe sollte doch im grafischen Avahi-Discover erscheinen.
Tut sie aber nicht
Auf meinem Notebook, was auf stable branch ist, ist es genau so.
Das ist für Neueinsteiger natürlich unschön, da sie denken es funktioniert nicht.
I think there may be an issue with the avahi-discover python script which causes the window to be empty.
Ich denke, es könnte ein Problem mit dem avahi-discover-Python-Skript geben, das das Fenster dazu veranlasst Leer sein.
Not a problem with the script but more the fact that it wants to write to a location that can only be written to using elevated privileges
Kein Problem mit dem Skript sondern mehr die Tatsache, dass es an einen Ort schreiben will, an den man nur mit erhöhten Berechtigungen schreiben kann
$ ls -la /usr/lib/avahi
total 304
drwxr-xr-x 2 root root 4096 23 dec 08:19 .
drwxr-xr-x 254 root root 282624 1 jun 16:21 ..
-rw-r--r-- 1 root root 20480 21 nov 2024 service-types.db
ls -la /usr/lib/avahi ✔
insgesamt 260
drwxr-xr-x 2 root root 4096 31. Mai 22:00 .
drwxr-xr-x 178 root root 237568 1. Jun 02:36 ..
-rw-r--r-- 1 root root 20480 21. Nov 2024 service-types.db
Das ist dann also was für die Dev’s
Gut das wir diesen Schönheitsfehler klären konnten.
Ich wusste echt nicht mehr wo ich suchen sollte.
@linux-aarhus
Same issue with upstream Arch Linux - so we will see what
Das gleiche Problem mit Upstream-Arch-Linux
It seems to be a standing issue with avahi
Es scheint ein ständiges Problem mit Avahi zu sein
→ Use of dbm causes problems with Python 3.13 · Issue #670 · avahi/avahi · GitHub
→ Fix issue with dbm.sqlite3 on readonly directories by mickael9 · Pull Request #698 · avahi/avahi · GitHub
EDIT:
I have devised a workaround - it is no optimal, it may not even be the right one - but if you rely on avahi discover service - it will work
Change the ownership of the folder /usr/lib/avahi including files
sudo chown root:avahi /usr/lib/avahi -R
Change permissions to allow avahi group to write into the folder including the existing db file
sudo chmod g+w /usr/lib/avahi -R
Finally add yourself to the avahi group
sudo gpasswd -a $USER avahi
Logoff and login to activate the new group.
3 Likes
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.