Closed Martan404 closed 9 months ago
I guess running in chroot is probably a bad idea since KDE hasn't generated any files when you try to run it during an Arch install. I got the inspiration from Chris' ArchTitus script. Maybe Konsave could throw an error if it's ran in chroot?
I managed to work around it by creating a shell script at $HOME/.config/plasma-workspace/env
This is how I went about it
# Install konsave
sudo -u $user pipx install konsave
# Download settings.knsv
sudo -u $user curl -L https://github.com/Martan404/Archer/raw/main/quiver/archer.knsv > /home/$user/archer.knsv
# Create folder and script as user
sudo -u $user mkdir -p /home/$user/.config/plasma-workspace/env
sudo -u $user touch /home/$user/.config/plasma-workspace/env/archer_setup.sh
# Write script
cat <<-END >> /home/$user/.config/plasma-workspace/env/archer_setup.sh
#!/usr/bin/env bash
sudo -u $user konsave -i /home/$user/archer.knsv
read -t 1
sudo -u $user konsave -a archer
rm -f /home/$user/archer.knsv
rm -f /home/$user/.config/plasma-workspace/env/archer_setup.sh
END
chmod a+x /home/$user/.config/plasma-workspace/env/archer_setup.sh
This issue is a duplicate of https://github.com/Prayag2/konsave/issues/89. I'll fix this as soon as possible!
Describe the bug I am in the process of making an Arch install script and I am trying to import and apply all the KDE plasma customization inside
chroot
before first boot. Importing and applying the settings works but if I try to usekonsave -s
,konsave -e
after my first boot then konsave will return emptyexport
andsave
folders with only aconf.yaml
fileAt first I got this error when trying to import. This results in only part of the settings being imported
Here's the konsave log
If I instead create the folders before importing the settings, like this
then I get no error, all the settings import properly but I can still not use the
konsave -s
,konsave -e
commands. I also tried creating the folders inside my script and then using konsave normaly after first boot with no problems so I am pretty sure that is not the issue.My script works fine until
sudo -u $user konsave -i /home/$user/kde-settings.knsv
.To reproduce Install Arch completely. Inside chroot before first boot run the command
konsave -i
Expected behavior I expect the
konsave -s
andkonsave -e
command to work after usingkonsave -i
inside chrootSystem information
Additional context Here's the script I am working on https://github.com/Martan404/Archer/blob/944360399ff6ff7c5e412622466eafe14d947d90/archer.sh#L966 The
konsave -i
command is run on line 966