Puppy Linux Discussion Forum

geo_c wrote: Wed Aug 21, 2024 5:30 pm

KDE is pretty cool, but it's a memory hog. ...

Why is this a concern if it does not impact performance?

I've, for 5 decades, know that how a system manages workload demands is much much more important than idle storage use.

But you may know something that is helpful in this regard.

Curious

Clarity wrote: Wed Aug 21, 2024 11:12 pm

geo_c wrote: Wed Aug 21, 2024 5:30 pm

KDE is pretty cool, but it's a memory hog. ...

Why is this a concern if it does not impact performance?

I've, for 5 decades, know that how a system manages workload demands is much much more important than idle storage use.

But you may know something that is helpful in this regard.

Curious

Well it's pretty simple. If I'm working on one my machines with 8GB of ram, and the operating system is using 1 or 2 GB of it, then when I try and run an Ardour project with 16 tracks of audio each with 4 plugins, the extra gig or two of ram expended on sliding windows and thumbnail popups is simply crowding out the application from available memory. This is crucial when trying to mix a large audio project, not to mention video. Especially when the load gets critical and you try to shut some things off as so not to crash the system. You start clicking around and the animations take even more memory, and bam, the program bombs out.

I definitely say KLV-KDE runs fast, it opens applications fast and generally is snappy, but it's not fast like Spectr, or even F96, and now KLV-boxer with JWM. They are like instantaneously fast. Spectr being the best. In that particular desktop there is simply no compositing, no animation, no window dressing even, no title bars, no buttons on the windows. You have to type meta+q to close a program window.

But it's apples and potatoes really.

I'm impressed that a graphical DE like KDE runs as well as it does, at least Sofiya's KLV version runs impressively well, and being Void underneath might have something to do with it's great performance.. It's certainly better than Windows and Mac, and it looks as good or better, certainly more customizable in the linux tradition. Wayland is nice, and KDE has so much development and user-friendly configurability that I wouldn't hesitate for a moment to recommend it to people.

So just for reasons stated above, when I'm really working and doing audio, I prioritize stability, predictability, simplicity, speed, and memory usage over eye candy and theme tools. User friendly is nice, it's great to pop open the system settings and get downloads of KDE themes. That's sweet for most people, myself included.

I will say that at least 4 or 5 applications bombed out on me for no apparent reason on Plasma. And from time time, windows kind of stick, or don't function quite 100%. They might refuse to resize. Usually this settles out, but it is present and totally in line with a heavy duty graphical interface, that being certain malfunctions and glitches. are likely to occur, maybe no fault of the desktop, but more with the application implementation trying to keep up with the latest developments.

EDIT: Just to follow up, I have no idea how memory allocation and cpu threading works. I can say that at present I only have Xfe, a gtkdialog window, and LibreWolf opened to the forum (a low resource web page) and my ram usage according to htop is 2.89 GB. It doesn't start there when I first open the browser, but it kind of builds up over time, and I'm inclined to think it has to do with some kind of caching that either the browser or wayland is doing. It's beyond my paygrade, but that was kind of thing behind my "memory hog" comment.

I'm spoiled with the fine tuned low ram usage of puppies I suppose. This kind of ram usage is probably considered quite low by most standards.

geo_c wrote: Wed Aug 21, 2024 9:39 pm

The way I understand this KLV to be setup, User spot has administrator privileges, so I simply run OctoXbps as spot user to install, which installs without the use of sudo. Maybe OctoXbps is setup to run as superuser automatically, but it works and applications are available to both root and spot, but the configs are written to spot.

If apps are also available to root as well as spot, then I would think OctoXbps has root privileges.
Did you build from the plug file or download the ISO?
(perhaps Sofia can explain what method she used to grant either spot or octoxbps) admin privileges.

williwaw wrote: Thu Aug 22, 2024 1:51 am

If apps are also available to root as well as spot, then I would think OctoXbps has root privileges.
Did you build from the plug file or download the ISO?
(perhaps Sofia can explain what method she used to grant either spot or octoxbps) admin privileges.

I downloaded the iso. I think the script was at the first post of this topic though.

