(gdb) bt #0 0x00007fcc7953c5e0 in termattrs_sp () from /lib64/libncursesw.so.6 #1 0x00007fcc79538cb7 in _nc_setupscreen_sp () from /lib64/libncursesw.so.6 #2 0x00007fcc7953358e in newterm_sp () from /lib64/libncursesw.so.6 #3 0x00007fcc79533aab in newterm () from /lib64/libncursesw.so.6 #4 0x00007fcc7952e80a in initscr () from /lib64/libncursesw.so.6 #5 0x00005616dd0c72a4 in main () likely same thing as e.g. https://bugs.gentoo.org/651914, also judging from what is being done in configure.ac (very quick check only; I can be wrong): hard-coded -ltinfo. I haven't checked with unstable versions. TERM is xterm-256color
see also (seemingly same bug): bug 654866 about app-admin/testdisk
util-linux doesn't hardcode tinfo ... it checks ncurses & tinfo independently via pkg-config as it should please attach a full build log as well as `emerge --info` to all of your bug reports
Sure, I will attach stuff later but now I'll just add > also judging from what is being done in configure.ac (very quick check only; I can be wrong): hard-coded -ltinfo. I actually meant "searched only for tinfo, not tinfow." (I don't know full details behind this but there are packages that crash with the combination of ncursesw+tinfo).
(In reply to Sławomir Nizio from comment #3) thanks for the clarification. in that regard, yes, util-linux-2.30 is broken. it was fixed upstream for util-linux-2.31: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=ad442a818c6eefabb8258a9949206e12f2296161 we only have 2.30 stable atm. prob should just roll forward.
Now that sys-apps/util-linux-2.32-r4 is stable this bug (from my point of view) can be closed.
