[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#21028: Performance regression in revision af1a69f4d17a482c359d98c00e

From: Clément Pit--Claudel
Subject: bug#21028: Performance regression in revision af1a69f4d17a482c359d98c00ef86fac835b5fac (Apr 2014).
Date: Tue, 14 Mar 2017 15:45:16 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0

On 2017-03-13 16:53, Eli Zaretskii wrote:
>> We know the exact commit that caused this regression, right?  So
>> how could the problem not be font-related, since reverting it fixes
>> the problem?
> Because using the same fonts here doesn't reproduce the problem. 
> Which means that the font data is not the culprit, there's some
> other factor at work here.

Ok, thanks.

>> What about the VM approach, or simply remote access on a VM that I
>> could provide?
> Debugging display problems without seeing the display is not 
> practical.

I was offering an ssh -X session, or VNC, or whichever remote desktop 
application could help, so as to give you access to the graphic display.  Would 
that help?


Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]