KLV-plasma-6-KDE-CE (stable Release )

[geo_c]

And the one package missing that makes MuseScore show up is: alsa-plugins-pulseaudio which wasn't installed.

I wasn't sure installing that was a good idea before, since I wasn't sure of the pulseaudio pipewire setup in KDE.

pulseaudio and pipewire are a bit confusing to me anyway.

So now MuseScore is 100% working the alsa-plugins-pulseaudio present.

[geo_c]

Finally, synthv1_jack is up and running with pw-jack synthv1_jack

Working 100%

So now I'm good to make music on KLV-KDE-Plasma!

Void and Plasma, what a great combination!

[geo_c]

@Sofiya I'm not able to set the time zone using the KDE auto time zone tool, because after asking for the spot password it fails to authorize the action.

What am I missing?

I looked to maybe link zoneinfo like in other KLVs, but there's nothing in it.

[geo_c]

@fredx181 I tried to run restore-sys on KLV-plasma, but I didn't get a backup upper_changes, and running it in the terminal shows it doesn't have permissions, presumably because I'm running as spot.

Should I do sudo ./restore-sys or something like that, or run it from a file manager opened with sudo? And do you think restore-sys should work in this case?

[rockedge]

@geo_c

sudo should work in both cases you've mentioned. <Permission problem==throw sudo in front of it>

Since user spot should be in the wheel group sudo will work without a password

[geo_c]

@geo_c

sudo should work in both cases you've mentioned. <Permission problem==throw sudo in front of it>

Since user spot should be in the wheel group sudo will work without a password

Yes I just ran the script from a sudo instance of Xfe and it worked.

So I now have this KLV-plasma fully loaded like my other pipewire-jack setups. I just ran the big Ardour app and it's a little tricky to get started opening an older project file. If it's started with the audio engine using Alsa driver, it doesn't show up in qpwgraph or helvum graph at all. So I switched the driver within Ardour, and that immediately caused both qpwgraph and helvum to bomb out. It's like it wrestles the driver from them or something. But once I set and saved the project with the jack driver, I could open Ardour with pw-jack Ardour and get it stable and in the graphs. I'll have to play with it more to really know how stable it will run. I always found Carla's connection graph to be best, but it seems it's not being maintained and may not come up to speed with pipewire/wayland, so I didn't install it. I was having issues with Carla in Airedale and Spectr.

Now that I have this instance of KLV-plasma loaded with applications, and desktop files (literally a couple hundred including all those stand alone plugins that have to be started with pw-jack) and portables with their desktop files all starting from the menu, and the whole thing backed up using fred's restore-sys, I can experiment some more. I didn't PFI or multi-instance this yet, but that's the next step and probably build it from scratch now that I have it somewhat figured out.

This upper_changes is already 3.5GB, way bigger than any of my other distros.

Oh, and now this distro is the kind I can stay logged into and get a day's work done!

[Sofiya]

@Sofiya I'm not able to set the time zone using the KDE auto time zone tool, because after asking for the spot password it fails to authorize the action.

What am I missing?

I looked to maybe link zoneinfo like in other KLVs, but there's nothing in it.

right-click on the clock widget -> Configure widget <<Digital clock>>

or in the terminal

Code: Select all

sudo ln -sf /usr/share/zoneinfo/Europe/Moscow /etc/localtime 

Europe/Moscow -- change to yours

[geo_c]

@Sofiya I'm not able to set the time zone using the KDE auto time zone tool, because after asking for the spot password it fails to authorize the action.

What am I missing?

I looked to maybe link zoneinfo like in other KLVs, but there's nothing in it.

right-click on the clock widget -> Configure widget <<Digital clock>>

or in the terminal

Code: Select all

sudo ln -sf /usr/share/zoneinfo/Europe/Moscow /etc/localtime 

Europe/Moscow -- change to yours

Thanks, I understand now. I was trying to use the "Change System Wide Timezone" button, but now I figured out the gui.

[geo_c]

KLV-Plasma-KDE running a theme called Noir-Dark-Global with Beauty Solar icons:

[geo_c]

I was missing a window shading feature in KDE, so I looked it up, and sure enough KDE-Plasma doesn't do window shading:

https://bugs.kde.org/show_bug.cgi?id=377162

With all the glitz you think that would be relatively easy.

[Clarity]

Results

