On Tue, Jan 15, 2019 at 07:57:30PM -0500, Thomas Dickey wrote:
> On Fri, Jan 04, 2019 at 05:30:22PM -0500, Thomas Dickey wrote:
> > On Fri, Jan 04, 2019 at 08:13:53PM +0100, Alexander Meyer wrote:
> > > Would this warrant to add "affects" tags for firefox and chromium to
> > > this bug? Not sure
On Fri, Jan 04, 2019 at 05:30:22PM -0500, Thomas Dickey wrote:
> On Fri, Jan 04, 2019 at 08:13:53PM +0100, Alexander Meyer wrote:
> > Would this warrant to add "affects" tags for firefox and chromium to
> > this bug? Not sure about the Debian policy here. In this case, the
>
> no - see
On Fri, Jan 04, 2019 at 08:13:53PM +0100, Alexander Meyer wrote:
> Would this warrant to add "affects" tags for firefox and chromium to
> this bug? Not sure about the Debian policy here. In this case, the
no - see https://www.debian.org/Bugs/server-control#affects
(since you're the only one to
On Fri, Jan 04, 2019 at 08:13:53PM +0100, Alexander Meyer wrote:
> * Thomas Dickey [2019-01-04 01:10]:
>
> > On Thu, Jan 03, 2019 at 05:56:26PM +0100, Alexander Meyer wrote:
> >> * Thomas Dickey [2019-01-02 10:46]:
> >>
> >>> I verified that the same issue exists in current code, and submitted
* Thomas Dickey [2019-01-04 01:10]:
> On Thu, Jan 03, 2019 at 05:56:26PM +0100, Alexander Meyer wrote:
>> * Thomas Dickey [2019-01-02 10:46]:
>>
>>> I verified that the same issue exists in current code, and submitted an
>>>
>>>
On Thu, Jan 03, 2019 at 05:42:47PM +0100, Alexander Meyer wrote:
> * Thomas Dickey [2018-12-31 20:32]:
>
> > On Mon, Dec 31, 2018 at 06:11:23PM +0100, Alexander Meyer wrote:
> >> * Thomas Dickey [2018-12-31 00:51]:
> >>
> >>> Can you make a backtrace for #341, please?
> >>
> >> Here it is:
>
On Thu, Jan 03, 2019 at 05:56:26PM +0100, Alexander Meyer wrote:
> * Thomas Dickey [2019-01-02 10:46]:
>
> > I verified that the same issue exists in current code, and submitted an
> >
> > https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/140
> >
> > with the attached fix.
>
>
* Thomas Dickey [2019-01-02 10:46]:
> I verified that the same issue exists in current code, and submitted an
>
> https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/140
>
> with the attached fix.
As a side note, visiting that particular page causes both Chromium and
Firefox to
* Thomas Dickey [2018-12-31 20:32]:
> On Mon, Dec 31, 2018 at 06:11:23PM +0100, Alexander Meyer wrote:
>> * Thomas Dickey [2018-12-31 00:51]:
>>
>>> Can you make a backtrace for #341, please?
>>
>> Here it is:
[...]
Thanks a lot for taking the time to investigate the issue and for
providing
On Tue, Jan 01, 2019 at 06:59:59PM -0500, Thomas Dickey wrote:
> On Tue, Jan 01, 2019 at 12:28:38PM -0500, Thomas Dickey wrote:
> > On Mon, Dec 31, 2018 at 02:32:58PM -0500, Thomas Dickey wrote:
> > > On Mon, Dec 31, 2018 at 06:11:23PM +0100, Alexander Meyer wrote:
> > > > * Thomas Dickey
On Tue, Jan 01, 2019 at 06:59:59PM -0500, Thomas Dickey wrote:
> On Tue, Jan 01, 2019 at 12:28:38PM -0500, Thomas Dickey wrote:
> > On Mon, Dec 31, 2018 at 02:32:58PM -0500, Thomas Dickey wrote:
> > > On Mon, Dec 31, 2018 at 06:11:23PM +0100, Alexander Meyer wrote:
> > > > * Thomas Dickey
On Tue, Jan 01, 2019 at 12:28:38PM -0500, Thomas Dickey wrote:
> On Mon, Dec 31, 2018 at 02:32:58PM -0500, Thomas Dickey wrote:
> > On Mon, Dec 31, 2018 at 06:11:23PM +0100, Alexander Meyer wrote:
> > > * Thomas Dickey [2018-12-31 00:51]:
> > >
> > > > On Sun, Dec 30, 2018 at 06:26:44PM +0100,
On Mon, Dec 31, 2018 at 02:32:58PM -0500, Thomas Dickey wrote:
> On Mon, Dec 31, 2018 at 06:11:23PM +0100, Alexander Meyer wrote:
> > * 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
On Mon, Dec 31, 2018 at 06:11:23PM +0100, Alexander Meyer wrote:
> * 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)
> >>
> >>
* 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
>> 338: segfault
>> 340: segfault
>> 341:
* 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 it - and possibly also why
>> I
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
> 338: segfault
> 340: segfault
> 341: segfault
Can you make a backtrace for #341, please?
On Sun, Dec 30, 2018 at 10:15:53PM +0100, Sven Joachim wrote:
> Control: unmerge -1
> Control: reopen -1
>
> On 2018-12-30 18:26 +0100, Alexander Meyer wrote:
>
> > * Sven Joachim [2018-12-29 19:20]:
> >>
> >> If you still get a segfault in xterm 341 (uploaded today), please tell
> >> me and I
Control: unmerge -1
Control: reopen -1
On 2018-12-30 18:26 +0100, Alexander Meyer wrote:
> * Sven Joachim [2018-12-29 19:20]:
>>
>> If you still get a segfault in xterm 341 (uploaded today), please tell
>> me and I will unmerge and reopen your bug.
>
> Unfortunately, I still get the same
On Sun, Dec 30, 2018 at 06:26:44PM +0100, Alexander Meyer wrote:
...
> Unfortunately, I still get the same segfault with 341. But I've just
> noticed that the behaviour changes depending on whether I have a
> fonts.conf file enabled or not.
>
> I normally use the fonts.conf file from
>
* 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 that looks similar:
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:
>>
>>> Package: xterm
>>> Version: 340-1
>>> Severity: important
>>> [...]
>>> I've found a bug report from Arch Linux that looks similar:
>>>
* 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.org/task/61115
>
> Strange that you looked in
Control: merge 916349 -1
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.org/task/61115
Strange that you looked in the Arch bugtracker, but
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
25 matches
Mail list logo