We’re saying the same thing. Whether it occured because of the update or during the update either due to the update itself or the hardware or the previous software, the system was borked. There’s no way to tell what the actual cause was as too many varibles were changed at once, as my system has been running for a 2-3 years with a few bit of unknowns installed before the update, and this live iso is more or less from March and rather lean yet i’ve had issues installing on a few random pcs that i’ve come across using this exact usb drive using the same iso file. Here is a link to a problem i had with it on a laptop, and all i did was reinstall again to fix it. It happens on windows too, planets/moon/sun or something in the wrong spot lol.
Hope everyone had a good thanksgiving. I’m going to attempt reinstalling, wish me luck.
1 Like
Why luck? I wish you success. 
2 Likes
Thanks everyone. I managed to reinstall, and since /home was separate, i kept my user and settings. It wasnt too hard, i made the mistake of creating a different username and trying to add my old user back, only to have the wrong uid and gid.
After I created a third user (the first was the new one that came with the fresh install, the second was the old one i added back) i was able to remove the freshly installed user and replace my old user with the fresh ones uid and gid, which was the default id of 1000, which matched my old home directory. Had to add it to the wheel group also for sudo. But it worked 
Ill have to redownload all of my programs, but that wont be hard since i tend to use them often. Im bound to run into them being missing lol (i should really keep a list.)
CPU usage is now a nice and cool 0.8% with an animated background and 1000 firefox tabs and 5 windows open and all info from opengl and opencl are normal. I still have this in the KDE info center:
_amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)
amdgpu: amdgpu_device_initialize failed.
_amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)
But after checking elsewhere, it seems it is because the KDE info center doesnt run as sudo, which if ran as sudo the error goes away, so it is a non issue.
Thanks again
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
I originally flagged this as solved, but it was not solved. Upon installing programs the issue returned, but I found the culprit. The remote desktop connection program NoMachine is whats causing it, even with hardware acceleration enabled/disabled. After removing it, the issue is gone and has not come back. Thanks again everyone 
2 Likes
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.