Dev1 Galaxy Forum / Daedalus, seatd, can’t have multiple X sessions

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (ralph.ronnquist) — Tue, 22 Aug 2023 23:34:50 +0000

Yes, https://git.devuan.org/devuan/xorg-server is where it happens. The review process of a fix is in full swing so you may hold your breath. well, maybe not... breath easy, but expect there's something coming soon.

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (GlennW) — Tue, 22 Aug 2023 20:29:52 +0000

I remember being able to have more than one GUI running on different tty's... but that went away and couldn't be done the same way.

Hoping for innovation.

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (semil) — Tue, 22 Aug 2023 19:11:47 +0000

Another possibility is probably within the infinitude of git.devuan.org. Maybe something will happen on some branch in https://git.devuan.org/devuan/xorg-server/branches as an indication of code getting into Daedalus. Or maybe not. That might be not the right region of git at all.

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (semil) — Mon, 21 Aug 2023 15:39:53 +0000

One possibility might be to look at

https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=xorg
https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=*seat*

each day. I would have to recognize when version numbers had changed.

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (semil) — Sun, 20 Aug 2023 15:27:01 +0000

Given that I won’t be using that Daedalus system regularly until this has been fixed, what is the most efficient way to check periodically from somewhere else whether the fix has happened yet?

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (semil) — Sat, 19 Aug 2023 23:30:19 +0000

ralph.ronnquist wrote:

I'm not sure there is a bug report, but that particular issue of having multiple Xorg (in different VT) with seatd, is currently being worked on, and I believe an update is coming fairly soon.

I’m glad to know that!

I don’t see a bug report, but I’m not experienced with the bug tracker.

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (golinux) — Sat, 19 Aug 2023 15:47:23 +0000

semil wrote:

If this forum is even capable of moving topics, that is.

Yes. If appropriate.

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (ralph.ronnquist) — Sat, 19 Aug 2023 15:08:58 +0000

I'm not sure there is a bug report, but that particular issue of having multiple Xorg (in different VT) with seatd, is currently being worked on, and I believe an update is coming fairly soon.

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (semil) — Sat, 19 Aug 2023 14:43:47 +0000

Would it be more appropriate to have this topic moved to a lower-level subforum where more of the right people might see it, since, strictly speaking, this subforum suggests being about things running on X and not about getting X to run.

If this forum is even capable of moving topics, that is.

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (semil) — Thu, 17 Aug 2023 19:35:34 +0000

I have always been using a plain startx in each, but using startx -- :1 for the second one fails in the same way.

Re: Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (delgado) — Thu, 17 Aug 2023 15:27:30 +0000

But you did something like startx -- :1, right?

Daedalus, seatd, can’t have multiple X sessions

dummy@example.com (semil) — Wed, 16 Aug 2023 23:18:41 +0000

I startx on one vt (pretty minimal, starts up a window manager).

I try to startx again on another vt — same user or different user — and it fails. seatd says "Could not add client: seat is VT-bound and has an active client".

Since I don’t know whether being VT-bound is good or bad, I found SEATD_VTBOUND=0 and tried that on the seatd invocation. But seatd is still unhappy because it still sees an active client regardless.

I presume switching away from a vt is supposed to make an X session become *not* active somehow.