All Projects

This bug is reported by Pacma, but in order to resolv it i recommend a different way to manage the default profile (wired):

Aparently if you have the default and the X profile configuration, if you select the X one and then try to connect, NC automatically changes to the default one making it impossible to autoconnect to the X profile.

I think that instead of the actual method of work, we should only permit one (and only one) autoconnect profile (not needed to be the “default” one), so there’s no possible to have 2 autoconnect profiles coexisting, if the user try this, a question message will appear asking if want to replace the autoconnect “previous” profile and use this one instead.

Hi Luis,

I added this issue in order to know what is the cause that the other options gives you a black screen

To install in failsafe mode could remove some features so if you are able to install it in normal mode it could be better, so let’s investigate the cause

The new disks health feature doens’t reports the correct values:

❯❯❯ cat /etc/elive/disks-health
disks_scanned=""
count_gshock="0"
count_sectors_reallocated="0"
count_sectors_pending="0"