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

gnome-session-x11-services-ready.target isn't started on Wayland session #2113

Open
bobby285271 opened this issue Nov 10, 2024 · 1 comment

Comments

@bobby285271
Copy link
Member

What Happened?

For me this is started on GNOME Wayland but not Pantheon Wayland.

I think gala will the place to file this issue since in GNOME this is started by gnome-shell (see this MR ("data: Add an abstract gnome-shell.target") for starting the systemd target, and this MR ("Add side channel for services to startup on Xwayland session") for init-xserver signal).

This is a problem for me since I found org.gnome.SettingsDaemon.XSettings.service has:

Requisite=gnome-session-x11-services.target gnome-session-x11-services-ready.target
PartOf=gnome-session-x11-services.target gnome-session-x11-services-ready.target

Steps to Reproduce

  1. Login to Wayland session.
  2. Run pgrep -fa gsd-xsettings and see no results.
  3. Run systemctl status --user gnome-session-x11-services-ready.target and find it inactive.
  4. Run systemctl start --user gnome-session-x11-services-ready.target.
  5. Run pgrep -fa gsd-xsettings and see it running.

Or specifically for me, the problem is Xwayland apps doesn't scale on my HiDPI screen. I did all the testing on NixOS, let me know if you can't reproduce this on elementary OS so I will look into downstream packaging instead.

Expected Behavior

gsd-xsettings runs on Wayland session.

OS Version

Other Linux

Session Type

Secure Session (Wayland)

Software Version

Latest release (I have run all updates)

Log Output

No response

Hardware Info

No response

@leolost2605
Copy link
Member

Not sure at all and I don't know the inner workings but I just want to bring the idea that this might be the cause for #1967

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants