Clicking oem-config-prepare in Desktop icon it requests password, although in the next reboot of system, the oem-config window does not appear in center of the screen and user cannot connect to wifi network. Running oem-config-prepare from terminal using sudo, previous bugs are solved. If you need more info, contact us, please. Thanks!
Hi, The problem has changed, now, it does not matter if you execute the desktop shortcut or the command by the terminal, when you restart the computer, only the mouse pointer and the black screen appear. :(
I'll have a look tomorrow.
Regression caused by bad installer merge http://bazaar.launchpad.net/~kdeneon/ubiquity-neon/trunk/revision/6398#d-i/source/user-setup/user-setup-apply SDDM again incorrectly attempts to autologin into a user that doesn't exist (oem user).
Thanks Can we apply the patch? or do we expect them to run in the next realease of KDE Neon?
After you run oem-config-prepare you can run `sudo rm /etc/sddm.conf` I've just checked and that makes the OEM configuration pass and then properly start up the login manager.
(In reply to Harald Sitter from comment #5) > After you run oem-config-prepare you can run > > `sudo rm /etc/sddm.conf` > > I've just checked and that makes the OEM configuration pass and then > properly start up the login manager. Thank you very much Harald! Have a nice day.
That patch is back in but now ISOs aren't building https://build.neon.kde.org/view/iso/job/iso_neon_xenial_useredition_amd64/190/console
New image up ready for testing https://files.kde.org/neon/images/neon-useredition/20180112-2350/ (I'll do it tomorrow)
So it would seem. Mind you, grub theming is still broken so the ISO continues to not meet UX expectations of plasma https://build.neon.kde.org/view/openqa%20%E2%9B%B7/job/openqa_xenial_useredition_installation_oem/25/testReport/junit/(root)/003_first_start/038_unmatched_needle/
Yes, at the end of the installation it tells me that it can not install grub ...
No, that's bug #380470 which should not happen if you connect to the internet during installation of the system. What the automated test is seeing is incorrect theming in GRUB (and as a consequence all terminals).
sorted for me