I second that. Unless I'm missing something, the solution wasn't to change the DNS addresses. He simply changed the file in /etc/resolv.conf to a regular text file instead of a symlink to /run.
Given that /run is not a normal mountpoint it sounds like applications were hitting some sort of snag when trying to follow the symlink. I'm assuming he did not change the contents of the resolv.conf This is also where distros start to diverge. On my machine /run mounts look like this $ mount |grep /run tmpfs on /run type tmpfs tmpfs on /run/user/1000 type tmpfs portal on /run/user/1000/doc type fuse.portal gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse I find it interesting that he is hitting a snag when trying to read a text file. Even more interesting that nobody else is having the same problem. -Ben On Monday, November 4th, 2024 at 9:56 AM, Tomas Kuchta <[email protected]> wrote: > Comcast does support IPv6 - it was one of the first ISPs to do so, AFAIK. > > I would think it would make sense to figure out the real issue and > configure IPv6 correctly. If my memory serves me right about half of the > internet is IPv6 enabled these days. > > Just a comment attempting to stop IPv6 misinformation, > -T > > On Mon, Nov 4, 2024, 08:14 Michael Ewan [email protected] wrote: > > > Yes. That triggered a memory of the reason my system (Linux Mint) was > > doing the same thing. It was caused by ipv6 queries that went nowhere, I > > do not need ipv6 and Comcast does not support it afaik, so I disabled it > > and everything is fine now. > > > > On Sun, Nov 3, 2024 at 2:37 PM Paul Heinlein [email protected] wrote: > > > > > On Sat, 2 Nov 2024, American Citizen wrote: > > > > > > > Tomas: > > > > > > > > I did a fairly good look into the /var folder. > > > > > > > > I don't see anything much from either the dmesg log or journalctl.log > > > > > > > > My system is still going into paralysis mode. For example I went to > > > > edit the logs in the var/log area and vim was halted for several > > > > seconds > > > > > > An unlikely but possible culprit: DNS. Is the first server entry in > > > your /etc/resolv.conf file valid? If so, does it resolve IPv4 and IPv6 > > > queries? > > > > > > DNS resolution delays impact systems in unexpected ways. > > > > > > Like I said: unlikely, but worth checking. > > > > > > -- > > > Paul Heinlein > > > [email protected] > > > 45°22'48" N, 122°35'36" W
