gpt.Signature is not a null-terminated string, but an 8-byte character array. Using `strcmp` will not provide a valid result. Use `strncmp` over the first 8 bytes instead.
Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
- Apply with p1, using a patch generated from git-format-patch.
- Use POSIX 'cd' over 'pushd, popd'
- Use OLDPWD to the find the patch, rather than making assumptions
about the relative location of it.
The keyboard: section should be used instead, which should do the right
thing on whatever platform cloud-init is being used on (writes
/etc/default/keyboard on Debian/Ubuntu, uses localectl on RHEL/Fedora,
runs setup-keymap on Alpine).
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038762
[2]: 2030788
On systems with a very large number of snap packages installed, there
are a considerable number of loop devices. In this case, the `lsblk`
command in linuxdrivelist fills the stdout pipe, blocks, and the
rpi-imager process assumes it has timed out [1].
This is a trivial work-around that simply excludes loop devices
(major=7) from the `lsblk` output. Given subsequent code excludes
everything starting with `/dev/loop` anyway, there should be no change
in user experience with this exclusion.
[1]: https://github.com/waveform80/imager-snap/issues/6
Rather than providing a free text template, as we've done so far, introduce a form to more stringently require information that we need to debug the problem.
Makes the filtering-behaviour userconfigureable during compile-time.
This way its easier to configure the imager for flashing SATA or NVME
Drives installed in your system (because of lack of adapters),
or if the drives are (accidentally) labled as systemdrives by drivelist.
tr() is not safe for strings that you move between contexts,
as it fails to provide a mechanism for specifying the context
of the string.
Regenerate the translation files, and use QCoreApplication to locate
the real translations.
Additionally, bodge a race condition between translator replacement
and OS list fetching, by marking the OS list as something to be
re-calculated on a translator change.
Fixes#799
But, as a consideration for users wanting to verify their password, add a 2s dwell time before the characters are masked. This timeout is prematurely terminated in the event that you enter another key.
Using onTextEdited meant that the clear() call would happen after the edit had actually happened.
Instead, use the Keys.onPressed handler, which happens earlier in the input chain.
