solus-project / os-installer Goto Github PK

'Finding your location' screen still shows up briefly (flickers) when the 'Find my location automatically' checkbox is not enabled.

See this video I put on YouTube: https://youtu.be/kf3lbqgBa_4

Filter "root" from the possible usernames to prevent users from creating it as an administrative account and then not being able to select the user during graphical login.

I would be great if the installer would support unattended mode, for example in conjunction with projects like https://fai-project.org/.

Seams to be on road map as OEM installer mode here https://dev.solus-project.com/T4235, without the possibility to vote for it.

Most people probably don't have a specific username in mind when they're setting up a user account, and I'd wager the majority of people use a username based on their real name anyway, so suggesting a username would save a few seconds of their install time.

For example, "John Doe" would suggest jdoe or "Jane" would suggest jane

And this suggestion mechanism wouldn't inconvenience users who have a specific username in mind (e.g. soluslover22) since they'd still have to type it in anyway.

When file copy is happening from USB to drive, some long filenames cause the window to expand and contract.

Ideally the files being copied would just be hidden and a gtk dropdown box could show the file being copied for those inclined to see it.

A quick fix is to wrap the filenames if they're too long or just limit the size of the gktbox?

People say the first impression is important.
The OS installer is one of the first contact people may have with Solus so although it's not really critical it would be good one day to make it multilingual.

When going through the installation there should be a user confirmation with something similar to...

'You are midway to installing/configuring an installation of Solus onto this computer. Are you sure you want to quit?'

Of course, at least a user confirmation when they are actually installing so that you don't quit after formatting their disks/partially installing the software such as...

'The installation is not yet complete and your system will not be bootable if the installer quits prematurely. Are you sure you want to quit?'

YouTube of bug/missing feature: https://www.youtube.com/watch?v=jRsY3f79yp0

Operating System: Solus 3
Budgie version: Budgie 10.4

The issue encountered

The keyboard layout french Switzerland used during the install isn't the right one, the french keyboard is used (azerty, not qwertz like in Switzerland). The french German one is correct but there is some variation.

Steps to reproduce the issue

Launch the Solus installer and select the french keyboard

I have reinstalled Solus couple of times, wiped the drive, run checks but nothing really solves it - my system crashes every 20 min with EXT4-fs error (reading directory lblock 0). Same thing happens with Ubuntu 17.10 and it only happens with my laptop while PC is fine.

After some digging I found this bug report which seem to perfectly match my problem (same hard drive but not sure if APST support is present in kernel 4.9.23 - edit: it is):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184

Any advice?

We can use independent installer Calamares

i cant install solus because the setup is crashing to desktop.

ISO: Solus 3 Budgie

The installer shows a "Not responding" message in the first execution (at the same time the Installer window appears), but the Installer is not unresponsive, clicking "Wait" closes the window and Installer can be used as normal.

This happened to me and a friend, our both PCs has low-range specs so I think that can be the problem.

Some timezone areas cannot be clicked or get assigned (highlighted) to the wrong area

YouTube: https://youtu.be/pJQFDaHJCdE

Similar to this bug?
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/342586

Fedora's Anaconda installer has the option to set-up a password-less user during the installation, it will be great to have this option on Solus' installer for setting up home/guest users (but without the horrible error of making the administrative privileges for those users an optional thing as Anaconda does).

BTW, I tried to use the good old passwd -d command to remove a pre-setted passwd for an home user but LightDM didn't catched it (as in Arch or Ubuntu).

Installer detects all ESPs but only shows the first suitable one as an option in combobox.

def get_suitable_esp(self):
""" Attempt to find the suitable ESP.... """
l = self.dp.collect_esp()
if not l:
return None
e = l[0]
if e.freespace < ESP_FREE_REQUIRED:
return None
return e

Ideally, the installer should let the user select which kernel should be installed (instead of having to eventually switch to another kernel after the installation).

I have a laptop with a slow sata bus but two drives, so I use a stripped LVM setup to bring it up to speed. I understand why the installer doesn't do this for the user, because striped drives double your risk on disk failure.

But I'm willing to set up LVM for myself in the terminal, and take that risk. It would be nice if the installer would show those logical volumes I set up.

I have used Rufus to make a bootable USB from a 64gb SanDisk drive that is formatted to FAT32. I have only got it to boot once and all it showed was Reboot To Firmware. Now it doesn't show up in the bios as UEFI or EFI.

I have an Acer switch alpha 12
Intel i5-6200U
8gb ram
256gb SSD

If all someone wants to do is dedicate a secondary or primary disk to Solus while leaving the others alone, currently the only way for them to install is through Manual partitioning. Would be nice if they could just select a whole drive and then do the auto-partitioning.

