search

limpkin / mooltipass

Github repository dedicated to the mooltipass project
https://www.themooltipass.com
521 stars 113 forks source link

Chrome browser update leaves two copies of MP Client running #111

Closed dehne closed 10 years ago

dehne commented 10 years ago

When testing with MP 0.4 I went to check what version of Chrome on Win 7 64-bit I was running using the About Chrome tab. Chrome detected that it needed an update and I told it to go ahead and then, when the download was done, to restart Chrome.

When Chrome restarted, a second copy of the MP Client appeared. Not a big deal, of course, but a little odd.

limpkin commented 10 years ago

This happened because restarted everything except its running applications. You don't get the same problem by closing / restarting chrome :)

dehne commented 10 years ago

Yes, that's correct. But if a user of MP follows the "normal" Chrome update path, this small oddity will definitely happen.

jnwatts commented 10 years ago

Aye, MP should have some kind of output on the oled even without the flash programmed. Unfortunately the current firmware currently extremely short on code space, though we could maybe draw a big X or other simple programmatic pattern. On Aug 18, 2014 6:57 PM, "dehne" notifications@github.com wrote:

Yes, that's correct. But if a user of MP follows the "normal" Chrome update path, this small oddity will definitely happen.

— Reply to this email directly or view it on GitHub https://github.com/limpkin/mooltipass/issues/111#issuecomment-52567079.