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
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.
Since #719, you can no longer use a local json file with --repo (At least in Qt 6). A network request to a file:// url has statusCode 0, which caused this check to fail previously.
- Simple implementation of OS list fetching in backend
- Replace frontend OS list fetching by calls to backend
- OS list updates are brought in asynchronously, avoiding excessive UI
blockage.
- "Erase" and "Custom" OS list options are always present, even in a
no-internet scenario
Based-On: cillian64/rpi-imager/oslist_backend
It is possible to connect to open wifi networks using raspi-config or
the wf-panel-pi GUI. It was also possible in rpi-imager but only with a
workaround - if you entered a dummy PSK it would be ignored if the SSID
was that of an open network. (This also meant a Pi could be tricked
into connecting to an open network on first boot even if a PSK was
configured).
The change in https://github.com/RPi-Distro/raspberrypi-sys-mods/pull/83
has a side effect which means that Pis will no longer connect to an open
network if a PSK is configured.
This commit lets the user enter no PSK to indicate that an open network
should be configured.
Resolves#424
