Opening programs in Xwayland

[Kabouik]

I recently switched to Sway and Wayland and one thing I noticed is sway-launcher-desktop now cannot open new windows for programs that would run in Xwayland, instead the launcher just silently fails. I was already using sway-launcher-desktop with urxvt before moving to Wayland, and those programs used to open correctly when I was still using Xorg. Is there anything that can be done about it?

[Biont]

Hm, I don't recall ever having an issue with something like this. It sounds kind of strange to be honest, since I cannot (yet) imagine what the launcher could be doing to mess things up here. Do you see anything significant in the log output?

[Kabouik]

Thank you for your message. It is good news already that this should work, I was not sure if this would be a known but unsolvable limitation. I can't tinker with my Wayland machine right now but I will post another message here once I have had a chance to check the log output. I will also try with another terminal emulator to run sway-launcher-desktop into, since all I have used for now is urxvt, which is an X terminal.

On 2022-09-03 21:56 Moritz Meißelbach @.***> wrote:

Hm, I don't recall ever having an issue with something like this. It sounds kind of strange to be honest, since I cannot (yet) imagine what the launcher could be doing to mess things up here. Do you see anything significant in the log output?

--
Reply to this email directly or view it on GitHub: https://github.com/Biont/sway-launcher-desktop/issues/68#issuecomment- 1236190061 You are receiving this because you authored the thread.

Message ID: @.***>

[Kabouik]

There is no logs at all when the issue occurs, tested both urxvt and foot as terminals.

However, these two terminals have a server/client feature that reduces the loading size of client windows, and this is one I am using. My issue seems to occur only when I try to use a client to run the script, such as:

for_window [app_id="^launcher$"] floating enable, sticky enable, resize set 40 ppt 55 ppt, border pixel 2, move position center
bindsym $mod+m exec TERMINAL_COMMAND=footclient footclient ´-a launcher ~/.config/sway-launcher-desktop/sway-launcher-desktop.sh 3>> /tmp/sway-launcher-desktop.log

# Or the urxvt equivalent

Somehow, if I change the second footclient for just foot, this seems to work, at the cost of just slightly longer startup time.

I didn't investigate the code within sway-launcher-desktop.sh but it is not clear to me what could interact with whether the script runs in a client terminal or not, but that was apparently the culprit in my case.