FS#65579 - KeePass crashes on start

Attached to Project: Community Packages
Opened by Yao Mitachi (yaomtc) - Friday, 21 February 2020, 05:43 GMT
Last edited by Giancarlo Razzolini (grazzolini) - Thursday, 02 April 2020, 08:13 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Giancarlo Razzolini (grazzolini)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
When I try to launch KeePass, a rectangle briefly appears on the screen, then disappears. I have attached terminal output.

Additional info:
* keepass 2.44-1
* See keepass-output.txt

Steps to reproduce:

1. Try to launch KeePass
2. KeePass does not launch
This task depends upon

Closed by  Giancarlo Razzolini (grazzolini)
Thursday, 02 April 2020, 08:13 GMT
Reason for closing:  Not a bug
Comment by Klaus Frank (agowa338) - Friday, 20 March 2020, 13:52 GMT
I get the same error. I've attached an strace of keepass starting.
   strace.log (946.5 KiB)
Comment by Klaus Frank (agowa338) - Friday, 20 March 2020, 14:02 GMT
`sudo keepass`
Therefore some permissions seam to be off.
Comment by Giancarlo Razzolini (grazzolini) - Friday, 20 March 2020, 14:26 GMT
What's the need for running keepass with sudo? Anyway, I'm looking at this.
Comment by Klaus Frank (agowa338) - Friday, 20 March 2020, 14:32 GMT
> What's the need for running keepass with sudo?

There is none, I just entered `keepass` into the wrong console window...
But it works with sudo...
Comment by exmatrikulator (exmatrikulator) - Friday, 20 March 2020, 22:23 GMT
thanks for the hint.
it has nothing to do with root (permissions). it's working, because you switched the user with a (nearly) new ".conf" dir.

env -i DISPLAY=:0 HOME=/tmp/keepass_home XAUTHORITY=/tmp/xauth-1000-_0 keepass

is working with my current user. so something is wrong with my home dir.
Comment by Klaus Frank (agowa338) - Saturday, 28 March 2020, 20:16 GMT
Thanks for the hint with the home directory, it turned out, a simple:

rm -rf .config/KeePass

solves the issue.
Comment by Giancarlo Razzolini (grazzolini) - Monday, 30 March 2020, 17:06 GMT
Could it be there were wrong permissions on that directory? As I've said, running sudo keepass is bad, because files will be owned by root. I'm not sure you needed to delete it, but good to know it works. I want to hear now from the OP to close this issue.
Comment by Yao Mitachi (yaomtc) - Thursday, 02 April 2020, 04:12 GMT
I have since fully switched to using KeePassXC. However having reinstalled KeePass, and seeing that the issue was still present, I tried deleting the ~/.config/KeePass folder. Can confirm this works. You can close this.

Also, I'd recommend anyone using KeePass right now try KeePassXC instead, especially with the auto-fill browser extensions. So much of a better experience. Thanks to whoever recommended it a month or so ago.

Loading...