Hello,
I noticed that Keepass v2.61 has been in unstable and testing for quite a while now. Is there a reason that it is not passed through to stable yet?
Several sources say that Keepass isn’t the recommended app on Manjaro due to the dependencies on Mono:
(KI generated content)
On Manjaro Linux, KeePassXC is the preferred and natively supported option, as it is a standalone Linux application, whereas the original “KeePass” requires a Mono dependency (Windows emulator) and therefore often leads to crashes.
There are two main installation methods:
Native (Recommended): Install KeePassXC directly via the package manager, as it is available in the extra repository and requires no external dependencies:
sudo pacman -S keepassxc
# Or via the Pamac graphical interface:
pamac install keepassxc
Personally i never used Keepass, since years, KeepassXC is our solution here.
7 Likes
There is no particular schedule of when stable is updated from testing - it will happen when testing is considered ready, and there is no way to predict it. If you are in a hurry you can switch to the testing branch: Switching Branches - Manjaro
2 Likes
Unfortunately, keepassxc is not exactly the same. Like when it comes to synchronizing the databases. So in some cases (like mine) switching to keepass is not an option.
Since it is in the repositories, it doesn’t matter if it is the recommended app. It is available and people might use it 
.
Based on some earlier discussions, it seemed like the maintainer abandoned it. And since this is some part of software that I consider sensitive, I already updated to 2.60 by creating my own PKGBUILD a while ago. Thus I rather do that again than switching branch.
However, I noticed that keepass was bumped to 2.61 in the arch repositories about a month ago and it is in unstable and testing for a while already. So I am simply curious if the maintainer have a particular reason, e.g. some issues I am not aware of to keep it back…
It will likely be part of the next stable snap.
Judging from the activity in Announcements > Testing Updates it may be just around the corner 
- Unstable is synced with an up-to-date Arch Linux mirror at reasonable intervals
- Testing branch is a snapshot of unstable
- Stable branch is a snapshot of testing branch
So to call Manjaro Linux rolling is a stretch - it is more like a stabilising process - in fact Manjaro unstable branch is the only real rolling set of packages.
- testing is a snapshot of unstable
- watching the issues accumulating in Announcements > Testing Updates
- a lot of users are relying on the above process to stablise
- when the testing branch has stabilised
- testing is snapped to stable branch
Creating a snapshot of testing to stable is usually delayed when Nvidia drivers is introducing issues for the current stable branch but there may be other issues known to the release manager which is @philm.
@philm puts a great amount of work into ensuring the stability of stable branch and this will reflect onto all packages waiting in testing branch.
This ensures that stable branch is as stable as it can be at the given point in time.
3 Likes
KeepassXC comes with KeeShare which works perfect.
Beside that you can use any sync tool you want. We are running it via Syncthing on all devices.
2 Likes
The last Manjaro stable update was at 2026-03-23 and keepass was last updated on Arch at 2026-03-18, see Arch Linux - keepass 2.61-1 (any)
Now, updating/rolling on Manjaro stable isn’t simply by delaying each package for two weeks or so (this would be nonsense) but works (a little simplified) by taking fixed snapshots as described in the wiki. Fast tracked security patches are forwarded directly - these aren’t part of the normal rolling.
Since the last stable snapshot was taken before 2026-03-18 (it has to be on the testing branch for some time to make sense) and since keepass 2.61 isn’t a fast tracked security patch this answers why it isn’t available on the stable branch yet.
There isn’t anything held back - if you prefer to get each package rolled out on its own immediately as it is done on Arch (so you handle the updating on your own like in “user-centric”) you can either switch to Manjaro unstable (read as constantly changing not as constantly breaking) or Arch itself (or some derivatives that go to the Arch stable repos directly).
5 Likes
Perfect, seems I was just a bit too impatient 
Okay, that might be true. In my opinion this results in a series of snapshots which remove the need of upgrades. I don’t like aving to practically reinstall everytime a new major release comes along and having to face a lot of big changes at once.
So for me the update policy of Manjaro is perfect and the reason, why I use it since many years.
So far none of the mobile variants I have looked at support KeeShare. I think there are some that are working on implementing KeeShare. So hopefully it will arrive not too far in the future.
And Syncthing cannot synchronize two databases if both have been changes individually.
I definitely do not prefer that (at the moment) on the machines I am administering. 
I might switch to testing some point.
It does seem that there has been some unlucky timings that made it feel like the update was lagging behind longer than usual. Thank you for clearing things up.
1 Like
The definition of rolling release doesn’t contain anything of how it is rolled - likewise the point release model doesn’t say anything about when there will be the next release - in half a year, in a year or are there service packs like some enterprise oriented distros do. There are other rolling releases like Solus for instance. Rolling itself doesn’t mean you have to roll out each package as soon as it builds
3 Likes
Quite true - my phrasing was not the best - and Manjaro’s rolling model has longer intervals between rolling the updates.
As @philm has said repeatedly
Manjaro is not about chasing Arch Linux
1 Like
From what i understand is that KeeShare is working properly between different devices. Haven’t used it so far.
Syncthing worked the last three years for me perfectly. I’ve shared two DB files across four different devices (2 Android, 2 Linux) plus a backup on my NAS. It even worked if my wife and I edited the files the same time. Only con is that only the last change has been updated. But that’s the nature of every sync tool.
Right now i am not using Syncthing any longer because i’ve changed the cloud provider which has a native sync tool.
Sorry for hijacking. Your question about the held back package is still valid and requires to be answered.
I’m not sure exactly what differences would prevent you changing (just because is valid) but I was using a database between KeePass and KeePassXC up until about a year ago with zero issues. The only reason I didn’t change the KeePass was because of a custom plugin I wrote for a specific use case that didn’t have the same functionality on XC.
1 Like
I think he’s referring to the sync features of Keepass
As in this? Synchronization - KeePass
KeePassXC does the same thing flawlessly. I’ve used it across 5 devices, all open at the same time from cloud storage (both dropbox and google drive). The app prompts to merge when it detects changes and I’ve never had a problem with database corruption or loss of entries.
1 Like
Exactly
Merge database only updates one database and leaves the other untouched. Since I have 3 databases, using merge to keep all three at the same state adds more complexity, than simply doing two “synchronize database” from the same instance of Keepass.
Keeshare on the other hand seems powerfull and addresses some shortcomings of the synchronize feature (as far as I can tell). However, it needs some learning and planning.
Currently, I don’t have the time and motivation for that 
And as a third reason that keeps me with KeePass is after using it since version 1, I am just familiar with it. So the activation energy to get me to chabge is quite high
Although, If one of them solves the Autotype on Wayland, so that KeePasa(XC) can detect the windows again, I will definitely use that one 
For a password manager that is a worst-case scenario in my eyes.
1 Like
As in the Secret Service Integration in KeePassXC? KeePassXC: User Guide
It’s working for me on KDE
More like for websites, and other software like steam, discord, and more that I can’t remember on the spot now.
Don’t ask me, ask the thread opener
Still a while away I believe. But KeePassXC have had some success in testing. I too am looking forward to that being solved.
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.