Discussion, talk and tips
https://forum.puppylinux.com/
KLV-plasma-KDE-CE-1.2 ... Wayland +Pipewire stable ( release )
There is also a choice of KDE-plasma-Void X11
ISO: ( 1.3 GB )
https://github.com/sofijacom/KLV-plasma ... KDE-CE-1.2
________________________________________________________________________________________________
Enjoy and have fun!!!
in condensed form I don’t know 
I could say one thing: unpacked "07firstrib_rootfs" weighs 3.7 Gb
what else can I say, it works pretty well, but you’ll have to tinker with the build plugin 
most likely it will be less if you throw out X11, since I have both X11 and Wayland
KDE-plasma-Void-CE-1.0 Wayland +Pipewire
Plugin permissions and re-assembly, much better, bugs and shortcomings fixed
@Sofiya is this a KLV in foundation?
I think it asks "Is this using the KLV base ('foundation')?" AS such, this project would constitute a KL topic thread.
@Sofiya your suggestion of excluding X11 is a good one as Wayland has matured enough to carry the display behavior loads for most 64bit PCs now and in the future.
Clarity wrote: ↑Sat Jul 06, 2024 7:46 pmI think it asks "Is this using the KLV base ('foundation')?" AS such, this project would constitute a KL thread.
@Sofiya your suggestion of excluding X11 is a good one as Wayland has matured enough to carry the display behavior loads for most 64bit PCs now and in the future.
I'll hold off on excluding X11 for now, this requires testing
Yes this is a KLV stream !!! build plugin used I'm still writing it
Since I worked with KDE about 10 years ago, a lot has changed at this stage.I'm looking for a middle ground
in order to exclude X11, all applications must use Wayland, at this stage not all applications use Wayland
KDE-plasma-Void-CE-1.0
Code: Select all
/mnt/sda2/2-QEMU/QEMU-2.5.0-ubu16.04.AppImage qemu-system-x86_64 -enable-kvm -cpu host -smp 4 -device AC97 -vga cirrus -m 4G -name 'KDE-plasma-Void-CE-1.0' -boot d -hda /mnt/sda2/2-QEMU/VirtualHDD.img -cdrom /root/Downloads/KDE-plasma-Void-CE-1.0.iso
@Sofiya Looks really nice!
How much RAM is being used right after system start? I do not know much about KDE, was it hard to fix the bugs in the plugins?
700 mb
The standard plugin is written from scratch "f_00_Void_KDE_plasma_no-kernel.plug"
I’m still writing, correcting, testing
KDE-plasma-Void-CE-1.0
password:spot
login:spot
Enjoy and have fun!!!
Code: Select all
[code]/mnt/sda2/2-QEMU/QEMU-2.5.0-ubu16.04.AppImage qemu-system-x86_64 -enable-kvm -cpu host -smp 4 -device AC97 -vga cirrus -m 4G -name 'KDE-plasma-Void-CE-1.0' -boot d -hda /mnt/sda2/2-QEMU/VirtualHDD.img -cdrom /root/Downloads/KDE-plasma-Void-CE-1.0.iso
[/code]
replace "/root/.oh-my-zsh" with "$HOME/.oh-my-zsh" in /home/spot/.zshrc
fixed in build plugin
When I get home later this week, I will run this build and start working with it.
Right now I'm working from my cell phone hotspot, and I don't want to do too many large downloads.
Right now I'm broadcasting from KDE-plasma-Void-CE-1.0
looks quite nice, Sofiya.
have you tried to run as root? specifically run Dolphin as root?
IIrc, krusader may be more root friendly, or at least it was a few year back when I last looked at KDE.
Code: Select all
Open Dolphin as root (KDE)Yes, of course I did, it needs to be enabled in Dolphin. not enabled by default
bluetooth check
Great job Sofiya !! (curiosity won, and tried it 
) I take my words back when I said KDE is too heavy, well, it uses more than double amount of RAM compared to Puppy with JWM of course, but runs very smooth on my laptop with 4GB RAM, posting from it now
williwaw wrote:have you tried to run as root? specifically run Dolphin as root?
Seems not:
Code: Select all
void-live% sudo dolphin
Running Dolphin with sudo is not supported as it can cause bugs and expose you to security vulnerabilities. Instead, install the `kio-admin` package from your distro and use it to manage root-owned locations by right-clicking on them and selecting "Open as Administrator".
void-live% sudo xbps-install kio-admin
Package 'kio-admin' not found in repository pool.EDIT: Oh, see now from post by Sofiya above there's a workaround.
My check for if an iso is ok is to mount it (I do it anyway often to copy files from the mountpoint for setting up a frugal install manually), if that works it should be right (but anyone correct me if I'm wrong please).
Code: Select all
md5 checksum:57b7c7097a5d306ba3f35c2b9524fde4 Hello @Sofiya Booted ISO file in a small VM. Updated packages, added FASTFETCH and all is operational. This KL version is updated as it is Wayland (LIVE) and upgraded to v6.1.52
Looks great 
Code: Select all
qemu-system-x86_64 -enable-kvm -vga cirrus -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -name "KL KDECE v1.0 via QEMU" -hda KDE-plasma-Void-CE-1.0.isoTested KL's KDECE v1.0 via USB boot to launch ISO file via Ventoy as well as SG2D.
Code: Select all
qemu-system-x86_64 -enable-kvm -vga cirrus -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -name "KL KDECE v1.0 via QEMU" -hda /dev/sdcSG2D boots exactly the same as direct ISO file boot with exact behaviors. Ventoy, though, traps after default menu starts.
grub2 parameter
Code: Select all
linux /KDE-plasma-Void-CE/vmlinuz w_bootfrom=UUID=fbb65611-fb5c-4b0c-8f21-331dabc54d23=/KDE-plasma-Void-CE w_changes=RAM2found in grub_config.txt in the iso works well and fast.
tried krusader, but some issues. (some research indicates it may not be quite ready for wayland)