Summary: | x11-libs/gtk+-2 ca't find its display under Xwayland anymore | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | brankob |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | brankob |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
hello-world GTK2 test |
Description
brankob
2021-10-17 16:06:33 UTC
Created attachment 745500 [details]
emerge --info
Created attachment 745503 [details]
hello-world GTK2 test
If it matters, I'm using: gui-libs/wlroots-9999 gui-wm/sway-9999-r4 ( 9999 failed to build, so I tweaked it) dev-libs/wayland-9999 dev-libs/wayland-protocols-9999 fwiw, it works fine for me with gtk2 apps still under GNOME. Your GDK_BACKEND settings are a bit excessive there - if a gtk3 app disables wayland usage, because it still has required X specific code in there, it won't start for you. However, this is unrelated to gtk2 woes, as gtk2 doesn't have GDK_BACKEND. GTK_BACKEND isn't a thing. I feel it's probably some environment issue, but I can't spot what it could be. Does it work in a fuller wayland DE without such big environment overrides? Or even with sway without this go_wl stuff? it behaves the same way even if I erase most of the settings except XDG_RUNTIME_DIR ( it needs that to start). And it behaves the same way under Weston or Enlightenment ( v0.24.2-r2 ). WRT GDK_BACKEND setting, it behaves the same way without it. I've just debugged it up to a point where gtk2 goes trough XOpenDisplay and xcb_connect to _xcb_open_abstract, where it tries to connect to Xorg/XWayland server through the unix socket"/tmp/.X11-unix/X0" and fails. After sway starts, map "/tmp/X11-unix" exists, but it's empty. |