Mystery crashes with SIGABRT
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| openbsd-inetd (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
I see seven crash reports of openbsd-inetd with SIGABRT reported now, with the first being 2017-08-30. Many of them are marked private as they may create private user information, and I haven't examined them in enough detail to be confident in making them public.
It's clearly some kind of probably valid problem that is causing this, so I'm creating this master public bug to track them to help affected users find each other.
Unfortunately as we don't know how to reproduce the problem, there isn't enough information for a developer to be able to address the problem so I'm marking this bug Incomplete.
Anyone interested in this bug: please feel free to use this bug to communicate and coordinate to help each other and to try to gather enough information to help us get this bug out of Incomplete status.
| Robie Basak (racb) wrote | #1 |
| Changed in openbsd-inetd (Ubuntu): | |
| status: | New → Incomplete |
| status: | Incomplete → Confirmed |
| Robie Basak (racb) wrote | #2 |
Incomplete will auto-expire which I don't want in this case, so I'll use Confirmed. But please note that the bug unfortunately make progress without further information such as steps to reproduce - so it is still effectively Incomplete.