As announced in our Solus 4.4 blog post we are deprecating our MATE edition and so this issue will not be addressed.

@jedibrooker, is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

Tracked at https://github.com/getsolus/solus-installer/issues/13

While Calamares doesn't strip leading/trailing spaces, it does actually tell you very clearly what's wrong. So this will indeed be resolved by switching to Calamares.

Calamares (I believe) can do this, it probably just has to be set up to do so. Something to look in to down the road.

Closing per request on the forums. Appears to be resolved.

In T10563#202105, @stalebrim wrote:

Did you format the disk as GPT?

Thanks for the detailed bug report. Since we are retiring os-installer, this won't be fixed for that. We will keep this issue in mind for its replacement.

What I am saying and have done is to select the Fat 32 partition, normally the ESP or EFI boot partition on the Windows disk (in this case), click on the right with the mouse, go to manage flags and untick the boot flag. It will untick the esp flag as well. Then, do the Solus install. Once it's done, you can reset the boot flag of the windows partition.
It will go back to boot and esp. It hasn't made any trouble on all my partition (Windows, OpenBsd, Mint, Solus and Fedora). It's just the time of the install. I found it here : https://discuss.getsol.us/d/4467-installer-not-seeing-new-efi-boot-partition

In T10324#201398, @Foid wrote:

Hi,
I went into the same problem (I have around 10 disks !!). On each ESP partition (boot Fat 32 parttion), with Gparted (didn't work with Kdedisk manager (can't remember the exact name)), I unticked flag boot (it comes with esp), that changed then to msftdata with the manage flags menu.
If your disk is empty, then on install, it will ask you if you want to create an Esp partition on the disk you expect. I actually found this solution on the forum (can't find it again, but it's there).
I would say on your case, you untick the boot flag of the windows partition, and bob's your uncle. (by the way, you can install Gparted with the live iso, it works fine).

Hi,
I went into the same problem (I have around 10 disks !!). On each ESP partition (boot Fat 32 parttion), with Gparted (didn't work with Kdedisk manager (can't remember the exact name)), I unticked flag boot (it comes with esp), that changed then to msftdata with the manage flags menu.
If your disk is empty, then on install, it will ask you if you want to create an Esp partition on the disk you expect. I actually found this solution on the forum (can't find it again, but it's there).
I would say on your case, you untick the boot flag of the windows partition, and bob's your uncle. (by the way, you can install Gparted with the live iso, it works fine).

Ran into this issue as well, instead of risking breaking dual booting between solus and manjaro, I popped my laptop open and removed my Manjaro drive while installing.

For me workaround is using gparted and creating new partitions. Also you need to untick "boot" flag from windows EFI partition and mark newly created Fat32 partition flak as "boot". After that installer will see the new EFI partition.

Have you tried manual partitioning? I found once I manually created /, swap and boot partitions like in the helpcenter docs, rebooted, it detected the new partition nicely.
https://getsol.us/articles/installation/disks/en/

installer issues need to be reported on github https://github.com/getsolus/solus-installer

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/29

Closing due to lack of response in over 30 days. Please reopen if you have more information to add.

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/15

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/28

Closing due to lack of response in over 30 days

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/27

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/26

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/24

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/23

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/22

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/21

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/20

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/19

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/18

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/17

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/16

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/16

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/16

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/15

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/13

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/14

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/13

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/12

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/11

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/11

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/10

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/9

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/8

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/6

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/7

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/6

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/5

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/4

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/3

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/2

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/1

@g66925 rn there's no control over swapsize during install phase, but you can control swappiness parameter during run-time

I am encountering the same issue on a GTX 1660S on a desktop with no iGPU on the processor. When I try to boot into Solus from USB, my display detects no more connection and goes black. I still hear the opening sound effect play and can open terminal from keyboard to run speaker-test, so I know it has to be an issue with the GPU compatibility.

At the moment, there are some accessibility issues that I ve tried to capture and described here:
https://github.com/getsolus/os-installer/issues/9

@STiAT Pretty straight-forward. If a volume is mounted in the Live system and you try to install to it, the partition management doesn't know how to unmount it before trying to format it.

@DataDrake is there any more information on what is the actual issue? I'm tempted to look into that.

This is a known bug and won't be fixed until the installer is rewritten or someone has time to patch the existing installer.

Yes my disks were simple configured. /home on my HDD, / on the SSD.

Hi there,

800x600 problem, not virtualbox problem. No "Catering" needed

Well did a real install and it's specifically a problem with 800x600 resolution, other resolutions in 4:3 work well. So not a VirtualBox problem.

Closing as WONTFIX as we do not cater to these sorts of virtualized environments.

Closing as WONTFIX as we do not cater to these sorts of virtualized environments.

I just tried Solus 4.2 Plasma and ran into this problem again.

This has been validated to now be resolved. Thanks @leapfog for testing.

Will (further) validate my network-manager-livecd addition when I generate the ISOs.

The more correct way to handle this is to have a network-manager-livecd package which ships with a file that sets the hostname-mode to none, which will inform NetworkManager to not manage the hostname and not set it. This should do the trick.

I managed to solve the issue by commenting out the following line from:

In T8973#178236, @DataDrake wrote:

Let us know how things go after 4.2 is out (please don't ask for an ETA).

Let us know how things go after 4.2 is out (please don't ask for an ETA).

Known bug. Won't be fixed until the installer rewrite.

The installer won't detect drives that don't have partition tables. You'll need to add a partition table using something like GParted before it will detect them. I agree that not detecting windows is an issue, but that's been reported elsewhere.

You are welcome, @Darius. Solus is pretty great, since it manages to combine the feature updates of a rolling release like Arch with the user-friendliness and stability of Ubuntu. The only real problem with it is a lack of available software at times due to this not having the community size and organisation of either Arch or Ubuntu. I get the feeling that Solus needs more maintainers for software packaging and development.

In T8973#178025, @Dolphin985 wrote:

I had problems with installing Solus with the UEFI too. I also ended up not getting to the GUI, but rather being in the Linux Mint (prior OS on device) GRUB menu. The difficulty of that for me was that UEFI mode for my bios doesn't naturally show USB drive extensions, and the legacy BIOS mode doesn't work with a UEFI flash drive. Did you check the formatting of your hard drive and Live USB drive, @Darius? Both of them need to be in GPT format, and the BIOS also needs to be set to UEFI mode to read them.