originallgb / keepassdroid

Automatically exported from code.google.com/p/keepassdroid
0 stars 0 forks source link

my data will not open. #161

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by hear...@gmail.com on 8 Feb 2011 at 8:36

GoogleCodeExporter commented 8 years ago
1. I open keepass version 1.9.1 on droidx
2. a file is listed and I am expected to put in password. Instead I get a 
choice of the two files to choose; 1. /sdcard/keepass/keepass.kdb  2. 
/mnt/sdcard/keepass/keepass.kdb  
After putting in my password to either file i get the following:  Root with two 
groups listed l. Internet  2. Email   Both are empty and all my data is nowhere 
to be found.
How doI retrieve my data asap.  Thank you.

Original comment by hear...@gmail.com on 8 Feb 2011 at 9:21

GoogleCodeExporter commented 8 years ago
I am have the same problem. Cannot find my Data.....HELP

Original comment by fzmicha...@gmail.com on 4 Sep 2011 at 2:31

GoogleCodeExporter commented 8 years ago
Wow, the audacity of users like you astounds me. "How do I retreive my data 
asap", the most arrogant and demanding, unknowledgable statement ever.

1: KeePassDroid is a reader. It is a READER. It did nothing with your "data". 
You tell IT where to find your data.
2: "ASAP". Or what? You'll f'ing sue someone? ASAP? That implies some kind of 
life threatening emergency or something. Should've understood that before you 
go willy-nilly tossing files around that you don't understand. News flash 
Blondie, but your Data (which typically implies multiple files, of which a KDBX 
file is only one) still will exist whereever your arrogant ass left it.

Meanwhile, I'm still trying to find a reason why I get a "Hashess didn't match" 
error when I try to open my kdbx file (from Dropbox) in keepassdroid. No love...

Original comment by falc...@gmail.com on 8 Oct 2011 at 9:48

GoogleCodeExporter commented 8 years ago
#3 2 ... LOL too funny

In addendum to this, I am using Samsung Galaxy S with Gingerbread. On my pc, I 
am using Keepass 2.20.1 and I just downloaded 1.99.7.2 on my phone. When I try 
to navigate to my .kdbx file on my skydrive, it won't find it. I have verified 
that the file exists, and it works from my pc just fine.

Any suggestions you have would be appreciated.

Original comment by jmp...@gmail.com on 30 May 2013 at 2:44

GoogleCodeExporter commented 8 years ago
Ok, I'm having a similar problem as jmp with the latest version 1.99.7.2. I 
have an old keepass 1.x .kdb file produced with KeepassX 0.4.6 that I'm trying 
to open from my Downloads folder. But when navigating to that folder the file 
just doesn't show up. Seems like a bug in 1.99.7.2 with listing files

Original comment by kil...@g7energies.com on 1 Jun 2013 at 4:34

GoogleCodeExporter commented 8 years ago
ok, this bug seems confirmed, I managed to open said .kdb file just when when 
manually TYPING in the path to it. Browsing to it just doesn't work, not matter 
what I ty

Original comment by kil...@g7energies.com on 2 Jun 2013 at 1:53

GoogleCodeExporter commented 8 years ago
Same issue with opening kdbx file on skydrive,  doesn't recognize it with 
keepassdroid app.  Any ideas?

Original comment by dmahl...@gmail.com on 6 Jun 2013 at 7:52

GoogleCodeExporter commented 8 years ago
Thanks #6, that's fixed my issue! It couldn't find my database file when I 
browsed to where I stored it but manually typing in the location worked.

Original comment by Nigelmul...@gmail.com on 16 Nov 2013 at 2:20

GoogleCodeExporter commented 8 years ago
I have Keypass version 1.27 on my PC (Windows 8) and just got a new Droid Maxx 
and installed keypassdroid.  I couldn't get my database.kdb file open either.  
I just tried typing it in as suggested by #6 and it retrieved my database.  
Thank you so much for sharing this bug.  

Original comment by JeriHar...@gmail.com on 11 Jun 2014 at 12:32