Checked, yes the build script is there. I have that also, I just took the easy way though.

geo_c wrote: Thu Aug 22, 2024 2:22 am

Checked, yes the build script is there. I have that also, I just took the easy way though.

the plug installs octoxbps, but I did not see any special configurations in the initial build for octoxbps

xbps-install -y git wget curl p7zip ark unzip tar dtrx xinit mpv smplayer vte3 dialog octoxbps

for spot tho, added to wheel group and given nopassword sudo rights

# Create user spot and put in wheel group (and more) and give wheel group nopasswd sudo rights
echo '%wheel ALL=(ALL) NOPASSWD: ALL' | (VISUAL="tee -a" visudo) # wheel group added to sudo no password required
useradd -m -G audio,video,wheel,storage -s /bin/bash spot
printf "spot\nspot" | passwd spot >/dev/null 2>&1 # Quietly set default spot passwd to "spot"

why include sudo if not used with a password?

williwaw wrote: Thu Aug 22, 2024 3:24 am

for spot tho, added to wheel group and given nopassword sudo rights

Code: Select all

# Create user spot and put in wheel group (and more) and give wheel group nopasswd sudo rights
echo '%wheel ALL=(ALL) NOPASSWD: ALL' | (VISUAL="tee -a" visudo) # wheel group added to sudo no password required
useradd -m -G audio,video,wheel,storage -s /bin/bash spot
printf "spot\nspot" | passwd spot >/dev/null 2>&1 # Quietly set default spot passwd to "spot"

why include sudo if not used with a password?

I think, though not certain, that this allows everything that might not be designed to run as root to function in a multi user environment as designed, but gives the flexibility and convenience of not having to type a password every time for accessing the root filesystem. So I think it's an easier configuration all around, and the build script could probably easily be tweaked to use a password for sudo if desired.

I would think that it could be setup with additional users and passwords added. In other words it's basically set up as a regular multi-user linux, no? Just that no password is required to access root using sudo.

geo_c wrote: Thu Aug 22, 2024 4:03 am

allows everything that might not be designed to run as root to function in a multi user environment as designed, but gives the flexibility and convenience of not having to type a password every time.......
......I would think that it could be setup with additional users and passwords added. In other words it's basically set up as a regular multi-user linux, no? Just that no password is required to access root using sudo.

might be easiest this way with the prevelence of electron apps, and the scary admonitions about the dangers of running as root that might keep some people away.

In other words it's basically set up as a regular multi-user Linux, no? Just that no password is required to access root using sudo.

This is it in a nutshell. We set up the "spot" user to be almost as special as "root" in a real multi-user system. Any any additional user added to the system would not be in the wheel group and would require a sudo password. But "spot" in KLV-Hyprland-CE and KLV-plasma-KDE-CE is designed to be the default user which brings it more in line with the main stream Linux distro's, but still is easy to do those administrative tasks and system level configurations one is faced with on a regular basis but not running as the "root" user

KLV-Boxer uses the same setup with "spot" in the wheel group as the other KLV's but is designed to be operated as root as well as spot and can be used as a totally new user at any time.

In KLV's "spot" is a special user that is like the 1st Officer on a ship.......second in command but not quite the Captain.

I'm not sure how I did this.

I somehow have the Konsole terminal automatically opening htop everytime it opens. If I open a new tab it also opens with htop, so now I have two instances of htop on tabs in the window. If I close htop, the tab or window simply closes and I can't get a fresh prompt in the window or tab to type commands.

I can't find any settings that would cause this in the Konsole settings and profiles.

I don't think I changed any Konsle config files manually. But it maybe it's zsh doing this?

If I split the Konsole window then I get a fresh zsh prompt. But I still have htop running in the one of the split windows.

My mind is boggled.

geo_c wrote: Thu Aug 22, 2024 1:50 pm

I'm not sure how I did this.

Nevermind, I found it in the Konsole settings. I somehow had it set to open with the command /usr/bin/htop

rockedge wrote: Thu Aug 22, 2024 12:08 pm

In other words it's basically set up as a regular multi-user Linux, no? Just that no password is required to access root using sudo.

This is it in a nutshell.

