On 2018-12-21 20:54 +0100, Alexander Meyer wrote:
> * Sven Joachim <svenj...@gmx.de> [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 the Arch bugtracker, but apparently not in
>> the Debian BTS…
>
> That came up via a web search as I had originally thought the bug had to
> do with mutt.
>
>>> But the last comment there claims the bug disappeared in 340 which is not
>>> the
>>> case for me.
>>
>> I could also still reproduce it, that's why I did not close #916349 in
>> the xterm 340-1 upload.
>
> I couldn't tell whether that bug was the same as mine, as none of the
> error messages mentioned there came up for me, also that bug doesn't
> talk about segfaulting.
Oh, indeed. But neither does the Archlinux bug report, it only mentions
the dreadful "X Error of failed request" which aborts xterm. And I
could reproduce that with xterm 338 trough 340, but not your segfault.
> If you think this is the same bug, then feel free to merge, of course.
If you still get a segfault in xterm 341 (uploaded today), please tell
me and I will unmerge and reopen your bug.
Cheers,
Sven
