Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gui] sway: Window contents are not rendered on Wayland backend #211

Open
keeakita opened this issue Nov 15, 2021 · 9 comments
Open

[gui] sway: Window contents are not rendered on Wayland backend #211

keeakita opened this issue Nov 15, 2021 · 9 comments
Labels
bug Something isn't working linux Linux-specific issues upstream Problem is in a dependency wontfix This will not be worked on

Comments

@keeakita
Copy link

keeakita commented Nov 15, 2021

Describe the bug
When run in Sway, psst only displays the background of the window, but none of the contents. This means when first run, it display7s the log in screen as an empty white square. This is Wayland-specific as it doesn't happen when run in XWayland.

To Reproduce

  • Build dev version
  • cargo run --bin psst-gui

Expected behavior
The contents of the windows should be displayed when using Wayland as the backend.

Screenshots
Log in screen, not working:
image

Log in screen, XWayland:
image

After setting up a profile via XWayland and launching via Wayland. Notice it seems to skip log-in, and remembers the user's theme setting:
image

Environment

  • OS: nixos unstable
  • Version: master / de5c12f

Additional context

  • Working version via XWayland: WAYLAND_DISPLAY= cargo run --bin psst-gui
  • Repros on the release build
  • I haven't had a chance to try other Wayland-based desktop environments
@keeakita keeakita added the bug Something isn't working label Nov 15, 2021
@jpochyla
Copy link
Owner

Hi @oslerw, Druid does not yet have a native wayland API. There is a Draft PR pending: linebender/druid#1498

@jpochyla jpochyla added linux Linux-specific issues upstream Problem is in a dependency wontfix This will not be worked on labels Nov 15, 2021
@filmor
Copy link

filmor commented Nov 17, 2021

For me it seems to be working just fine on the current master on Wayland (also running sway), no idea how if druid is not there, yet :)

@keeakita
Copy link
Author

@filmor -- out of curiosity, what version of Wayland are you running, and on what distro? I can do more testing to try to narrow down why it's reproducible on my system but not yours.

@filmor
Copy link

filmor commented Nov 29, 2021

This is Gentoo Linux. The relevant(?) versions are:

Package Version
sway 1.6.1
wayland 1.19.0

@thebiblelover7
Copy link

@oslerw @filmor Psst works perfectly fine for me on GNOME wayland. (I can verify it's running on wayland by running xeyes)
I'm on arch using GNOME on wayland, and this is my wayland and mutter version

wayland 1.20.0-1
mutter 41.2-1

@ToxicMushroom
Copy link

isn't this fixed now ?
linebender/druid#2079
and psst is already running with an app_id which means it runs on wayland in my experience.

@dacioromero
Copy link

It worked fine on Gnome Wayland, but doesn't for me on KDE Wayland now that I've switched. I'm also running NixOS.

Since druid uses some GTK stuff I was able to force XWayland with GDK_BACKEND=x11.

@arch-btw
Copy link
Contributor

arch-btw commented Apr 1, 2023

Strange, it's working on Wayland for me.

Can those affected please provide the output of:

echo $GDK_BACKEND:$WAYLAND_DISPLAY:$DISPLAY:$XDG_RUNTIME_DIR

And does the following command make it work how it should?

GDK_BACKEND=wayland psst-gui

@skykanin
Copy link

I'm also running into this issue on Hyprland using psst version unstable-2023-05-13.
System: Linux 6.5.2, NixOS, 23.11 (Tapir), 23.11.20230911.3a2786e

$ echo "$GDK_BACKEND:$WAYLAND_DISPLAY:$XDG_RUNTIME_DIR"
wayland:wayland-1:/run/user/1000

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working linux Linux-specific issues upstream Problem is in a dependency wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

8 participants