> [...] if using hybrid graphics where the primary is Intel and the secondary is nvidia, sway would continue to work (just without nvidia monitors) and the user would never see the log message. Then they're likely to create issues related to outputs not working, causing us to invest time in troubleshooting it, only to find that they are using nvidia and never saw the warning."
So yes, you can run sway with the nvidia module loaded, just please unload it and test again before you report bugs.
> So yes, you can run sway with the nvidia module loaded, just please unload it and test again before you report bugs.
If that were the language used in the issue tracker, then fine. It's sensible to request that users reproduce the bug with the proprietary driver blacklisted before reporting. But the attitude they're projecting is hostile and unconstructive. The bug tracker says: > If you are using the nvidia proprietary driver for any reason, you have two choices:
>
> 1. Uninstall it and use nouveau instead
> 2. Use X11+i3 and close your browser tab
>
> If `lsmod | grep nvidia | wc -l` shows anything other than zero, your bug report is not welcome here.
Furthermore, sway's behavior is to check whether the proprietary driver is loaded and, if so, exit unless sway is started with the flag --my-next-gpu-wont-be-nvidia. It's hostile, childish, and very off-putting to a potential user and contributor.I don’t want to settle for Intel GPU, because I have a clearly superior GPU available (Nvidia). I don’t want to settle for X, because I have a clearly superior API available (Wayland). I have a 4k OLED display, because if it is there, why settle for something worse? I realize that enthusiasts are rare, but it’s us who help iron out the bugs for the newest hardware, and it is sad to see such an alienating attitude from fellow cutting-edge developers.