1. Forum
  2. FidoNet
  3. ALT.OS.LINUX.MAGEIA

  • System NOT booting into KDE Gui

    From Vincent Coen@2:250/1 to All on Fri Mar 21 15:40:37 2025
    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



    SEEN-BY: 25/0 21 250/0 1 2 3 4 5 8 13 14 15 362/6 712/1321
  • From Gilberto F da Silva@2:250/1 to All on Sat Mar 22 00:07:27 2025

    9sj1kdId3qarXIfXddRGm1yA2fJMYuekHhqsLYoSspZFlOGhP3czTsLwIzaawBjQnHL36Um 2wbXsHP3H2+HdWyp/eQ13UjRO58QEEGcwS8htp9nfFy7myEx9gqBBztskm1VeUzUFW/GGBnu CO/1iLfDt6lXob1vogq4+QXNmzsx6NjtQ91ZD5a4XtB+BMW6bpknQAtyYj30mIPa/y8n6eYv 7HnfBIkI7bl6OQ85/+LlQoKuMExs4SVm9RJeBeFhhMLyzc+/lVURWvStgX6FgHdMwwxnUK13 /T71SeXVBQvk4zYmpHMTgU7uTO2v8vNSIyjJV6H+4yRC8nwllrCvGuUr3iTT0LpB7l1DSi5M jqZJA/51Df95hyyUjy+T9jb6ljvY1QZxea4qusI+XWJ6OBuL6d5fxDWq1tDzx0bzAWgGyvMk HQIv+6iRkUmRidklkJCuOzZ9vOxnMFPLyXgIqytiq2/JsT+Nl9r7wbr5cTE159u7LVAoITCF WygqGzdAT3/IMMuC3em3i+AGPxBX7hH3xWDZxhQy+jNIhTfvi7JJ30t4DjhT3WWMSt5bso9X 29/5+T8bXNfXlHqoE/ebjwADBQ//ck3LyNoQcycCZEYkiBds24ReyAMs+tX8VY1HBHYfC4m6 h+g1JnO6J5CAnxZh4j/uFIOqdiaryVMu4eTIcvRQnrK3orzUNSkpsGSkdZb+04CEc3pOBygk K1HskK+qOr173+NcnCqCSOJhKHX42V7Ez7WfR0BAZQSSY/hY/IDsDpILh+r53WvmrPauYJ/Y STYtJbT+O/xACKfPG9n6HteXIDr8pSpDDeFWQBtIRiqJH20d1remGLVWQKzM6N6T7aFnxpzi 7blICODDHX4KD6K+zJu/uWPxTKgP27cEquKN8ZTGZQBZTmyKxF6utL3ljWE+JvL5zQ0xzwHK 90vbLAiBVFn2Pr0yqjZKdJ3s871I+Ilk3/QKWbBOcsqKiXpK5t+mFSvTVF5RYhVKDnAC4KCd RDVOw5zcYQyFKfmzPEO9u22hZm2Cq3OwviBo/KcXlLedG6TqacjDkLKBEhq1du7m0ZdAlQIf kqgVDsyS0BwM6Clsi5NPdi96XrHUxSg1t4bK02zqRvXF5dM/jKNOh0nM/SZhaHrCphmHxZzi sXMnr4TXZlbdHVDFRHCf2zxldMEbHUVXxO0/2AzFV3RFjZJPesCjitDasXTe14b/DYL3EI8O dxc1fFSN6nxDnXCi/pnD/r1znY/CwlQXAg0f2NjNv3ydBZ0pGKdC5qfUdMQA4a2IYQQYEQgA CQUCZk59rAIbDAAKCRB0C/CavLb3GhglAP9bhXjIBHPyyAI/xqgTmGkDqi5rNaa5tN8LHf1M pPyNiwD/UUOzfgpWhsFfVRC1FopTuJ3UjpSvmDMDJVy2Lp4A4Mw=
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256

    Vincent Coen escreveu:
    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


    On machines using systemd, you can use the command:

    systemctl set-default graphical.target

    to set the graphical boot as default.

    - --

    Abraços

    Gilberto F da Silva
    -----BEGIN PGP SIGNATURE-----
    Comment: +-----------------------------------------------------+
    Comment: ! https://t.me/Gilberto_F_da_Silva !
    Comment: +-----------------------------------------------------+

    iHUEAREIAB0WIQSWDU9sZ+hOyX91n7l0C/CavLb3GgUCZ93/PwAKCRB0C/CavLb3 GtbJAP9+uD2DATtl4qZ8B62ndRAcHFaCEDk496Si99Afe9cKzgEAlhsS4SAMiK3b Uplrq87gGmys001tiNCAd9QMOIFui1Y=
    =Kh8F
    -----END PGP SIGNATURE-----

    --- MBSE BBS v1.1.0 (Linux-x86_64)
    * Origin: Hejmo (2:250/1@fidonet)
  • From Bobbie Sellers@2:250/1 to All on Mon Apr 14 21:19:53 2025
    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)