Summary
On some Fedora setups, LUKSbox is installed correctly but the in-app file
browser does not show up / does not display mounted vault contents. The vault
itself appears to open fine, only the file manager view is affected.
Key finding
The problem correlates with how the system reached Fedora 44, not with
Fedora 44 itself:
- ✅ Fresh Fedora 44 installs: file browser works correctly.
- ❌ Systems upgraded from Fedora 43 → Fedora 44: file browser fails to show.
This was confirmed by @Hxs2fJKjYZ, who reproduced the failure on multiple
upgraded machines while a clean install worked. It suggests something stale left
behind by the upgrade (leftover config, a dangling/mismatched dependency, GTK /
xdg-mime / file-manager integration, or cached state) rather than a regression in
the LUKSbox build itself.
Impact
If confirmed, any system upgraded into Fedora 44 (rather than freshly
installed) may be affected, which is a fairly large potential population.
Environment
- LUKSbox version:
- OS: Fedora 44 (reached via in-place upgrade from Fedora 43)
- Desktop environment / file manager:
- Install method:
Steps to reproduce
- Upgrade a machine from Fedora 43 to Fedora 44.
- Install / run LUKSbox.
- Open a vault.
- Observe that the file browser does not appear / shows no contents.
Expected behavior
The file browser displays the mounted vault contents, as it does on a fresh
Fedora 44 install.
Actual behavior
File browser does not show up on upgraded systems.
What would help us diagnose
We don't have many samples of this yet. If you hit the same issue, please share:
- Whether your Fedora 44 was a fresh install or an in-place upgrade.
- Desktop environment and default file manager.
- Any console / stderr output when launching LUKSbox from a terminal.
- Output of relevant integration state, e.g.:
echo $XDG_CURRENT_DESKTOPxdg-mime query default inode/directory- whether the system file manager is reachable
- If you found a workaround that fixes it on an upgraded system, please post it —
we'd be grateful.
Notes
Unrelated to this bug, v0.2.2 is in packaging with transfer-speed improvements
(deferred flushes for large multi-file transfers) plus an opt-in "eager sync"
option, per-inode dirty tracking, and better DirectFido handling in the GUI.
Summary
On some Fedora setups, LUKSbox is installed correctly but the in-app file
browser does not show up / does not display mounted vault contents. The vault
itself appears to open fine, only the file manager view is affected.
Key finding
The problem correlates with how the system reached Fedora 44, not with
Fedora 44 itself:
This was confirmed by @Hxs2fJKjYZ, who reproduced the failure on multiple
upgraded machines while a clean install worked. It suggests something stale left
behind by the upgrade (leftover config, a dangling/mismatched dependency, GTK /
xdg-mime / file-manager integration, or cached state) rather than a regression in
the LUKSbox build itself.
Impact
If confirmed, any system upgraded into Fedora 44 (rather than freshly
installed) may be affected, which is a fairly large potential population.
Environment
Steps to reproduce
Expected behavior
The file browser displays the mounted vault contents, as it does on a fresh
Fedora 44 install.
Actual behavior
File browser does not show up on upgraded systems.
What would help us diagnose
We don't have many samples of this yet. If you hit the same issue, please share:
echo $XDG_CURRENT_DESKTOPxdg-mime query default inode/directorywe'd be grateful.
Notes
Unrelated to this bug, v0.2.2 is in packaging with transfer-speed improvements
(deferred flushes for large multi-file transfers) plus an opt-in "eager sync"
option, per-inode dirty tracking, and better DirectFido handling in the GUI.