Bug 23614

Summary:	draknetcenter crashed (Can't call method "iter_nth_child" on an undefined value)
Product:	Mageia	Reporter:	Javier Díaz <javier_diaz>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakx-net-2.32.2-1.mga6	CVE:
Status comment:

Description Javier Díaz 2018-09-28 21:29:14 CEST

The "draknetcenter" program crashed. Drakbug-17.88.3 caught it.

hibernando portátil

Can't call method "iter_nth_child" on an undefined value at /usr/lib/perl5/vendor_perl/5.22.2/Gtk3/SimpleList.pm line 186.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/Glib/Object/Introspection.pm:67
Glib::Object::Introspection::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1562
mygtk3::flush() called from /usr/lib/libDrakX/mygtk3.pm:1552
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:857
ugtk3::main() called from /usr/lib/libDrakX/network/netcenter.pm:212
network::netcenter::main() called from /usr/libexec/draknetcenter:30

Theme name: oxygen-gtk
Kernel version = 4.14.70-desktop-2.mga6
Distribution=Mageia release 6 (Official) for x86_64
CPU=Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz

Comment 1 Marja Van Waes 2018-09-29 14:39:03 CEST

Ah, this happened to someone in Mageia 5, too, see bug 19706 , but I closed that report because Mageia 5 is no longer maintained and because I hadn't seen any Mageia 6 or later reports with this error, yet.

Assigning to the Mageia tools maintainers.

CC: (none) => marja11
Assignee: bugsquad => mageiatools
Summary: draknetcenter crashed => draknetcenter crashed (Can't call method "iter_nth_child" on an undefined value)

Comment 2 Aurelien Oudelet 2020-08-16 18:54:55 CEST

Does this still valid bug?

CC: (none) => ouaurelien

Comment 3 Aurelien Oudelet 2020-08-26 11:10:08 CEST

Since this reports about MAgeia 6 and not answered 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