3 ms·
> If no one complains, either no one is using it, or the software is doing its work. Or it crashed and they couldn't be bothered to report it. Looks the same
by kwhitefoot 4y ago
> If no one complains, either no one is using it, or the software is doing its work.
Or it crashed and they couldn't be bothered to report it. Looks the same as no one used it but has a different cause.
- sph 4y agoIf one person globally used a feature, it crashed and they didn't report it (so it was not critical for them), it's a massive waste of time and energy to commit and maintain a test case for it. In fact, perhaps that feature has no place existing at all in the first place and should be dropped. You're underrating the fact that Linux's massive and diverse user base is a great filter for bugs. Only the weirdest heisenbugs can survive this filter, and because of their nature, they wouldn't be tested anyway.
- michaelt 4y agoWe're supposed to be reporting Linux crashes? I always assumed the fact I can reliably break Linux on Laptop A with Docking Station B by doing Action C was pointless to report, because how is anyone supposed to reproduce it if they don't own Laptop A and Docking Station B?
- sph 4y agoCan you reliably break Linux on Laptop A with Docking Station B? Then go here: https://bugzilla.kernel.org https://bugzilla.kernel.org (and follow the big yellow notice) There's a good chance it's a firmware or hardware bug Linux cannot fix, but it's worth a shot. But to answer your question, Laptop A and Docking Station B probably interface with each other with the same two chips/subsystems present in other devices. And if they work with Linux, the maintainers of these drivers, often the manufacturers, are publicly listed and are the ones that will try and troubleshoot it with you.
- baq 4y agoSometimes it’s just obvious like a bad assumption.