![]() Registered Member ![]()
|
Help!
So last night I attempted an update of something like 518 files per Discover. The initial upgrade failed. I attempted it again with the same result. Then I successfully update maybe a dozen or two selected files with no noticeable issues. This morning I started the system and neon stops prior to reaching the login screen. It looks like its hanging at the point where its attempting to recognize my hard drives. Its an understatement to say assistance would be appreciated. Loved Neon up to this strange occurrence... ![]() Thanks, Jeff |
![]() Registered Member ![]()
|
Can you get to a TTY console (e.g. Ctrl+Alt+F2)? If you can, login and try these commands:
Currently running KDE Neon 5.22.5 and 5.19.4 (with Windows 10 in a VM); migrated from Linux Mint 17.3
|
![]() KDE Developer ![]()
|
You don't need to sudo pkcon. pkcon is perfectly capable of asking for permissions as necessary.
Annoyed with bbcode since 1999.
|
![]() Registered Member ![]()
|
I didn't realize that because I don't usually need these commands, Discover usually works for me.
Currently running KDE Neon 5.22.5 and 5.19.4 (with Windows 10 in a VM); migrated from Linux Mint 17.3
|
![]() Registered Member ![]()
|
Thanks for the suggestions. I managed to log back in to Neon and its running well but Discover is not. I ran the command you suggested and ended up with similar issues. Discover will not upgrade anything even though its telling me 613 files are ready for upgrade. The error it gives is that Ubuntu (version number something) is not yet available. "signature failure" "Ubuntu bionic inrelease is not yet available" and it repeats variations of that 4 or 5 times... So I'm the only one with this problem I guess? Thanks, jeff |
![]() Registered Member ![]()
|
I ran your suggested commands and all seemed fine until I shut the system down.
When I booted back up the next day, no Neon logon. I ended up reinstalling Neon and formatted only the root partition. Neon reached the logon screen and I logged on. Many apps of course weren't available. Sometime later I attempted to re-add the apps using Discover. All seemed fine until I tried to launch one of the prior apps accidentally. Plasma crashed. I couldn't get it to restart via command line. I did get konsole to restart my pc and rebooted to no logon again. Once again I reinstalled and am in Neon Wayland as I type. I'm afraid to try to use Discover to do any upgrades. Any suggestions anyone on why this might be happening? Thanks, jeff |
![]() Registered Member ![]()
|
I have to admit that my impression of Discover so far is not very favorable.
I hesitate for the time being to install any of the apps that I would like to add or upgrade any files for fear of ending up with an inaccessible Neon again. Any help or even some sound speculation would be appreciated. Thanks again, Jeff |
Registered users: Baidu [Spider], Bing [Bot], Google [Bot], Yahoo [Bot]