Bug 63

Summary: SIT_TC9_TS20 - Installer stopped working during firmware update process
Product: TestProduct Reporter: Sahil Parbhaker <sahil.parbhaker>
Component: TestComponentAssignee: No one <sysadmin>
Status: RESOLVED FIXED    
Severity: major CC: brian.roberge, danielh, mohankumar.karruppusamy, nikhil.desai
Priority: Highest    
Version: unspecified   
Hardware: All   
OS: All   
Attachments: Logs
Screenshot of error message
Screen Shot
Log File
json

Description Sahil Parbhaker 2018-08-10 20:45:15 EDT
Created attachment 20 [details]
Logs

Steps to reproduce the bug

1.Activate sensor with reader
2.Go to update screen and click update
3.Let the reader update and disconnect ¾ of the update
4.Unplug the reader
5.Click the try again button
6.Plug the reader and click next to the update screen
7.While updating the reader update application stops working

Expected:
It should update the firmware to the latest version 2.8

Actual:
Installer stopped working at the start of update process

Platform
Windows 7 Ram 4gb 64 bit OS
Firmware Installer :LibreUpdate_749_141
Comment 1 Sahil Parbhaker 2018-08-10 20:49:53 EDT
Created attachment 21 [details]
Screenshot of error message
Comment 2 Nikhil Desai 2018-08-15 20:38:25 EDT
Per team meeting, Aug 15, issue is detected on intermittent basis.
Comment 3 Brian Roberge 2018-08-17 16:22:49 EDT
I have fixed a couple of bugs in this area (disconnecting device near the end of the update) since this bug was created.  You should try and reproduce it.
Comment 4 Mohan Kumar Karruppusamy 2018-08-21 18:39:37 EDT
Tested with the build 787_141 on both windows 7 and windows 10, still the same behavior.

Attached the windows 10 logs and screen shot.
Comment 5 Mohan Kumar Karruppusamy 2018-08-21 18:40:33 EDT
Created attachment 32 [details]
Screen Shot
Comment 6 Mohan Kumar Karruppusamy 2018-08-21 18:41:05 EDT
Created attachment 33 [details]
Log File
Comment 7 Mohan Kumar Karruppusamy 2018-08-21 18:41:26 EDT
Created attachment 34 [details]
json
Comment 8 Mohan Kumar Karruppusamy 2018-08-22 00:33:37 EDT
*** Bug 68 has been marked as a duplicate of this bug. ***
Comment 9 Brian Roberge 2018-08-22 05:19:20 EDT
Fixed in build 788
Comment 10 Danny Hutchings 2018-11-14 17:02:11 EST
Fix seen in build 905