| Summary: | drakrpm segfaulted | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Florian Hubold <doktor5000> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | doktor5000, marja11 |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpmdrake-6.20-1.mga5 | CVE: | |
| Status comment: | |||
|
Description
Florian Hubold
2016-01-16 22:17:15 CET
Seems drakbug couldn't report the remaining bits properly. For the part "what was I doing when the program crashed": closing rpmdrake via the "quit" button CC:
(none) =>
doktor5000
Marja Van Waes
2016-01-17 08:29:33 CET
CC:
(none) =>
marja11 @ Florian, Thank you for having taken the needed time to report this issue! If I searched correctly, then there is only bug 16833 of which the traces look similar (even if it was triggered differently), which was reported against Mageia 5, too. I don't find that this issue is still valid in Mageia 6 or later. We regret if it never got fixed for Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. Closing as OLD Resolution:
(none) =>
OLD |