[BRLTTY] BRLTTY blocked on console while Orca is running on Wayland

[Elias Oltmanns]

Hi Samuel,

you are onto something there:

On 2025-12-19 at 14:44:27 (+0100), Samuel Thibault <samuel.thibault at ens-lyon.org> wrote:
> Hello,
> Elias Oltmanns, le ven. 19 déc. 2025 14:32:14 +0100, a ecrit:
>> - Braille device responds to Orca now (as expected).
>> - Switch to tty2 in text mode.
>> - The braille device still shows Orcas output
> 
> It looks like orca doesn't manage to properly claim only the VT of the
> wayland session.
> 
> When running inside a terminal, do you have these environment variables
> set:
> 
> XDG_VTNR 
> WAYLAND_DISPLAY
> DISPLAY
> WINDOWPATH

What exactly do you mean by „running inside a terminal“? Would that be
on the text console, or „terminal“ launched from the GNOME app starter?

On tty1 in text mode, i.e. when no GNOME is running yet, XDG_VTNR=1 is
set, but none of the other three you mentioned.

According to:
https://wiki.archlinux.org/title/GNOME#Manually
I have created the following file:
$ cat /etc/systemd/system/getty at tty1.service.d/wayland.conf
[Service]
Environment=XDG_SESSION_TYPE=wayland

This allows me to launch GNOME by executing on tty1:
     gnome-session

When I launch „terminal“ from within my GNOME session, XDG_VTNR is not
set anymore, but DISPLAY and WAYLAND_DISPLAY are. No WINDOWPATH, though,
I'm afraid.

> 
> Please also post the content of
> 
> /proc/1234/environ
> 
> where you replace 1234 with the pid of orca, so we get to know what
> exactly orca has as environment variables.

This file appears to be empty since cat produces no output. Do you have
any suggestion how to proceed?

Best,

Elias