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 values.
Ha, that's an excellent hint, I indeed have set some of them (many years ago). > What resources do you have set for URxvt? (See the > output of "appres URxvt" or of "xrdb -query -all") Original values: % appres URxvt | grep tabbed URxvt.tabbed.tab-bg: 248 URxvt.tabbed.tab-fg: 0 URxvt.tabbed.tabbar-bg: 0 URxvt.tabbed.tabbar-fg: 248 If I changed them to the defaults, as in % appres URxvt | grep tabbed URxvt.tabbed.tab-bg: 1 URxvt.tabbed.tab-fg: 0 URxvt.tabbed.tabbar-bg: 0 URxvt.tabbed.tabbar-fg: 3 `urxvt -pe tabbed' doesn't segfault anymore but works as intended. (Setting tab-bg and tabbar-fg to 85, which used to work at some point, according to the comments in my ~/.Xresources, also leads to a segfault in screen.C:656. Same for 239 which should work according to rxvt-unicode(1). Using colour names (grey, red, yellow) leads to a different result: no segfault, tabs are created (as in: can be used with the keyboard) but the tabbar is just a black area at the top So yeah, something in the colour handling of at least the tabbed extension seems to have changed with the new patch. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: The Mamas and The Papas: Twelve-Thirty (Young Girls Are
signature.asc
Description: Digital Signature
