Re: Xorg tearing fix on Intel HD Graphics 4000

[Roel Janssen <roel@gnu.org>]

Chris Marusich writes:

> Roel Janssen <roel@gnu.org> writes:
>
>> Chris Marusich writes:
>>
>>> Roel Janssen <roel@gnu.org> writes:
>>>
>>>> Ricardo Wurmus writes:
>>>>
>>>>> Hi Roel,
>>>>>
>>>>>> With the following patch to the Xorg configuration file, I have a
>>>>>> tear-free GuixSD experience.  I wonder if this is upstreameable in some
>>>>>> way.  This patch is probably too broad in effect.  Can I change it so
>>>>>> that only the graphics card I have will be affected by this patch?
>>>>>
>>>>> I’m not sure about this, but you can apply it only to your system by
>>>>> changing the slim-service’s “startx” value like this:
>>>>>
>>>>> --8<---------------cut here---------------start------------->8---
>>>>>     (modify-services %desktop-services
>>>>>       (slim-service-type
>>>>>        config => (slim-configuration
>>>>>                   (inherit config)
>>>>>                   (startx (xorg-start-command
>>>>>                            #:configuration-file
>>>>>                            (xorg-configuration-file
>>>>>                             #:extra-config
>>>>>                             (list your-fix)))))))
>>>>> --8<---------------cut here---------------end--------------->8---
>>>>>
>>>>> But I suppose what you want is to apply it unconditionally in Guix and
>>>>> have the X server ignore it for all but this one graphics card, right?
>>>>
>>>> No, not necessarily.  I could no longer do 'guix pull && guix system
>>>> reconfigure ...', which I attempted to solve by upstreaming this patch.
>>>
>>> Why wouldn't you be able to do a 'guix pull && guix system reconfigure'?
>>
>> Because that would build a system generation which doesn't contain the
>> patched Xorg config.  Ricardo's snippet solved that.
>>
>>>
>>>> I wonder if anyone else is having the same problem on this hardware..
>>>
>>> Yes, I have this problem.  I use a Lenovo X200.  Like Mark, graphical
>>> Emacs doesn't display characters right, and it's difficult to tell what
>>> the buffer actually contains, sometimes.  I've reconfigured my system to
>>> use the extra Xorg config you've provided in this thread, and I'll let
>>> you know in a week or two if it seems to have fixed the problem.
>>
>> Thanks.
>>
>> Kind regards,
>> Roel Janssen
>
> Just wanted to close the loop here: I have not had any tearing problems
> since applying the patch.  Sounds like the problem has been resolved
> through a slightly different means, though (with commit
> b049ae2f9708794f83c41171c19ffdfe4f11807e).  Accordingly, I've removed
> the extra xorg configuration from my operating system configuration file
> and simply reconfigured using the latest origin/master.

I also removed the extra Xorg configuration snippet from my system
configuration, and I too don't have the tearing problem anymore.

>
> Thank you for starting this discussion!  It's really nice to be able to
> use graphical emacs now without needing to frequently invoke M-x
> redraw-display.

Thanks for confirming that this issue has been fixed.

Kind regards,
Roel Janssen