#869 Database Lock Timer Setting Not Working

open
nobody
None
5
2012-09-17
2010-05-28
Jim Frame
No

This is an item that I thought was going to be fixed in v3.22 (3464), but it's still not working on my Windows XP SP3 system. The setting defaults to 5 minutes. When I change it to 120 minutes and save the database, the setting is retained during the Windows session. However, when Windows is shutdown and relaunched, the timer is once again set to 5 minutes.

Discussion

  • DrK
    DrK
    2010-05-29

    You and me both - especially as I thought I had fixed it!

    I will look again.

    David

     
  • DrK
    DrK
    2010-05-31

    I can't reproduce this. Works for me. I did find that if you change a preference stored in the database, it did not enable the Save toolbar button or the Save menu item in the File menu. I have now corrected this at revision 3473.

    Note the Idle Timeout value is a database preference and stored within the database header. It can be different for different databases.

    Also, PaswordSafe does not store anything in memory between starting and stopping an instance of it. I therefore cannot understand why shutting down Windows and restarting it will have any different effect to completely closing PasswordSafe and restarting it within the same Windows session.

    David

     
  • Jim Frame
    Jim Frame
    2010-05-31

    "I did find that if you change a preference stored in the database, it did not enable the Save toolbar button or the Save menu item in the File menu. I have now corrected this at revision 3473."

    That may have been the problem -- I've been clicking on the disk icon after changing the timer value, but upon looking closer it's grayed out. I also noticed that File|Save and the disk icon are grayed out even after adding a new database entry. I had to add one and then delete it before File|Save or the icon became available.

     
  • DrK
    DrK
    2010-06-01

    Ahhh - if that was the problem - I will close this Bug Report as fixed at revision 3473 (actually I have made it 'Pending' and the system will close it automatically in about 2 weeks).

    I can upload a version for you to test if you really need it before the next formal release. Let me know by adding a comment to this Tracker item.

    David

     
  • Jim Frame
    Jim Frame
    2010-06-04

    At this point I'm not sure what the problem is. I've gone through several power-off reboot cycles and I'm still seeing the timer reset to 5 minutes whenever I log on and launch the application. There's definitely a problem with the File|Save process, as editing the database doesn't result in any save options except Save As. I've tried doing a Save As to the same filename, but that hasn't altered the timeout setting behavior.

     
  • DrK
    DrK
    2010-06-04

    Do you want me to upload a version at revision 3473 for you to try?

    David

     
  • DrK
    DrK
    2010-06-04

    Following the problem with revision 3470, as documented in Bug Report 3010541, and the lack of the necessary files on my system to analyse the dump, I have recreated a version at this revision 3473 and archived the necessary files should anyone get dump testing this build.

    I will keep these files either until this problem is solved or the next formal release is made available.

    The rebuilt version can be found at:

    http://pwsafe.org/tmp/pwsafe_V3.22.01.3473-20100604.zip

    Please let us know if this fixes your issue.

    David

     
  • Jim Frame
    Jim Frame
    2010-06-04

    In installed 3473, and will report my experiences. Thanks!

     
  • Jim Frame
    Jim Frame
    2010-06-04

    Um, make that "I've installed 3473, and will report my experiences."

     
  • DrK
    DrK
    2010-06-12

    Anything to report? Is it fixed? Can I close this Tracker item?

    David

     
  • Jim Frame
    Jim Frame
    2010-06-12

    I'm afraid I'm still experiencing the problem: upon every reboot and launch of PWS the timeout setting is 5 minutes. I change it to 120 minutes, and it remains at that value until the end of the Windows session, but goes back to 5 minutes at the next login and launch.

     
  • DrK
    DrK
    2010-06-12

    Then I am sorry but I can't do any more on this - it works for me. Maybe Rony can reproduce this problem.

    Note: This is a database preference and so after changing its value - you MUST save the database to retain the new value.

    You may want to try the latest version as it has some extra fixes in it (unrelated to your problem). It is at:

    http://pwsafe.org/tmp/pwsafe_V3.22.01.3478-20100612.zip

    David