2) connected the Trezor device, SElinux alerts go off immediately the plug-in tries to run ... checking into details for the SEAlert gives a few options for allowing mozilla plugins correct access to root locations ... ok, w/e
SELinux is preventing /usr/lib64/firefox/plugin-container from write access on the chr_file .
just playing at this stage so not going to allow that for real until I think through what it is trying to do but play along since I'm not putting any coins anywhere near this until I understand it
This should be okay. SELinux rules obviously don't expect that browser should talk to USB...
3) device connects and immediately get a firmware is out-of-date message
This is also fine. We've released new firmware since we stocked this batch of devices.
that flashes up only long enough for me to read first two lines then disappears ... so need to keep disconnecting and reconnecting device until I can read the whole message ...
Well, this is definitely a bug. Could you please report this to
support@bitcointrezor.com together with the output from the Javascript console? There's "show log" in right bottom corner of site which should do the job. Log will help us a lot.
4) connect device while holding down both buttons and page asks do I want to update firmware ... sure what else am I going to do, rewrite it myself? ...
Haha. The security question is there for obvious reason, so user cannot be guided by malicious software to bootloader mode without knowing that the firmware can be replaced without any further confirmation.
error message flashes up
Update Failed
b._session is null
and browser becomes very sluggish, cpu fan kicks in signifying usually a runaway process (most likely the mytrezor plugin I expect)
Hm, this may be related to previous issue with flickering dialog. As a temporary workaround, reloading the site and re-connecting the Trezor directly to bootloader mode (without letting the dialog about outdated firmware appear) might help. I know, it's definitely bug and we'll hunt it, but this may actually help instantly.
Thanks Slush.
Ok, I tried what you suggested but similar behaviour with the plug-in essentially making the browser sluggish and unsusable. I was unable to retrieve a log due to the unresponsiveness.
There is however a bright side.
I then tried to do the recommended procedure on a fedora 32-bit using the appropriate .rpm plug-in and it all went as per the manual. So the firmware is now updated and Trezor is initialised with a seed, etc.
Now taking the Trezor back to the 64-bit machine it appears to be doing the correct things with the standard wallet behaviour (no firmware issues now) but is still really slow and sluggish to keyboard and mouse inputs. So I think it might be just that the 64-bit .rpm plug-in is buggy. Another point on the plug-ins are they open source? Can I see the source and how the binaries are built, i.e. I would like to test build the .rpm packages myself and check if it is specific to my fedora platform or if it is RH-derivative wide issue. Also I'm interested to see what the plumbing of securing the plug-in binaries looks like.