| Summary: | net_applet segfaulted (stuff.so ) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | gil gil <puntogil> |
| Component: | RPM Packages | Assignee: | Olivier Blin <mageia> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-net-applet-1.0-1.mga2 | CVE: | |
| Status comment: | |||
|
Description
gil gil
2011-11-30 15:03:21 CET
Manuel Hiebel
2011-11-30 15:13:23 CET
Summary:
net_applet segfaulted =>
net_applet segfaulted (stuff.so ) bug 3865 could be a duplicate of this one, Perl's trace is the same. Reporter is the same, too. CC:
(none) =>
marja11
Manuel Hiebel
2012-01-25 18:09:39 CET
Assignee:
tmb =>
mageia Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher. Is this one still valid for Mageia 2 rc? If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. If it wasn't assigned correctly, please assign back to Bug Squad and explain. Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja Keywords:
(none) =>
NEEDINFO Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Status:
NEW =>
RESOLVED |