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.
For all you know, it could just be going through the motions to deceive you, no?
Also: off topic.
Absolutely! Pretty much anything with closed source binaries could be doing the same thing. Even if you remove the power source (unplug, remove battery, etc.), they could have some power source like a capacitor hidden on the device that keeps power to certain components long after power has been removed (my sprinkler timer coming off my hose does this so I don't lose all my settings when I need to replace the batteries).
There is no way to guarantee a device isn't doing anything nefarious without having an intimate knowledge of that device and the software being used inside it (not just the OS, but the drivers and firmware). If you don't, you're accepting the risk that your device is doing things you don't intend for it to do.
I say, "ignorance is bliss" and just ignore all that risk.
Tue Jul 27 21:12:53 UTC 2021
a/sysvinit-scripts-15.0-noarch-4.txz: Rebuilt.
rc.S: Change /var/run to be a symlink to /run rather than bind mounted.
This works around an issue with solid-5.84.0. While there is a patch
available for solid, it's probably best to handle the legacy /var/run
location in the same way that most other distributions do.
Unfortunately, this change needs to be made at boot time before /var/run
would be mounted, so a reboot will be required. Make sure that the new
/etc/rc.d/rc.S.new is moved to /etc/rc.d/rc.S before rebooting.
Thanks to ZhaoLin1457.
Show the Plasma Application launcher : Meta key doesn't work anymore ...
X11 or wayland
plasma 5.22.4
EDIT :
it was only my shortcut that has gone ...
BTW, for those who don't know the trick :
If you want to have only META for the app launcher
right clic on application launcher / configuration / shortcut
==> META + F1
Tue Jul 27 21:12:53 UTC 2021
a/sysvinit-scripts-15.0-noarch-4.txz: Rebuilt.
rc.S: Change /var/run to be a symlink to /run rather than bind mounted.
This works around an issue with solid-5.84.0. While there is a patch
available for solid, it's probably best to handle the legacy /var/run
location in the same way that most other distributions do.
Unfortunately, this change needs to be made at boot time before /var/run
would be mounted, so a reboot will be required. Make sure that the new
/etc/rc.d/rc.S.new is moved to /etc/rc.d/rc.S before rebooting.
Thanks to ZhaoLin1457.
Whilst this may fix the specific issue in Slackware, I feel it is still important to patch solid as well. The developer has acknowledged that there is a bug in solid:
Quote:
Reading the libmount docs again, it indeed says that mnt_fs_get_root() can return NULL, so I've replaced strcmp with qstrcmp
There may be other - as yet undiscovered - situations which trigger this crash, so hopefully the patch for solid will also be incorporated into Slackware soon.
In other words, the rc.S patch fixes the specific, the solid patch fixes the generic.
Whilst this may fix the specific issue in Slackware, I feel it is still important to patch solid as well. The developer has acknowledged that there is a bug in solid:
There may be other - as yet undiscovered - situations which trigger this crash, so hopefully the patch for solid will also be incorporated into Slackware soon.
In other words, the rc.S patch fixes the specific, the solid patch fixes the generic.
--
Pete
I have found a crash with the unpatched solid-5.84.0 even on the latest updated -current, even the Plasma5 desktop is considerably more solid.
This command will make Dolphin or Krusader to crash, but the desktop itself will survive well, at least according with my experience:
Code:
mount --bind / /mnt/tmp
I'we used this command since long time, because on /mnt/tmp you will get a "clean" filesystem for root (without /dev, /proc, /sys and other mountpoints) which is perfect for doing full backups of root partition via RSYNC or tarballing.
I believe that this crash is reproducible, feel free to play with it.
The fix is to apply either my patch or the upstream patch for Solid.
Last edited by LuckyCyborg; 07-28-2021 at 03:15 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
