I am probably not the right person to debug the problem or make a recommendation as to right fix/hack. Having said that however, I have managed to trace back the problem to the following conflict between the stock displaymanager.service configuration and the stock wdm-config definitions: In /usr/lib/X11/display-manager (lines 141:147) we find; # for i in $DISPLAY_MANAGERS # do # name="${i}_vars" # type -t $name &> /dev/null || continue # PIDFILE=/var/run/$i.pid # $name $DM && break # done So logically enough $PIDFILE is defined as /var/run/wdm.pid and later in /usr/lib/X11/display-manager (line 207) /var/run/displaymanager.pid is linked to /var/run/wdm.pid # ln -snf $PIDFILE $PIDFILELNK However in /etc/X11/wdm/wdm-config (lines 6:13) the following configuration is set # DisplayManager.errorLogFile: /var/log/xdm.errors # DisplayManager.pidFile: /var/run/xdm.pid # DisplayManager.authDir: /var/lib/xdm # DisplayManager.keyFile: /etc/X11/xdm/xdm-keys # DisplayManager.servers: /etc/X11/xdm/Xservers # DisplayManager.accessFile: /etc/X11/xdm/Xaccess So when wdm is started it sets /var/run/xdm.pid as its PID file. So the displaymanager.service is never able to find the wdm.pid PID file. For now I have fixed this by defining DisplayManager.pidFile as /var/run/wdm.pid in /etc/X11/wdm/wdm-config (line 7). WDM and Windomaker are now running once again as well as they always did in older versions of openSUSE. I don't know if this is the best way to fix this, so any suggestion welcome. Also if there is a better place to file this feedback with the openSUSE developers or the Windowmaker developers, just let me know. Michael On 17/02/2019 16:04, Michael Hieb wrote:
On February 17, 2019 8:35:39 PM UTC, "Carlos E. R." <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday, 2019-02-17 at 16:14 -0000, Michael Hieb wrote:
...
## update-alternatives --config default-displaymanager ... # * 5 /usr/lib/X11/displaymanagers/wdm 10 manual mode
Here is the output from journalctl and systemctl -l status displaymanager.service. ## systemctl -l status displaymanager.service # display-manager.service - X Display Manager # Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled) # Active: failed (Result: timeout) since Sun 2019-02-17 15:09:37 GMT; 4min 9s ago # Process: 2592 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS) # Tasks: 7 (limit: 4915) # Memory: 127.3M # CGroup: /system.slice/display-manager.service # ├─2671 /usr/bin/wdm # ├─2673 /usr/bin/wdm # ├─2676 /usr/bin/X -nolisten tcp -br vt7 -keeptty -auth /var/lib/xdm/authdir/authfiles/A:0-iKlpYk # └─2753 -:0 # # Feb 17 15:08:07 espejo display-manager[2592]: Command: localectl set-keymap uk #Feb 17 15:08:08 espejo display-manager[2592]: I: Using systemd /usr/share/systemd/kbd-model-map mapping #Feb 17 15:08:08 espejo root[2622]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers #Feb 17 15:08:08 espejo root[2622]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config # Feb 17 15:08:08 espejo display-manager[2592]: Starting service wdm..done # Feb 17 15:08:08 espejo systemd[1]: display-manager.service: Can't open PID file /var/run/displaymanager.pid (yet?) after start: No such file or directory #Feb 17 15:09:37 espejo systemd[1]: display-manager.service: Start operation timed out. Terminating. #Feb 17 15:09:37 espejo systemd[1]: display-manager.service: Failed with result 'timeout'. # Feb 17 15:09:37 espejo systemd[1]: Failed to start X Display Manager. # Feb 17 15:09:37 espejo systemd[1]: display-manager.service: Triggering OnFailure= dependencies. Beyond noting that the service fails to write /var/run/displaymanager.pid, I cannot spot the problem. Well, it is starting xdm, not wdm. See the references to /etc/init.d/xdm in the log.
In the past, changing displaymanager was not possible if it was running. The correct procedure would be to switch to text mode (runlevel 3), thus stopping the display manager, then change it, then start it again by going to runlevel 3. Else, the system would try to stop the wdm when what was
running yet was xdm, thus fail.
Maybe you just need to reboot. I rebooted after making the change, upon which I experience the timeout.
- -- Cheers, Carlos E. R. (from openSUSE 15.0 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXGnFmxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVw28AoJNB/ppvt1uCzhwEjNz0 wtTvLJBhAJ43WtoPKWM6whx9P27XR0AtM9Bepg== =ZOzq -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org