chipass: init at 2026.09.0

[provokateurin]

Inits ChiPass, a hard fork of KeepassXC. The packaging code and tests were copied from KeepassXC and adjusted according to https://codeberg.org/ChiPass/ChiPass/src/branch/main/INSTALL.md.

For some reason the theming is off:

I'm not sure if that is an issue with the packaging or upstream (because there is no theme switcher in ChiPass, so it could be intentional?).

I can confirm that the KeepassXC browser extension just works OOTB and so far there are no plans to fork it as well, so no additional changes are needed for it: https://codeberg.org/ChiPass/ChiPass/issues/144

CC @whitequark

Things done

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.
• Follows the automation/AI policy.

[provokateurin]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 562875
Commit: a1069773cf017e1d2c753f27486d826bdcdbc414

---

x86_64-linux

✅ 1 package built:

• chipass

[whitequark]

The theming is definitely off. We did change the theme code (for branding and code quality reasons) but it's not supposed to look like Win95. If you run the flake in the repo, does it pick up a theme for you?

[provokateurin]

I built and ran the flatpak from the repo and it doesn't have the same issue (it just looks like KeepassXC in the screenshot above). There is very little difference between the packaging code for KeepassXC and ChiPass, so I'm not sure where the issue is. It could be related to the Qt6 migration, but I'm not sure how to figure that out.

[arcayr]

haha got distracted and sniped. thanks stardew valley.

the theming issue above doesn't happen to me if i build yours, same as mine. are you doing wonky stuff with your qt themes?

yours:

---

mine:

---

the flatpak (light mode because it's in flatpak and won't be picking up themes):

---

i think mainProgram will need to be ChiPass, not chipass, for this. the compiled binaries are as such (nix run .#chipass here will fail - check the result dir).

everything else works by my eye. i'm not super pumped about the firefox bridge thing (i don't really like it in keepassxc either ... weird crossover of concerns), but that's a minor thing.

[provokateurin]

are you doing wonky stuff with your qt themes?

No, as far as I know.

i think mainProgram will need to be ChiPass, not chipass

That's correct, I will fix it.

[arcayr]

No, as far as I know.

if you set QT_STYLE_OVERRIDE=Fusion, does it show up with the ~normal theme?

if i set it to Windows, which is the other available option to me, it shows up looking like the op (but dark mode):

[provokateurin]

if you set QT_STYLE_OVERRIDE=Fusion, does it show up with the ~normal theme?

With that it looks like in your screenshots, but still not like it does for me in the flatpak (using the KDE Plasma Breeze theme).

[provokateurin]

$ QT_STYLE_OVERRIDE=Breeze ./result/bin/ChiPass
QApplication: invalid style override 'Breeze' passed, ignoring it.
	Available styles: Breeze, Windows, Fusion
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/91268/root")

[arcayr]

i've dropped a question to the kde big brains on matrix. should hopefully have an answer in a bit, as i'm nowhere near familiar enough with qt to identify the specific issue.

another user has replicated this on their own kde install, so it's not just you.

[whitequark]

How do I replicate the failure?

[arcayr]

edit: the below assumes you have the flakes and nix-command cli, but if you can use the flake in the chipass repo you should be set on this front. not 100% sure where you are on the nix scale so apologies if any of this is obvious, just wanted to get it clear from the get-go.

---

How do I replicate the failure?

sorry, i was going to message you on fedi but didn't want to bother you with something that is probably some niche nix packaging bug. 😅

nix run github:provokateurin/nixpkgs/chipass-init#chipass

will pull this pr, build it, and run it.

if you're wanting env vars in you'll also need --impure:

QT_DEBUG_PLUGINS=1 QT_STYLE_OVERRIDE=Breeze nix run --impure github:provokateurin/nixpkgs/chipass-init#chipass

i'm not on kde but if i inject breeze into my env w/ nix shell nixpkgs#kdePackages.breeze, and then run the second command, it shows up using breeze.

if you want the underlying dev env to go full manual you can nix develop github:provokateurin/nixpkgs/chipass-init#chipass. each of the steps the nix deriv takes can be done manually then:

unpackPhase && patchPhase && configurePhase;

# ... do whatever 

buildPhase;

normally it'd be something like abi compat issues with the version of qt, but that doesn't seem to be the issue here because it works with the QT_STYLE_OVERRIDE command, and i peeped the chipass source which doesn't seem to be doing anything odd with qt.