On 28/2/18 10:11 am, Ed Greshko wrote:
On 02/28/18 04:37, Stephen Morris wrote:
> I might be getting confused with Ubuntu, but I thought there was a .conf file
> somewhere that held the specification of the default display manager that could
> easily be edited to swap between any of the available display managers that you
> happen to have installed.
With the advent of systemd there hasn't been a configuration file for a long time.
It is extremely easy to switch between DM's.
systemctl --force enable gdm or kdm, or sddm, or lightdm or whatever.
Thanks Ed, I switched from gdm to kdm by the following:
sudo systemctl disable gdm.service
sudo systemctl enable kdm.service
With kdm I don't get the issue, so to try and debug where/what the issue
is I switched back to gdm which as expected exhibited the issue again.
To eliminate the old issue of gdm and kde not functioning together
properly I started up gnome (both gnome, I assume with wayland, and
gnome for xorg). It appeared from this that the system update I did that
prompted this mail has stuffed gnome on my system. The gnome session I
started was running the wrong resolution, it wasn't running the
resolution it was on the last time I used gnome, the horrific lag that
gdm was getting the gnome desktop was as well, and when I eventually was
able to start konsole for the shell as I always do, the konsole session
went haywire with things like randomly single keypresses storming that
key across the screen. Despite all this I was able to start top, which
highlighted that Gnome-Shell was using 450 - 800 % of the cpu, so it
looks like the updated stuffed gnome-shell on my system, but I'm not
sure that that explains the desktop resolution being destroyed. The next
question with this is how, as a starting point do we get Gnome-Shell fixed.
regards,
Steve
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org