* Thomas Dickey [2018-12-31 00:51]:
> On Sun, Dec 30, 2018 at 06:26:44PM +0100, Alexander Meyer wrote:
> ...
>> This is the behaviour I get across xterm versions:
>> (everything with libfontconfig1 2.13.1-2)
>>
>> fonts.conf enabled:
>> 337: works
>
* Thomas Dickey [2018-12-30 23:14]:
> On Sun, Dec 30, 2018 at 10:15:53PM +0100, Sven Joachim wrote:
>> On 2018-12-30 18:26 +0100, Alexander Meyer wrote:
>>> So the segfault only happens with that fonts.conf.
>>
>> Thanks, that explains why others did not see i
* Sven Joachim [2018-12-29 19:20]:
> On 2018-12-21 20:54 +0100, Alexander Meyer wrote:
>
>> * Sven Joachim [2018-12-21 20:38]:
>>
>>> On 2018-12-21 20:16 +0100, Alexander Meyer wrote:
>>>
>>>> I've found a bug report from Arch Linux tha
* Sven Joachim [2018-12-21 20:38]:
> On 2018-12-21 20:16 +0100, Alexander Meyer wrote:
>
>> Package: xterm
>> Version: 340-1
>> Severity: important
>> [...]
>> I've found a bug report from Arch Linux that looks similar:
>> https://bugs.archlinux
Package: xterm
Version: 340-1
Severity: important
Dear Maintainer,
after updating from 337-1 to 338-1 in testing, xterm crashes with a segfault
when certain Unicode characters appear in the buffer. This only happens when I
have selected a font using the -fa option. It doesn't seem to matter which
5 matches
Mail list logo
