Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Unable to open Safes #76

Closed
rampra opened this Issue Feb 18, 2012 · 26 comments

Comments

Projects
None yet
3 participants

rampra commented Feb 18, 2012

Hi

I have been using Password Gorilla 1.5.3.6 on my MacBok Pro Mac OS X 10.6.8 for a while and suddenly for the last 2 weeks I am unable to open any of the existing safes. It was always remembered my last safe used and I would just type in the master combination to open. Now the database field is blank and even f I point to the folder where I have the safes, it would not let me select them. It allows me to create new one but not let the old one open or merge

Please help I have a number of entries that I don't have access to now

Than you
Ram

Collaborator

rich123 commented Feb 18, 2012

This is very odd. Did you change your PWGorilla version two weeks ago? Or were you using 1.5.3.6 when you were still able to open the saved safes?

What happens when you try to browse to the folder where the safes are by using the button next to the selected database field on the PWGorilla initial screen? Will it allow you to select a safe?

If not, can you check something. Check the access permissions on the safes themselves using whatever Mac tool allows you to check file access permissions. It may be that the files are not set to allow "reading" which might be why they are not "selectable". This is however just a pure guess on my part at the moment.

rampra commented Feb 18, 2012

This may give some clues. I installed 1.5.3.3 on April 15 2010 and using all along. My safe was last modified Feb 11, 2012 and last accessed Feb 13, 2012. File has no extension and read & write enabled for me.

Either 0n 13th or soon after I downloaded 1.5.3.6 thinking it would help. Now there is no diff between them when i try to open the old database. They don't allow me to choose my database or any file for that matter. I tried open, import and merge. I also copied the original file and I have .bak files as well. What could be wrong?

rampra commented Feb 18, 2012

Well when I typed the filename manually rather than using the dialog box, i managed to open the database

Another question - whenever i minimize or timeout, there is no way for me to unhide / restore the app on Mac. I have to force quit and re-open. how do i overcome this issue?

Collaborator

rich123 commented Feb 18, 2012

File has no extension and read & write enabled for me.

Can you try changing the names to have an extension of ".psafe3". The initial default for PWGorilla's open file dialog window is to only show files ending in ".psafe3" or ".dat" (the older psafe2 format). If there appears to be no files from which to pick in the open dialog, this might be a possible reason.

Another question - whenever i minimize or timeout, there is no way
for me to unhide / restore the app on Mac. I have to force quit and re-open.
how do i overcome this issue?

On this item, I am unsure of an answer, as I do not have access to a MacOS system with which to test. Is there any standard way under MacOS to obtain a list of running programs and unminimize them? Something along the lines of Alt+Tab for Windows?

In any case, if it is completely hidden, then something is going wrong, I just do not know what given my lack of a MacOS system. Zdia does have access to a MacOS system, so hopefully he will be better able to answer this question than I.

rampra commented Feb 19, 2012

Thanks Rich; I am sure the problem I mentioned about getting Gorilla into focus should have been a known issue. There isn't any easy way for me to find, view logins after the set time-out period. Find brings the dialog box but I cannot type anything; I cannot scroll through the entries either as there is no way to unhide that. The best option is to quit Gorilla after each use and open again when i needed. Thank you anyway and let me know if I should close the original issue here and open this as a new issue

Collaborator

rich123 commented Feb 19, 2012

Were you able to open/access your original password safes? Did you try adding a .pwsafe3 extension? Did that help in any way?

Find brings the dialog box but I cannot type anything;

When you say "Find", do you mean PWGorilla's "Find login" dialog, or the MacOS X equivalent of the old MacOS Finder? Because if it is the PWGorilla "Find" dialog, then not being able to type into it is normal in a "locked" situation. There is supposed to be a "locked database" window during locked state (looks very similar to the initial open database window) into which you would enter your master password to "unlock" PWGorilla.

Overall I am confused as to exactly what you see when PWGorilla locks itself. The expected behavior is for all open windows to be removed from the screen, and a single "locked database" window replaces them. That single "locked database" window is supposed to allow you to enter your master password to unlock and bring back all the windows that were opened when it locked itself. If you are getting other odd (and unusable) windows open then something is going wrong, I just do not know what that is yet.

rampra commented Feb 19, 2012

  1. Yes, I am able to open/access my original password safes either my manually typing the filename that has no extension or through the Open Dialog box pointing to file with the proper file name extension.
  2. I am referring to PWGorilla's UI. I have Lock when idle after x minutes set. Once PWGorilla locks / iconizes / hides the app, I am unable to restore the PwGorilla window to an usable interface. I could see it in the task bar, double-clicking it shows the app specific menu, but any dialog box that appears during that time is inaccessible. For e.g, I might get the open database dialog box but I cannot position cursor on Password field to type password. Or I could get to the Find command (all depends at which state it locked) but I cannot type anything in the Find field; I just cannot position cursor or set focus to the field. Effectively I need to force quit the application and restart fresh to search or add entries.

Hope this helps to understand the situation i encounter with the UI

Collaborator

rich123 commented Feb 19, 2012

  1. Good. Glad to hear that renaming the files worked.
  2. This helps. Something is clearly going wrong somewhere, because when you double click the task bar, you should get the "unlock" dialog, and you should be able to type into the password entry field. Or at least that is supposed to happen, but clearly is not for your system for some reason. Did PWGorilla always act this way, even with older versions, or is this a new occurrence with the new version?

rampra commented Feb 19, 2012

  1. Thank you
  2. It had always acted like this on my MacBook Pro / Mac OS X; the workaround I use is to quit PWGorilla after each iteration then open again from recent items
Owner

zdia commented Feb 19, 2012

@rampra:

I did the following hiding test on my mac:

  1. Lock it manually

