KLA Manjaro JWM

[josejp2424]

@josejp2424

I was getting myself familiar with pacman by trying an installation of qemu virt-manager.
When I did this it gave the below information about breaking dependencies.
I looked up how to resolve this and didn't find anything that really helped much.
I did an update first on it - pacman -Syy
As a last resort I deleted those not knowing how this would affect the system.
I used the command pacman -R .... for each the required by listed.

How should something like this be corrected?

Code: Select all

  pacman -S virt-manager
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing gst-plugins-base-libs (1.24.7-1) breaks dependency 'gst-plugins-base-libs=1.24.6-1' required by gst-libav
:: installing gstreamer (1.24.7-1) breaks dependency 'gstreamer=1.24.6-1' required by gst-libav
:: installing gst-plugins-base-libs (1.24.7-1) breaks dependency 'gst-plugins-base-libs=1.24.6-1' required by gst-plugins-bad-libs
:: installing gstreamer (1.24.7-1) breaks dependency 'gstreamer=1.24.6-1' required by gst-plugins-bad-libs
:: installing gst-plugins-base-libs (1.24.7-1) breaks dependency 'gst-plugins-base-libs=1.24.6-1' required by gst-plugins-good
:: installing gstreamer (1.24.7-1) breaks dependency 'gstreamer=1.24.6-1' required by gst-plugins-good
 

Doing this allowed me to run pacman -S virt-manager successfully.

But when I did a reboot, it locked up so I had to do a power down/up to get it back. So there probably should be a better way to do that.

By the way I sure like the colorful prompts you used for the bash terminal.

Thanks

hi @JusGellin

I realized the errors ; they will be fixed in the update. The scripts I use to update the ISO had some errors that I didn't notice, and I saw that the process wasn't completing. But thank you for pointing out the errors.

[wiak]

@josejp2424@Sofiya

I haven't had time to check build details on this or the LXDE variant of late but noticed an error in older Manjaro LXDE variant.

lt is definitely recommended to always use the latest FR initrd because even though older variants will usually 'work' for some functions the initrd provides, some important new functionality would be missing and there could also be some unfixed bugs. The latest FR initrd/init has the following header info:

Code: Select all

#!/bin/sh
# initrd/init: simple switch_root init with overlay filesystem set up.
# Copyright William McEwan (wiak) 26 July 2019+; Licence MIT (aka X11 license)
# version="7.0.3"; revision="-rc1" Date: 05Apr2024

In other words, you should be using FR initrd/init version 7.0.3-rc1. If you are using something older, that is not a good idea.

You can always find the latest initrdXXX-latest.gz here:

https://gitlab.com/firstrib/firstrib/-/ ... type=heads

Note that Arch Linux stores modules in zstd format so the 'standard' initrd-latest.gz won't work as a skeleton initrd.gz with huge kernels on that one. Instead, you should use initrd_kmod-latest.gz from the above gitlab repo because that contains a kmod binary that handles zstd compressed modules (rather than relying on busybox, which WILL NOT support zstd compressed modules). The alternative of course is to store non-zstd modules inside a special variant of the FR initrd, but much better and simpler IMO to use that kmod-including FR initrd variant.

[fredx181]

for KLA " Arch " it does not work .This only works for "KLV-Airedale"

I haven't used an arch KL in awhile, but I think I ran the backup script successfully in the past. I noticed you had posted a link to a recent topic where @fredx181 made a Debian Dog version available. Is it possible you are using that one? Or are you using the one I posted and it failed with KLA?

If the restore-sys script doesn't work for KLA distros, I can verify that it works for every KLV distro I've used. Those would be KLV-airedale, KLV-boxer, KLV-hyprland, KLV-bspwm, KLV-awesome, KLV-KDE-plasma, KLV-spectr, am I missing one?

The version that you published, as well as the other versions.for KLA " Arch " it does not work

I had a look at why for KLA " Arch " it does not work (tested on KLA Manjaro LXDE).
And was surprised (not pleasantly ) that the mountpoint of the drive containing upper_changes is not in /mnt (edit: anyway, not always) (as it is in KLV AFAIK, done from the initrd).
So the thing is that restore-sys uses findmnt to check for that, but it finds a non existing upper_changes directory.
(as it has apparently been switched to e.g. /media/root/ ... /upper_changes rather than /mnt/ ... /upper_changes).

Here's new restore-sys script (named it restore-sys2 to avoid confusion) that works at least on KLA Manjaro LXDE (and still on KLV too) :
# 2024-10-15 restore-sys2 , should support running from KLA, double checks for real mountpoint of the drive containing upper_changes

restore-sys2.gz

Remove fake .gz and make executable

(7.07 KiB) Downloaded 8 times

EDIT: Tested also on KLV-hyprland but couldn't make it work, I guess it has to do with (default) login as user "spot", using sudo didn't work for me either.

[Sofiya]

I haven't used an arch KL in awhile, but I think I ran the backup script successfully in the past. I noticed you had posted a link to a recent topic where @fredx181 made a Debian Dog version available. Is it possible you are using that one? Or are you using the one I posted and it failed with KLA?

If the restore-sys script doesn't work for KLA distros, I can verify that it works for every KLV distro I've used. Those would be KLV-airedale, KLV-boxer, KLV-hyprland, KLV-bspwm, KLV-awesome, KLV-KDE-plasma, KLV-spectr, am I missing one?

The version that you published, as well as the other versions.for KLA " Arch " it does not work

I had a look at why for KLA " Arch " it does not work (tested on KLA Manjaro LXDE).
And was surprised (not pleasantly ) that the mountpoint of the drive containing upper_changes is not in /mnt (edit: anyway, not always) (as it is in KLV AFAIK, done from the initrd).
So the thing is that restore-sys uses findmnt to check for that, but it finds a non existing upper_changes directory.
(as it has apparently been switched to e.g. /media/root/ ... /upper_changes rather than /mnt/ ... /upper_changes).

Here's new restore-sys script (named it restore-sys2 to avoid confusion) that works at least on KLA Manjaro LXDE (and still on KLV too) :
# 2024-10-15 restore-sys2 , should support running from KLA, double checks for real mountpoint of the drive containing upper_changes
restore-sys2.gz

EDIT: Tested also on KLV-hyprland but couldn't make it work, I guess it has to do with (default) login as user "spot", using sudo didn't work for me either.

EDIT: Tested also on KLV-hyprland but couldn't make it work, I guess it has to do with (default) login as user "spot", using sudo didn't work for me either.

In KLV-hyprland it should be launched like this

Code: Select all

sudo env WAYLAND_DISPLAY="$XDG_RUNTIME_DIR/$WAYLAND_DISPLAY" XDG_RUNTIME_DIR=/user/run/0 dbus-run-session -- restore-sys2

or open the manager as a superuser, put the file "restore-sys2" there and run

[fredx181]

In KLV-hyprland it should be launched like this

Code: Select all

sudo env WAYLAND_DISPLAY="$XDG_RUNTIME_DIR/$WAYLAND_DISPLAY" XDG_RUNTIME_DIR=/user/run/0 dbus-run-session -- restore-sys2

or open the manager as a superuser, put the file "restore-sys2" there and run

The latter is far easier to remember !

[josejp2424]

Update for JWM : a second window manager has been added, which I use quite a bit, and it is BSPWM.
Switching from JWM to BSPWM is simple, and if you install another desktop environment, you can also do it from the GUI wmswitcher.
Additionally, the errors that occurred during updates have been fixed. I will keep the new updates using the KLA updater.
I don't think I will release more ISOs; I will just keep updating it, which will be easier.

DOWNLOAD

https://sourceforge.net/projects/kla-ma ... WM-1.4.iso

# MD5
f64ebf64a668fa38c06184e550ac8dcf Manjaro-JWM-1.4.iso

[Amol]

Great news josejp2424! i' ve got problem with the 1.3 version with pesistence contrary to the LXDE version.
Best regards,
Amol
P.S: I'm under KLA-OT2 right now and persistence runs great.

[josejp2424]

Great news josejp2424! i' ve got problem with the 1.3 version with pesistence contrary to the LXDE version.
Best regards,
Amol
P.S: I'm under KLA-OT2 right now and persistence runs great.

hi @Amol .
What happens to you with persistence? What is the problem?

[JusGellin]

@josejp2424
1. I tested the save2flash to see if it was working. It seems to from my tests.
What I did was add a folder to each of the base linux hierachy file system and did a save2flash before reboot.
The expected folders did the save ok when it came up. I did the same thing by deleting those folders and
they were gone when i did a save2flash and rebooted.

2. I found that when I changed the Display Settings at menu > System > Monitor Settings for the monitor to go to 1920x1080, it would immediately take the settings
for the current session and work properly. But if I did a save2flash and rebooted, it wouldn't retain the new setting and would go back to 1024x768.
This seems to be a problem.

