imager ignore the setting i put in (v1.8.1)

[Sharonhazan]

i use the advance setting, and its seems to ignore all the setting i put in
like hostname and user and password, it run as Admin on win 10

[tdewey-rpi]

Thanks for the report, @Sharonhazan.

Can you confirm what OS you were attempting to customise?

[Sharonhazan]

Bullseye lite on rpi 3b

[tdewey-rpi]

I'm not able to reproduce this failure, up to the point of booting the Raspberry Pi 3B. Imager is writing the customisation as I'd expect.

When you say rpi-imager seems to ignore all the settings, how are you observing the failure - on the Raspberry Pi device itself?

[Sharonhazan]

I'm not able to reproduce this failure, up to the point of booting the Raspberry Pi 3B. Imager is writing the customisation as I'd expect.

When you say rpi-imager seems to ignore all the settings, how are you observing the failure - on the Raspberry Pi device itself?

yes, when i boot the pi (headless) i dont see that he got the hostname i gave him and i don't able to connect to the SSH, even on the deafult pi user and password

[Sharonhazan]

its seems that there is something in my pc that makes it not to work, tried in my work laptop and it seems to work

[tdewey-rpi]

@Sharonhazan How did you install v1.8.1? Did you previously have Raspberry Pi Imager installed?

[Sharonhazan]

from the rpi website
on the pc i think i had, yes

[tdewey-rpi]

In the Windows Terminal, could you send me the output from reg query "HKCU\Software\Raspberry Pi\Imager"?

[Sharonhazan]

HKEY_CURRENT_USER\Software\Raspberry Pi\Imager
beep REG_SZ true
eject REG_SZ false
telemetry REG_SZ true
x REG_DWORD 0x400
y REG_DWORD 0x25e

HKEY_CURRENT_USER\Software\Raspberry Pi\Imager\caching
HKEY_CURRENT_USER\Software\Raspberry Pi\Imager\imagecustomization

from the pc. which is currently installed

[tdewey-rpi]

Making sure you remove your password from the output, can you also send me the output from reg query "HKEY_CURRENT_USER\Software\Raspberry Pi\Imager\imagecustomization"?

[Sharonhazan]

hostname    REG_SZ    PI-Server
sshEnabled    REG_SZ    true
sshUserName    REG_SZ    Sharon
sshUserPassword    REG_SZ    

[tdewey-rpi]

Thanks, @Sharonhazan. That confirms that Raspberry Pi Imager has at least persisted your settings in the manner I'd expect.

Can you please walk me through your precise button-press sequence in the Imager, so that I can confirm I'm doing the same steps in my testing? Include which buttons you press in any dialog windows that appear, please.

[Sharonhazan]

choosing RPI3 on "raspberry pi device" -> "choose OS" choosing bullseye (legacy) lite -> choosinng storage -> editing setting -> save -> yes -> are you sure to erase all "yes"

[jmfullerton]

I've seen the same problem doing customizations for a Raspberry Pi Zero W, Raspberry Pi 3B, Raspberry Pi 4 and Raspberry Pi 5. When I boot on the various PIs, it appears that the WiFi hostname hasn't been set. Every time after I created the first image, when I look at the customizations again the SSID is still set, but showing the password it is a hash and not what I entered. I'm running the Imager on Windows 11. Seems the only solution is to do configuration over a wired ethernet with SSH. It also took a little bit of time to find out that SSH wasn't configured because it's on a separate tab from all the other network settings.

[Sharonhazan]

i might managed to fix it?
i deletedt the cache on the AppData\Local\Raspberry Pi\Imager
and reimaged

[tdewey-rpi]

i might managed to fix it? i deletedt the cache on the AppData\Local\Raspberry Pi\Imager and reimaged

Thanks for the update, @Sharonhazan, because that's given me an investigation avenue. That data contains the QML cache, and because we've changed QML behaviour I'm going to try some exotic upgrade paths to v1.8.1 and see if I can reproduce your failure this way.

[tdewey-rpi]

@Sharonhazan, thanks again for your updated report. Based on your information, I found NixOS/nixpkgs#197010, which in turn sent me to issues reported in other projects where manually deleting the QML cache would seemingly resolve the problem.

Based on this workaround being used in numerous places, I've added a patch to enforce this in Raspberry Pi Imager. This will increase application start time - potentially noticably. Unfortunately, however, I feel the trade off should favour correctness over perceived load time.

[Sharonhazan]

this function already in the imager or it will be in the next version?

[tdewey-rpi]

@Sharonhazan It'll be released with v1.8.2, which is currently blocked behind #714 -- which I'm actively working on.

[Sharonhazan]

ok, thanks
i will wait

[Technorocker]

I too am experiencing this on both the PI zero W and a 3B which is frustrating when Im trying to setup a headless installation and have to question why and whats going on cause it never correctly gets the WIFI settings working. Then I start questioning all the settings and start hunting through config files to see what was and wasnt applied

I just did a reimage for the 3B and reentered all the config settings in imager. luckily I went desktop version(which Id rather not) to see what was going on. on boot it does show the hostname and the username I chose but the network didn't connect. I opened the wpa_supplicant.conf file and it didn't have any WIFI settings in it. just

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

my output from reg query "HKEY_CURRENT_USER\Software\Raspberry Pi\Imager\imagecustomization"

C:\WINDOWS\system32>reg query "HKEY_CURRENT_USER\Software\Raspberry Pi\Imager\imagecustomization"

HKEY_CURRENT_USER\Software\Raspberry Pi\Imager\imagecustomization
    hostname    REG_SZ    rhasspy1
    keyboardLayout    REG_SZ    us
    sshEnabled    REG_SZ    true
    sshUserName    REG_SZ    user1
    sshUserPassword    REG_SZ    $5$7MJw/YuZOB$FxJpJgN.m/sH.sdCuXqQLFGRNAgIuG/kGrjvM8u.187
    timezone    REG_SZ    America/Toronto
    wifiCountry    REG_SZ    CA
    wifiPassword    REG_SZ    9535a491cd82d4ef8799c665c74d42ae943ecd50465549cb4320a5bb0409
    wifiSSID    REG_SZ    mywifi

I am also using v1.8.1 imager

[maxnet]

I opened the wpa_supplicant.conf file and it didn't have any WIFI settings in it.

That's normal now RPI OS switched to NetworkManager.
Doesn't use wpa_supplicant.conf but sends the configuration to wpa_supplicant through other channels.

Can normally see connection profiles with "nmcli con"
Although I am not sure whether or not it remembers the connection if it never succeeded in connecting at least once...

[Technorocker]

@maxnet thanks for the update, I was unaware of that part. Either or though. The imager still isnt configuring the wifi setting to be able to connect on boot up, unless Im missing something and it doesnt automatically and im supposed to manually connect after its booted, but that'd kinda defeat the purpose of headless setup I'd think.