Fedora 40 KDE new install networking issues

Ask Fedora
, , ,
1

Hello everyone! I’m not new to linux but I am new to Fedora. Compared to other distros this one has been very challenging to get setup properly, but the upside is it has all the features I’ve been wanting.

I have a brand new installation of Fedora 40 KDE that I installed using sysguides.com instructions for btrfs, encryption, snapper, etc. This guide uses the CLI route and starts you off with a Fedora Minimal system, then you install a DE from there. This system was not setup using the typical Anaconda installer route.

Most things are working well but I’m struggling with networking issues. I have internet access but everything else seems to be broken. I cannot see my networked printer, KDE connect does not see any devices, I cannot see my network shares, etc. In Windows terms, it seems like “network discovery” is turned off.

In my research, I learned something about avahi and found that avahi is not a user of any groups on this system, although the packages are installed. I was unable to find the right commands to setup avahi in the right user groups with the right permissions.

How do I proceed? What info can I provide to help diagnose the problem?

2

Why did you use that guide instead of the normal KDE Spin?

This is just causing troubles for no reason.

these issues may be firewall related or due to missing packages.

Please just install the KDE Spin or Kinoite if you want to have a reasonably configured desktop. It exists for a reason, and these issues dont happen there.

2 Likes
3

Added manual-install

4

Well if you really want to know…

I was looking for help installing fedora kde with btrfs, luks, snapshots and rollback, all setup and working. That guide gave me all the info I was seeking and I didn’t find it elsewhere. Also it’s my understanding that the anaconda installer doesn’t support encrypting the boot partition.

So this is what I’m doing and I’m not looking for advice to just start over.

5

You probably need this:

sudo firewall-cmd --permanent --add-service=samba-client
sudo firewall-cmd --reload
3 Likes
6

Don’t know, but also check if Samba stuff is installed

$ rpm -qa --qf "%{NAME}\n" | grep samba
samba-common
samba-client-libs
samba-common-libs
samba-client

If avahi stuff is installed

$ rpm -qa --qf "%{NAME}\n" | grep avahi
avahi-libs
avahi
avahi-glib
avahi-gobject

And also CUPS stuff

$ rpm -qa --qf "%{NAME}\n" | grep cups
cups-libs
cups-filesystem
cups-client
cups-ipptool
python3-cups
libcupsfilters
cups-browsed
cups-filters-driverless
cups
cups-filters
bluez-cups
gutenprint-cups
cups-pk-helper

Then check if these services are running

$ systemctl status cups
$ systemctl status avahi-daemon

Back to your specific question:

$ getent passwd | grep avahi
avahi:x:70:70:Avahi mDNS/DNS-SD Stack:/var/run/avahi-daemon:/sbin/nologin

$ getent group | grep avahi
avahi:x:70:
3 Likes
7

Thanks to you both! I’ll get on that and update this thread ASAP! I appreciate it very much

1 Like
8

Ran those - response was “success” for both. But it did not solve the problem

1 Like
9

Samba stuff is installed. Here’s the list:

samba-common
samba-common-libs
samba-client-libs
samba-client
samba-libs
samba-dcerpc
samba-ldb-ldap-modules
samba-common-tools
samba

Avahi stuff is installed, here’s the list:

avahi-libs
avahi
avahi-glib
avahi-gobject
avahi-tools

Likewise, cups:

cups-libs
cups-filesystem
cups-client
cups-ipptool
python3-cups
libcupsfilters
cups-browsed
cups-filters-driverless
cups
cups-filters
gutenprint-cups
bluez-cups
cups-pk-helper

systemctl status cups returned this -

● cups.service - CUPS Scheduler
     Loaded: loaded (/usr/lib/systemd/system/cups.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Mon 2024-07-22 18:26:18 MDT; 1 day 16h ago
TriggeredBy: ● cups.path
             ● cups.socket
       Docs: man:cupsd(8)
   Main PID: 1660 (cupsd)
     Status: "Scheduler is running..."
      Tasks: 1 (limit: 37980)
     Memory: 29.6M (peak: 53.9M)
        CPU: 1.745s
     CGroup: /system.slice/cups.service
             └─1660 /usr/sbin/cupsd -l

Jul 23 17:26:58 [1660]: REQUEST localhost - - "POST / HTTP/1.1" 200 214 Create-Printer-Subscriptions client-err>
Jul 23 17:26:58 [1660]: REQUEST localhost - - "POST / HTTP/1.1" 200 563 Create-Printer-Subscriptions successful>
Jul 24 11:04:34 [1660]: REQUEST localhost - - "POST / HTTP/1.1" 200 303 Create-Printer-Subscriptions successful>
Jul 24 11:04:34 [1660]: REQUEST localhost - - "POST / HTTP/1.1" 200 153 Cancel-Subscription successful-ok
Jul 24 11:04:34 [1660]: REQUEST localhost - - "POST / HTTP/1.1" 200 451 Create-Printer-Subscriptions successful>
Jul 24 11:04:37 [1660]: REQUEST localhost - - "GET /admin/conf/cupsd.conf HTTP/1.1" 401 0 - -
Jul 24 11:04:37 [1660]: REQUEST localhost - puppy "GET /admin/conf/cupsd.conf HTTP/1.1" 200 6787 - -
Jul 24 11:04:37 [1660]: [CGI] ippfind (PID 6436) stopped with status 2!
Jul 24 11:04:37 [1660]: [cups-deviced] PID 6408 (driverless) stopped with status 2!
Jul 24 11:04:39 [1660]: REQUEST localhost - puppy "POST / HTTP/1.1" 200 2092 CUPS-Get-Devices -

systemctl status avahi-daemon:

avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Wed 2024-07-24 11:05:10 MDT; 6min ago
TriggeredBy: ● avahi-daemon.socket
    Process: 6587 ExecStart=/usr/sbin/avahi-daemon -s (code=exited, status=255/EXCEPTION)
   Main PID: 6587 (code=exited, status=255/EXCEPTION)
        CPU: 5ms

Jul 24 11:05:10 [1]: Starting avahi-daemon.service - Avahi mDNS/DNS-SD Stack...
Jul 24 11:05:10 [6587]: Failed to find user 'avahi'.
Jul 24 11:05:10 [1]: avahi-daemon.service: Main process exited, code=exited, status=255/EXCEPTION
Jul 24 11:05:10 [1]: avahi-daemon.service: Failed with result 'exit-code'.
Jul 24 11:05:10 [1]: Failed to start avahi-daemon.service - Avahi mDNS/DNS-SD Stack.

This output remained the same after running getent passwd | grep avahi and getent group | grep avahi. Those two commands did not return anything.

10

Let’s check the results:

sudo firewall-cmd --get-active-zones
sudo firewall-cmd --list-all
grep -e ^hosts: /etc/nsswitch.conf
1 Like
11

So your first question was legit, it is the point.
Just try to add the avahi group and user.

12 

sudo firewall-cmd --get-active-zones
public (default)
  interfaces: wlo1

sudo firewall-cmd --list-all
public (default, active)
  target: default
  ingress-priority: 0
  egress-priority: 0
  icmp-block-inversion: no
  interfaces: wlo1
  sources: 
  services: dhcpv6-client mdns samba-client ssh
  ports: 
  protocols: 
  forward: yes
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules:

grep -e ^hosts: /etc/nsswitch.conf
hosts:      files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] myhostname dns
1 Like
13

