saidar segmentation fault

[vigilian]

Erreur de segmentation (core dumped)

[Joshua Powers (powersj)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

[Launchpad Janitor (janitor)]

[Expired for libstatgrab (Ubuntu) because there has been no activity for 60 days.]

[greg606 (greg606)]

I also have this after longer running saidar -c
ubuntu 17.04

[greg606 (greg606)]

I have it on two different 17.04 machines.

[Tim Bishop (tdb)]

This is the same as Debian bug #916220. It's fixed by libstatgrab 0.92. Unfortunately, it's not yet in Debian upstream, or Ubuntu.

[Christian Ehrhardt  (paelzer)]

Thanks Tim, I added the bug link to the related Debian bug.

I agree that so far I only see 0.91 in both Distros.

TBH I never heard of this package and wondered as it is even in main oO.
I found that it is in for corosync that uses it.

We are post feature freeze for Eoan which means it is unlikely to move to full 0.92 anway.
But if we'd know the particular fix this might be a chance to squeeze it into Eoan and SRU from there.
After all =>Xenial all are on 0.91 so the same should apply everywhere.

I saw "Fix various file descriptor leaks." in the changelog, but was confused by [1] being reverted right after.

[1]: https://github.com/libstatgrab/libstatgrab/commit/d87efe0feee9bb85481d415809ca7e211d836df7

@Tim - do you happen to know the individual fix and steps to reproduce the bug (required for SRUs)? So that we might consider picking that for <=Eoan?

[Andreas Hasenack (ahasenack)]

This may be tricky to reproduce reliably on a test machine, unless you own a system where it is already happening.

In the upstream bug at https://github.com/libstatgrab/libstatgrab/issues/102, there is a hint that https://github.com/libstatgrab/libstatgrab/commit/84fd8c38ee4feb0117ed22ab56f6b46661411ec6 might fix the problem. For SRU purposes, we need a verification step. Would people affected by this be able to test a package from a ppa with that patch to see if it fixes the problem?

[Rafael David Tinoco (rafaeldtinoco)]

There are other comments saying that the issue does not seem to be solved:

https://github.com/libstatgrab/libstatgrab/issues/102#issuecomment-509715203

I'm marking this as incomplete since we still need a dump to do anything further.

[Brian Murray (brian-murray)]

The Eoan Ermine has reached end of life, so this bug will not be fixed for that release