RAM requirements for this unsupported use case are unknown.
can you please define “unsupported use case”?
Is this to incentivize paid support? What is the cost of that?
No.
None available at time of writing.
Sorry, can you explain further please? This answer is a bit terse…
Is paid support available, if so what is the cost.
Is there a bug in the installer script, or is it user error. As stated, there was
no obvious option for where to install the bootloader.
How can this be recovered.
Regarding bootloader, no help can be provided without the debug log.
Look at the bottom of above screenshot.
If debug log cannot be obtained then how can I provide the debug log?
Is there a 3rd party provider which offers Kicksecure support?
In your documentation, it shows a boot menu with “persistent” options.
For the kick xfce .iso file provided there is only a “live” mode.
There is a discrepancy between the docs and the live .iso.
A terminal window automatically opens when starting the installer. The massive wall of text is the debug log. Please provide after finishing calamares.
Company recommendations are unavailable. A decent software development company with Debian skills should be able.
Because it is a live iso.
You can only get that after installing to (internal or external) hard drive.
Some screenshot might be outdated saying ISO instead of Live ISO but ISO is always live. We’ll update that at some point in the future.
Couple of issues getting calamares installer logs; when you select “toggle log”
it does show a substantial log of the python installer script, but once the install
is finished, it exits the log screen and it doesn’t allow you to access it again.
Is there a better way to get a log file?
The log file is extensive, is there any specific error to look for?
In general with kick, there appears to be a problem with the installation of
bootloaders onto the USB stick, because when attempting to boot, it doesn’t
recognize an OS.
Open a terminal. Run
install-host
The extensive output there includes the installer log.
No. Calamares isn’t in its entirety isn’t developed by Kicksecure. Nor are most of the tools included. It’s Open Source. Based on thousands of people developing software.
The way it works:
- there is an issue
- log is provided
- developer reads, searches logs
What probably does not exist: Developers memorizing the debug output so well that they can tell you selectively what to copy and what to leave out. Requires too much time to think about and explain.
There might be a bug on some hardware, which we’ll fix in the next release:
But that bug isn’t installation of the bootloader to the wrong device.
In my direct experience, that is in fact the source of the bug.
“install-host” simply launches the Calamares installer tool again, this
doesn’t produce any sort of log.
You can access the log using “toggle log” only until the installer is finished
and then it completely disappears. This is just constructive feedback.
Kicksecure is release under which software license? It is a non-profit?
I can appreciate that there is finite resources to fix these issues, I wonder what
could improve this.
when is the next scheduled release of kicksecure?
There is no ETA (estimated time of arrival).
Detailed instructions added here just now:
Calamares ISO Installer - Logs Access
Many answers are possible. I am not sure I can provide any better answer than any AI chat bot.
One answer is money and/or volunteers
That is a highly complex complex question that are probably most projects asking themselves. Also highly speculative, opinionated, with the potential of lots of distracting discussion with no action.
Related:
2 posts were split to a new topic: AI chatbot for Kicksecure
2 posts were split to a new topic: Are bootloader / MBR issues an indicator of malware compromise?
A post was split to a new topic: Could UEFI/BIOS exploits/rootkits be a potential source of compromise?
2 posts were merged into an existing topic: Why .img image format?
3 posts were split to a new topic: Why .img image format?