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

Sway requires mesa-dri #22007

Closed
notramo opened this issue May 16, 2020 · 9 comments
Closed

Sway requires mesa-dri #22007

notramo opened this issue May 16, 2020 · 9 comments

Comments

@notramo
Copy link

notramo commented May 16, 2020

System

  • xuname:
    Void 5.4.40_1 x86_64 GenuineIntel uptodate rFFFFFFF
  • package:
    sway-1.4_3

Expected behavior

mesa-dri is installed with sway

Actual behavior

Sway doesn't start unless I manually install mesa-dri.

Steps to reproduce the behavior

Install sway, but not mesa-dri.
Start Sway from the console.

@st3r4g
Copy link
Contributor

st3r4g commented May 16, 2020

This is currently documented in https://docs.voidlinux.org/config/graphical-session/wayland.html#video-drivers
I agree that the mesa drivers should be automatically installed by default, but adding them to sway is wrong. Instead, libglvnd should pull them in as default GL provider, but this is not so easy to achieve cleanly with current packaging situation

@notramo
Copy link
Author

notramo commented May 16, 2020

What about adding an install message with the link?

@st3r4g
Copy link
Contributor

st3r4g commented May 16, 2020

Users are encouraged to read the docs. Relying on install messages is poor because they can be easily lost in xbps install log (and many people don't pay attention to them anyway)

@ericonr
Copy link
Member

ericonr commented May 27, 2020

@st3r4g would this really solve the issue? If someone had installed nvidia drivers as the libglvnd provider, and then installed Sway, it still wouldn't work. I'm not sure what the best solution would be :c

@st3r4g
Copy link
Contributor

st3r4g commented May 27, 2020

Well I'd say users are expected to know that sway doesn't work with nvidia drivers. Adding a hard-dependency to mesa-dri wouldn't work either, because users still won't be prevented from installing nvidia (they will be side-by-side with the mesa drivers). The only way would be with a conflicts= but... ugh

@notramo
Copy link
Author

notramo commented May 28, 2020

Users are encouraged to read the docs. Relying on install messages is poor because they can be easily lost in xbps install log (and many people don't pay attention to them anyway)

Do it harm anything? If not, why not add it? It's better than nothing.

@ericonr
Copy link
Member

ericonr commented May 28, 2020

@notramo the way I see it, this is due to Void's policy for packages. We tend to not bundle anything that's not essential. For example, you can install an X window manager and that won't pull in the actual Xorg server, because you might desire to run that through the network instead. For wayland, you could use the X backend (for some reason) or even the headless one, and in that case it won't make sense for mesa-dri to be installed.

@Duncaen
Copy link
Member

Duncaen commented May 28, 2020

Do it harm anything? If not, why not add it? It's better than nothing.

Yes it makes people even less likely to read actually important INSTALL messages, like the recent openssh update that required the user to restart sshd for new connections to work.

@ericonr
Copy link
Member

ericonr commented Jan 21, 2021

This is being discussed in #27286 and #18712 , closing this.

@ericonr ericonr closed this as completed Jan 21, 2021
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

4 participants