password not accepted on persistence?
mmh, it worked for me, but i will try again before to publish 3.8.20
@vesteve58 can you type here the special characters that your passwrod used ? (not your entire password, only the non normal characters, note that accents may probably not work for that
I had exactly the same issue lol, i don't remember how "good" is the 3.8.19 version with the fonts but maybe (just maybe) on 3.8.20 works better, which includes the final versions of these font configurators, in any case I agree again with you @triantares , im also used of small fonts, i work entirely on 96dpi on probably the same screen (el_dpi_get shows 157x157), bigger fonts for me is a waste of space
maybe this was a bug, i will check that too on the next build
@Franc what tool do you use to create your Elive USB's?
which part? can you specify more? or can you include a screenshot? (with your phone you can do it and upload it to https://pasteboard.co/ )
they stopped to work? maybe this is due to a different kernel drivers btw next build will have kernel 5.10
just "apug" and hit the "restart desktop configurations" (from the menu), having all your apps closed previously, this will crash your e16 and create a new default conf by elive, this transparency issue has been fixed recently and ohter things so, just get a fresh conf
note: the new version includes the conky conf in a new format
yeah and use "elive-skel upgrade" for that
me thinks we need having it available on the menus
important: after some tiring betatestings seems like the new kernel 5.10 is incompatible with the creation (again: creation) of the persistence partition
So seems like we have 2 possibilities here:
- ignore kernel 5.10 and switch back to the kernel 5.9 (this of course will include a few less of the new drivers for the very-new machines)
- show a message telling the user to reboot with the older kernel on which he can create the persistence partition and use it with the new kernel too (this can sound a bit confusing, but can be a solution)
So... what do you think? which option would be the best one?
in any case the "tell the user how" is here, good to have, so the question is, we should use an older kernel to avoid this issue or just go with the new one and deal with it?
also, anything to improve in the explanatory message to not have a feel of "elive is " ?