On Wed, 13 Feb 2019 22:01:07 -0500, Ryan Kavanagh wrote:
> On Thu, Feb 14, 2019 at 12:19:26AM +0100, gregor herrmann wrote:
> > Does this help?
> It does, thank you. I managed to produce a second segfault at a
> different location by providing the colour resources under URxvt.tabbed
> with bogus v
Hi,
On Thu, Feb 14, 2019 at 12:19:26AM +0100, gregor herrmann wrote:
> Does this help?
It does, thank you. I managed to produce a second segfault at a
different location by providing the colour resources under URxvt.tabbed
with bogus values. What resources do you have set for URxvt? (See the
outp
On Wed, 13 Feb 2019 17:12:10 -0500, Ryan Kavanagh wrote:
> On Wed, Feb 13, 2019 at 10:31:44PM +0100, gregor herrmann wrote:
> > After upgrading to 9.22-5, urxvt -pe tabbed just leads to a segfault.
> > Downgrading to 9.22-4+b1 helps.
> I am unable to reproduce this. Could you please submit a backt
Control: tags -1 + unreproducible moreinfo
On Wed, Feb 13, 2019 at 10:31:44PM +0100, gregor herrmann wrote:
> After upgrading to 9.22-5, urxvt -pe tabbed just leads to a segfault.
> Downgrading to 9.22-4+b1 helps.
I am unable to reproduce this. Could you please submit a backtrace?
Thanks,
Ryan
Package: rxvt-unicode
Version: 9.22-5
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
After upgrading to 9.22-5, urxvt -pe tabbed just leads to a segfault.
Downgrading to 9.22-4+b1 helps.
Cheers,
gregor
- -- System Information:
Debian Release: buster/sid
APT prefers unstable
5 matches
Mail list logo