Raspberry Pi Imager problems

New here so sorry if this is in the wrong category.

Using the latest version of Raspberry Pi Imager I tried to install Octo on a 32GB Micro-SD (from a Linux system). Used ctrl-shift-x to enter SSID, pwd and region and it wrote just fine until the end where it complained that it can't write the startup file. Naturally it didn't boot into WLAN and also didn't use the changed SSH passwd.
Not that it stopped me as I edited the octopi-wpa-supplicant file and made the pwd change after logging in via SSH but it may be a bit of a problem for beginners.
What I would also suggest to add in the instructions on the download page is to recommend running sudo apt update and sudo apt upgrade as the image is naturally a bit outdated (had 160 upgrades to install)

System is running great and the best thing I did to my 3D printer!

I can't see any existing issues about it on the RPi Imager GitHub page. It might be worth reporting your problem with failing to write the firstrun.sh script (I think that's what it's called). You are right that it definitely would confuse some people.

Doesn't using ctrl-shift-x to change the WiFi parameters get overridden in OctoPi by the octopi-wpa-supplicant.txt file?

OctoPi also enables SSH by default so that setting isn't needed in the ctrl-shift-x menus. Changing the host name and setting locale are the only things that I would change. You can set the hostname by creating a octopi-hostname.txt file in /boot as well.

ctrl-shift-x is recommended on the octoprint download page and naturally one uses it as a start. Changing the SSH password from there and entering the WLAN parameters is easier for a beginner too. But it just didn't work. As I am running Linux since 1998 it wasn't a game stopper but I am sure that many will have problems with it if they aren't familiar with Linux.

Using ctrl-shift-x and setting the WiFi parameters will end up in the octopi-wpa-supplicant.txt file when you first boot the image. RPi imager creates a firstrun.sh script that puts them in there when you boot it.

There's been a lot less questions about connecting to WiFi since we switched the main install tutorial on OctoPrint.org - Download & Setup OctoPrint to use that, since it can auto fill (no typos) and Linux Vs windows line endings are not an issue etc.

Where does the RPi imager create the firstrun.sh file?

In the root of the boot partition.

So I just ran the RPi imager (on Windows 10), used the ctrl-shift-x menu, and wrote an SD card.

After removing and inserting the SD card (on Windows 10), I examined the /boot partition. There is no firstrun.sh script. The octopi-wpa-supplicant.txt isn't changed either.

The only file written this year :slightly_smiling_face: was cmdline.txt and it does contain systemd.run=/boot/firstrun.sh.

Presumably you did enter some WiFi credentials, if that's what you are looking for? If it doesn't create the script it usually throws an error as the OP was talking about.

That's expected - as I said before it only adds them to octopi-wpa-supplicant.txt after boot.

I can't tell if you're trying to say the process doesn't work, or just trying to see how it works yourself - the RPi imager works for everyone else just fine.

Well excuse me.

Working fine is probably a very generous description. RP Imager works fine as long as one doesn't use ctrl-shift-x to enter some data. At least on 3 different Linux machines with different distros.
With OctoPrint it just throws the error message and doesn't write the firstrun.sh file. With Raspberry Pi OS after entering WiFi credentials, SSH key aso with ctrl-shift-x it pops up a warning "Verifying write failed. Contents of SD card is different from what was written to it" and doesn't finish. Card requires a re-formating to be usable again.

In my world that would be considered to be broken....... The only "good news" is that it is less broken with OctoPrint than with RP-OS.