Bug 27272

Summary:	mgaapplet-update-checker crashed
Product:	Mageia	Reporter:	boris hamilton <hamilton3999>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	ouaurelien
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	mgaonline-3.30-3.mga8	CVE:
Status comment:

Description boris hamilton 2020-09-13 09:33:26 CEST

The "mgaapplet-update-checker" program crashed. Drakbug-18.33 caught it.

updating check

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: Breeze
Kernel version = 5.8.7-desktop-1.mga8
Distribution=Mageia release 8 (Cauldron) for x86_64
CPU=AMD E1-7010 APU with AMD Radeon R2 Graphics

Comment 1 Aurelien Oudelet 2020-09-13 16:14:40 CEST

Hi,
Thanks reporting this.

We have some questions.
1) What online repositories are configured?
Could you list which are activated in Mageia Control Centre => Software => Configure repositories?

2) You are using Mageia Cauldron. Which Desktop do you use? And what Media have you used to install?

Keywords: (none) => NEEDINFO
CC: (none) => ouaurelien

Comment 2 Aurelien Oudelet 2020-12-09 20:28:53 CET

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 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.

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