[Mageia-discuss] beta2 woes

[Maarten Vanraes]

Op zaterdag 07 april 2012 22:18:27 schreef Tony Blackwell:
> Not getting very far at all with M2beta2 x86_64.  Similar problems on 2
> machines, one laptop one desktop, both of them 4 yrs old or so.  md5 of
> the install disk is OK.
> 
> 1.  Choosing lilo at install always results in failure to boot.  The
> system sits frozen showing boot linux message.  Looking at the system
> via M1 from another partition showed syslog had not been created yet (at
> least on the laptop after 1st failed lilo boot - its there on desktop
> after several reboots)

is it https://bugs.mageia.org/show_bug.cgi?id=5044 ?

> 2. re-running the whole install as new install, keeping everything the
> same, but choosing grub results in a bootable beta2.  I then select
> update all sources and allow this to complete.  Then select update your
> system, it updates glibc and a short list of other things, then
> terminates silently; I'd expected it would come back with an extended
> list of packages to update.  Re-running update manually, MCC brings up
> the 'Please wait' sliding progress bar, then immediately above it "A
> fatal error occurred: Couldn't open RPM DB () at
> /usr/lib/perl5/vendor_perl/5.14.2/Rpmdrake/open_db.pm line 74.."

that is https://bugs.mageia.org/show_bug.cgi?id=4918 ?

already fixed, but since this is on beta2, it'll only be visibly fixed in beta3

> i.e.  I either can't boot it with lilo or can't update it if I got it up
> via grub.
> 
> 3.  Related prblem I guess.  Going in via MCC, vi hardware, to set
> screen stuff has been very flakey.  It now tells me needs to install
> task-x11. OK-ing this gives a brief note about preparing packages
> installation, results in failure "unable to open rpmdb"
> 
> I'm chasing around in circles with this.  Do I need to put these in
> separate critical bug reports?
> tonyb

indeed related.

you can follow the workaround on the bug above.