Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 05 Feb 2021 18:13:27 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 253277] x11/xtrans: Don't unlink existing UNIX sockets => allows multiple X sessions from sddm
Message-ID:  <bug-253277-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253277

            Bug ID: 253277
           Summary: x11/xtrans: Don't unlink existing UNIX sockets =3D>
                    allows multiple X sessions from sddm
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: x11@FreeBSD.org
          Reporter: olivier.freebsd@free.fr
             Flags: maintainer-feedback?(x11@FreeBSD.org)
          Assignee: x11@FreeBSD.org

Created attachment 222189
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D222189&action=
=3Dedit
Patch against the ports tree

Patch that removes the `unlink` call before binding some UNIX socket.

The problem with the existing approach is that, when Xorg is launched as
`root`, it can always unlink existing sockets, which it does when no displa=
y is
explicitly specified and `-displayfd` is used.

Moreover, the X server removes the UNIX socket when exiting (even in most
abnormal cases).

Typically, sddm exactly triggers the problem. So when you try to open anoth=
er
session through it, the first session's sockets are crushed and it becomes
stale.

I'm proposing the patch here since it is not practically useful on platforms
that launch Xorg with an unprivileged user and because upstream seems inact=
ive.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253277-7788>