3. Also I found the the Locale Manager from the Welcome to KLA Manjaro! would change the time zone setting but wouldn't retain it in the gui application.
So once I set it and went back to look it would indicate it is back at the default. This happens even after a save2flash reboot the next time.
But the time and zone are correct which I also verified from the terminal using the command timedatectl.
This is not a problem making the correct time zone work, but is a problem not showing the setting in the gui application called Locale Manager.

I hope this helps you.

Thanks

[Amol]

Hello to all !
I've tested the JWM-1.4 version and have the same persistence problems than jusGellin.The most annoying is the resolution which doesn't stay after a reboot.
There is also the mouse theme which doesn't stay after a reboot.The others parameters stay after reboot.
Best regards,
Amol

[Sofiya]

@josejp2424
1. I tested the save2flash to see if it was working. It seems to from my tests.
What I did was add a folder to each of the base linux hierachy file system and did a save2flash before reboot.
The expected folders did the save ok when it came up. I did the same thing by deleting those folders and
they were gone when i did a save2flash and rebooted.

2. I found that when I changed the Display Settings at menu > System > Monitor Settings for the monitor to go to 1920x1080, it would immediately take the settings
for the current session and work properly. But if I did a save2flash and rebooted, it wouldn't retain the new setting and would go back to 1024x768.
This seems to be a problem.

3. Also I found the the Locale Manager from the Welcome to KLA Manjaro! would change the time zone setting but wouldn't retain it in the gui application.
So once I set it and went back to look it would indicate it is back at the default. This happens even after a save2flash reboot the next time.
But the time and zone are correct which I also verified from the terminal using the command timedatectl.
This is not a problem making the correct time zone work, but is a problem not showing the setting in the gui application called Locale Manager.

I hope this helps you.

Thanks

2. I found that when I changed the Display Settings at menu > System > Monitor Settings for the monitor to go to 1920x1080, it would immediately take the settings
for the current session and work properly. But if I did a save2flash and rebooted, it wouldn't retain the new setting and would go back to 1024x768.
This seems to be a problem.

add to /root/Startup -- exec_lxrandr-autostart

Code: Select all

#!/bin/sh
exec exec_desktopfile.awk ~/.config/autostart/lxrandr-autostart.desktop

1) Remove .FALSE.gz
2) make executable chmod +x exec_lxrandr-autostart

[josejp2424]

The problem of not saving the configuration of xrandr is that it is not launching the .desktop files located in /root/.config/autostart.
I'm going to have to do an update.
Thanks @Amol and @JusGellin for the tests.

[JusGellin]

add to /root/Startup -- exec_lxrandr-autostart

Code: Select all

#!/bin/sh
exec exec_desktopfile.awk ~/.config/autostart/lxrandr-autostart.desktop

Attachments
exec_lxrandr-autostart.FALSE.gz

Hello, @Sofiya
I was going to ask for your help for exactly what I'm supposed to do with this but figured it out.

I thought that since the download had the suffix .FALSE.ga it meant that it should be renamed without that part.
I then put the file now called exec_lxrandre-autostart into the directory called /root/Startup.
But at first it didn't work on a reboot.

I saw from the code you listed that this was a shell program so I next looked at its permissions.
I knew a shell program needed to have executable permissions, which it didn't have, so I changed all to have them.
Then I rebooted, changed the monitor settings, again rebooted with save2flash.
On the reboot, it came up with the desired setting I wanted - yay!

Thanks

[Sofiya]

add to /root/Startup -- exec_lxrandr-autostart

Code: Select all

#!/bin/sh
exec exec_desktopfile.awk ~/.config/autostart/lxrandr-autostart.desktop

Attachments
exec_lxrandr-autostart.FALSE.gz

Hello, @Sofiya
I was going to ask for your help for exactly what I'm supposed to do with this but figured it out.

I thought that since the download had the suffix .FALSE.ga it meant that it should be renamed without that part.
I then put the file now called exec_lxrandre-autostart into the directory called /root/Startup.
But at first it didn't work on a reboot.

I saw from the code you listed that this was a shell program so I next looked at its permissions.
I knew a shell program needed to have executable permissions, which it didn't have, so I changed all to have them.
Then I rebooted, changed the monitor settings, again rebooted with save2flash.
On the reboot, it came up with the desired setting I wanted - yay!

Thanks

Yes, you did everything correctly, I just forgot to specify that the file should be made executable

1) Remove .FALSE.gz
2) make executable chmod +x exec_lxrandr-autostart

[Amol]

Hello to all !
I've made the tip of sofiya in rox-filer easyly.That corrects the problem of screen resolution persistence.THANKS !.
Hey, josejp2424, think about to add the tool for the touchpad.
Best regards,
Amol