SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thanks for confirming. It should be noted that the font changes affect only the UI of applications; Firefox, for example, display all fonts in web pages correctly.
In my case the fonts cannot "grow" on me since they are a variant of Courier. Not very ugly in itself but very inadequate for an UI/UX font.
Yes that's what I see too, just the applications fonts. I kind of like the change, sort of...
Nah it's quite ugly. It should be fixed. Reverted to previous version in the while.
Actually, I am wondering if it is a kde issue only. I noticed that the font that kde was using in my settings was "Noto Sans [Goog]". However, if I try to set the fonts again, it is called "Noto Sans" without the "[Goog]" bit. Resetting all the kde fonts to "Noto Sans" and restarting the GTK apps fixes the problem for me on two different machines.
I am not sure what prompted the change of names but a lot have changed recently, including fontconfig and GTK3. It could be that GTK3 is quite strict about font names whereas qt5 seems to happily use "Noto Sans" when asking for "Noto Sans [Goog]".
I realize that Pat bumped XFCE to 4.14 finally, but I still hope however that XFCE 4.16 comes out on time to be included. Right now it is pre2 release.
I'm puzzled why pat would put in 4.14 if he was thinking about upgrading in the end to 4.16. My guess is that he wants to avoid 4.16 because of the controversial CSD that 4.16 is enforcing and avoid another heated debate in the slackware community.
I'm puzzled why pat would put in 4.14 if he was thinking about upgrading in the end to 4.16. My guess is that he wants to avoid 4.16 because of the controversial CSD that 4.16 is enforcing and avoid another heated debate in the slackware community.
It could've been getting the prep work done, because the 4.12 to 4.14 jump was a port to a new toolkit (GTK3) and possibly required other under-the-hood changes. 4.16 *might* be a more minor update as far as dependencies and the base system as it is starting to add features once the port to GTK3 was done (I say *might* because I have no idea for sure).
Actually, I am wondering if it is a kde issue only. I noticed that the font that kde was using in my settings was "Noto Sans [Goog]". However, if I try to set the fonts again, it is called "Noto Sans" without the "[Goog]" bit. Resetting all the kde fonts to "Noto Sans" and restarting the GTK apps fixes the problem for me on two different machines.
I am not sure what prompted the change of names but a lot have changed recently, including fontconfig and GTK3. It could be that GTK3 is quite strict about font names whereas qt5 seems to happily use "Noto Sans" when asking for "Noto Sans [Goog]".
I was playing around with this. I set fonts to the default in System Settings, Fonts, Fonts on reload of GTK apps fonts are back to the way there were before. Or at least not the fonts being use previously. That Noto Sans [Goog] has been there for a while. I noticed it before the fontconfig version upgrade.
Hey pat. You really should have mwm listed as a window manager in xwmconfig if one has motif installed. I didn't know for the longest time this hidden wm was available until I read about it. This wm is just as usable as twm and should be listed rather than hidden away.
I will take a chance by adding my opinion here regarding the inclusion (or not) of XFCE 4.16:
Since we (as the community) are preparing for the 15.0 release, historically the X.0 releases being "game changers" and "new bringers", I see no good reason for Pat to skim on shipping the latest and greatest, and the 4.16 certainly seems to be past the "troubled waters" and brings even more of the "dreaded GTK-3" to bear?
Only good reason to shy away from 4.16 would be if 15.0 is so close (biting tongue & crossing fingers) that we don't have time to wait out for the 4.16.z release to become stable enough
x/fontconfig-2.13.92-x86_64-1.txz: Upgraded.
I'm pretty sure there was a good reason to switch to 2.13.92 on the devel
release path, but I'm not sure the same can be said about 2.13.93. We'll
stick with this one for now until there's a stable release or another good
reason to bump it.
Thank your for this! fontconfig-2.13.93 messed up with style default fonts under Fluxbox (fonts under menus have changed from lucida-sans, the default, to something that remembers me of times-news-roman - not sure of it, but menus became ugly). Back to normal.
There is a bug with mwm. With the xwmconfig script for current, 14.2, and others since 2012 it is listed under skel for xwmconfig. But it never shows up for me either in 14.2 or current. This needs to be fixed because mwm is supposed to be showing up in xwmconfig.
Edit: If I could clarify further what I think is wrong pat, motif doesn't have the xinitrc patch for the slackbuild while xfce,windowmaker,fvwm, and fluxbox for example have it. All you need to do pat is just make sure that the xinitrc patch is made for mwm and xwmconfig will find it.
The latest Gimp can be built against libheif and friends to enable support for avif import and export. I am about to compile it all together myself (most required build scripts are available on SBo) but it would be nice to have support for avif in Gimp 'out of the box'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.