Date: Fri, 07 Apr 2023 12:08:41 +0200 From: =?UTF-8?Q?Jos=C3=A9_P=C3=A9rez?= <fbl@aoek.com> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: x11@freebsd.org Subject: Re: x11/sddm fails to start with latest ports on current Message-ID: <3c1530adecb5634e998f385a2e9091f2@mail.yourbox.net> In-Reply-To: <20230404181410.b5d4212200109e475e1e7801@bidouilliste.com> References: <bfe2742acda80d52923d70391235bdcf@mail.yourbox.net> <ee7a370bbba3226f40d46e37af70cb4b@mail.yourbox.net> <20230404181410.b5d4212200109e475e1e7801@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
El 2023-04-04 18:14, Emmanuel Vadot escribió: > On Tue, 04 Apr 2023 17:51:57 +0200 > José Pérez <fbl@aoek.com> wrote: > >> 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, > > Yes this is (was) caused by the syscall kqueue1 addition, > libepoll-shim detected it because NetBSD had it but we weren't > compatible. > This should be fixed by > https://cgit.freebsd.org/src/commit/?id=dac310248826c37b60306c1b25fb94c35802196d > > Cheers, > >> >> 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 >> > Hi Emanuel, thank you so much, both issues have been solved. Now the screen remains black and with no cursor when sddm starts but, at least, xinit works. There are no errors in sddm or X logs, so this needs to be investigated. BR, -- José Pérez
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3c1530adecb5634e998f385a2e9091f2>