[opensuse-kde3] "failed" display-manager service works as expected
# journalctl -u display-manager -- Logs begin at Mon 2016-11-28 04:06:57 EST, end at Wed 2018-01-31 04:15:02 EST. -- Jun 30 23:06:36 kdm[12087]: :0[12087]: pam_unix(xdm-np:session): session opened for user ##### by (uid=0) -- Reboot -- Jul 19 07:02:19 systemd[1]: Starting X Display Manager... Jul 19 07:02:19 display-manager[1647]: /etc/vconsole.conf available Jul 19 07:02:19 display-manager[1647]: KEYMAP: us Jul 19 07:02:19 display-manager[1647]: Command: localectl set-keymap us Jul 19 07:02:19 display-manager[1647]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Jul 19 07:02:19 display-manager[1647]: Starting service kdm..done Jul 19 07:02:19 systemd[1]: PID file /var/run/displaymanager.pid not readable (yet?) after start. Jul 19 07:02:20 kdm_config[1672]: Multiple occurrences of key 'AllowRootLogin' in section [X-*-Core] of /opt/kde3/share/config/kdm/kdmrc Jul 19 07:02:20 kdm_config[1672]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Jul 19 07:02:20 kdm_config[1672]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Jul 19 07:03:47 kdm[1691]: :0[1691]: pam_unix(xdm-np:session): session opened for user #### by (uid=0) 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. ... -- Reboot -- Jan 30 23:04:00 systemd[1]: Starting X Display Manager... Jan 30 23:04:02 display-manager[1770]: /etc/vconsole.conf available Jan 30 23:04:02 display-manager[1770]: KEYMAP: us Jan 30 23:04:02 display-manager[1770]: Command: localectl set-keymap us Jan 30 23:04:03 display-manager[1770]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Jan 30 23:04:03 display-manager[1770]: Starting service kdm..done Jan 30 23:04:03 systemd[1]: display-manager.service: PID file /var/run/displaymanager.pid not readable (yet?) after start: No such file or directory Jan 30 23:04:03 kdm_config[1816]: Multiple occurrences of key 'AllowRootLogin' in section [X-*-Core] of /opt/kde3/share/config/kdm/kdmrc Jan 30 23:04:03 kdm_config[1816]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Jan 30 23:04:03 kdm_config[1816]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Jan 30 23:05:04 kdm[1825]: :0[1825]: pam_unix(xdm-np:session): session opened for user ##### by (uid=0) Jan 30 23:05:30 systemd[1]: display-manager.service: Start operation timed out. Terminating. Jan 30 23:05:30 systemd[1]: Failed to start X Display Manager. Jan 30 23:05:30 systemd[1]: display-manager.service: Unit entered failed state. Jan 30 23:05:30 systemd[1]: display-manager.service: Failed with result 'timeout'. I see no evidence of KDM failure using the PC. I'm typing this in a KDE3 session started from KDM3. Why are these putative systemd failure messages in the journal? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 01/31/2018 03:46 AM, Felix Miata wrote:
Jan 30 23:05:04 kdm[1825]: :0[1825]: pam_unix(xdm-np:session): session opened for user ##### by (uid=0) Jan 30 23:05:30 systemd[1]: display-manager.service: Start operation timed out. Terminating. Jan 30 23:05:30 systemd[1]: Failed to start X Display Manager. Jan 30 23:05:30 systemd[1]: display-manager.service: Unit entered failed state. Jan 30 23:05:30 systemd[1]: display-manager.service: Failed with result 'timeout'.
this is an X issue and not KDM. Do you have KDE set as default DM in sysconfig? -- 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
David C. Rankin composed on 2018-02-09 21:23 (UTC-0600):
Felix Miata wrote:
Jan 30 23:05:04 kdm[1825]: :0[1825]: pam_unix(xdm-np:session): session opened for user ##### by (uid=0) Jan 30 23:05:30 systemd[1]: display-manager.service: Start operation timed out. Terminating. Jan 30 23:05:30 systemd[1]: Failed to start X Display Manager. Jan 30 23:05:30 systemd[1]: display-manager.service: Unit entered failed state. Jan 30 23:05:30 systemd[1]: display-manager.service: Failed with result 'timeout'.
this is an X issue and not KDM. Do you have KDE set as default DM in sysconfig?
# grep kdm /etc/sysconfig/displaymanager DISPLAYMANAGER="kdm3" # rpm -qa | grep dm- | grep kd kdebase3-kdm-3.5.10.1-329.2.x86_64 -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 02/09/2018 09:41 PM, Felix Miata wrote:
David C. Rankin composed on 2018-02-09 21:23 (UTC-0600):
Felix Miata wrote:
Jan 30 23:05:04 kdm[1825]: :0[1825]: pam_unix(xdm-np:session): session opened for user ##### by (uid=0) Jan 30 23:05:30 systemd[1]: display-manager.service: Start operation timed out. Terminating. Jan 30 23:05:30 systemd[1]: Failed to start X Display Manager. Jan 30 23:05:30 systemd[1]: display-manager.service: Unit entered failed state. Jan 30 23:05:30 systemd[1]: display-manager.service: Failed with result 'timeout'.
this is an X issue and not KDM. Do you have KDE set as default DM in sysconfig?
# grep kdm /etc/sysconfig/displaymanager DISPLAYMANAGER="kdm3" # rpm -qa | grep dm- | grep kd kdebase3-kdm-3.5.10.1-329.2.x86_64
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? Also what about the systemd startup of the DM? Any changes from 42.2? $ cat /usr/lib/systemd/system/display-manager.service [Unit] Description=X Display Manager Requires=var-run.mount Conflicts=getty@tty7.service plymouth-quit.service After=ypbind.service gpm.service time-sync.target winbind.service acpid.service Wants=remote-fs.target dbus.socket systemd-user-sessions.service systemd-logind.service After=remote-fs.target dbus.socket systemd-user-sessions.service systemd-logind.service getty@tty7.service plymouth-quit.service [Service] Type=forking PIDFile=/var/run/displaymanager.pid ExecStart=/usr/lib/X11/display-manager start ExecStop=/usr/lib/X11/display-manager stop ExecReload=/usr/lib/X11/display-manager reload KillMode=process [Install] WantedBy=graphical.target Alias=xdm.service Really strange? -- 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
David C. Rankin composed on 2018-02-10 00:26 (UTC-0600):
Felix Miata wrote:
David C. Rankin composed on 2018-02-09 21:23 (UTC-0600):
Felix Miata wrote:
Jan 30 23:05:04 kdm[1825]: :0[1825]: pam_unix(xdm-np:session): session opened for user ##### by (uid=0) Jan 30 23:05:30 systemd[1]: display-manager.service: Start operation timed out. Terminating. Jan 30 23:05:30 systemd[1]: Failed to start X Display Manager. Jan 30 23:05:30 systemd[1]: display-manager.service: Unit entered failed state. Jan 30 23:05:30 systemd[1]: display-manager.service: Failed with result 'timeout'.
this is an X issue and not KDM. Do you have KDE set as default DM in sysconfig?
# grep kdm /etc/sysconfig/displaymanager DISPLAYMANAGER="kdm3" # rpm -qa | grep dm- | grep kd kdebase3-kdm-3.5.10.1-329.2.x86_64
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. If I login on vtty3 and startx either KDE3 or IceWM to :1, no new dmessages or journal messages are generated. This is the dmesg tail: [783013.870346] CIFS VFS: bogus file nlink value 0 [783016.334736] CIFS VFS: bogus file nlink value 0 [783016.445703] CIFS VFS: bogus file nlink value 0 [839304.070453] fctar[14428]: segfault at 2d0 ip 00007f600916c911 sp 00007ffd8adb51d0 error 4 in libpthread-2.22.so[7f6009163000+18000] [871076.996885] CIFS VFS: bogus file nlink value 0 [871077.394883] CIFS VFS: bogus file nlink value 0 [871078.435236] CIFS VFS: bogus file nlink value 0 [871078.685051] CIFS VFS: bogus file nlink value 0 That fctar error was from trying to read a .tgz file misnamed .zip.
Also what about the systemd startup of the DM? Any changes from 42.2?
$ cat /usr/lib/systemd/system/display-manager.service [Unit] Description=X Display Manager Requires=var-run.mount Conflicts=getty@tty7.service plymouth-quit.service After=ypbind.service gpm.service time-sync.target winbind.service acpid.service Wants=remote-fs.target dbus.socket systemd-user-sessions.service systemd-logind.service After=remote-fs.target dbus.socket systemd-user-sessions.service systemd-logind.service getty@tty7.service plymouth-quit.service
[Service] Type=forking PIDFile=/var/run/displaymanager.pid ExecStart=/usr/lib/X11/display-manager start ExecStop=/usr/lib/X11/display-manager stop ExecReload=/usr/lib/X11/display-manager reload KillMode=process
[Install] WantedBy=graphical.target Alias=xdm.service
Really strange?
If there is I'm missing it: cat /usr/lib/systemd/system/display-manager.service [Unit] Description=X Display Manager Requires=var-run.mount Conflicts=getty@tty7.service plymouth-quit.service After=ypbind.service gpm.service time-sync.target winbind.service acpid.service Wants=remote-fs.target dbus.socket systemd-user-sessions.service systemd-logind.service After=remote-fs.target dbus.socket systemd-user-sessions.service systemd-logind.service getty@tty7.service plymouth-quit.service [Service] Type=forking PIDFile=/var/run/displaymanager.pid ExecStart=/usr/lib/X11/display-manager start ExecStop=/usr/lib/X11/display-manager stop ExecReload=/usr/lib/X11/display-manager reload KillMode=process [Install] WantedBy=graphical.target Alias=xdm.service -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
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? -- 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
David C. Rankin composed on 2018-02-10 02:14 (UTC-0600):
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?
The only thing wrong that I can see is inexplicable error messages being logged. KDM and sessions aren't working any worse than expected by the open KDE3 BOO bugs, e.g. https://bugzilla.opensuse.org/show_bug.cgi?id=1047852 -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
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
participants (2)
-
David C. Rankin -
Felix Miata