[09:08] <lotuspsychje> !info linux-image-generic
[14:02] <Kow> hey anyone getting massive man-db corruption issues ever since 2.8.6-1 was pushed into eoan repos on 8/3?
[14:02] <Kow> Issue just started yesterday... so immediately I checked and sure enough there was a man-db update
[14:03] <Kow> I will revert to prior version and see if issue disappears
[14:03] <Kow> the result is a segfault - probably because man-db is leaking tons of memory when it's processing all these corrupted files
[14:03] <Kow> (or what it sees as corrupted anyways)
[14:06] <TJ-> Bug #1838871 
[14:07] <Kow> thanks TJ... I'm not the greatest at finding bugs in launchpad, more of a debian person myself
[14:07] <Kow> having said that, this is probably an upstream issue assuming ubuntu just pulled from deb repos
[14:08] <Kow> time to follow the cookie crumbs
[14:08] <TJ-> it does look that way... I'd 'ping' cjwatson in #ubuntu-devel 
[14:08] <Kow> found it
[14:08] <Kow> I'll try and link it to the deb bug
[14:09] <Kow> really debian needs to fix this... or the actual package maintainer
[14:09] <Kow> sorry, the actual developer of man-db - this stinks like an issue with the actual source itself and not package or distro specific
[14:10] <TJ-> yes, cjwatson! https://metadata.ftp-master.debian.org/changelogs//main/m/man-db/man-db_2.8.6-1_changelog
[14:10] <TJ-> it shouldn't have got into the archives like this - tests should have detected the issue
[14:12] <Kow> I am surprised they put a major version release directly into unstable
[14:13] <Kow> there is a reason experimental exists :P
[14:14] <Kow> oh Colin is the dev haha alright, well this should be well on the way to getting resolved then