Bug 27873 - draklive-install crashed
Summary: draklive-install crashed
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-19 11:26 CET by Dave Hodgins
Modified: 2020-12-19 21:10 CET (History)
1 user (show)

See Also:
Source RPM: draklive-install-2.26-1.mga8
CVE:
Status comment:


Attachments

Description Dave Hodgins 2020-12-19 11:26:50 CET
The "draklive-install" program crashed. Drakbug-18.37 caught it.

Installing from the  Mageia-8-beta2-Live-Xfce-i586.iso in a vb guest with just 512 MB ram.


update-grub2 failed:  at /usr/lib/libDrakX/any.pm line 706.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/libDrakX/any.pm:706
any::setupBootloader__grub2() called from /usr/lib/libDrakX/any.pm:240
any::setupBootloader() called from /usr/sbin/draklive-install:398
main::setup_bootloader() called from /usr/sbin/draklive-install:102
main::install_live() called from /usr/sbin/draklive-install:72

Theme name: Adwaita
Kernel version = 5.9.12-desktop586-1.mga8
Distribution=Mageia release 8 (Cauldron) for i586
CPU=AMD FX(tm)-4170 Quad-Core Processor
Comment 1 Dave Hodgins 2020-12-19 11:33:39 CET
This was encountered while confirming bug 27872.
Comment 2 Lewis Smith 2020-12-19 20:12:08 CET
Dave, you did not say much about how you were installing, especially with relation to that other bug. It is not the same error; but would it happen if you upped the VM memory to 768Mb?

CC: (none) => lewyssmith

Comment 3 Dave Hodgins 2020-12-19 21:10:33 CET
This was selecting install from the boot menu. With 768MB, it finishes ok.
I'll close this bug as fixed, as I've now asked atelier to modify
https://www.mageia.org/en/support/ to indicate 768MB is required for live iso
installs.

I normally give each vb guest 4GB ram, so would normally never have encountered
this bug.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.