Why doesn't F-secure key work on Chrome 32.0.1700.107 m ?

Hello

 

I've been using F-secure key for while.

After Chrome updated itself to  version 32.0.1700.107 m

F-secure key doesn't work anymore, with following symptoms:

 

The password box opens up in top left corner and chrome selects everything and does not send correct password.

 

The only way to login with chrome is copy password from f-secure key and paste as plain text from popup menu in password field. 

IE 11 continues to work ok.

 

br,

tajuton  (= brain free)

 

Best Answer

Comments

  • RanSagyRanSagy Posts: 5

    This helped. Thanks!

  • JassuJassu Posts: 42

    And after the restart of chrome, it is again toggled off. So every single time you restart chrome you have to toggle that on again Smiley Sad

  • UkkoUkko Posts: 3,180 Superuser

    With Google Chrome 34 (?) that already indeed looks... like each start of browser.... that setting dropped to default.

  • JassuJassu Posts: 42

    Solution is to start chrome with "--force-renderer-accessibility" - unfortunately i havent found any other way to do this now...

    Ukko
  • Lauri_HLauri_H Posts: 59 Former F-Secure Employee

     

    Edit:

    disregard, hadn't read the whole thread through, just the last coupla previous ones, this was already mentioned before. 

     

    Hello, you can also do it after starting chrome:

     

    type: chrome://accessibility/ in the chrome address bar, and click "on" to turn it on. This seems to be a working workaround for now while waiting for chrome to fix their issue. 

     

     

  • JassuJassu Posts: 42

    Yes, but you have to do that every single time that you start chrome, starts to get frustrating...

    Ukko
  • UkkoUkko Posts: 3,180 Superuser

    Yes,

     

    How I can to understand for Google Chrome less than 34-version able to use "workaround" by settings (and it worked - how I remember);

    But with Google Chrome 34 that "accesibility-option" with each start of browser... dropped to default (?!); Workaround work - but it's can be a little hard to do always : )

     

    Possibly I not really love Google Chrome and do not often use that browser.... and just checked last words about "situation". Because probably - it's can be related already with Google Chrome 33 (if it was);

     

    Anyway - looks... that previously tips about "editing"-command-line for start browser... maybe work... and can be new "current" workaround (http://community.f-secure.com/t5/F-Secure-Key/Why-doesn-t-F-secure-key-work-on/m-p/49037/highlight/true#M370)

This discussion has been closed.