Concern?

Screenshot_KLV-KDE_v1.2.jpg (90.8 KiB) Viewed 1910 times

QPWgraph is very useful to correct output path

Screenshot_KLV-KDE_v1.2 Audio.jpg (22.29 KiB) Viewed 1895 times

Curious

[Clarity]

For KDE v6.1.4 here is a video of all that is new from v6.1.3.

I like the way the announcer uses the Cube is the presentation.

Enjoy

[Clarity]

Phoronix reports KDE progress, yesterday

My tests of KLV-KDE v1.2 have gone very well

Enjoy

[Sofiya]

FreeTube
https://freetubeapp.io/#download
https://freetubeapp.io/

[geo_c]

Well of course after I get KLV-Plasma-KDE-CE-1.1 completely configured and full of my favorite applications, copied to 5 different machines and reading all my symlinked libraries and such, then @Sofiya puts out another iso. Well I may stay one behind for awhile.

I really am enjoying this KDE plasma stuff. It feels.....professional...but it still won't be appropriate for live stage audio work, Spectr rules in that department for it's rock solid stability, keystroke operation, and low resource usage.. But for doing all the business-like daily routines, and using computers at my office and teaching locations, KDE plasma fits.

I am basically doing the final icing on the cake and getting Ranger file manager to work perfectly, and I had much trouble getting ranger to display images and thumbnails of pdf's and video. So I carefully experimented and finally figured out that it's most likely the Konsole terminal that is the problem, as it finally clicked when I was reading the comments in the ranger rc.conf file which states that this image preview feature is supported for certain terminals.

After not getting it to work in Konsole, I simply started uxterm from Konsole using sudo uxterm, then ranger, and it all worked as expected. (I have configs in root, and configs in spot, and ranger previews work perfectly in uxterm running from either root or spot)

However, I do not know how to make uxterm look "not bright white." I tried using .Xresources and that didn't work, which using Wayland and not Xorg it makes sense that it wouldn't.

Anyway the Konsole, zsh, and uxterm setup can get a little confusing to a simple guy like myself.

Still, I have ranger working in uxterm, and that's a good start.

I tried using Yazi a week ago, and it seemed to have limited functions compared to ranger, which is a super workhorse file manager. I use ranger all the time for manipulating and editing scripts and text files. The preview functions are also great for moving around images and pdf's.

[rockedge]

I do not know how to make uxterm look "not bright white." I tried using .Xresources and that didn't work, which using Wayland and not Xorg it makes sense that it wouldn't

Try starting with:

Code: Select all

uxterm -bg black -fg green

[geo_c]

Try starting with:

Code: Select all

uxterm -bg black -fg green

Oh there we go! Very easy. Maybe I can make a destop file for it. I used uxterm -bg black -fg cyan, and it looks nice.

So I guess the next step is uxterm --help for all the options.

[Sofiya]

Try starting with:

Code: Select all

uxterm -bg black -fg green

Oh there we go! Very easy. Maybe I can make a destop file for it. I used uxterm -bg black -fg cyan, and it looks nice.

So I guess the next step is uxterm --help for all the options.

in /home/spot/
Logout and login again

.Xresources

Code: Select all

xterm*geometry: 110x25
xterm*faceName: terminus:normal:pixelsize=10
!xterm*font: -*-dina-medium-r-*-*-10-*-*-*-*-*-*-*
xterm*dynamicColors: true
xterm*utf8: 2
xterm*eightBitInput: true
xterm*saveLines: 512
xterm*scrollKey: true
xterm*scrollTtyOutput: false
#xterm*scrollBar: true
#xterm*rightScrollBar: true
xterm*jumpScroll: true
xterm*multiScroll: true
xterm*toolBar: false
XTerm*background: black
XTerm*foreground: gray
XTerm*title: terminal
XTerm*saveLines: 1024
xterm*decTerminalID: vt340
xterm*numColorRegisters: 256
xterm*sixelScrolling: 1
xterm*sixelScrollsRight: 1

UXft*antialias: true
UXft*autohint: true
UXTerm*background: #002b36
UXTerm*foreground: #839496
UXTerm*cursorColor: grey
#UXTerm.vt100.geometry: 84x25+150
UXTerm*faceName: Monospace Regular 
UXTerm*faceSize: 10

[geo_c]

in /home/spot/
Logout and login again

.Xresources

Code: Select all

xterm*geometry: 110x25
xterm*faceName: terminus:normal:pixelsize=10
!xterm*font: -*-dina-medium-r-*-*-10-*-*-*-*-*-*-*
xterm*dynamicColors: true
xterm*utf8: 2
xterm*eightBitInput: true
xterm*saveLines: 512
xterm*scrollKey: true
xterm*scrollTtyOutput: false
#xterm*scrollBar: true
#xterm*rightScrollBar: true
xterm*jumpScroll: true
xterm*multiScroll: true
xterm*toolBar: false
XTerm*background: black
XTerm*foreground: gray
XTerm*title: terminal
XTerm*saveLines: 1024
xterm*decTerminalID: vt340
xterm*numColorRegisters: 256
xterm*sixelScrolling: 1
xterm*sixelScrollsRight: 1

UXft*antialias: true
UXft*autohint: true
UXTerm*background: #002b36
UXTerm*foreground: #839496
UXTerm*cursorColor: grey
#UXTerm.vt100.geometry: 84x25+150
UXTerm*faceName: Monospace Regular 
UXTerm*faceSize: 10

I did try adding an .Xresources file earlier, but I must have done it wrong. I'll do it again using yours.

I'm also looking at the zsh configs, and getting a feel for how they interact. I'm working on changing the zsh theme at the moment.

I also have sourced some personal bash functions in /etc/bash/bash.d, and they are working in uxterm, but I may need to source them in zsh to get them working as spot in Konsole.

It's been a worthwhile effort to learn how to use linux multi-user. The interesting thing, is that if a person is not an administrator and simply uses their own user account, I guess life is fairly simple, they install stuff, and mount drives as user, etc. But if one wants to tweak the system as root administrator, it actually requires a lot more terminal use and typing sudo, than say a puppy running as root exclusively. Also a lot more thought goes into how to give permissions to files across drives and users.

Basically I've changed permissions on all my shared external files to root:spot, and that works across the board for puppies, root-user KL's, and spot-user KL's. But the trick comes when editing and re-saving those files with applications that will give the file permissions based on what user it's running from. Like Geany for instance. If I edit from root and save, then the file is root:root and I have to chown it to root:spot so it's universally accessible.

But I can kind of get around that using shared directories outside the system by updating them with chown -R, and it also required me to update all my rsync scripts to preserve ownership when syncing.

So I'll have a directory structure like this:

Code: Select all

/
|_KLV-Plasma
|_KLV-Airedale
|_dbox.sync (root:spot)
|_portableAPP (root:spot)

and an rsync script that looks like this allowing me to sync a directory to another machine and use it from puppies and KLs running as spot:

Code: Select all

#!/bin/bash

rsync -r -t -v --progress --delete --modify-window=1 -l -H -s -X -p -o -g /mnt/sdb1/portableAPP /mnt/home

[geo_c]

@Sofiya adding .Xresources worked perfectly. So I must have had a buggy .Xresources earlier, or simply didn't do things in the proper order.

I changed the zsh theme and changed it back to built-in, because I realized what I am probably really trying to do is change the background in Konsole from brown to something darker. I haven't figured out where to look for that config yet. Chaning colors from the Konsole settings menu only changes the UI colors.

[Sofiya]

@Sofiya adding .Xresources worked perfectly. So I must have had a buggy .Xresources earlier, or simply didn't do things in the proper order.

I changed the zsh theme and changed it back to built-in, because I realized what I am probably really trying to do is change the background in Konsole from brown to something darker. I haven't figured out where to look for that config yet. Chaning colors from the Konsole settings menu only changes the UI colors.

Set up profile

[geo_c]

Set up profile

But oh! this is great, you can just download themes like all the rest of the KDE thematic elements.

[Sofiya]

Set up profile

But oh! this is great, you can just download themes like all the rest of the KDE thematic elements.

For this reason alone, KDE was my main system after Mint

[geo_c]

For this reason alone, KDE was my main system after Mint

KDE is pretty cool, but it's a memory hog. On this 16GB ram machine it is not an issue, but it's sitting at 2.2GB of ram with only LibreWolf opened to the forum, Conky, and Xfe running currently. When I'm on spectr that same scenario would be sitting at around 1GB or sometimes less. Spectr boots in around 365Mb.

