On Thu, Jan 25, 2018 at 12:26 PM, Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote:
On 01/26/18 01:00, InvalidPath wrote:
> I did a cursory google last night for wayland on Plasma... didnt have much luck. I
> need to discover what part of Gnome borked me over this AM.
This thread has been rather long, and fragmented. So, just 2 observations which you
need to think about.
1. I tried Wayland on KDE on 2 machines and I was highly unimpressed. I would not
recommend it.
2. I see "gdm" mentioned at various times. GDM is the Gnome Display Manager. If
you're running it, and you removed the Gnome packages and you didn't enable another
display manager that would explain your blank screen.
After you remove the Gnome packages see what this link points to...
ll /etc/systemd/system/display-manager.service
Probably still pointing to gdm.service.
So, then issue...
systemctl -f enable sddm.service
The link should change..... Then reboot.
--
A motto of mine is: When in doubt, try it out
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Ah ha Ed! You might have just hit the nail on the head ( and yeah sorry for the frags.. we're neck deep in TLS stuff at work, then my personal issues I got cross-wired for a spell)
So looking in the display-manager.service I see the following:
[Unit]
Description=GNOME Display Manager
# replaces the getty
Conflicts=getty@tty1.service
After=getty@tty1.service
# replaces plymouth-quit since it quits plymouth on its own
Conflicts=plymouth-quit.service
After=plymouth-quit.service
# Needs all the dependencies of the services it's replacing
# pulled from getty@.service and plymouth-quit.service
# (except for plymouth-quit-wait.service since it waits until
# plymouth is quit, which we do)
After=rc-local.service plymouth-start.service systemd-user-sessions.service
# GDM takes responsibility for stopping plymouth, so if it fails
# for any reason, make sure plymouth still stops
_OnFailure_=plymouth-quit.service
[Service]
ExecStart=/usr/sbin/gdm
KillMode=mixed
Restart=always
IgnoreSIGPIPE=no
BusName=org.gnome.DisplayManager
StandardOutput=syslog
StandardError=inherit
EnvironmentFile=-/etc/locale.conf
ExecReload=/bin/kill -SIGHUP $MAINPID
[Install]
Alias=display-manager.service
So I think you are right.. I'd have to change this file to point towards the PLasma equivalent of GDM.
Description=GNOME Display Manager
# replaces the getty
Conflicts=getty@tty1.service
After=getty@tty1.service
# replaces plymouth-quit since it quits plymouth on its own
Conflicts=plymouth-quit.service
After=plymouth-quit.service
# Needs all the dependencies of the services it's replacing
# pulled from getty@.service and plymouth-quit.service
# (except for plymouth-quit-wait.service since it waits until
# plymouth is quit, which we do)
After=rc-local.service plymouth-start.service systemd-user-sessions.service
# GDM takes responsibility for stopping plymouth, so if it fails
# for any reason, make sure plymouth still stops
_OnFailure_=plymouth-quit.service
[Service]
ExecStart=/usr/sbin/gdm
KillMode=mixed
Restart=always
IgnoreSIGPIPE=no
BusName=org.gnome.DisplayManager
StandardOutput=syslog
StandardError=inherit
EnvironmentFile=-/etc/locale.conf
ExecReload=/bin/kill -SIGHUP $MAINPID
[Install]
Alias=display-manager.service
So I think you are right.. I'd have to change this file to point towards the PLasma equivalent of GDM.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
