I’m with you. I’ve never really liked the look of QT, but I think I’m going to go for it anyway. It’s always felt more plasticky and artificial, compared to GTK feeling more grounded and earthy. Plus, KDE has always felt cluttered in every way they can clutter it. So I was into the boxes (I was partial to fluxbox) and XFCE back in the day. Played with Gnome 3 a bit, had a cyclical love and ultimately hate relationship with it, but got hung up on Gnome as the best option when I wanted to switch to Wayland.

I’ve been using Cosmic since January, and I like it, but I’m left wanting more out of it. I was thinking of spinning my own environment with LabWC, but… meh. It’s a lot of work, and I want something more integrated.

I’ve been using KDE in Asahi on my Macbook Air a bit, and I guess I could use it more. But I don’t really use that machine a ton, either. Mostly for it’s better speakers than my Thinkpad, and I have it connecting a VPN automatically until I can be bothered to switch from iwd/systemd to network manager on my primary.

God I wish Gnome would change it’s tune, and stop being so militantly simplistic. The idea of extensions is great, but using a rolling release distro is rough when you’re relying on a bunch of extensions to make your DE suitable. I really like their approach to UX at it’s foundation. Cosmic is showing a lot of promise, and has that configurability built in, and I do look forward to where it goes. but it’s going to have this problem where a lot of the software that looks best in it is libadwaita, which enforces drastically different UX.

Ah, now I remember why I bought the Macbook.

Evolution being just a little bit clunky is a massive improvement from the Gnome 2 and early Gnome 3 days, for what it’s worth.

Thanks, I’ll have to sit my ass at my desk so I can try it again. I wonder if there’s much delta between what you’re using and the beta I’m on from Extra. Though it does look like there are some new betas in Extra-Testing.

I’ll need to give tiling another try, I started using alpha 5 back in January and there were some pretty nasty bugs in tiling mode back then that made me think maybe a memory leak or something. After 15-20 minutes performance would get horrible until switching back to floating, though I’m fuzzy on the details.

Is there any capability to leave an open space? Honestly, I like tiling more for the orderliness above and beyond snapping than the dynamism. Aaaaaand that’s reminding me why I was looking at building out a LabWC environment, it has configurable snap zones.

I started dabbling in around 2000, getting sick of the instability of Windows, and it seeming like the next logical step of geekdom.

I tried a LOT of distros. Mandrake, Connectiva, Red Hat to Fedora Core, Slackware, Debian Woody, Crux, etc etc. I drifted in a Debian-centric circle until I finally landed on Arch. Lost my way for a bit during my IT career, supporting Windows I ended up just using that. But I’m back to Arch now as my daily, Debian for some networking projects, and a bit of Fedora from time to time when I need to spin something up quick.

Not really for the purpose of this thread, since pretty much anything can do what OP is asking, but any idea how the Juno Tab compares to the Starlabs Starlite in regards to build quality, cooling, and what not? I noticed the other day that the Starlite has been updated with an N350 CPU. Though it is up to a $765 starting price…

Once or twice a year I start thinking it would be nice to have a tablet. Then within a month I wonder wtf I want a tablet for.

Is it still relying on Halium?

Edit: It seems it does use Halium

https://liliputing.com/flx1s-is-a-new-linux-phone-thats-mostly-a-downgrade-from-the-flx1/

I think I’ll keep looking into importing a Jolla C2.

Yeah, I think that’s my backup plan is to get some powered speakers and Pi’s to run Snapcast. But it adds a lot of complexity, and more power requirements at the speaker. On the other hand, it’s more hackable than a speaker running a specific piece of software directly, without any real alternatives like I would get with a Pi. Thanks!

Oh no, I know. I’m just limited to wireless right now because I’m renting an old house with massive amounts of insulation. So I had tried to get the Sonos speakers working with a combined sink wirelessly, but it just wasn’t able to keep up, leading to intermittent interruptions to the stream. I’m going to play with that wired in a test environment at some point, but I think I’d prefer something like Snapcast over Airplay.

But once I buy a house in the coming months, I’ll do some low voltage runs to support the audio network, among other things. I figure I’ll probably have a dedicated POE switch so I don’t have to worry too much about QoS, probably Mikrotik if Ubiquiti doesn’t release some new EdgeSwitch gear.

I’m just not sure if the software is there yet, with Pipewire AES67 support. It was “new” in v1, with I think some PTP patching in the first point release. So I’m trying to see if anyone has cut their teeth on this yet, since it’s going to be pretty costly to get gear. I imagine I can just create a combined sink, but I’m not sure if PTPv2 is just automagic within the RTP configuration of Pipewire.

And potentially needing a second server for MPD/Pipewire is something I’m keeping in the back of my head. I’m hoping to run it in a container on the NAS server, probably running Debian (or maybe something more cutting edge if I’m reliant on new Pipewire releases). But RTP and PTP might need something a bit more dedicated to the task. It’s not like I’m doing broadcast or some other form of professional audio here, so I’m optimistic that a container will be fine. Just a single 16/44 FLAC decode to combined AES67 sink. And since containers use a shared kernel, I wouldn’t need to worry about the clock scheduling issues some hypervisors had with Asterisk and Free Switch in my previous life working on VOIP networks. But I’m also not planning on a ton of cores, 4-8 only in a low voltage CPU, sooooo… I dunno.

Well, right now I don’t really have a setup. I bought the Sonos speakers when I was experimenting with the Apple ecosystem a few years ago, but now that I’m fully back on Graphene/Linux they haven’t been worth the trouble. I don’t have an audio server yet, I’m just storing on my laptop and playing locally to headphones/XLR Genelecs using Quod Libet.

What I’ll end up with is probably a home built NAS running stuff like MPD and Home Assistant in containers. I’ll have either a VLAN or dedicated switch for audio.

The Genelecs I’m looking at for AES67 stuffs are the Smart IP Installation series like this 4410a. I’m pretty sure these are full audio-over-IP using AES67/Dante, and not using IP only for control. Unless Genelec documentation on these sucks. If they were to require XLR, I’d choose a different speaker that does not, or run structural audio cables to a multi-zone receiver.

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.

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.

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

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.

Interesting that it works when the VPN is connected, though. I also believe that systemd-resolved is installed on just about any system using systemd, but often isn’t enabled, without problem. Enabling it would generally involve a resolv.conf symlink and a config, so maybe that config was hijacked by Mullvad (or OP configuring Mullvad), and there’s no upstream DNS server available when the VPN isn’t connected.

I missed that it’s Linux Mint in the original post, and it looks like Mint has started using systemd-resolved. The Arch wiki might be useful to OP on how things are configured:

https://wiki.archlinux.org/title/Systemd-resolved

Ok, so something setup 127.0.0.53 as your DNS server, and isn’t removing it correctly. I think it’s safe to say it’s Mullvad, since it works using that DNS server IP when connected. Is that IP in your resolv.conf, or is resolv.conf maybe a stub, and you’re using systemd-resolved?

Ok, so does the VPN bring it’s own DNS? Some VPNs do, so it may explain why everything suddenly works fine when you connect.

When not connected to VPN, are you able to dig or nslookup internet names? Local names? A server timeout will be very different from an nxdomain or an empty SOA, in the response.

Are you able to telnet to a public web server on TCP/443?

One thought I’m having is, maybe at some point you set a static IP on your wifi interface, but screwed up the subnetting.

Have you ever messed with network manager or systemd-resolved internal settings, maybe trying to setup multicast DNS or caching?