Last night I used the clear_memory.sh you provided awhile back, and that cleared about 300-400Mb of ram.

It seems to build up ram usage rather quickly when browsing intensive web pages. I don't know much about memory management methodology, but maybe it's different when running wayland/plasma.

It does run fast though for the amount of graphic capability in operation.

[Sofiya]

For this reason alone, KDE was my main system after Mint

KDE is pretty cool, but it's a memory hog. On this 16GB ram machine it is not an issue, but it's sitting at 2.2GB of ram with only LibreWolf opened to the forum, Conky, and Xfe running currently. When I'm on spectr that same scenario would be sitting at around 1GB or sometimes less. Spectr boots in around 365Mb.

Last night I used the clear_memory.sh you provided awhile back, and that cleared about 300-400Mb of ram.

It seems to build up ram usage rather quickly when browsing intensive web pages. I don't know much about memory management methodology, but maybe it's different when running wayland/plasma.

It does run fast though for the amount of graphic capability in operation.

As for memory, yes - beauty requires sacrifice, so I have " Swap " enabled for reliability. although 8 gig of memory is enough

[Sofiya]

To mount the swap partition during system boot

in /etc/fstab register UUID
get UUID by entering in terminal sudo blkid /dev/sda3 - where "sda3" is the partition where your Swap is located replace with yours

fstab

Code: Select all

#
# See fstab(5).
# <file system>	<dir>	<type>	<options>		<dump>	<pass>
tmpfs		/tmp	tmpfs	defaults,nosuid,nodev   0       0

# Swap
UUID=67e75917-d277-4581-8741-4f821cb520ab none swap defaults 0 0

[Sofiya]

KLV-plasma-KDE-CE

[williwaw]

I guess life is fairly simple, they install stuff, and mount drives as user, etc.

what have you found is the easiest configuration or process to mount and install as spot?

[geo_c]

I guess life is fairly simple, they install stuff, and mount drives as user, etc.

what have you found is the easiest configuration or process to mount and install as spot?

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.

I may be fuzzy on how it works, but that's how it appears. The whole graphic part of the desktop is setup as spot, so I have never actually run as root, as there is no root login option on the login screen. Instead I simply open things I want to run with root privileges using sudo from a terminal.

As far as mounting goes I do this: I have mount scripts which you have seen before and I have posted elsewhere on the forum. They display mountable devices and can mount to /mnt or /run/media/root. So what I do is link all my scripts into the system from a library outside the system, and that library has root:spot permissions, so it's linked to /root/my-applications/bin and /home/spot/my-applications/bin. I have both these directories in the executable path in /etc/bash/bash.d so that I can run the scripts from a terminal as either. When I mount, I open a terminal and type sudo [my-mount-script-name] so that I can mount and access the drive and copy files to either root or spot. The data and program files on these drives have their permissions all set to root:spot so they can be read, written, and executed from either (but not the other installed OS directories of course, they retain there original permissions, which is root mostly)

I like to have options. This has been working well, and honestly I've been running this KLV-KDE-plasma this way for about 4 days straight, copying and accessing files between multiple drives and multiple machines. It's all working well.. I boot up spectr when I want to manipulate the KDE-plasma install directory, and that's refreshing, because spectr runs as root, and I don't have to worry too much about permissions, that is unless I save an edited file, or copy using Xfe and the permissions are written as root:root again. So I have to watch that. Mostly I run rsync scripts which preserve the permissions, or cp -a.

But like I mentioned in a post above, I adjusted about a hundred of these rsync scripts to make sure they preserve these root:spot permissions when I transfer and sync files. Geany's search and replace function made it fairly straight ahead.

[geo_c]

To mount the swap partition during system boot

in /etc/fstab register UUID
get UUID by entering in terminal sudo blkid /dev/sda3 - where "sda3" is the partition where your Swap is located replace with yours

Thanks, I have a couple of computers and bootable USB drives setup with swap files, but I mostly haven't run a swap partition in quite awhile. I used to set my puppies up either with a swap file, or with a swap partition. But my experience is once the OS is using the swap file, it's almost too late. I've been able with these amazing forum OS's to run for a few years now without ever touching a swap partition.

Of course if I was doing some kind of video editing or something, I might crash the OS, but also it seems like when doing a task so resource intensive, once the swap file is utilized, performing the desired task becomes unmanageable.