Arch Linux

Description:
If you open a roxterm with `roxterm --fork` (like I do from my xbindkeys) it will open one, but on the second execution, crashes, taking any other roxterms with it

Additional info:
* package version(s) -- Happening with 3.1.3-1 and 3.1.4-1 reliably

strace of the first `roxterm --fork`: http://sprunge.us/YTRF
dmesg output:
[ 52.537378] roxterm[1781]: segfault at 0 ip 00007f2a11a7ebda sp 00007fffb2533f88 error 4 in libc-2.22.so[7f2a119ee000+19b000]
[ 2491.154637] roxterm[1932]: segfault at 0 ip 00007fb506f8bbda sp 00007ffc3d024808 error 4 in libc-2.22.so[7fb506efb000+19b000]
[ 2534.606903] roxterm[2589]: segfault at 0 ip 00007f2392e7ebda sp 00007fff03fdc8a8 error 4 in libc-2.22.so[7f2392dee000+19b000]
[ 2644.436654] roxterm[3806]: segfault at 0 ip 00007f1ab38c2bda sp 00007fff225e9758 error 4 in libc-2.22.so[7f1ab3832000+19b000]


Steps to reproduce:

roxterm --fork in any other terminal
roxterm --fork in any other terminal again

Interestingly, sometimes if you don't fork the first one to the background `roxterm`, you can fire off more using `roxterm --fork`, but if and only if the first one remains not forked.

With roxterm 3.0.2-1 segfaulting goes away, and everything works just fine.