Bug 34510 - drakrpm crashed with new version (3.mga10) of gtk+3
Summary: drakrpm crashed with new version (3.mga10) of gtk+3
Status: RESOLVED DUPLICATE of bug 34437
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: 2025-07-25 08:12 CEST by alain brasseau
Modified: 2025-07-25 08:24 CEST (History)
0 users

See Also:
Source RPM: rpmdrake-6.32-4.mga10
CVE:
Status comment:


Attachments

Description alain brasseau 2025-07-25 08:12:12 CEST
The "drakrpm" program crashed. Drakbug-18.69 caught it.

saisie de caractere pour rechercher un paquet

FATAL: could not convert value -1494491120 to enum type GdkEventType at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 161.
Perl's trace:
drakbug::bug_handler() called from /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm:161
Glib::Object::Introspection::__ANON__() called from /usr/share/perl5/vendor_perl/Gtk3.pm:446
Gtk3::Gdk::Event::_rebless() called from /usr/share/perl5/vendor_perl/Gtk3.pm:592
Gtk3::main() called from /usr/share/perl5/vendor_perl/Gtk3.pm:537
Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1550
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:857
ugtk3::main() called from /usr/share/perl5/vendor_perl/Rpmdrake/gui.pm:609
Rpmdrake::gui::ask_browse_tree_given_widgets_for_rpmdrake() called from /usr/libexec/drakrpm:835
main::run_treeview_dialog() called from /usr/libexec/drakrpm:859

Theme name: Breeze
Kernel version = 6.15.7-desktop-2.stablenew.mga10
Distribution=Mageia release 10 (Cauldron) for x86_64
CPU=AMD FX(tm)-6300 Six-Core Processor
Comment 1 sturmvogel 2025-07-25 08:24:40 CEST
Please check fir existing bugreports! This is the 14th duplicate.

*** This bug has been marked as a duplicate of bug 34437 ***

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


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