Security -> Lock Now
In the "Database locked" dialog I pushed the yellow button for hiding it
Working with Mac software with Gorilla in background (icon visible in the task bar)
Right click on Gorilla icon
Choosing the top entry "Password Gorilla"
"LockedDatabase" dialog appears
Type master password
Gorilla is back working alright

  1. Waiting for timeout with LockDatabase dialog (Setting idle time to 1 minute):

result like in 1)

  1. enabled preference checkbox: iconify on autolock

And yes, issue confirmed: There is no menu option to return to PWGorilla with right click.

I will look for the cause.

rampra commented Feb 20, 2012

That helps; I am disabling iconify on autolock for now. I am able to restore / unhide the app.

I will watch out for the fix, thank you.

Owner

zdia commented Feb 20, 2012

@rampra

I have found a solution which works on my MacOSX 10.6.2.

Are you able to patch the source gorilla.tcl and run it with wish or would you need an executable version?

rampra commented Feb 20, 2012

Well I could try if you can give me the steps; I am not a developer by any means :)

Owner

zdia commented Feb 20, 2012

After you have downloaded, decompressed the tarball from https://github.com/zdia/gorilla/tarball/master and installed PWGorilla in a folder of your choice then you would patch the file sources/gorilla.tcl in adding before line 5001 the command

update idletasks

which will help to synchronize the Tk event-loop with the event-loop of Mac's Aqua. Finally the code would look like:

...
    #
    # Run dialog
    #

    update idletasks
    focus $aframe.mitte.pw.pw
    if {[catch { grab $top } oops]} {
        set ::gorilla::status [mc "error: %s" $oops]
    }

    if { $::gorilla::preference(iconifyOnAutolock) } {
        wm iconify $top
    }
...

You can launch PWGorilla by calling Wish and sourcing the file gorilla.tcl or you use the commandline by typing from inside PWGorilla's sources/ folder:

tclsh gorilla.tcl

My Snow Leopard 10.6.2 still has installed a Tcl/Tk environment per default. I don't know if newer OSX versions still support Tcl/Tk. But you can get ActiveState's community edition by free.

Hope it will work!

Owner

zdia commented Feb 20, 2012

Now the database field is blank and even f I point to the folder where I have the safes, it would not let me select them.

Supposed you mean the combobox in the Open dialog then an empty database list means that PWGorilla did not find the file gorilla.rc. It is per default in the folder

$HOME/Library/Preferences/gorilla.rc

Selecting databases causes no problems on my Mac because the native FileDialog is opening if I push the folder button in Gorilla's OpenDialog which is presenting me all existing files without extension filtering.

Owner

zdia commented Feb 25, 2012

@rampra

You can download for a test the following fixed MacOSX version:

zdia.de/packages/gorilla/1.5.3.6/gorilla_pre1537.zip

File selection is put per default to "*" so you can see and select all files and unhide after "iconify after autolock" should work, too.

rampra commented Feb 26, 2012

@zdia

Excellent, thank you very much. I downloaded and installed it but soon encountered an error: "Error: item node300 not found" and I am unable to choose either of the options OK | Skip Message | Details >>
I believe I encountered this when i tried to search an entry. Never seen this before. Any clue?

Collaborator

rich123 commented Feb 26, 2012

At the moment, no clue. Attempting a "find" in my test database using the above version simply returns "text not found" in the status line.

Can you attempt to reproduce the error? If you can learn the steps to reproducing it, then we can also reproduce it as well and thereby have a better chance of tracking down the cause.

rampra commented Feb 27, 2012

I believe these were the steps:

  1. Used Command-F to locate an entry
  2. Moved that entry to the root level by drag and drop
  3. Command-G to locate it again
  4. Encountered the error with hour glass; cannot clock any buttons
  5. PWGorilla locked the database with hour glass; unable to enter master key;
  6. Left the dialog boxes as is for advice

Thanks

Collaborator

rich123 commented Feb 27, 2012

Those steps repeat the error under Linux as well, although under Linux Gorilla is still usable and can be closed normally.

If you can't click any buttons, your only real choice is to kill/close via whatever method MacOS offers to kill off a broken task.

What I have learned to this point is the bug is triggered by performing a "find next" (command/control+G) after having done a drag-and-drop operation. If you do a standard "find" (command/control+F) the bug is not triggered. So until I locate, and fix the issue, you can avoid encountering it again by not performing a "find next" after a drag-and-drop.

rich123 added a commit that referenced this issue Feb 27, 2012

Fix for additional Issue #76 bug: Error: item node300 not found
Also fixed a "variable not found" error when attempting a "find next" before
any "find" operation.
Collaborator

rich123 commented Feb 27, 2012

@rampra - Commit 22c6d31 fixes the issue of "node not found" for me under Linux. Unfortunately I do not have the Mac package build scripts so you will have to wait for @zdia to build a new test Mac package for you to try.

rampra commented Feb 27, 2012

You guys rock; I will wait for the new package

Thank you

Collaborator

rich123 commented Feb 27, 2012

Alternately, if you want to try, you can edit the gorilla.tcl file beneath the gorilla.app dir in your applications directory and make the changes by hand that are in the commit.

Owner

zdia commented Mar 1, 2012

@rampra

Here is the newest package for the node300 fix:

zdia.de/packages/gorilla/1.5.3.6/gorilla_pre1537_1.zip

Could you test if you can select all the *.bak files?

rampra commented Mar 5, 2012

@zdia

Works great; I can move entry and still Cmd-G; I can open.bak or files too

Thank you

zdia added a commit that referenced this issue Mar 7, 2012

Owner

zdia commented Mar 7, 2012

You are welcome

@zdia zdia closed this Mar 7, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment