Hey all, n00b here. I've been a KDE user for awhile, but hadn't ever run Neon. I decided to give it a try when I bricked my Fedora install trying to install the latest NVIDIA drivers and rebuild the initramfs.

Anyway, I decided to install Neon after backing up my home directory and wiping the drive. Everything went smoothly during the install, but on first boot, I wasn't able to login. I tried the password I had literally just set a few minutes ago during install several times to no avail. I thought maybe I had hit cap locks or something accidentally, so I tried various combinations of nearby keys thinking maybe I had hit a neighbor key at some point in the password and didn't know it since I was typing by feel and not looking. Nothing worked. So, since I had just installed and it only took a couple minutes, I decided to try again.

After freshly installing a second, the same thing happened. This time I tried no password at all and it worked, even though I set one in the installer. So now I'm at a desktop and there are 3 updates. It won't let me install them. I find out that I'm not in the sudoers file. So, now I have a user account that works because I could set the password, but I can't change root without sudo, I can't install any packages or do anything useful without sudo capability.

Is there a default password for root that I can use to take full advantage of this install, or am I totally borked? Is another re-install attempt worth doing at this point? The installer saved my WiFi SSID and password between installs, so I'm wondering if I can set the root password in the Live CD/USB environment and have it transfer to the hard drive install that way. Any suggestions?

BTW, I picked this distro because I've decided that I want to develop for KDE (and linux in general) and this came with a lot of the necessities out of the box.

EDIT: I should have mentioned that I downloaded the Developer Edition, which could obviously make a difference.

I've run into the same problem. I've tried all four versions of Neon and the only one that appears to be working as expected right now is the User edition. Testing, Unstable, and Developer editions all appear to have the issue you described above.

Hopefully there is a solution to this, or maybe a new iso that resolves the issue.

I'd be willing to perform an update from User to Unstable/Developer edition but that doesn't appear to be straight forward. Perhaps I just didn't find the correct instruction to make it work.

Same here, so I installed Neon user, I then changed

/etc/apt/sources.list.d/neon.list

I changed both lines from /user to /unstable

then updated with

pkcon refresh && pkcon update

However, there was a discrepancy between pkcon and discover: they didn't know what the other had done. Anyway, when I rebooted, I didn't get a panel and discover listed more updates so I installed them with discover and it is fine now and on unstable 5.19.8. Maybe if I had just used discover? It's been more than a year from Neon for me so I simply assumed pkcon was still the thing. Anyway, I hope this helps.

An update on how to do this:

Install Neon User, run updates with Discover, logout and login.

Edit neon.list as above (tested with unstable but testing should be the same), run pkcon refresh, then update with Discover, it will complain, so logout.

Log back in (it will take a while ~1min) and re-run updates with Discover (as it should still be there, if not Ctrl-alt-F2 and run plasma-discover, then switch back with Ctrl-alt-F1).

Logout and login and all should be well.

My guess is this is a Calamares bug and Neon user is on the previous version.

This appears to work, thank you. The only issue I'm seeing now, hopefully the one one , is that when clicking on the application launcher search no longer works. i can manually select the application to launch but not search for it. when using "alt-space" i can still search. It only appears to affect the application launcher. Any thoughts on how to correct this issue?

I noticed that launcher search doesn't work on unstable but works ok on the user edition so it's a bug. Anyway I use the dashboard.