LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   All Things KDE5/Plasma for Slackware Users. (https://www.linuxquestions.org/questions/slackware-14/all-things-kde5-plasma-for-slackware-users-4175670109/)

j12i 07-26-2021 10:39 AM

Quote:

Originally Posted by mlangdn (Post 6269728)
Some have non-removable batteries. Powering off does the same thing.

For all you know, it could just be going through the motions to deceive you, no?
Also: off topic.

bassmadrigal 07-26-2021 03:35 PM

Quote:

Originally Posted by j12i (Post 6269803)
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.

brianL 07-26-2021 03:40 PM

Remember your tinfoil hat & underpants.

cwizardone 07-26-2021 10:01 PM

Quote:

Originally Posted by brianL (Post 6269893)
Remember your tinfoil hat & underpants.

Here you go,a little humor on the subject,
https://www.youtube.com/watch?v=GKD_Arf94zU

USUARIONUEVO 07-27-2021 04:23 PM

Nice changelog today for solid issue...

Quote:

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.

marav 07-27-2021 04:46 PM

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

pchristy 07-28-2021 02:01 AM

Quote:

Originally Posted by USUARIONUEVO (Post 6270246)
Nice changelog today for solid issue...

Quote:

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
Link: https://invent.kde.org/frameworks/so...bfdb79e7d3d1b6
(Scroll to bottom)

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

atelszewski 07-28-2021 02:43 AM

Hi,

Quote:

Originally Posted by pchristy (Post 6270319)
Whilst this may fix the specific issue in Slackware, I feel it is still important to patch solid as well.

I support this with my many years of experience in engineering C/C++ code.

--
Best regards,
Andrzej Telszewski

LuckyCyborg 07-28-2021 02:54 AM

Quote:

Originally Posted by pchristy (Post 6270319)
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:

Link: https://invent.kde.org/frameworks/so...bfdb79e7d3d1b6
(Scroll to bottom)

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.

marav 07-28-2021 03:18 AM

Quote:

Originally Posted by LuckyCyborg (Post 6270328)
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

no crash here :-(
I really don't know why, I have neither the crashes related to Solid 5.84, nor the others that people bring up...
It's annoying

LuckyCyborg 07-28-2021 03:21 AM

Quote:

Originally Posted by marav (Post 6270333)
no crash here :-(
I really don't know why, I have neither the crashes related to Solid 5.84, nor the others that people bring up...
It's annoying

Looks like you are a lucky one... ;)

BTW, after the last updates (which applied the ZhaoLin1457's patch) you get the proper path on Doplhin?

I talk about /run/media/ path for the mounted USB drives.

marav 07-28-2021 03:29 AM

Quote:

Originally Posted by LuckyCyborg (Post 6270334)
Looks like you are a lucky one... ;)

BTW, after the last updates (which applied the ZhaoLin1457's patch) you get the proper path on Doplhin?

I talk about /run/media/ path for the mounted USB drives.

exactly

Code:

mount --bind / /mnt/tmp
it highlights that Dolphin prefers the "bind" mount to the others
as a result, when I go to the root, dolphin goes to /mnt/tmp

LuckyCyborg 07-28-2021 03:45 AM

Quote:

Originally Posted by marav (Post 6270337)
exactly

Code:

mount --bind / /mnt/tmp
it highlights that Dolphin prefers the "bind" mount to the others
as a result, when I go to the root, dolphin goes to /mnt/tmp

BTW, what kernel release you use? The stock generic 5.13.5 ?

marav 07-28-2021 04:15 AM

Quote:

Originally Posted by LuckyCyborg (Post 6270338)
BTW, what kernel release you use? The stock generic 5.13.5 ?

I have the same behaviour with the stock generic 5.13.5 as with mine (5.10.53)

pchristy 07-28-2021 04:35 AM

And I'm on 5.12.15

I don't think its kernel related...

--
Pete


All times are GMT -5. The time now is 09:45 PM.