KeePassXC

[user0815]

Dear All,
Does anyone have or know where to download this module? I tried myself at least 10 times with USM but get most of the time LIBS.txt error. It seems to depend on which dependency packages I choose. Finally I have a working xzm, but it’s bigger than 130mb, for keepassxc a weird big size. Thanks in advance.
Cheers

[Ed_P]

I have a keepassx module, 2.0.3, that is only 516.1KB. Not sure what the XC version is.

USM LIB.txt errors can be caused by bad mirrors. Did you update the databases before running USM

An automated USM mirror fix is sesm.sh which is described here. [INFO & SCRIPT] Slackware Mirror Settings for USM


-update-

I just tried building keepassxc and it requires a bunch of dependencies and I ended with the LIB.TXT error also. It looks like keepassxc requires some libreoffice packages and they can indeed be huge. Are you sure the keepassx module won't work for you?

[AcnapyxoB]

Try AppImage:
https://github.com/keepassxreboot/keepa ... 4.AppImage

[Ed_P]

How does one use an AppImage with Porteus?

[ncmprhnsbl]

How does one use an AppImage with Porteus?

make it executable and run it... ie. in term(in the directory where the appimage is):

Code: Select all

$ chmod +x KeePassXC-2.3.3-x86_64.AppImage
$ ./KeePassXC-2.3.3-x86_64.AppImage

if it doesn't work, the output may give some clue about what's missing..

[user0815]

@Ed: Yes, keepassx works for me, but its latest version 2.0.3 was more than two years ago, and I like to try the new one which has active development, keepassXC is a fork and actively maintained.

@AcnapyxoB and ncmprhnsbl: thanks a lot for your advises. It works great for me. The only drawback I see now is that I cannot create a module out of the ApImage for now, maybe there is a way. Thanks again.

ps. itś a pity that such useful information is not easy to find for newbies like me.

[Ed_P]

ps. itś a pity that such useful information is not easy to find for newbies like me.

Hopefully now it won't be for others.

The only drawback I see now is that I cannot create a module out of the ApImage for now

I'm not sure you need to but it would be convenient.

https://appimage.org/ I suspect we will be seeing more of these files.

Or not. OpenShot not working

[ncmprhnsbl]

The only drawback I see now is that I cannot create a module out of the ApImage for now, maybe there is a way.

once it's executable it will run like any script or binary, so:
(from the same directory as the appimage, as root user)

Code: Select all

mkdir -p /tmp/build/usr/bin
cp -a KeePassXC-2.3.3-x86_64.AppImage /tmp/build/usr/bin
mkdir -p /tmp/build/usr/share/applications
echo -e "[Desktop Entry]\nName=KeepPassXC\nExec=/usr/bin/KeePassXC-2.3.3-x86_64.AppImage\nType=Application\nTerminal=false\nCategories=Accesories;Utility;" > /tmp/build/usr/share/applications/keeppassxc.desktop
dir2xzm /tmp/build KeePassXC-2.3.3-x86_64-AppImage.xzm 

[Ed_P]

Show off. A interesting approach though. I will have to study it.

This is what I used to create a module.

Code: Select all

#!/bin/bash

# Save AppView as a mod file
# Place file in the /tmp folder and make executable via chmod +x first

# For KeePassXC execute it one time and choose the Install option before running this. 

MOD=KeePassXC
VRSN=2.3.3       
TO=/mnt/sda6/porteus4.0/Optional                             # Change to fit your environment #

if [ `whoami` != "root" ]; then
    echo "Enter root's password"
    su -c "sh $0 $1"
    exit
fi

if [ -d /tmp/mod/ ]; then
   rm -rf /tmp/mod
fi
mkdir -p  /tmp/mod

# copy mod files

cp -a --parents /tmp/*AppView                                                                      /tmp/mod/
cp -a --parents /home/guest/.local/share/mime/application/x-keepass2.xml                           /tmp/mod/
cp -a --parents /home/guest/.local/share/mime/packages/keepassxc.xml                               /tmp/mod/
cp -a --parents /home/guest/.local/share/applications/appimagekit-org.keepassxc.KeePassXC.desktop  /tmp/mod/
cp -a --parents /home/guest/.config/keepassxc/keepassxc.ini                                        /tmp/mod/
cp -a --parents /home/guest/.local/share/icons/hicolor/*/*/*keepassxc*.png                         /tmp/mod/

echo
du -ch  /tmp/mod/  
echo Changed files copied. Press Enter to create module, Ctrl+C to exit.
read

du -h   /tmp/mod/
echo 
dir2xzm /tmp/mod /tmp/$MOD.xzm     &&     rm -rf /tmp/mod

echo 
ls -sh  /tmp/*.xzm
#read

DIR () {
ls -lght --time-style long-iso $1 | awk '{print $5,$6,$4,$7}'
}

echo
echo Press Enter to copy /tmp/$MOD.xzm to $TO, Ctrl+C to exit.
DIR     /tmp/$MOD.xzm 
if [ -f /$TO/$MOD.xzm ]; then DIR /$TO/$MOD.xzm; fi 
read
cp      /tmp/$MOD.xzm  /$TO
echo Finished!
read  

[ncmprhnsbl]

ok, so presumably when this appimage launches it offers to create/install a .desktop file.. (or does so automatically)(EDIT ok "choose install option")
and it's Exec= line points to whereever you launched it from (which would need to be outside the union(live filesystem) if you're not using changes/save file)(EDIT ok "TO=/mnt/sda6/porteus4.0/Optional" )

[Ed_P]

Actually once the xzm module is Activated the KeePassXC desktop Exec points to the AppImage file in /tmp.


-update-

Exec="/tmp/KeePassXC-2.3.3-x86_64.AppImage" %U

There is also a section of the desktop file that I don't understand how it gets invoked.

[Uninstall]
Name=Remove desktop integration for KeePassXC
Exec="/tmp/KeePassXC-2.3.3-x86_64.AppImage" --remove-appimage-desktop-integration