The "drakconf" program crashed. Drakbug-18.45 caught it. Bonjour, J'essai le version Mageia 8 à partir d'une clé USB (live). Voici le premier plantage de "drakconf". Context : J'ai voulu ajouter des composants graphiques pour procéder aux essais de cette version 8 ;-(( Cordialement, F.A. mcc.css:1:0Failed to import: Erreur lors de la lecture du fichier : Erreur d'entrée/sortie at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 67. Perl's trace: drakbug::bug_handler() called from /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm:67 Glib::Object::Introspection::__ANON__() called from /usr/libexec/drakconf:95 Theme name: Adwaita Kernel version = 5.10.16-desktop-1.mga8 Distribution=Mageia release 8 (Official) for x86_64 CPU=Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
Pouvez-vous nous fournir davantage d'infos, en commençant par quel ISO vous essayez. [which ISO?] Puis du système Live (poster le résultat) : $ inxi -MS [ask for system details] et décrire qu'est-ce que vous faisiez pour produire le crash. Ajouter de logiciels via MCC ou Add/Remove software? [what exactly were you doing to get the crash? Adding s/w via MCC or Add/Remove s/w?] Avez-vous essayer l'operation plus qu'une fois ? L'échec, est-il persistant ou parfois ? [Is the failure persistent or sometimes?] Si vous essayez le même operation du ligne de commands dans un terminal : # urpmi ..... est-ce qu'il marche ? [does it work from command line?] --- For ref, other 'drakconf crashed' bugs, which do *not* look the same: bug 26707, bug 21814, bug 24957
Status: NEW => NEEDINFOCC: (none) => lewyssmith
Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
CC: (none) => ouaurelienKeywords: (none) => NEEDINFO
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, 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 their 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: NEEDINFO => RESOLVEDResolution: (none) => OLD