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

  • Starting KDE gui system

    From Vincent Coen@2:250/1 to All on Thu Mar 13 17:44:08 2025
    Hello All!

    After an update to MGA 9 on a SSD and having strange results read a file produced in a Cobol program that produces Error 61 File sharing Failure
    when no other instance of any program in application running I decided to reboot the system and at the same time check for updates on my MGA 9 test partition on a HDD.

    So having done that I reboot the system and decided to also do a update procedure for my Windows 10 system also on the HDD (possibly a wee
    mistake).

    After some 4 hours I noticed that the screen was locked with a low
    percentage for two fix packs downloading so decided to reboot back into
    Windows to try and get it to continue - which it did abet after a further 2 hours. I should point out that I have a 135Mb download connection via a
    Virgin Media cable link so it is not my speed :(
    Just down to MS servers etc and 2 - 3 hours is more the norm.

    After all this and letting W10 reboot a time or two I reboot into my
    primary MGA system on the SSD - whoch was the reason for doing all this in
    the 1st place only to find that it booted into the non graphic login for
    tty1 - ditto tty2 through tty6 available via alt/ctl/f2 - f6.

    So then tried run sddm which failed finding it so did a sudo sddm and while running found that any created files are owned by root - so not good.

    I gave up at this point and loaded the 2nd partition (HDD) and got the
    system up and running but as the HDD is a WD Red a lot slower but it
    allowed the system to run my bbs, apache and ftp services. Left it and went
    to bed as it was now close to 04:00.

    Needless to say next day I cannot think of a way around this as looking at
    the grub2 data having pressed e on the boot menu found they looked the same between the SSD which works and the HDD which does not boot to KDE.

    So the question - How the devil do I get the SSD to boot into the KDE GUI.


    Please help as the HDD system has missing apps like texlive and that when installing does not work so well producing errors so really need to get the
    SSD working again andNO, I have no idea what went wrong or what I did that
    has caused this sorry state of affairs to my system.




    Vincent



    SEEN-BY: 25/0 21 250/0 1 2 3 4 5 8 13 14 15 362/6 712/1321
  • From David W. Hodgins@2:250/1 to All on Thu Mar 13 19:45:36 2025
    On Thu, 13 Mar 2025 13:44:08 -0400, Vincent Coen <[email protected]> wrote: <snip>
    So then tried run sddm which failed finding it so did a sudo sddm and while running found that any created files are owned by root - so not good.
    <snip>

    Not sure what caused the problem, but most likely there are now root owned files
    in /home.

    From https://wiki.mageia.org/en/Never_use_just_su

    =============
    If the mistake has already been made, it can be fixed with:
    $ su -
    Password:
    # chown -Rc tester:tester /home/tester

    The option "c" for chown causes the command to show the changes it has made and option "R" stands for recursively. You need to exchange "tester" with your actual user id.

    If IMAP is used for mail, the mail directory will need to have it's group changed back to mail with:
    # chgrp -Rc mail ~/mail
    =============

    Then reboot. If that doesn't fix it, try a different display manager.

    Regards, Dave Hodgins

    --- MBSE BBS v1.1.0 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Vincent Coen@2:250/1 to David W. Hodgins on Thu Mar 13 21:15:02 2025

    Hello David!

    13 Mar 25 19:45, David W. Hodgins wrote to all:

    On Thu, 13 Mar 2025 13:44:08 -0400, Vincent Coen <[email protected]>
    wrote: <snip>
    So then tried run sddm which failed finding it so did a sudo sddm
    and while running found that any created files are owned by root -
    so not good.
    <snip>

    Not sure what caused the problem, but most likely there are now root
    owned files in /home.

    From https://wiki.mageia.org/en/Never_use_just_su

    =============
    If the mistake has already been made, it can be fixed with:
    $ su -
    Password:
    # chown -Rc tester:tester /home/tester


    How do I recover/reset, etc, the primary system to use the KDE Gui ?



    Vincent



    SEEN-BY: 25/0 21 250/0 1 2 3 4 5 8 13 14 15 362/6 712/1321