EbonJaeger I tried a new thing with spoiler tags, but adding them is a pain because they have to be in just the right place. Still didn't quite get it right. Hrm...

It's fine without spoilers! I read everything anyway! 😛

    ReillyBrogan brent Specifically it now uses the system versions of libaom, libdav1d, libvpx, libwebp, and libwebpdemux.

    Oh, wait, does that imply that these new libs uses joey's new glibc hwcaps work? I.e., they will support AVX2 and whatnot if the CPU supports it and mesa/nvidia hwdecode of the GPU supports it?

        With the new update conky seems to be segfaulting inside libcairo

          EbonJaeger
          I Love this presentation.
          Would be cool if the contributor name could be clickable or we just over mouse pointer on it and see avatar and info about the person who worked to make us all proud and cool!
          Good job Y'all!

            ermo Yes, if they're built with that option. Some of the referenced libs are.

              Hi,

              Nice, having such informative posts is really awesome.
              Just an idea: bring them to the main website as a regular blog post as it was used to be:
              https://getsol.us/2017/05/08/this-week-in-solus-install-44/
              and link the discussion here.

              Not every newcomer is checking the forums (not sure about that), but everyone considering switching / trying Solus will take a look at the main website / blog. Having more posts there is proving the project is VERY VERY active, which will lead to more users (again not sure about this statement, just thinking aloud).

              PS: for those of us using dnscrypt and pi-holes at home, what would be the best way to disable the systemd-resolved ? I tried to disable and mask the service, but something keeps removing my custom /etc/resolv.conf ?
              I really appreciate having one more option to choose from, systemd-resolved is not my thing.

              Cheers,
              PY

                presianbg

                sudo mkdir -p /etc/tmpfiles.d/
sudo ln -sv /dev/null /etc/tmpfiles.d/systemd-resolve.conf

                This will disable tmpfilesd from re-creating the /etc/resolve symlink on boot. Although, why not just configure systemd-resolve to use your pi-hole as the DNS server? That would work just as well.

                    ReillyBrogan

                    Thanks, I will try that.
                    I would like to use the dnscrypt-proxy as my local resolver. (for many reasons and functionalities, which are not covered by systemd-resolved).

                    Cheers,
                    PY

                        olivir

                        The segfault is only visible if you open conky in the debugger, but yes, the visible symptom is conky not opening (because the segfault causes it to crash on startup).

                            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

                                ReillyBrogan

                                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.

                                  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)