Installer doesn’t understand XFS and only offers to format pre-existing partitions, without the ability to use them, which makes migrating /home more difficult.

As for file system creation and mount options, both Arch’s Wiki and XFS own FAQ recommend sticking to defaults.

In the partition manager system, the previous button should take us back to the screen where we can select a drive.

The installer should support the installation of proprietary kernel modules to assist in installations,
i.e. nvidia, broadcom-sta, and co

Original G+ post: https://plus.google.com/+RaffaeleTranquillini/posts/TsTc7rYYAUZ

Thanks.

Description
Selecting a non-latin keyboard layout results in a dead-end in the installer.

More Details
The Keyboard Layout selection happens before setting hostname, username, password etc.
If the Keyboard Layout is selected to be a non-latin layout this will mean that some of the next steps won't be able to be completed. Specifically it won't be possible to set a hostname leading into a dead end.

Workaround
Go back on previous steps and select a latin layout. Finish the installation. Boot on the installed system and configure it to include a non-latin keyboard.

When this happens
This problem happens whenever the keyboard layout is selected to be a non-latin keyboard layout. There are two cases this happens:

1. The user chooses a non-latin keyboard manually
2. The installer suggests a non-latin keyboard to the user which the user most probably accepts (when finding the user's location automatically and the user lives in a country that normally uses a non-latin keyboard)

Suggestions
This issue could be resolved in various ways:

1. Moving the keyboard layout selection as the final option.
   This isn't optimal as the user won't be able to enter their username and password afterwards when booting on the system as they won't have a latin keyboard layout.

2. Keeping the English keyboard layout and asking the user to select a secondary keyboard layout.
   If the user tries to set hostname, username etc. with non-latin characters it might be helpful for the message to inform the user that specifically latin letters are required for those fields.
   The current message for hostname is:

Hostnames must be lowercase, and only contain letters, numbers, hyphens and underscores.Hostnames must also start with a lowercase letter.

3. Disabling all non-latin keyboard layouts from being selected on the installer. This would also mean the installer would never suggest a non-latin keyboard. The user would add a non-latin keyboard after the installation procedure on the installed system.

UPDATE: If suggestion 2 were to be implemented one might want to think which English layout shall be the default (there are many e.g. EN(US), EN(UK) etc.)? The installer on first selection has a list of languages (those are the languages on which the installer will appear) and for English it says English (United States).

I installed Solus on a laptop with and SSD drive and a PC with Samsung Evo 950 SSD. In both cases I opted to remove all partitions and make a clean install and in both cases the installation failed saying that it could not write to drives.

After restarting, all the partitions were gone and if I exactly repeat the steps as before everything installs without a problem. In both cases Solus was overwriting Ubuntu partitions.

Can't really test it again as I now installed Solus on both PCs but thought I would report it.

Currently swap only seems to get added on UEFI, so we have a logic fail. This should be considered a blocker for the next release.

Solus installer does not align partitions optimally.

After a fresh install

# parted /dev/sda
(parted) align-check optimal 1
1 not aligned

When installing Solus Budgie, under "Chose a language", the Norwegian language has the wrong "names" so it doesn't sort properly:

Bokmål, Norwegian
Norwegian Nynorsk

I suggest renaming them:

Norwegian, bokmål
Norwegian, nynorsk

...that would have made me curse a few minutes less:

1. language selection. It seriously took me some minutes to figure out those vertical 3 dots are actually a button that makes the other languages appear. Could you make it such that pressing a letter, it'll expand automatically and goes to that initial letter? or a little language search box?
   I think by enabling your location and suggesting languages, it left me out of the english language suggestion. Perhaps always have english visible also?

2. Please make the hard disk selection refreshable with a button or so. Don't know how many times I had to restart that installer after having figured the boot flags are missing or I need that swap partition, or split another partition in parts. Only way is to quit installer and run again.

During the disk config mode, the ability to set a partition's mount point manually is missing. Users may have partitions (such as/home) that preserve old data.

Ubuntu is going to now default to swapfiles on new installs. Potentially quite a good idea, so we should investigate the exact details and consider implementing this in Solus via the installer

http://phoronix.com/scan.php?page=news_item&px=Ubuntu-Switching-To-Swap-Files

http://blog.surgut.co.uk/2016/12/swapfiles-by-default-in-ubuntu.html

Pinged @xnox to query whether to use sparse or allocate the regions beforehand

Add an option to split free/non-free software to allow installer to dynamically install the non-free bits like codecs.

A fresh Solus installation on an SSD will add the option discard on \etc\fstab and enable the fstrim.timer. This seems redundant as adding any of the two will enable TRIM on SSDs.

According to the ArchWiki (and some references there) there are cases where fstrim.timer is preferred over the discard option.

Title says it all really, I would love the ability to manually assign mountpoints to existing partitions, for example a separate /var (still heavily advised when using a SSD/HDD combination) and separate data partitions (like in my case in order to have data accessible from multiple installed operating systems). Apart from /, swap, /home and /var I have three separate data partitions with rather odd names I would like to access without having to mess with /etc/fstab later.

A similar request was made two months ago but that issue was closed after, I assume, adding the /home option. Instead of reopening that I was requested to open a new issue, so here it is.

I didn't found a way to keep the existing Grub of my multiboot system. The only option is to write the Solus bootloader in main EFI. It could be useful to add Solus by simply refresh the bootloader list, as instance, with the update-grub command. Sorry for my approximative english.

It could be worth using it in order to avoid duplicating work.

We should properly support ibus configuration and region selection at install time.
This might require splitting the installer up into a "Post install" section for it to all work nicely,
i.e. we need to write dconf values

At the moment, when I hit the super key, type "software", hit enter and open up the software centre in Budgie, I am taken to a "Home" page.

What I would like to be able to do is search the packages straight away rather than have to go and click on Search. I think Solus packages rather than having to worry about 3rd party packages is a fine default or maybe a split results page of matches from the home page to show the origin of that result.

If the target partition is mounted (I think for me it was the ESP partition), the installer fails with a permission error message.

Could be solved by checking if the target partition is mounted and unmounting it/informing the user if it is not possible.

I recently had to help a friend install Ubuntu 16.04 LTS on his computer. When I hit reboot after installing the os and screen came up where it said that I should remove installation media and then hit enter to reboot.

That is actually a really good thing for noobs like my friend because most computer boots to the usb stick again after rebooting. Thus I think a feature like that would be a really good addition to the Solus installer, in order to make it easier for beginners. :D

Copy paste from G+ page :D

Burned solus iso through dd command, specifically dd bs=4M if=SolusFTW.iso of=/dev/sdb && sync from arch wiki. Everything went fine and I was able to get uefi menu to start solus USB but that was pretty much it. After selecting solus it's just a blank screen. Nothing else. No output or anything like that. Tried installing it in dell xps 13 developer edition, 2013 version.

Hello

i tested solus but whenever i boot in to the live system the system doesent identify my usb ports an so i cant use my mouse and keyboard.

Motherboard:Gigabyte 970-UD3P rev. 2

Hi,
I tried to set up dual boot as described in many tutorials. First set up Windows and afterwards solus with manually setting the partitions. No problem so far, Windows also created the EFI Partition with boot flag, but Solus installer can't find this Partition. Also if i try to create a new one its not working. I have the 2017.01.01 build and an uefi notebook. Normal install without Windows works like a charm.

How can I figure out where the problem is?

Long story short, Solus updates its kernel packages more often than most distros.
If Solus owns GRUB, not an issue. If it doesn't - they must update-grub from the
other distro.

Except they don't, and think its a bug. It's not. So stick a massive disclaimer into
the UI to explain this.

We should be recording the resume=UUID=$SwapUUID to the cmdline when installing Solus, so that people can properly resume from sleep/suspend without having users edit things.

TODO:

• Write custom /etc/default/grub with the DEFAULT Cmdline edited
• Write it in the UEFI entry

Source: https://plus.google.com/u/0/+UnBarbu/posts/45GfrFLYTYL

Using the latest available Iso (https://solus-project.com/2017/01/01/solus-releases-iso-snapshot-20170101-0/) and you install Solus with the "Erase All Contents" option and you choose to use LVM and LUKS the swap partition created by the installer is not activated (i.e. its not in the fstab file) so you have to get the UUID and add one entry manually to activate it on your system.

Add support for newer internal storage devices present on current gen laptops and desktops.

every time I install vlc or firefox or just upgrade my system their is this error which states that 'updating manpages database failed'. Also in conjunction to that there is this another error that is
/usr/bin/mandb: error while loading shared libraries: libgdbm.so.4: cannot open shared object file: No such file or directory
So what I can do to resolve this error in solus budgie

Scrolling the list of languages to get to your language of choice takes awhile (I only had to go to English CA) I can imagine someone who's language is near the bottom not enjoying it that much.

I suggest making the list searchable, so a user can more readily find their language.

So I'm thinking about adding support encrypted installs and there are two ways of doing,

• EFI part, not encrypted
• Encrypted root partition password for encrypted swap part using luks
• Encrypted swap partition using luks

• EFI part, not encrypted
• LVM on encrypted using luks
• LV for root, swap etc

Just wondering what peoples views are before I start working on it.

(Setup for lvm and luks https://gist.github.com/jasonwryan/4618490)