I can't get Keepassx to work on Karmic

Bug #535236 reported by WindyWeather
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
keepassx (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: keepassx

cannot make a working kdb file with keepassx 0.4.1 under Ubuntu 9.10.
I've tried on two different systems. One with a fresh install of keypassx
0.4.1 from the software center.

Following steps were used:

1 Run keepassx.
2 click cancel to get back to a blank screen.
3 click the new icon to get a SET MASTER KEY dialog
4 enter a password
5 click OK
6 enter the password again
7 click ok.
8 Make a new entry using the add new entry dialog
9 fill out the entry
10 close the entry dialog
11 Save the database as test.kdb
12 Close Keepassx
13 run keepassx again
14 navigate to the keypass file that was saved - if the keyfile does not
show it.
15 enter the password as before
16 Observe the error that says the Hash test failed. The key is wrong or
the file is damaged.

The attached file has the secret "secret" with no quotes.

So keepassx is completely useless as far as I can tell.

thanks,

windy

Revision history for this message
WindyWeather (windyweather) wrote :
Revision history for this message
Daniel Hahler (blueyed) wrote :

I cannot reproduce this here.
btw: I do not understand the second point: when starting KeePassX, I get straight to the main window, nothing to cancel. And what black screen?

I can verify however that opening your test file fails, with the error you've mentioned.

Saving a new file myself works however. I'm attaching mine for testing. Password is 12345.

Changed in keepassx (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Daniel Hahler (blueyed) wrote :

(I'm using Lucid, but keepassx 0.4.1-1, too)

tags: added: kernel-series-unknown
tags: removed: kernel-series-unknown
Revision history for this message
WindyWeather (windyweather) wrote :

"black screen" [sic] that was blank screen. I mean the main window with no contents. When I run keepassx I get a dialog that asks for the secret and gives me that last file I opened. I cancel this screen to create a new file. I use the "New file" button on the tool bar. This presents a dialog to set the secret.

Revision history for this message
WindyWeather (windyweather) wrote :

I just tried the test.kdb.kdb file with passphrase 12345 and it failed.
In this case I used a launcher on the taskbar and then browsed to the key file and entered the passphrase.

But then I tried it another way and it worked. To have it work, double click on the key file and enter the passphrase in the dialog.

So. To have keepassx fail, launch keepassx with a launcher on the taskbar. If you do this, and then enter a passphrase and browse to a file, you always get HASH FAILURE.

If instead, you click on a file created in the above method, you get a dialog with a disabled keyfile browse line, and no indication which file you are opening, but if you enter the correct passphase the file opens correctly.

I have tried my file above and several other files and they all worked correctly as well.

So, the bug is apparently a problem with the correct processing of the passphrase in several cases when launching keepassx.

cheers,
windy

Changed in keepassx (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Daniel Hahler (blueyed) wrote :

Thanks for your investigation.

I guess it's related to the environment the process is running in then. Can you create a script like the following, and call it both from the launcher and normally, then append the outputs here? (or diff them manually and tell about the difference)

#!/bin/sh
set > /tmp/bug-env-$$

You should have two files then with $$ being replaced by a number (the process ID).

Changed in keepassx (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
WindyWeather (windyweather) wrote :

Ok. Here's an archive of the files based on your request.

Revision history for this message
Robert Roth (evfool) wrote :

Thank you for reporting this bug to Ubuntu. Karmic reached EOL on 30 April 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Oneiric and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

Changed in keepassx (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for keepassx (Ubuntu) because there has been no activity for 60 days.]

Changed in keepassx (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.