I think I only found 1 or 2 posts on this when googling, or dudugoing:
When doing this:
The PATH is there, no idea why it is warning me, but it only warns me when I sudo snap install dynu-utils.
I get no warning when I have already sudo -i and then snap install dynu-utils
mikx4 ✓ 2025-10-01 14:31:01 cachyos-x8664 ~
$ sudo snap install dynu-utils
Warning: /var/lib/snapd/snap/bin was not found in your $PATH. If you’ve not restarted your session
since you installed snapd, try doing that. Please see How to fix snap binaries not found
for more details.
Either log out and back in again, or restart your system, to ensure snap’s paths are updated correctly.
This shouldn’t occur after a reboot, if it does, there’s likely some conflict elsewhere but the fix is to ensure $PATH contains /snap/bin by default for users.
Not having this won’t outright break things but does have the potential to cause some disruptions depending on what snaps you’re using. (Mostly classic snaps, given the ecosystem, or CLI primary snaps as you’d have to use snap run each time).
I’d not treat this as a warning if you have rebooted. It’s an outright error, although an error that isn’t fatal in most contexts.
If you installed Cmake as a snap for example, expecting it to be used by all other packages on the system, you would find it broken by this problem, as no other package would be able to find it.