Sync Update for Week 41, 2023
presianbg Ah, I assume you need DNSSEC support then? It's a shame that systemd-resolve doesn't have good support for it yet, that was a huge point of contention when we were discussing integrating it. systemd-resolve is a huge QOL feature for most users however which is why it won out it the end. It integrates quite seamlessly with NetworkManager which means that VPNs that push out DNS servers work pretty much as users expect them to (combined with DNS routes received when roaming between different networks). I've got a bunch of DNSSEC-related issues followed on the systemd tracker so hopefully once the issues are resolved we can enable DNSSEC again by default.
Side-note, would you be interested in becoming the maintainer for dnsscrypt-proxy? I notice it hasn't been updated in a while and usually it's best if people who are actively using a package are the ones who keep it updated.
Discord 0.0.32 cherry-picked
- Edited
In reverse order:
YES, I would like to give it a try with maintaining some packages... maybe dnscrypt-proxy and VCMI, maybe others once I get familiar with the process. (I will give it a try in the end of the month due traveling plans).
Of course DNSSEC is nice to have, but I prefer dnscrypt-proxy over systemd-resolved because of the forwarding, cloaking and filter/block capabilities (the config files are very easy to maintain and clear to read).
I didn't knew systemd-resolved is fixing the DNS path resolution via VPN, but I still prefer the "static routes", which dnscrypt-proxy is offering.
Do not get me wrong, having systemd-resolved enabled by default is 100 times better than what we had before and really appreciate it.
- Edited
Hey. How about supergfx plasmoid for KDE? 
Very useful thing. This plasmoid I see in Nobara linux
For me everything was ok, except the switch to systemd-resolved.
Not actually a problem, but since dns via systemd is new to me, I am not sure how to manage this, eg changing my primary dns.
Any suggestions, resources, docs on this ?
alexxtasi systemd-resolved integrates with NetworkManager, so it will use the DNS server(s) of the NetworkManager interfaces you have. You can manually modify those DNS servers via NetworkManager and it will automatically update the DNS servers that systemd-resolved- uses. This is best for when you may want to swap DNS servers as you activate and deactivate networks (for instance, if your device is a laptop that you move between networks or if you use VPNs and may wish to use a different DNS server when the VPN is active).
If however you would prefer to always use a particular DNS server you can specify it by by creating the file file /etc/systemd/resolved.conf.d/dns_servers.conf and putting in contents like the following
[Resolve]
DNS=192.168.35.1 fd7b:d0bd:7a6e::1
Domains=~.I'd recommend checking the Arch wiki for more complete configuration instructions.
ReillyBrogan thanks for the suggestions ... I 'll try Arch's wiki, but strange is that there is no /etc/systemd/resolved.conf.d/ directory in my system !!
~ $ ls -l /etc/systemd/resolved.conf.d/
ls: cannot access '/etc/systemd/resolved.conf.d/': No such file or directory
~ $ ls -l /etc/systemd/
total 8
drwxr-xr-x 4 root root 4096 Οκτ 19 11:41 system
drwxr-xr-x 2 root root 4096 Μαΐ 10 20:11 user(Solus GNOME here with the latest update)
alexxtasi thanks for the suggestions ... I 'll try Arch's wiki, but strange is that there is no /etc/systemd/resolved.conf.d/ directory in my system !!
That's because Solus is (aiming to be) stateless (https://github.com/clearlinux/clear-linux-documentation/blob/master/source/guides/clear/stateless.rst) [there will be a page on that topic on our own Help Center soon]
...so is it safe to just create the /etc/systemd/resolved.conf.d/ directory and in there create dns_servers.conf file as suggested ?
forgive my ignorance on whether or not create system dirs...
elusian Ok, so I have read that there is an issue with conky: (segfault causes it to crash on startup).
I also encounter very very weird behaviour under GNOME X11 when running conky. Just wanna be sure if it's like the same thing you have described, or a whole other issue:
So basically I had only three programs running: chrome in multiple windows, gnome-terminal in multiple windows and rednotebook. Then I ran conky and could observe extremely strange behaviour:
normally, the conky "window" only gets displayed when hiding all windows, e.g. on an empty workspace.
But when switching workspaces after running conky, the conky "window" or how you call it got displayed on top of the running application.
I observed several scenarios:
a)by then pressing super+D, which should hide all windows, only the conky window got hidden and back on top of all windows by pressing super+D again.
b) another time, I couldn't switch between windows on the same worksapce. Either by pressing alt+tab and choosing another program or by opening overview and choosing another window on the same workspace did't show any effect. Didn't switch the active window.
c) I was on a workspace where only a gnome-terminal was running. But behind the gnome-terminal was the chrome-window shown, which was running on another worskace! By opening overview, I could see that there only was the terminal running on this workspace, but after closing overview, there was the terminal window, and behind it the chrome window. Though I did't test if I could interact with this background chrome window.
Even after killing conky, the chrome window from another workspace was shown behind the terminal window. Only after I switched to another workspace and the back, the chrome window from another workspace was gon and only the terminal window left.
Okay, I don't know if the strange behaviour I have described inthe previous post was caused by conky or something else. Long after I have killed conky, GNOME continued to behave strangely: When pressing super+end for switching to the last = empty workspace, it switched to the last = empty workspace, but again displayed a window from another workspace in the background, like a wallpaper. Couldn't interact with it.
I then restartet GNOME shell with alt+F2, r, enter. GNOME stopped acting weird. Even after starting conky then.