The "mgaapplet-update-checker" program crashed. Drakbug-18.45 caught it. I was doing nothing wiht the applet; it just appeared SEGV Glibc's trace: 0: /usr/lib/libDrakX/auto/c/stuff/stuff.so(+0x95d5) [0x7fad5eb1c5d5] 1: /lib64/libperl.so.5.32(Perl_pp_entersub+0x217) [0x7fad5e866a67] 2: /lib64/libperl.so.5.32(Perl_runops_standard+0x2e) [0x7fad5e85d01e] 3: /lib64/libperl.so.5.32(Perl_call_sv+0x364) [0x7fad5e7c42d4] 4: /lib64/libperl.so.5.32(Perl_perly_sighandler+0x229) [0x7fad5e84b899] 5: /lib64/libc.so.6(+0x3b520) [0x7fad5e5d1520] 6: /lib64/libperl.so.5.32(+0x104a1c) [0x7fad5e854a1c] 7: /lib64/libperl.so.5.32(Perl_hv_common+0x852) [0x7fad5e858272] 8: /lib64/libperl.so.5.32(Perl_hv_common_key_len+0x37) [0x7fad5e859577] 9: /usr/lib64/perl5/vendor_perl/auto/URPM/URPM.so(+0xf5e8) [0x7fad5d4325e8] 10: /usr/lib64/perl5/vendor_perl/auto/URPM/URPM.so(+0x13c15) [0x7fad5d436c15] 11: /usr/lib64/perl5/vendor_perl/auto/URPM/URPM.so(+0x149f7) [0x7fad5d4379f7] 12: /usr/lib64/perl5/vendor_perl/auto/URPM/URPM.so(+0x1515d) [0x7fad5d43815d] 13: /lib64/libperl.so.5.32(Perl_pp_entersub+0x217) [0x7fad5e866a67] 14: /lib64/libperl.so.5.32(Perl_runops_standard+0x2e) [0x7fad5e85d01e] 15: /lib64/libperl.so.5.32(perl_run+0x31f) [0x7fad5e7ccd7f] 16: /usr/bin/perl() [0x40125a] 17: /lib64/libc.so.6(__libc_start_main+0xea) [0x7fad5e5bde3a] 18: /usr/bin/perl() [0x40129a] Perl's trace: drakbug::bug_handler() called from /usr/lib/libDrakX/drakbug.pm:41 drakbug::__ANON__() called from /usr/lib64/perl5/vendor_perl/URPM.pm:204 (eval)() called from /usr/lib64/perl5/vendor_perl/URPM.pm:204 URPM::_parse_hdlist_or_synthesis() called from /usr/lib64/perl5/vendor_perl/URPM.pm:220 URPM::parse_synthesis() called from /usr/share/perl5/vendor_perl/urpm/media.pm:1532 urpm::media::_parse_synthesis() called from /usr/share/perl5/vendor_perl/urpm/media.pm:1538 urpm::media::_parse_synthesis_or_ignore() called from /usr/share/perl5/vendor_perl/urpm/media.pm:840 urpm::media::parse_media() called from /usr/share/perl5/vendor_perl/urpm/media.pm:742 urpm::media::configure() called from /usr/bin/mgaapplet-update-checker:63 Theme name: Adwaita Kernel version = 5.10.37-desktop-2.mga8 Distribution=Mageia release 8 (Official) for x86_64 CPU=Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz
Thank you for reporting this. Bug 22042 + recent duplicates noted therein is the nearest I can find for mgaapplet-update-checker crashing, but that/those are a looping problem. This looks quite different. Can you please say whether this happened just once, or whether you have seen it again? And what desktop are you using?
CC: (none) => lewyssmithStatus: NEW => NEEDINFO
Thank you. It has happened twice before. It occurs randomly and appears to occur when the applet is functioning in the background. When it has happened I have been browsing using Waterfox G3.2.1 (64-bit) I am using KDE plasma 5.20.4, KDE Frameworks 5.76.0, QT 5.15.2 These crashes have only been occuring in the past couple of months and have happened 3 times. I cannot relate them to any specific update/upgrade that has happened in that time.
Thank you for the clarifications. I cannot see anything else to ask before assigning this to the Tools group.
Assignee: bugsquad => mageiatoolsStatus: NEEDINFO => NEWCC: lewyssmith => (none)
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=29995
*** Bug 30893 has been marked as a duplicate of this bug. ***
CC: (none) => emanuelgauler
We stopped supporting Mageia 8 almost 8 months ago https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/ That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not. If this particular bug did not get fixed for Mageia 8, then we do regret that. If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field. If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing Mageia is a community project, meaning that we, the users, make Mageia together. The more active contributors we have, the more bug reports will get fixed. Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D
Status: NEW => RESOLVEDResolution: (none) => OLD