MTR segmentation fault on azl3

[AZaugg]

Describe the bug When running mtr on azl3 we see a segfault, this should not happen

To Reproduce Run mtr

Expected behavior MTR should not throw a segmentation fault

Screenshots

$ mtr
Segmentation fault (core dumped)

[AZaugg]

Seeing a issue with MTR on azurelinux 3, it is seg faulting

$ mtr
Segmentation fault (core dumped)

Core file shows us

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fa17d17b171 in _nc_init_acs_sp () from /usr/lib/libtinfo.so.6
(gdb) bt
#0  0x00007fa17d17b171 in _nc_init_acs_sp () from /usr/lib/libtinfo.so.6
#1  0x00007fa17d1b2e8a in _nc_setupscreen () from /usr/lib/libncurses.so.5
#2  0x00007fa17d1afb21 in newterm () from /usr/lib/libncurses.so.5. <<<<< So not a issue with MTR, looks like issue with ncursors
#3  0x00007fa17d1ac150 in initscr () from /usr/lib/libncurses.so.5
#4  0x000057b8f2bd4f70 in mtr_curses_open (ctl=ctl@entry=0x7fff3f77daa0) at ui/curses.c:801
#5  0x000057b8f2bd0a2e in display_open (ctl=0x7fff3f77daa0) at ui/display.c:97
#6  0x000057b8f2bcc2fb in main (argc=<optimized out>, argv=<optimized out>) at ui/mtr.c:823
(gdb)

Looks like we are using libncurses.so.5 with libtinfo.so.6, i think this is a ABI issue between ncurses5 and ncurses6