Bug 16833

Summary:	drakrpm-editmedia segfaulted
Product:	Mageia	Reporter:	Doug Laidlaw <laidlaws>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	rpmdrake-6.20-1.mga5	CVE:
Status comment:

Description Doug Laidlaw 2015-09-26 14:29:38 CEST

The "drakrpm-editmedia" program crashed. Drakbug-16.104 caught it.

Reconfiguring drakconf to see a local repository to replace the DVD, which is an infernal nuisance.  It is getting about time I looked for a better distro, after being with Mandrake/Mandriva/Mageia from Mandrake 8 until now.

SEGV
Glibc's trace:
4: /usr/lib/perl5/5.20.1/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sighandler+0x213) [0x7fd6d4a3e443]
5: /lib64/libpthread.so.0(+0x10180) [0x7fd6d3c0c180]
6: /lib64/libgtk-3.so.0(+0x1467c4) [0x7fd6c5ac37c4]
7: /lib/../lib64/libglib-2.0.so.0(+0x1d462) [0x7fd6c72f7462]
8: /lib64/libgtk-3.so.0(+0x146897) [0x7fd6c5ac3897]
9: /lib/../lib64/libgobject-2.0.so.0(g_object_unref+0x125) [0x7fd6c75fbd55]
10: /lib64/libgtk-3.so.0(+0x14872d) [0x7fd6c5ac572d]
11: /lib64/libgtk-3.so.0(+0x13d037) [0x7fd6c5aba037]
12: /lib/../lib64/libglib-2.0.so.0(g_ptr_array_foreach+0x3b) [0x7fd6c72f85bb]
13: /lib/../lib64/libglib-2.0.so.0(+0x1e650) [0x7fd6c72f8650]
14: /lib64/libgtk-3.so.0(+0x13fc22) [0x7fd6c5abcc22]
15: /lib/../lib64/libgobject-2.0.so.0(g_object_unref+0x125) [0x7fd6c75fbd55]
16: /lib/../lib64/libglib-2.0.so.0(+0x379d7) [0x7fd6c73119d7]
17: /lib/../lib64/libglib-2.0.so.0(g_hash_table_remove_all+0x1a) [0x7fd6c731276a]
18: /lib/../lib64/libglib-2.0.so.0(g_hash_table_destroy+0xe) [0x7fd6c73127de]
19: /lib64/libgtk-3.so.0(+0x27448d) [0x7fd6c5bf148d]

Perl's trace:
drakbug::bug_handler() called from /usr/lib/libDrakX/drakbug.pm:41
drakbug::__ANON__() called from /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/Glib/Object/Introspection.pm:58
(eval)() called from /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/Glib/Object/Introspection.pm:58
Glib::Object::Introspection::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1266
mygtk3::MagicWindow::AUTOLOAD() called from /usr/lib/libDrakX/mygtk3.pm:1561
mygtk3::may_destroy() called from /usr/lib/libDrakX/mygtk3.pm:1522
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:859
ugtk3::main() called from /usr/lib/perl5/vendor_perl/5.20.1/Rpmdrake/edit_urpm_sources.pm:516
Rpmdrake::edit_urpm_sources::edit_callback() called from /usr/lib/perl5/vendor_perl/5.20.1/Rpmdrake/edit_urpm_sources.pm:1184
Rpmdrake::edit_urpm_sources::__ANON__() called from /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm:341
(eval)() called from /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm:341
Gtk3::main() called from /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm:294
Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1521
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:859
ugtk3::main() called from /usr/lib/perl5/vendor_perl/5.20.1/Rpmdrake/edit_urpm_sources.pm:1215
Rpmdrake::edit_urpm_sources::mainwindow() called from /usr/lib/perl5/vendor_perl/5.20.1/Rpmdrake/edit_urpm_sources.pm:1244
Rpmdrake::edit_urpm_sources::run() called from /usr/libexec/drakrpm-editmedia:38

Theme name: AlaDelta
Kernel version = 3.19.8-desktop-3.mga5
Distribution=Mageia release 5 (Official) for x86_64
CPU=Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz

Comment 1 Doug Laidlaw 2015-09-26 16:41:10 CEST Comment hidden (off-topic)

Whether I have a mouse in MATE seems to be hit-or-miss.  On the first attempt, no.  Log out and in again, and it is back.

Samuel Verschelde 2015-09-28 09:50:24 CEST

Assignee: bugsquad => thierry.vignaud

Comment 2 Doug Laidlaw 2015-09-28 12:26:31 CEST

Comment 1 belongs to your mouse pointer bug, not this one. This one seems identical to Merkus' bug under Mga 4, which was closed for EOL.  I was trying to redirect the CD repos to copies on my HD.

Comment 3 Marja Van Waes 2018-04-14 13:55:46 CEST

@ Doug,

Thank you for having taken the needed time to report this issue!

If I searched correctly, then there is only bug 17510 of which the traces look similar (even if it was triggered differently), which was reported against Mageia 5, too. 

I don't find that this issue is still valid in Mageia 6 or later.

We regret if it never got fixed for Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

Closing as OLD

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

Comment 4 Doug Laidlaw 2018-04-14 15:47:41 CEST

Thanks Marja. This bug is so old, I had forgotten it even existed!