jcarax

Yup, no way I'm enabling play services and installing Messages just to use RCS. I mostly use Signal, anyway.

What we should really be fighting for is more federation between messaging platforms.

It will probably have an SD card slot like the FP5.

Now if only I could get a meaningful reply to a bug preventing complete account deletion, either on github or from support. It seems they modeled their support structure on Google's.

Well, they probably want a leaner version for lower end phones anyway, along the lines of the Go versions of many of their apps. Luckily I won't have to worry about this shit running Graphene, with no intention of running an LLM, so 8GB would be fine if I had any need to move on from my Pixel 8 prematurely.

Hey, maybe it'll cause some fairly quick, large discounts. My Pixel 5 backup with a rather shattered screen could use a replacement.

I was pleasantly surprised with Evolution the last time I tried to use Gnome, it used to be a buggy, bloated mess. But alas, I can't manage to use Gnome for more than a release or two. Now I'm looking for a decent Wayland native alternative to Thunderbird, but it just doesn't exist without DE bloat at this point. Maybe someone will build a modern replacement for Sylpheed/Claws.

Ok, so the resolv.conf is being used to put systemd-resolved in the forwarding path, with it listening on 127.0.0.53. That's how Mint does things, so don't touch that file.

Your resolved.conf has no DNS servers or fallback DNS servers configured, so it should just use the DNS servers handed out by DHCP. Either your DHCP servers isn't handing out a DNS server (unlikely, since other machines work), NetworkManager was configured to not use DHCP DNS servers, or you're hitting some bug causing the same. I suspect you may have configured NetworkManager for this, maybe it was overriding the VPN DNS. Or maybe you accidentally set the NetworkManager DNS backend to dnsmasq, when it should be systemd-resolved in Mint.

You could try uncommenting that FallbackDNS line and adding a couple space separated DNS servers, maybe your router IP. Mine looks like this:

#DNS= FallbackDNS=1.1.1.1 1.0.0.1 #Domains=

That will hopefully allow VPN DNS to work when it's connected, and fall back to other DNS servers when not. If not, we could try taking a look at NetworkManager configs. It's been a bit, I use systemd-networkd now, but I could spin up a VM.

I think they care about their customers just about as much as they care about making money, and aside from GOG, the competition simply does not. It's a pretty good demonstration to how capitalism has failed us, to be honest, because any of those competitors would have been able to compete if they hadn't treated their customers like shit.

If you wanted to, you could post your /etc/resolv.conf and /etc/systemd/resolved.conf here. I don't know if there might be a configuration directory option for systemd-resolved, so keep an eye out for a potential directory like /etc/systemd/resolved.d that might have the configs instead.

Uhm... interesting hyperbole during a time where America is literally facing down a fascist dictator.

Did you ever come back to this and figure it out? My curiosity is killing me :)

And I think it's probably not in resolv.conf, that's a stub that kind of redirects things to systemd-resolved. So I think it's in the forwarder config of that.

Be careful, I was just looking over the Arch docs I linked you to, and I think the configs have changed substantially in the last few months. There's a good chance that the configs in Mint look substantially different.

Agreed, though I don't think they disabled systemd-resolved, because it still works using 127.0.0.53 when they're connected to the VPN. So the daemon must be running, unless Mullvad itself has a DNS forwarder using the same loopback. I suspect they either hard coded some upstream DNS server for Mullvad, because Mullvad might not have supported systemd-resolved yet. Or maybe they set a permission on the configs, and something changed with the user context of Mullvad processes.