On 02/10/2018 02:14 AM, David C. Rankin wrote:
On 02/10/2018 01:15 AM, Felix Miata wrote:
Well, that's what I have too and that hasn't changed in a long time. Do you have any other desktop installed that you can check startx with? (I generally install fluxbox and i3) Like 'startfluxbox' or 'startkde' from the command line? The problem is on this my main machine, so I'm not shutting down KDM or the session and 15 open apps to try.
Uugh Felix,
I'm being stupid... I didn't focus on the "display-manager service works as expected" part.
So kdm is working as expected an the problem are the error messages:
Jul 19 07:03:49 systemd[1]: display-manager.service start operation timed out. Terminating. Jul 19 07:03:49 systemd[1]: Failed to start X Display Manager. Jul 19 07:03:49 systemd[1]: Unit display-manager.service entered failed state.
You have launched KDE3 from kdm and it then enters a failed state? Can you "Log Out", "End Current Session" and get back to the kdm greeter? Or, is that the problem, once it is launched, you can't logout and have the X-session reset to bring kdm back up?
Also, your kdm is behaving just like my kdm and I'd never picked through the logs to check, e.g. $ jcnl -b -u display-manager -- Logs begin at Thu 2018-02-01 23:18:24 CST, end at Sat 2018-02-10 02:15:12 CST. -- Feb 08 14:57:52 wizard systemd[1]: Starting X Display Manager... Feb 08 14:57:53 wizard display-manager[2008]: /etc/vconsole.conf available Feb 08 14:57:53 wizard display-manager[2008]: KEYMAP: us Feb 08 14:57:53 wizard display-manager[2008]: Command: localectl set-keymap us Feb 08 14:57:53 wizard display-manager[2008]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Feb 08 14:57:53 wizard display-manager[2008]: Starting service kdm..done Feb 08 14:57:53 wizard systemd[1]: display-manager.service: PID file /var/run/displaymanager.pid not readable (yet?) after start: No such file or directory Feb 08 14:59:22 wizard systemd[1]: display-manager.service: Start operation timed out. Terminating. Feb 08 14:59:22 wizard systemd[1]: Failed to start X Display Manager. Feb 08 14:59:22 wizard systemd[1]: display-manager.service: Unit entered failed state. Feb 08 14:59:22 wizard systemd[1]: display-manager.service: Failed with result 'timeout'. Feb 08 15:04:43 wizard kdm[2972]: :0[2972]: pam_unix(xdm:session): session opened for user david by (uid=0) I think this is normal behavior. kdm calls startkde if that is the session you chose and then dies. It stays dead until you logout which triggers a re-init of the display and launches another kdm session. Now there are some aspects of kdm (and the current kdm for FW5) that have never been squared with systemd (multi-seat, etc..) That's why we still have the setting (somewhere) to reinitialize display on logout -- to trigger a restart of the display manager. It's been about 3 years since I waded though all this building TDE on arch. This behavior isn't unique to suse and is more the ratty behavior of the display managers being shoehorned into systemd (and plymouth, etc..) Looking 13.1 initialized kdm differently, not using display-manager.service. but a symlink to startkdm (the specifics of which I have forgotten). -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org