so one can just as well use su or su - when running a terminal as spot and doing root stuff?
are there applications that need passwordless sudo run in the background?

so one can just as well use su or su - when running a terminal as spot and doing root stuff?

Yes.

are there applications that need passwordless sudo run in the background?

only in KLV-Airedale and KLV-Boxer does the OctoXBPS update notifier which runs as the spot user can be enabled to start during the system boot. It can be started with sudo -u spot or run-as-spot.

KLV-plasma-KDE-CE is running as the true spot user at boot so this variant does not run passwordless sudo in the background.

KLV-plasma-KDE-CE

4 desktops + cube included

Mod + W
Mod + G
Mod + C

KLV-plasma-KDE-CE

KLV-plasma-KDE-CE
https://github.com/sofijacom/KLV-plasma ... a-city.jpg

@Sofiya

Nice! I like the bigger panel (tray). Very cool background.

rockedge wrote: Mon Sep 16, 2024 8:28 pm

@Sofiya

Nice! I like the bigger panel (tray). Very cool background.

https://github.com/sofijacom/KLV-plasma ... a-city.jpg

KDE v6.6 is out with Cross Desktop Thumbnails +

FYI

Yazi - Blazing Fast Terminal File Manager

Yazi - Blazing Fast Terminal File Manager

• To use Yazi, you must have the following prerequisites installed:
  ----------------------------------------------------------------------------------------------
  file - (for file type detection)
  Yazi can be optionally extended with other command line tools to enable additional features.
  ----------------------------------------------------------------------------------------------
  nerd-fonts-symbols-ttf - (recommended)
  ffmpegthumbnailer - (for video thumbnails)
  7zip , p7zip - (for archive extraction and preview)
  jq - (for JSON preview)
  poppler - (for PDF preview)
  fd - (for file searching)
  rg - "ripgrep" (for file content searching)
  fzf - (for quick file subtree navigation)
  zoxide - (for historical directories navigation)
  ImageMagick - (for SVG, Font, HEIC, and JPEG XL preview)
  xclip / wl-clipboard / xsel (for system clipboard support)

--------------------------------------------------------------------------------------------
Added more to the config for " size_and_mtime "

yazi.toml

# ~/.config/yazi/yazi.toml
[manager]
linemode = "size_and_mtime"

init.lua

-- ~/.config/yazi/init.lua
function Linemode:size_and_mtime()
	local time = math.floor(self._file.cha.modified or 0)
	if time == 0 then
		time = ""
	elseif os.date("%Y", time) == os.date("%Y") then
		time = os.date("%b %d %H:%M", time)
	else
		time = os.date("%b %d  %Y", time)
	end

	local size = self._file:size()
	return ui.Line(string.format("%s %s", size and ya.readable_size(size) or "-", time))
end

in /home/spot/.config/yazi ---- repackaged

@Sofiya :-

Very neat distro, Sofiya. This is some seriously good work. I like it.

Well done!

Mike.

mikewalsh wrote: Wed Oct 02, 2024 9:03 am

@Sofiya :-

Very neat distro, Sofiya. This is some seriously good work. I like it.

Well done!

Mike.

Yes, it's an extremely solid and versatile KDE-Plasma OS. Versatile in the user setup, being setup to run-as-spot with administrator privileges, allowing for fairly easy tweaking of the root configurations, while still being a secure non-run-as-root OS.

I have a fully loaded pipewire-jack-app install of it on all my machines which runs audio and video apps to their full capabilities using wayland/pipewire.

I'll be honest, KDE isn't my favorite desktop, just a bit too busy for my style, and I found myself dumbing down the animations and so forth, but the KDE tools are very throrough and intuitive, and I would recommend this distro for any one coming from a mainstream Linux, Win, Mac background who would want to see mature gui tools and desktop/theme capabilities.

It's smooth, fast, and stable. And of course @Sofiya has it looking polished and clean.

And I'll add, I'm a big fan of Void's rolling release, conservative yet up-to-date package management. Their updates almost never break anything.

Since the release of KLV_KDE CE I had previously ran the the build script and used the new 07rootfs in my install. Yesterday, I decided to change the installation to a Pseudo Full Install. Renaming the unsquashed 07rootfs to upper_changes. Following the initial set up I created a new squashfs of the upper_changes as backup.

