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.
Change log:
## Highlights
- Fix a potential race/crash.
- Fix some problems with negotiation of large integers and floats.
- Fix JACK sysex MIDI event handling.
- Some more smaller fixes and improvements.
## PipeWire
- Fix a potential race when adding/removing a port to be scheduled.
## Modules
- Fix FFADO default device handling. (#4023)
## SPA
- Fix in integer overflow and float/double compare in POD.
In my system, the output of the 'locale' command showed that the LC_ALL environment variable is not set to anything.
This specifically gives some trouble with Qt6, Plasma 6, and even some Java applications when rendering Unicode filenames.
I had the LC_ALL env variable set to eng_US.UTF-8 and made that permanent by including it in /etc/profile.d/lang.sh. I don't know if that's the proper place to do it, but it worked until recently there was an update that overwrote that file, my locale went to the old setting and the weird behavior in Qt6 started again.
Thus I request that the LC_ALL be set to the value en_US.UTF-8 by default, if possible. Thanks in advance!
In my system, the output of the 'locale' command showed that the LC_ALL environment variable is not set to anything.
This specifically gives some trouble with Qt6, Plasma 6, and even some Java applications when rendering Unicode filenames.
I had the LC_ALL env variable set to eng_US.UTF-8 and made that permanent by including it in /etc/profile.d/lang.sh. I don't know if that's the proper place to do it, but it worked until recently there was an update that overwrote that file, my locale went to the old setting and the weird behavior in Qt6 started again.
Thus I request that the LC_ALL be set to the value en_US.UTF-8 by default, if possible. Thanks in advance!
If something is demanding that LC_ALL be set to anything, that's a bug. Otherwise, why have any variable other than LC_ALL?
Qt should (according to their documentation) look at LANG if LC_ALL isn't set.
In our case, if we set LC_ALL to anything then we'll lose LC_COLLATE=C and everything will start sorting differently. I'd personally find this annoying. It might (would) also break a lot of scripts that depend on a consistent sort order.
This release contains no user-visible changes. It just fixes the test
suite to have a better infrastructure for fonts, and in particular
fixes a right-to-left test case that started failing with Pango 1.52.1.
If something is demanding that LC_ALL be set to anything, that's a bug. Otherwise, why have any variable other than LC_ALL?
Qt should (according to their documentation) look at LANG if LC_ALL isn't set.
In our case, if we set LC_ALL to anything then we'll lose LC_COLLATE=C and everything will start sorting differently. I'd personally find this annoying. It might (would) also break a lot of scripts that depend on a consistent sort order.
Thanks for the explanation Pat. Meanwhile, I'm holding off the upgrade to 6.7 since I need a recompile of the Plasma 6 stack. Will test again after the upgrade to see whether this bug is still present.
I built it on & installed it on slackware64-current.
Ran several 32bit windows programs.
Ran several 64bit windows programs.
Even installed a really old copy of Mozilla v1.0 32bit and ran it just fine.
(simply could not access HTTPS sites due to such an old Mozilla not being able to validate the certificate)
Can we have zram as a service from the box mister BDFL ? ...
I am most certain there might be other use cases in the wild...
Recently i installed 15.0 on a box, kept the huge kernel, and while migrating/updating + various other parallel task i had hangs/delays until
i switched to kernel-generic+zram-swap(a swapfile would have solved it also of course, but i don't need/want one).
Zram would make it possible to guarantee that there is always some swap space.
Even if it's only a few mb it can prevent weird behavior in
some scenarios, and a few mb stolen from ram won't hurt any device.
The huge kernel has zram configured as module, if this is changed to 'y' zram could be used from the
very beginning of an installation. The installer swap-menu could be extended to provide the option to
stay on zram(and set a size), or add conventional swap, etc.
I suggest that srain 1.7.0 be added to -current as hexchat is being discontinued.[/URL]
The problem is srain cloned horrible Google interface meant for pads/tablets, which Google doesn't know about making usable/faster desktop interfaces. If anything, KVIRC or some classic-style IRC client with 'File Edit View Help' (easier/faster) etc., style menus should replace HexChat, when it needs to be replaced, which isn't anytime soon. Slackware still has XMMS when virtually all other GNU/Linux moved to XMMS2 maybe over a decade ago.
The huge kernel has zram configured as module, if this is changed to 'y' zram could be used from the
very beginning of an installation. The installer swap-menu could be extended to provide the option to
stay on zram(and set a size), or add conventional swap, etc.
I don't think it's a good idea to build in such modules that someone might use unless they are needed to boot. You need several commands to set up the zram swap, so why wouldn't you run 'modprobe zram', too?
The 15.0 installer initrd image does not include the zram module, but it could be included. In case you have large jobs to do when running the installer (?).
Slackware 8.1, file FAQ.TXT: "If you've got 4 MB and you're getting 'virtual memory exceeded in new' warnings, make sure you set up and activate a swap partition before running setup.". Note: it said 4 MB, not 4 GB... I don't think most users need swap nowadays when running the install disk.
Last edited by Petri Kaukasoina; 05-25-2024 at 02:18 AM.
I don't think it's a good idea to build in such modules that someone might use unless they are needed to boot. You need several commands to set up the zram swap, so why wouldn't you run 'modprobe zram', too?
The 15.0 installer initrd image does not include the zram module, but it could be included. In case you have large jobs to do when running the installer (?).
zram as module in the initrd image would also work. It's not about large jobs while running the installer, but(if zram on slackware would be officially supported like conventional swap) to have the option to setup zram as swap in the installer-menu.
Also, it's not necessarily about big swap space, but to have it at all.
E.g. have a minimum swap as default, this could be done without drawback(i think) with zram.
Interesting read: https://linuxblog.io/linux-performan...ap-part2-zram/
zram as module in the initrd image would also work. It's not about large jobs while running the installer, but(if zram on slackware would be officially supported like conventional swap) to have the option to setup zram as swap in the installer-menu.
Also, it's not necessarily about big swap space, but to have it at all.
E.g. have a minimum swap as default, this could be done without drawback(i think) with zram.
Interesting read: https://linuxblog.io/linux-performan...ap-part2-zram/
I don't think you need zram in the installer initrd image to have the option to setup zram as swap in the installer menu. It would be enough for the installer to configure the installed system.
FWIW the installer of Slint64-15.0 enable swap in zram early in its initramfs itself, then set it in the installed system in "auto" partitioning mode (btrfs with subvolumes for /home / and swap). Here and now:
Code:
didier[~]$ LANG=C free -th
total used free shared buff/cache available
Mem: 15Gi 2.1Gi 10Gi 807Mi 2.9Gi 12Gi
Swap: 31Gi 0B 31Gi
Total: 47Gi 2.1Gi 42Gi
didier[~]$ swapon
NAME TYPE SIZE USED PRIO
/swap/swapfile file 1024M 0B 5
/dev/zram1 partition 31G 0B 32567
didier[~]$ zramctl
NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram1 zstd 31G 4K 59B 20K 8 [SWAP]
# quote of my /etc/fstab below
# Initially /dev/sda5
UUID=c275f3fa-55e8-4357-90d2-2b757bfd0118 / btrfs subvol=@,compress=zstd:3,discard=async,noatime 0 0
# Initially /dev/sda5
UUID=c275f3fa-55e8-4357-90d2-2b757bfd0118 /home btrfs subvol=@home,compress=zstd:3,discard=async,noatime 0 0
# Initially /dev/sda5
UUID=c275f3fa-55e8-4357-90d2-2b757bfd0118 /swap btrfs subvol=@swap,compress=zstd:3,discard=async,noatime 0 0
/swap/swapfile none swap pri=5 0 0
I also set a swapfile, the idea beeing that if used the user could realize that the system is slowing down before going AOM, but probably not very useful.
Last edited by Didier Spaier; 05-25-2024 at 02:35 PM.
Reason: s/EOM/AOM/ (out of memory)
glib2-2.80.2-x86_64-1 are causing xfce mousepad to segmentation fault
Xfce Mousepad app causes segmentation fault when running, and this happens when appmenu-gtk-module is installed (I'm using vala-panel-appmenu). I searched the internet and discovered that the bug was fixed, according to the links below. Please correct this in Slackware. Thanks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
? ...
