Description of problem: MCC/drakconf fails to start after clean install. I set the component as "installer", but it could be an issue with the ldetect-lst package. Version-Release number of selected component (if applicable): Mageia 8 Beta 2 How reproducible: Always reproducible. Steps to Reproduce: 1. Fresh install of Mag 8 Beta 2 from classic x86_64 DVD, Plasma UI 2. Let installer install any pending updates 3. (Don't know if this is part of the error chain, but it's what I did) Switch to NetworkManager using the steps in the Wiki: https://wiki.mageia.org/en/Switching_to_networkmanager 4. Try to start MCC from icon. Prompts for password, then nothing. 5. Start MCC from console as root and got the following: [neosoft /root] # drakconf Too late to run INIT block at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 257. Ignore the following Glib::Object::Introspection & Gtk3 warnings Subroutine Gtk3::main redefined at /usr/share/perl5/vendor_perl/Gtk3.pm line 539. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. Missing usbtable (should be /usr/share/ldetect-lst/usbtable) 6. Run 'update-ldetect-lst' which created usbtable.gz file. After that, mcc launched fine. Additional information: neosoft /root] # rpm -qa |grep ldetect-lst ldetect-lst-0.6.15-1.mga8 ldetect-lst-0.6.16-1.mga8 [neosoft /root] # rpm -qif /usr/sbin/update-ldetect-lst Name : ldetect-lst Version : 0.6.15 Release : 1.mga8 Architecture: x86_64 Install Date: Sun 27 Dec 2020 09:40:28 PM PST Group : System/Kernel and hardware Size : 6751879 License : GPLv2+ Signature : RSA/SHA256, Fri 20 Nov 2020 09:27:30 AM PST, Key ID b742fa8b80420f66 Source RPM : ldetect-lst-0.6.15-1.mga8.src.rpm Build Date : Fri 20 Nov 2020 09:14:37 AM PST Build Host : localhost Packager : ghibo <ghibo> Vendor : Mageia.Org URL : http://gitweb.mageia.org/software/ldetect-lst/ Summary : Hardware list for the light detection library Description : The hardware device lists provided by this package are used as lookup table to get hardware autodetection. Name : ldetect-lst Version : 0.6.16 Release : 1.mga8 Architecture: x86_64 Install Date: Sun 27 Dec 2020 10:11:36 PM PST Group : System/Kernel and hardware Size : 6780580 License : GPLv2+ Signature : RSA/SHA256, Wed 16 Dec 2020 01:58:09 PM PST, Key ID b742fa8b80420f66 Source RPM : ldetect-lst-0.6.16-1.mga8.src.rpm Build Date : Wed 16 Dec 2020 12:59:19 PM PST Build Host : localhost Packager : tmb <tmb> Vendor : Mageia.Org URL : http://gitweb.mageia.org/software/ldetect-lst/ Summary : Hardware list for the light detection library Description : The hardware device lists provided by this package are used as lookup table to get hardware autodetection.
Assignee: bugsquad => mageiatools
A perhaps unrelated comment would be why are two versions of ldetect-lst installed? Shouldn't the 0.6.16 package have upgraded the previous one?
The comment is related, if you have 2 version this is probably because there was a crash during installation, after installing the new version but before removing the old one. If the installation had completed it would have run update-ldetect-lst for you: $ rpm -q --scripts ldetect-lst postinstall program: /usr/sbin/update-ldetect-lst preuninstall program: /usr/sbin/update-ldetect-lst --clean
CC: (none) => pterjan
Interesting. I don't recall any obvious crashes in the installer between when it did the initial install and the updater ran.
Please attach /root/drakx/report.bug.xz from your installed system. That will show if there any problems during installation.
CC: (none) => mageia
From the report, first package was installed at "Sun 27 Dec 2020 09:40:28 PM PST" (so probably the install), and the one where there was a crash while installing the update was at "Sun 27 Dec 2020 10:11:36 PM PST" half an hour later.
Created attachment 12164 [details] crash bug report Oh, I do remember an error now! Sorry for the lapse in memory. Attached is the bug report file.
From the log: * installUpdates: successfully added media * running: gurpmi2 --auto-select with root /mnt * ERROR: killing runaway process (process=gurpmi2, pid=12746, args=--auto-select, error=ALARM at /usr/lib/libDrakX/run_program.pm line 235. ) * step "installUpdates" took: 0:11:24 so looks like you got hit by the default 10 minute timeout. I thought I'd disabled that...
Ah, I disabled it in draklive-install. I've now applied the same fix to the classical installer.
Source RPM: (none) => drakx-installer-stage2Status comment: (none) => fixed in gitStatus: NEW => ASSIGNEDAssignee: mageiatools => mageiaSummary: drakconf fails to start unless ldtect-lst is run first => drakconf fails to start unless ldtect-lst is run first due to aborted installation of updated packages
Yeah you only did for removing pkgs previously: http://gitweb.mageia.org/software/drakx/commit/?id=8ceeb6e06e4fd26f038dcf314d1bccead4132797
CC: (none) => thierry.vignaud
The fix was released before the final Mageia 8 ISOs were built, and I haven't seen any similar reports since, so closing.
Status comment: fixed in git => fixed in drakx-installer-stage2-18.39-1.mga8Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED