xserver forces 96 DPI on randr-1.2-capable drivers, overriding correct autodetection

Michal Suchanek hramrach at centrum.cz
Fri Sep 23 10:15:06 PDT 2011

On 23 September 2011 18:37, Alex Deucher <alexdeucher at gmail.com> wrote:
> On Fri, Sep 23, 2011 at 10:58 AM, Michal Suchanek <hramrach at centrum.cz> wrote:
>> On 22 September 2011 19:34, Alan Coopersmith
>> <alan.coopersmith at oracle.com> wrote:
>>> On 09/22/11 08:32, Michal Suchanek wrote:
>>>> Hello,
>>>> Can anybody, please, explain how this bug[1] could have remained in
>>>> Xorg for two years assuming any sanity is remaining among Xorg
>>>> developers?
>>> If we were sane, we wouldn't still be working on X, especially not
>>> after people pile on abuse for things like that.
>> There are obviously people sabotaging X already since the change went
>> in more than two years ago and stayed in spite of being pointed out as
>> bogus.
>> I can understand that it is not possible to fix all issues at once or
>> that implementing new features may bring new bugs but actively
>> breaking a previously working feature is a different thing altogether.
>> If "we won't talk about this" is the only answer then that's also an
>> answer I guess.
> Feel free to deal with all the "my fonts are too big" bugs that come
> up when the xserver uses the real dpi.  A lot of people expect a
> hardcoded 96 dpi whether it makes sense or not.

And a lot of people expect readable text even on small notebooks. So
you get lots of bugs one way or another.



More information about the xorg-devel mailing list