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

Difference between Smithay/wayland-server and C libwayland wrt display lock file naming #759

Open
jonleivent opened this issue Sep 4, 2024 · 0 comments

Comments

@jonleivent
Copy link

Smithay/wayland-server/src/socket.rs ListeningSocket::bind_absolute uses PathBuf::with_extension to derive the lock file name from the display name. This means that given a display name like "wayland.0", it will use "wayland.lock" instead of "wayland.0.lock". C libwayland does a normal concatenation, so it will use "wayland.0.lock".

Most practical scenarios involving the lock file involve multiple identical (wrt options) invocations of the same Wayland compositor intended to be the only compositor for a particular user. In such cases, with_extension instead of normal concatenation would not make any difference.

However, it may make a difference in scenarios involving multiple distinct compositors, perhaps one compositor and one or more sub-compositors, with display names that differ only in their extension.

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

1 participant