Bug 34520 - drakrpm crashed when starting to type in search field
Summary: drakrpm crashed when starting to type in search field
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-30 10:17 CEST by Jani Välimaa
Modified: 2025-07-30 10:30 CEST (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Jani Välimaa 2025-07-30 10:17:23 CEST 
The "drakrpm" program crashed. Drakbug-18.69 caught it.

Start typing in search field after selecting it via mouse click.

FATAL: could not convert value 1079849262 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: Adwaita
Kernel version = 6.12.40-desktop-1.mga10
Distribution=Mageia release 10 (Cauldron) for x86_64
CPU=Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
Comment 1 sturmvogel 2025-07-30 10:30:27 CEST 
17th duplicate…

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

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.