Open webfinder42 opened 1 month ago
The default is to NOT update the existing configuration files. The right answer really should be DO update the existing configuration files unless you modified them, then in that case compare the 2 and include the changes made by us.
I'm sorry if I didn't express myself clearly enough but that is also what I did "No" to update the existing configuration files.
login screen with KDE works, but when I login with the user blackscreen/No desktop.
Do you want me to do this again on a new fresh installation and try again? or can you replicate the issue?
Yes and you will need to select Y to update the config files when apt asks you.
So I did it all two more times, fresh install on new SD card.
Booted into KDE started rsetup -> ran the update from the program Selected Yes to update config files when apt asked me [its a loong waiting time]
So I think I may have found the problem, either it is because I only run with 1 user on the system and have deleted the "rock" user from the Radxa First Boot Configuration (config.txt) and then I also added this:
Configure locale
Commands:
update_locale
update_locale da_DK.UTF-8
It works after a default image now... where i did not edit the config file.. its just funny that all works but cannot be updated after removing 1 user and updating the locals
Does the system need both rock and radxa user?
I don't think the system needs either users. Locale might change some commands' output which might be more likely.
Can you check if both conditions must exist for it to fail to boot?
Okay I will try, I just have one question regarding before.txt, it only runs on first boot?
Yes. It will be deleted after the system is up.
I have done a fresh installation of this image: rock-4se_debian_bullseye_kde_b38.img.xz and ran an update through rsetup -> update
I get the login screen after reboot with KDE and can login with my user/password but KDE doesn't load the desktop? it is just completely black screen and can move the mouse around. (i can see the mouse)
What's wrong? and is there a fix?