I agree, so far adding the avahi group and user appears to be the issue but I haven’t been able to find the right commands to get that done. I ran the two you provided but that didn’t appear to work. Am I doing something wrong?

14

These commands don’t add users or groups. They only show the users and groups on the system. With grep, you limit the list. If they are not in place, then the output is empty.

1 Like
15

Got it. Thanks for explaining, I am learning something new today. So I’m still stuck looking for the right commands to do that

16

The command to add users is useradd

However, before doing this manually, try to reinstall the avahi package.
sudo dnf reinstall avahi

And check again if the user was created with getent passwd

3 Likes
17

That was a good idea. Can’t believe i hadn’t tried that already. Now we are getting somewhere. Not solved but progress anyway

I’m familiar with useradd but didn’t know the right commands for proper groups/permissions. Anyway, reinstall got that part done.


$ getent passwd | grep avahi
avahi:x:70:70:Avahi mDNS/DNS-SD Stack:/var/run/avahi-daemon:/sbin/nologin

$ getent group | grep avahi
avahi:x:70:

$ sudo systemctl enable --now avahi-daemon.service
[sudo] password for puppy: 
puppy@puppy-fedora-3550:~$ systemctl status avahi-daemon
× avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Wed 2024-07-24 14:52:26 MDT; 5s ago
   Duration: 847us
TriggeredBy: ● avahi-daemon.socket
    Process: 9883 ExecStart=/usr/sbin/avahi-daemon -s (code=exited, status=255/EXCEPTION)
   Main PID: 9883 (code=exited, status=255/EXCEPTION)
     Status: "avahi-daemon 0.8 starting up."
        CPU: 7ms

Jul 24 14:52:26 avahi-daemon[9883]: Successfully dropped root privileges.
Jul 24 14:52:26 avahi-daemon[9883]: avahi-daemon 0.8 starting up.
Jul 24 14:52:26 systemd[1]: Started avahi-daemon.service - Avahi mDNS/DNS-SD Stack.
Jul 24 14:52:26 avahi-daemon[9883]: Successfully called chroot().
Jul 24 14:52:26 avahi-daemon[9883]: Successfully dropped remaining capabilities.
Jul 24 14:52:26 avahi-daemon[9883]: No service file found in /etc/avahi/services.
Jul 24 14:52:26 avahi-daemon[9883]: Failed to create server: No suitable network protocol available
Jul 24 14:52:26 avahi-daemon[9883]: avahi-daemon 0.8 exiting.
Jul 24 14:52:26 systemd[1]: avahi-daemon.service: Main process exited, code=exited, status=255/EXCEPTION
Jul 24 14:52:26 systemd[1]: avahi-daemon.service: Failed with result 'exit-code'.
18

When browsing the network, I get this new error:

The Zeroconf daemon (mdnsd) is not running.

19

It is very difficult for those using standard Fedora installs to help with ad-hoc installations. When starting out with Fedora, you should start with one of the official Fedora spins. Once that is working you can ask about changes you would like to see. Some of them may already be available.

There are comments on sysguide that mention lack if wifi support. You didn’t mention if you are using wifi or wired network, but you should raise your issue on the Sysguide site.

1 Like
20

Thanks George for another discouraging comment, super helpful. I already got the message from boredsquirrel.

No doubt this is not the easy way. But the bottom line for me is if I can’t setup Fedora with BTRFS, LUKS (including the boot partition), and snapper, then I may as well go back to Debian. I just assumed there would be some documentation somewhere that could straighten this out. If Fedora can get it right with the Anaconda install, then the information is somewhere. And I’m going to learn a lot along the way.

Wifi and wired both work except for this avahi issue. Currently using wifi.