This bug was fixed in the package man-db - 2.7.2-1
---
man-db (2.7.2-1) unstable; urgency=medium
* New upstream release:
- Stop storing the database handle in a global variable (LP: #1304261).
-- Colin Watson Sun, 16 Aug 2015 17:30:19 +0100
** Changed in: man-db (Ubuntu)
** Branch linked: lp:debian/man-db
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304261
Title:
mandb crashed with SIGSEGV in gdbm_close
To manage notifications about this bug go to:
https://bugs.l
** Changed in: man-db (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304261
Title:
mandb crashed with SIGSEGV in gdbm_close
To manage notifications
I can't be absolutely sure why this is happening, because allocation
crashes like this often show up somewhere after the point where things
started to go wrong. However, the way man-db keeps track of its
database handle is asking for trouble: it's all done by way of a big
global variable, which mi
** Summary changed:
- error appeared when installing yumi
+ mandb crashed with SIGSEGV in gdbm_close
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304261
Title:
mandb crashed with SIGSEGV in gdbm_
