IMO that reaction is healthy, as long as it isn’t a hostile “you’re holding it wrong” (which was not my intent, and is very much a community problem). Communal troubleshooting is the nature of the Linux desktop.
If you don’t want advice, that’s fine, probably reasonable based on what you described. But I have had some similar (but not so severe) issues with Fioo and Xonar cards that got fixed with some low level configs I had no idea existed.
And maybe I could get to some more in-depth solution that sorts it out, but that’s me spending time on a problem that a) I shouldn’t have to, and b) I have a functional workaround for already.
Communal troubleshooting is the nature of Linux desktop, but also a massive problem. You shouldn’t need communal troubleshooting in the first place. It’s not a stand-in for proper UX, hardware compatibility or reliable implementation. If the goal is for more people to migrate to Linux the community needs to get over the assumption that troubleshooting is a valid answer to these types of issues.
Which is not to say the community shouldn’t be helpful, but there’s this tendency to aggressively troubleshoot at people complaining about issues and limitations and then to snark at people actively asking for help troubleshooting for not reading documentation or not providing thorough enough logs and information. I find that obnoxious, admittedly because it’s been decades, so I may be on a hair trigger for it at this point.
IMO that reaction is healthy, as long as it isn’t a hostile “you’re holding it wrong” (which was not my intent, and is very much a community problem). Communal troubleshooting is the nature of the Linux desktop.
If you don’t want advice, that’s fine, probably reasonable based on what you described. But I have had some similar (but not so severe) issues with Fioo and Xonar cards that got fixed with some low level configs I had no idea existed.
And maybe I could get to some more in-depth solution that sorts it out, but that’s me spending time on a problem that a) I shouldn’t have to, and b) I have a functional workaround for already.
Communal troubleshooting is the nature of Linux desktop, but also a massive problem. You shouldn’t need communal troubleshooting in the first place. It’s not a stand-in for proper UX, hardware compatibility or reliable implementation. If the goal is for more people to migrate to Linux the community needs to get over the assumption that troubleshooting is a valid answer to these types of issues.
Which is not to say the community shouldn’t be helpful, but there’s this tendency to aggressively troubleshoot at people complaining about issues and limitations and then to snark at people actively asking for help troubleshooting for not reading documentation or not providing thorough enough logs and information. I find that obnoxious, admittedly because it’s been decades, so I may be on a hair trigger for it at this point.