On Sunday 08 April 2018 17:34:21 David C. Rankin wrote:
On 04/08/2018 09:21 AM, David C. Rankin wrote:
All,
On a new 42.3 install, the journal is filling with hundreds of messages on boot:
Apr 08 07:40:05 wizard systemd-udevd[1386]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
Why should systemd be looking for the /org/freedesktop/hal/udev_event?
Aren't we building with --nohal? or should I have installed something else to provide this dependency?
KDE3 is running great -- I was just surprised to see the boot messages when I checked with:
$ journalctl -n -l -b -p 3
Do we need to do something with:
/usr/lib/udev/rules.d/90-hal.rules ?
or create a dummy socket?
There are 1074 lines with this error generated in the journal on boot. I suspect this is also what is leading to the display-manager being reported as failed (which doesn't hurt anything since it is restarted between desktops):
sc -l status display-manager.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 2018-04-08 07:42:06 CDT; 1h 50min ago Process: 2916 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS) Tasks: 2 (limit: 512) CGroup: /system.slice/display-manager.service ├─3220 /opt/kde3/bin/kdm └─3252 /usr/bin/Xorg -br -nolisten tcp :0 vt7 -auth /var/lib/xdm/authdir/authfiles/A:0-fD4PDi
Apr 08 07:40:36 wizard display-manager[2916]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Apr 08 07:40:36 wizard display-manager[2916]: Starting service kdm..done Apr 08 07:40:36 wizard systemd[1]: display-manager.service: PID file /var/run/displaymanager.pid not readable (yet?) after start: No such file or directory Apr 08 07:40:46 wizard kdm[3856]: :0[3856]: pam_unix(xdm:session): session opened for user david by (uid=0) Apr 08 07:42:06 wizard systemd[1]: display-manager.service: Start operation timed out. Terminating. Apr 08 07:42:06 wizard systemd[1]: Failed to start X Display Manager. Apr 08 07:42:06 wizard systemd[1]: display-manager.service: Unit entered failed state. Apr 08 07:42:06 wizard systemd[1]: display-manager.service: Failed with result 'timeout'.
Any thoughts on fixing this?
just an ideas: a) diff to some other displaymanager service init file like /etc/systemd/system/xdm.service or something else. b) or just create custom service /etc/systemd/system/kdm3.service
-- 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