As seb128 explained, this is an issue with libvte-2.91-0 and is scheduled to be addressed in 0.68 and work arounds do exist.
As seb128 explained, this is an issue with libvte-2.91-0 and is scheduled to be addressed in 0.68 and work arounds do exist.