I have just done the first full update of the system downloading about 600 MB of updates. Update went smoothly, the system is running well following the update. After reboot saving changes, I have created a new backup squashfs of the upper_changes.

Thanks @wiak, @Sofiya and all involved with Kennel Linux.

Hello @Sofiya

This distro is fabulous, as others are also sharing. I have couple bits of info which you might find useful for members.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
First, "I think" this distro should move from 'Developer Work' sub-area to its own subarea, as I feel this distro will be long-term in the KL area with followers who want the wonderful desktop it offers and the baked apps that it brings.

I have tested this distro versus the Neon distro. This KL distro matches in every way the Neon distro provisions. AND IT IS STABLE!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Second, here is a video from yesterday high-lighting the refinements that the developers of KDE v6.2 gives that I'm sure you would want to review.

Since this appears to be the last KDE update for the year, would a newer ISO be in the works?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This distro is so well polished its beyond compare for a unique category in the forum! Your venture into this has turned out a GREAT distro. I thank you for ALL of this work's effort you have given us members. And thank @wiak and ALL of the KL developers ALSO whose work precedes; that provides some foundation to this distro category.

AGAIN, thanks and congratulations of this gift from you, to us forum members.

Yes, great distro, but it isn't under any 'developer work sub-area', it is under KLA releases. We have so many individual different KL releases we simply dont have forum space to give each a totally separate area.

But there are two big issues about exactly this matter. Big issue IMO is that most KL devs release new versions as brand new thread. For example, there are now tons of different KLV-Airedale threads and similarly KLA Hyperland. Result is that it is almost impossible to identify current release with certainty, and such a waste of forum space.

My opinion is should be one thread per distro type only and first post of that thread should be edited to point to newest release each time new release occurs. Also moderators/!admins need to be informed and instructed to pin new release threads so all are available at top of their relevant KL forum area (for this case that would be under the KLA area).

What do others feel about this.

This pic illustrates what I was asking.

.
This would mean a dedicated sub-area for KL-KDEs similar and consistent with the KL area's current layout. Thus not a change to KL area, merely moving KDE from Developer Work subarea.

Ah ok... I didn't pick up it was in some dev area sorry

Also, it is a klv not a kla; my brain packed in a bit today

Termv

A terminal iptv player written in bash

kio-admin-24.08.2_1.x86_64.xbps -- update

kio-admin implements a new protocol admin:/// which gives administrative access to the entire system. This is achieved by talking, over dbus, with a root-level helper binary that in turn uses existing KIO infrastructure to run file:// operations in root-scope. Or simply put: admin:// is exactly like file:// but redirected over dbus to gain administrative privileges.

Allows the user to manage files as administrator with Dolphin using the admin:// KIO protocol. This is necessary because Dolphin should not be run as root (and refuses to do so, instead suggesting this package).

https://gitlab.com/sofija.p2018/kla-ot2 ... 86_64.xbps

Void Linux Installation QEMU/KVM

QEMU/KVM does not require a DKMS module to operate, unlike VirtualBox.

Installing required packages

sudo xbps-install -Su virt-manager libvirt qemu

• To enable KVM your user must be added to the 'kvm' group:

  usermod -aG kvm <username>

  Don't forget to load the appropiate KVM module for your CPU (x86 only):

  modprobe kvm-amd # for AMD CPUs
  modprobe kvm-intel # for Intel CPUs

Adding yourself to emulator user groups:

sudo usermod -aG kvm spot
sudo usermod -aG libvirt spot

Load the appropriate module ( Intel or amd ) and start the daemons:

modprobe kvm-intel  or  modprobe kvm-amd
sudo ln -s /etc/sv/libvirtd /var/service
sudo ln -s /etc/sv/virtlockd /var/service
sudo ln -s /etc/sv/virtlogd /var/service

Use vsv to check the status of the services:
sudo vsv status virt

• After you log out of your session and log back in, or restart your computer, you will be able to run virt-manager and create/add the first virtual machine.

run from menu system -> virt-manager