Xorg remap to old code #1414
Replies: 2 comments 5 replies
|
Please, stop these pointless discussions and wasting time. The development git is used mainly by some companies and manufacturers, but those who used it and had problems with these commits also removed them manually, in addition to asking the xorg developers to revert them. xorg is a large and delicate component, pushing for a change to xlibre now is unnecessary and would waste the Mint team's time. Years ago, I had already seen regressions in xorg during testing on Debian unstable + experimental. For experienced users, it is not a problem to operate from the terminal when xorg is not working and fix it, but for most Mint target users, it could be problematic. |
|
Enough. I can say that currently there are no plans to use XLibre. Will/Could that change? No idea. I can't tell the future. What I do know is that these discussions aren't productive and can't stay friendly. I'm closing and locking this along with any others that get opened based on this subject for now. |
Uh oh!
There was an error while loading. Please reload this page.
Including @clefebvre in the hopes this doesnt get locked without an answer or explanation like a related thread did.
Xorg has removed 2 years worth of updates due to personal quarrels between open source devs, making it significantly worse than all alternatives. Can the x11 and related packages in the mint apt repos be locked to before that intentional regression, if they will not be replaced with xlibre? I have used extrepo version of xlibre on mint for over a month now and have found no issues on my system (an amd 395+ with a 9060xt via thunderbolt. one of the more jank setups that would need to be tested) and instead seen major improvements (no tearing and games run better).
preventing new users from using intentionally regressed versions of x11 should be a bare minimum, even if Mint is still planning to slow roll towards wayland instead of just adopting xlibre that works as a drop-in replacement.
All reactions