basecamp
fix: Ensure systemd-resolved is enabled
The commit adds a migration that enables systemd-resolved, which was disabled on
some systems, leading to DNS resolution errors post omarchy 2.0-migration, as seen in
issue basecamp#1110 and issue basecamp#1072.
This is also run as part of the install/config/network.sh-script, to cover new installs as well as migrations
Just running this command did not resolve it for me. But maybe requires a reboot?
claude suggested, maybe totallt wrong (but worked) to also symlink.
Enable systemd-resolved to start automatically on boot
sudo systemctl enable systemd-resolved
Also make sure the resolv.conf symlink is correct
sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
I'd suggest if it doesn't help for you that you may be having a different issue, as multiple people (myself included) were helped by the fix.
I'd also be very skeptical of untested claude fixes.
Yes maybe, but some process should make sure /etc/resolv.conf matches the stub to make some cli tools able to resolv dns. Maybe your solution will fix this after a reboot, will try later today.
But seems to be some different discussions and solutions cooking for this issue so I am sure it will be fixed in the appropiate way.
I also had some issues with this, for example the Store page in Steam didn't work, but everything else seemed to work fine. I got an error indicating a DNS-issue, so did some troubleshooting with Gemini.
I had a file /etc/resolv.conf which was a static file with the following content:
# Resolver configuration file.
# See resolv.conf(5) for details.
Gemini claimed that it had to be a symlink to /run/systemd/resolve/stub-resolv.conf.
I ran the following commands:
mv resolv.conf resolve.conf.bak
sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
sudo systemctl restart systemd-resolved.service
I restarted the Steam client and it seems to have been fixed.
