![]() ![]() Here is the link to the requested trace file: Did anybody experience anything similar, and how to fix? There's a bug report on Debian describing a similar issue,, but I'm already running the version of man-db that supposedly fixed the problem (2.8.3). Man: nroff: Bad system call (core dumped) Man: tbl: Segmentation fault (core dumped) Man: /usr/lib/man-db/manconv: Bad system call (core dumped)man: preconv: Segmentation fault (core dumped) Zcat < /usr/share/man/man1/man.1.gz: Bad system call (core dumped) usr/bin/mandb: zcat < /usr/share/man/man1/grub-file.1.gz: Bad system call (core dumped)įurthermore, manpages throw errors and are empty: Manual page man(1) line ?/? (END) (press h for help or q to quit)man: usr/bin/mandb: zcat < /usr/share/man/man1/grub-editenv.1.gz: Bad system call (core dumped) usr/bin/mandb: /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE -q: Bad system call (core dumped) usr/bin/mandb: zcat < /usr/share/man/man1/wodim.1.gz: Bad system call (core dumped) usr/bin/mandb: zcat: Bad system call (core dumped) Ever since I upgraded from 17.10 to 18.04, whenever I install or run updates and the subsequent man-db update occurs, the system gets stuck for ten minutes or so spitting out errors and hitting the cpu hard. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |