I'm seeing some weird kerning on some typefaces on some websites in Firefox today, after updating yesterday. Example:

"No ti fica tions" is especially bad... I guess "fi" and "ti" form ligatures but it doesn't explain some of the other stuff.

ReillyBrogan Ok
I use shotcut it can use Quicksync will check some others out and like stated handbrake can use it.

    I experience the same font problems as @synth-ruiner , not only on firefox, but brave as well. First time I have a complaint since I installed solus in 2016 ! keep up the good work.

      Sync went great, i must again say how happy I am that i found this distro.

      170 packages updated on Budgie. All uneventful = great work by the Solus team. 🙏

      I had the font kerning issues too during testing, but they went away after a few reboots.

        It was so fast that I was surprised it was already done! ^^

        ReillyBrogan second reboot did not solve the problem here, sadly. The old "have you tried to turn it off and on again" does not seem to work here 🙂

          Try this to see if it fixes it:

          cd /usr/share/fonts/conf.d/
sudo rm 10-hinting-full.conf
sudo ln -srv /usr/share/fontconfig/conf.avail/10-hinting-slight.conf 10-hinting-slight.conf
sudo fc-cache -f -s

          Then reboot.

            No issues here, guess I did not notice the font kerning issue, I don't know if it was fixed or never had it. Update went smooth, I really like GNOME 46, been back to Solus since a couple of weeks and some things are working better than they did on Fedora so I guess I'm staying.

              juampiursic Solus is certainly a good place to stay haha. Though I am curious about what things work better on here compared to Fedora in your experience.

                Staudey

                Just to be clear, since nobody mentioned it in this thread, the solution is to add require 'cairo_xlib' on top of the lua file (together with require 'cairo')

                    On the other hand, there are still problems with conky: the refresh are not regular, it seems to freeze every few seconds, and according to the system monitor, while it's frozen it's consuming a full core of CPU.
                    It's not a particular measurement that is doing this, since I split my widgets by category and all of them do it (at the same time), so it might be the rendering.

                    Edit: I guess it might be this?

                      • [deleted]

                      • Post #32

                      EbonJaeger

                      Our entire nftables stack has been updated and rebuilt this cycle. With this update, we now use nftables by default instead of the legacy xtables. This update also removes ebtables and libnetfilter_acct. Users of Docker, lxd, libvirtd and firewalld shouldn't have to do anything in response to the switch to nftables by default. Users doing things more manually may want to make a note of this, however. If you use containers or VMs, please reboot after updating, as interesting things can happen when the kernel mixes xtables and nftables firewall rules.

                      Does this change affect users/usage of ufw?