Re: x11/sddm fails to start with latest ports on current
Date: Tue, 04 Apr 2023 15:51:57 UTC
Hi, so I need to have this working one way or another, so I bypassed sddm and launched X directly (via xinit/startx) and in either cases I end up with this: [ 71.222] (II) Using input driver 'libinput' for 'System keyboard multiplexer' [ 71.222] (**) System keyboard multiplexer: always reports core events [ 71.222] (**) Option "Device" "/dev/input/event0" [ 71.222] (EE) Segmentation fault at address 0xb0 [ 71.222] (EE) Fatal server error: [ 71.222] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 71.222] (EE) [ 71.222] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 71.222] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 71.222] (EE) At the same time I see this in /var/log/messages Apr 4 16:26:13 kernel: pid 97974 (Xorg), jid 0, uid 0: exited on signal 6 Apr 4 16:26:21 devd[82755]: notify_clients: send() failed; dropping unresponsive client Is anyone else experiencing this issue with current? Thank you. BR, El 2023-04-03 17:55, José Pérez escribió: > Hi, > I am experiencing sddm failing with this error: > [12:55:45.875] (II) DAEMON: Running: /usr/local/bin/X -nolisten tcp > -auth /var/run/sddm/{4222cd10-f4fa-45ce-a0e0-ec395a5e9be0} -background > none -noreset -displayfd 17 -seat seat0 vt9 > [12:55:46.584] (EE) DAEMON: Failed to read display number from pipe > [12:55:46.584] (EE) DAEMON: Could not start Display server on vt 9 > > This used to work up to ports/current from a few weeks ago. > > > I checked perms in /var/lib/sddm/ and they seem ok > drwxr-xr-x 4 sddm sddm 4 Apr 3 12:43 sddm/ > > I have dbus running (but not hald). > > Can anyone reproduce or has idea what to look for? > > Env: > FreeBSD 14.0-CURRENT #1 main-n261959-cfccc7f30a01: Mon Apr 3 06:28:40 > CEST 2023 > sddm-0.19.0_8 QML based login manager > > > Thanks. > BR, -- José Pérez