Reply-To:
blissInSanFrancisco@mouse-potato.com
On 3/21/25 08:40, Vincent Coen wrote:
Hello All!
My system that has multi partitions on a SSD (primary) and a HDD has had
some updates and needed a reboot because of some funnies with some
appl. seeing files.
So on the shutdown I booted into a 2nd partition holding MGA9 and updated that one and then did the same for a win10 system before rebooting to the primary one.
On the boot it showed the graphic screen but when completing the start up went to the tty service instead of booting up via sddm.
Now I logged in and tried running sddm but it could not find it (owned by root?) so I did a sudo sddm and while this worked (but showed flashing red screen) worked but any files created are owned by root so no good and am force to use the other MGA9 partition on a HDD.
So the question - How do I get back the primary system to boot into KDE GUI
?
While I cam running using the HHD system there are various packages not installed on it and it is a lot slower so would like to get back to using
the SSD version - plus it is annoying me that the problem arose anyway :(
Vincent
It is a large mistake to update anything to do with Windows
that is not Windows running in a Virtual Box. The reason is simple
Windows does kernel updates without warning you and rewrites its
UEFI partition with no regard for the GNU/Linux files. I read all
the time about people who run Windows and Linux on separate disks
but the same sort of problem occurs.
Updating a virtualized Windows instance may cause problems
with the virtual tool being used.
bliss - just my very humble opinion and a fact.
--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: nil (2:250/1@fidonet)