there is a problem with the display managers (GDM, LightDM)... judging by the logs, they start without errors, but after starting, the monitors switch to power saving mode and do not react to anything...

  • OK, i solved the problem

    for some reason the mesalib libraries were broken
    i checked it via eopkg check mesalib mesalib-32bit

    i just reinstalled them and voila

Can you elaborate a bit further?
Is this problem occuring after boot in login-manager if you don't login right away? Or after you have logged into your DE?
What edition of Solus are you using?

Does this happen in a live ISO or on a installed system? Because you are referring to Solus 4.5.
Is your system up to date? If so, you are basically running Solus 4.6.

Can you describe the problem further?

    Sebastian

    Is this problem occuring after boot in login-manager if you don't login right away?

    Yes, it is.

    What edition of Solus are you using?

    Originally it was MATE edition (in 2019), but now i have installed 4 GTK-based DE (MATE, GNOME, Budgie, Xfce). Before that, this setup worked perfectly.

    Does this happen in a live ISO or on a installed system? Because you are referring to Solus 4.5.

    I didn't try...

    Is your system up to date? If so, you are basically running Solus 4.6.

    Yes, it was yesterday, but version 4.5 is written in /etc/os-release.

      As it was discussed in Solus 4.6 Release Thread, for some technical issues an up to date Solus identifies currently as 4.5, even through it is actually 4.6.

      Having 4 DE's installed might be a recipe for trouble.
      In your Initial post, you mention 2 login managers, one of them GDM.

      Are you using GDM?
      Cause this sounds a bit to me like an issue where GDM automatically sends your computer to suspend if you haven't logged in within 5 minutes.
      Might this be your issue?
      In this case pressing power button might wake you up from suspend.
      If suspend is working on your machine.
      Since suspend is prone to break, it's just a stupid GDM default.

        Sebastian

        Are you using GDM?

        I have tried both DM and GDM and LightDM installed separately at different times.

        Anyway, i will be waiting for the upgrade to v4.6 via eopkg. If something goes wrong after this upgrade, I will write about it in this thread.
        Sorry, i read about the os-release issue after i posted this.

        My computer does not suspend work. DM just turn off both my monitors.

            etokarew After installing gdm or lightdm (or really any other of the conflicting packages) try a sudo usysconf run -f It seems that some usysconf triggers do not run for replaced packages

                Staudey

                I used different Display Managers because this problem occurred after a regular reboot of my PC (in this time it was GDM). I tried LightDM and got the same thing.

                try a sudo usysconf run -f It seems that some usysconf triggers do not run for replaced packages

                I have run it, and everything seems to be fine. But after that i did not reboot my PC, i just restarted the DM service via systemctl restart lightdm.service.

                  OK, i solved the problem

                  for some reason the mesalib libraries were broken
                  i checked it via eopkg check mesalib mesalib-32bit

                  i just reinstalled them and voila

                    etokarew OK, i solved the problem

                    Oh sorry, as per your previous post it sounded like the problem was already solved. That's why I (and I assume others) provided no more input)