Bug 27604 - mgaapplet-upgrade-helper crashed
Summary: mgaapplet-upgrade-helper crashed
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-14 15:01 CET by Bruno Sellin
Modified: 2020-11-29 12:08 CET (History)
1 user (show)

See Also:
Source RPM: mgaonline-3.24.1-1.mga6
CVE:
Status comment:


Attachments

Description Bruno Sellin 2020-11-14 15:01:43 CET
The "mgaapplet-upgrade-helper" program crashed. Drakbug-17.88.3 caught it.

MAJ de Mageiea 6 vers 7

Can't locate object method "get_xid" via package "Glib::Object::_Unregistered::GdkWaylandWindow" at /usr/libexec/mgaapplet-upgrade-helper line 205.
Perl's trace:
drakbug::bug_handler() called from /usr/libexec/mgaapplet-upgrade-helper:205
main::upgrade() called from /usr/libexec/mgaapplet-upgrade-helper:74

Theme name: Adwaita
Kernel version = 4.14.62-desktop-2.mga6
Distribution=Mageia release 6 (Official) for x86_64
CPU=AMD A4-3420 APU with Radeon(tm) HD Graphics
Comment 1 Aurelien Oudelet 2020-11-16 21:15:23 CET
(In reply to Bruno Sellin from comment #0)
> The "mgaapplet-upgrade-helper" program crashed. Drakbug-17.88.3 caught it.
> 
> MAJ de Mageiea 6 vers 7
> 
> Can't locate object method "get_xid" via package
> "Glib::Object::_Unregistered::GdkWaylandWindow" at
> /usr/libexec/mgaapplet-upgrade-helper line 205.

Wayland ? in Mageia 6?
I really suggest you to run this on a strong GNOME on Xorg session.

This can't be reproduced as Mageia 6 is EOL for so long time.

At last, please do a release upgrade through a M7 Classical ISO and choose upgrade path. Make sure you add online repos while upgrading to have all necessary packages to be upgraded.

Please report successful (or not) here.
I will close this OLD later this month.
Leaving this in Bugsquad for now.

CC: (none) => ouaurelien

Comment 2 Aurelien Oudelet 2020-11-29 12:08:23 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 their 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.