Arch Linux

brunox

Member

Registered: 2011-02-10

Posts: 5

[SOLVED] urxvt segfault in i3-gaps-git

Hi,

after installing i3 gaps and getting some dotfiles I have an issue with urxvt, it segfaults whenever I open it on a blank workspace or if I open it on a horizontal tile (with maximum width). It happens everytime, also when I switch the window to a blank workspace. There is no issue when I open it in a vertical tile and there's something else open.

I have no clue what provokes this and how to prevent this, so I'm asking for a little help

in case it helps, this is the output and backtrace from gdb:

Starting program: /usr/bin/urxvt 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x000000000042a654 in rxvt_term::scr_alloc() ()
(gdb) bt
#0  0x000000000042a654 in rxvt_term::scr_alloc() ()
#1  0x0000000000416a49 in rxvt_term::scr_reset() ()
#2  0x0000000000428faf in rxvt_term::resize_all_windows(unsigned int, unsigned int, int) ()
#3  0x0000000000419edb in rxvt_term::x_cb(_XEvent&) ()
#4  0x00000000004330ca in rxvt_display::flush_cb(ev::prepare&, int) ()
#5  0x0000000000438a0e in ev_invoke_pending() ()
#6  0x0000000000439475 in ev_run ()
#7  0x0000000000419213 in main ()
(gdb) 

Here are some dotfiles:
.Xdefaults
.Xresources
.i3/config
these dotfiles are slightly modified from the original found here https://github.com/id101010/LinuxDotFiles

feel free to ask for any info i can provide that can shed some light on this issue.

thanks for your time

Last edited by brunox (2016-11-10 12:21:26)

skualito

Member

Registered: 2008-11-19

Posts: 203

Re: [SOLVED] urxvt segfault in i3-gaps-git

Hello,

I tried your config files, and urxvt segfaults here too, with regular i3. I guess there's a problem with this line:

URxvt.saveLines:            9000000

in file `.Xdefaults`. When commented, urxvt doesn't segfault.

brunox

Member

Registered: 2011-02-10

Posts: 5

Re: [SOLVED] urxvt segfault in i3-gaps-git

Yes, it seems that line was the culprit. Thank you very much

I'll mark the thread as solved.

Last edited by brunox (2016-11-10 12:21:59)