To answer the last question on links, check the following.
Link to known issues in debian bookworm:
Link to release notes:
and here:
With a problem during installation such as appears in post #16, there are several things you can do to discover some information about it.
One step is to find the log file for the installation and see if it has any useful information. During installation, it's usually the case that the user can access the virtual consoles through pressing the keys:
cntl+alt+F1, cntl+alt+F2, cntl+alt+F3, cntl+alt+F4.
In the past usage there has usually been 4 terminals, one of which is the GUI installer, but since I haven't used it recently, I can't say more about this particular disk version.
Once a log file has been found, it can usually be opened by one of the following commands
Code:
more <logfile>
less <logfile>
cat <logfile>
vi <logfile>
where <logfile> is the name of the logfile in the filesystem.
Logfiles could be in a number of different locations in the filesystem like / or /root or /root/.cache depending on the installation configurations. One can search through the filesystem on the terminals in the usual way changing directories and listing files including dotfiles.
Another means of looking for a basis for the problem is to search the source code of the calamares installer which is here:
https://github.com/calamares/calamares
On nosing through the source code, in the file: netinstall.conf is the following comment:
That's about as close as I could get to any explanation. Essentially the on-screen message in post #16:
looks like a few things could have occurred. For example, the installer was not able to access the network location for the default web browser in order to install it for the user to use at this point in the installation because that location was unreachable at this particular point in time during the installation. Or, perhaps there's a problem with the hardware itself, which is often what an "input/output" error means ... the operating system may have trouble accessing the location on the disk where the application is located and so can't "take" it to RAM to run it, hence that error message. It's possible there's a bug in the code itself, though since it "worked in cinnamon", mentioned in post #16, it's difficult to know.
It's probably worth noting that linux is free of cost and the licence that is issued with the kernel and so many of the applications is an Open Source licence like the GPLv2 which is very clear and includes this statement: