Bug 26806 - mgaapplet-update-checker crashed
Summary: mgaapplet-update-checker crashed
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-17 19:59 CEST by Elmar Stellnberger
Modified: 2020-08-27 11:01 CEST (History)
2 users (show)

See Also:
Source RPM: mgaonline-3.30-3.mga8
CVE:
Status comment:


Attachments

Description Elmar Stellnberger 2020-06-17 19:59:44 CEST
The "mgaapplet-update-checker" program crashed. Drakbug-18.28 caught it.

done nothing

detecting looping forever while trying to resolve dependencies.
Aborting... Try again with '-vv --debug' options at /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm line 1288.
Perl's trace:
drakbug::bug_handler() called from /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm:1288
URPM::resolve_requested__no_recommends_() called from /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm:1170
URPM::resolve_requested__no_recommends() called from /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm:1100
URPM::resolve_requested() called from /usr/share/perl5/vendor_perl/urpm/select.pm:347
urpm::select::resolve_dependencies() called from /bin/mgaapplet-update-checker:79

Theme name: Adwaita-Xfce
Kernel version = 5.7.1-desktop-1.mga8
Distribution=Mageia release 8 (Cauldron) for x86_64
CPU=Intel(R) Core(TM)2 Extreme CPU Q9300  @ 2.53GHz
Comment 1 Lewis Smith 2020-06-17 21:02:19 CEST
I doubt whether there is enough information here to pursue it. Was this a one-off occurrence? Did the error window pop up out of nowhere, or were you doing anything package related at the time?

As it crashed, did you notice whether it re-established itself in Systray? If it did, it would have later done the same automatic update check. Can you say whether any automatically notified updates have happened since, either during the same session or a later one?

CC: (none) => lewyssmith

Comment 2 Dave Hodgins 2020-06-17 22:24:03 CEST
https://pkgsubmit.mageia.org/ shows the perl stack is in the process of being
rebuilt which takes several hours due to the large number of packages involved.
As mgaapplet is written in perl, it's likely that a prior update installed part
of the perl update.

Wait until the perl rebuild has finished, then install the rest of the updates.
It may require a reinstall if the partial update already installed has broken
urpmi. Cauldron is not expected to be stable until it reaches version freeze.

CC: (none) => davidwhodgins

Comment 3 Elmar Stellnberger 2020-06-18 12:10:31 CEST
I did not do anything package related and magaapplet keeps crashing several times within a session.
Comment 4 Lewis Smith 2020-06-18 14:24:34 CEST
Bad news. Clearly this problem is special to you.
Following Dave's comment 2, I suggest the following:

1. Kill mgaapplet
 $ ps ax | grep mgaapplet
 $ kill xxxx

2. Try updating the system with Mageia tools
Either
 # urpmi --auto-update --auto
the disadvantage of which is that it does (tries) all updates without choice;
Or
 MCC-Manage Software-Update Your System
the advantage of which is that you could de-select everything except just the Perl updates, and try just those.

If none of these work, it looks like urpmi etc are broken. So...

3. Try using DNF to update the system
I know nothing of this, but believe it uses the same rpm database. I cannot advise about its specific usage, but the man page is comprehensive. Start with:
 $ dnf check             [checks the rpm database]

And if nothing works:
> It may require a reinstall if the partial update already installed
> has broken urpmi. Cauldron is not expected to be stable until it reaches
> version freeze.
Comment 5 Aurelien Oudelet 2020-08-27 11:01:49 CEST
Since 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.

Users who have experienced this problem are encouraged to upgrade to the latest update of our 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.

Resolution: (none) => OLD
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.