| Summary: | Segmentation fault on rpmdrake when updating latest gstreamer rpms | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Andrew Holmes <manganeseuk> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | AmandaOralie812, financecajole, hanajendi8, ouaurelien |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Andrew Holmes
2021-02-11 01:20:56 CET
Hi, thanks reporting. Updates were done well? Do you quit rpmdrake and Mageia Control Centre by using File => Quit menu? And after this triggers the segfault? CC:
(none) =>
ouaurelien Note that I answered this 4 minutes after it was reported... and no answer... And NO, closing rpmdrake right after updating stuff does not trigger the segfault. It is the already reported "File => Quit" way which is the correct meanwhile... So after carefully compared above report and Bug 26944 it is a duplicate. *** This bug has been marked as a duplicate of bug 26944 *** Resolution:
(none) =>
DUPLICATE I checked this on another x64 machine shortly afterwards, and on that machine there was no segfault observed. Also, the original (first machine as reported here) has also not repeated the segfault following more recent updates. Shortly after, I verified this on [url=https://1001games.io/]1001 games[/url] another x64 machine, and there was no segfault there either. Additionally, with more recent updates, the original (first machine as mentioned here) has likewise stopped experiencing segfaults. CC:
(none) =>
hanajendi8 I am so fortunate to have you <a href="https://1001games.io/">1001 games</a> because your words have taught me how to live and how to contribute to myself. In the short time that followed, I verified [slime rancher 2](https://slimerancher2.co) this on another x64 machine, and there was no segfault there. Additionally, the first (first machine as described here) hasn't had the segfault again with more recent updates. CC:
(none) =>
AmandaOralie812 Claire, it seems to me that this is a race issue, but the journalctl file and the xsession-errors file don't give any hints about what the problem might be. Would it be possible for you to terminate the mate-panel process and then restart the computer from the command line if you are still experiencing this issue with the final testing isos? Kindly post the results, thank you. https://slope-game.io CC:
(none) =>
financecajole |