asbru-cm/asbru-cm

AppImage release not supporting KeePassXC connection

Open

#1157 opened on Sep 5, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Perl (1,090 stars) (144 forks)batch import
bughelp wantedpackaging

Description

Describe the bug AppImage release not supporting KeePassXC connection

Tried on the new Debian Trixie installation as well as on the Debian Bookworm installation - where Asbru was installed system-wide and the system-wide installation was working while AppImage was not. It has to do something with AppImage generally - having the dependencies in its virtual system package, I guess. Anyway Is there a way to override?

Anyway, the AppImage is showing the keepass-cli binary normally loaded and the right version. As well as correct paths to the Database and Key file....

To Reproduce Steps to reproduce the behavior:

  1. Install the AppImage version with the same config you're using (in case you use KeePassXC connection).
  2. Connections will be failing, declaring they haven't found any passwords from the database
  3. When you try to pull the database to re-select the right entry, the Database popup will be blank (no entries visible)

Expected behavior It should work as usual

Environment (please complete the following information):

  • OS: Debian Bookworm/Trixie
  • Ásbrú Version 6.4.0
  • KeePassXC cli 2.7.4 / 2.7.10

Contributor guide

Tech stack
None
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
AppImage packagingKeePassXC CLIasbru cm codebase structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate how the AppImage is built and packaged in the repository. Check the keepassxc integration code in the asbru cm codebase, specifically the part that calls keepassxc cli. Look at differences between system wide installation and AppImage to identify missing dependencies or path issues. The issue reporter mentions that the AppImage shows the keepass cli binary and correct paths but still fails, so focus on the actual execution environment inside the AppImage.