Bug 18463 - Four defective rpms during boot.iso install
Summary: Four defective rpms during boot.iso install
Status: RESOLVED DUPLICATE of bug 18413
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: 6sta1
Depends on:
Blocks:
 
Reported: 2016-05-15 18:46 CEST by William Kenney
Modified: 2016-05-19 19:44 CEST (History)
3 users (show)

See Also:
Source RPM: see list in Description
CVE:
Status comment:


Attachments
Error: 'script' failed for memtest86+-5.01-10.mga6.x86_64 (691.01 KB, image/jpeg)
2016-05-16 05:06 CEST, William Kenney
Details
M6 failed transactions during boot.iso install (934.50 KB, image/jpeg)
2016-05-18 20:42 CEST, William Kenney
Details
M6 failed operation during boot.iso install (499.15 KB, image/jpeg)
2016-05-19 18:46 CEST, William Kenney
Details

Description William Kenney 2016-05-15 18:46:19 CEST
Description of problem:

On real hardware with up-to-date repo.

About every week I start with a completely blank hard drive and
attempt an install of M6 using the latest boot.iso. Todays install
resulted in an aborted install and an error message that flagged
the following rpms as not installable:

hylafax+-client-5.5.8-2.mga6.i586.rpm
mgetty-sendfax-1.1.37-1.mga6.i586.rpm
pulseaudio-module-x11-8.0-5.mga6.i586.rpm
pulseaudio-utils-8.0-5.mga6.i586.rpm

This bug is for reference only and may only be a temporary condition.
William Kenney 2016-05-15 18:47:37 CEST

Whiteboard: (none) => 6-sta1

Comment 1 Marja Van Waes 2016-05-15 20:08:09 CEST
(In reply to William Kenney from comment #0)
> Description of problem:
> 
> On real hardware with up-to-date repo.
> 
> About every week I start with a completely blank hard drive and
> attempt an install of M6 using the latest boot.iso. Todays install
> resulted in an aborted install and an error message that flagged
> the following rpms as not installable:
> 
> hylafax+-client-5.5.8-2.mga6.i586.rpm
> mgetty-sendfax-1.1.37-1.mga6.i586.rpm

This is the third time I see a report about a problem with hylafax+-client and mgetty-sendfax in installer... in former reports it was about them conflicting.

Thomas Spuhler suggested to obsolete mgetty, because it's been dead upstream for a while (last tarball I see is the one we use, from 2010
ftp://mgetty.greenie.net/pub/mgetty/source/1.1/ )

(see also bug 18413 and bug 18215 )

Can you tell me which selections (DEs and/or package groups and/or individual packages) you made while installing?

Assigning to Thierry, beause he'll know how to prevent that mgetty-sendfax can be chosen during install


> pulseaudio-module-x11-8.0-5.mga6.i586.rpm
> pulseaudio-utils-8.0-5.mga6.i586.rpm
> 
> This bug is for reference only and may only be a temporary condition.

Keywords: (none) => 6sta1
CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud
Whiteboard: 6-sta1 => (none)

Comment 2 William Kenney 2016-05-16 00:43:37 CEST
(In reply to Marja van Waes from comment #1)

> Can you tell me which selections (DEs and/or package groups and/or
> individual packages) you made while installing?

This was an attempt at installing Plasma 64-bit. I guess it was using
these i586 packages instead?
Comment 3 Charles Edwards 2016-05-16 01:01:43 CEST
When the category Workstation/Internet Station is selected hylafax+-client and
all 5 mgetty rpms including mgetty-sendfax are auto selected.

If the user also selects individual pkg selection they can be removed under
Workstation/Internet Station/Other.

Their removal does not cause the removal of any other pkgs.

CC: (none) => cae

Comment 4 William Kenney 2016-05-16 02:46:18 CEST
What about the pulseaudio rpm's?
Comment 5 William Kenney 2016-05-16 05:04:55 CEST
Ran the test again to capture the error screen and didn't get the
errors a second time.
But I did get an error I've seen repeatedly:

Error: 'script' failed for memtest86+-5.01-10.mga6.x86_64

Screen shot attached. After getting through this I ok'd the install of
the proprietary video driver ( nvidia ) and the system got into an endless
reboot after that was installed. I'll try again in another few days.
Comment 6 William Kenney 2016-05-16 05:06:12 CEST
Created attachment 7798 [details]
Error: 'script' failed for memtest86+-5.01-10.mga6.x86_64
Comment 7 Charles Edwards 2016-05-16 05:30:26 CEST
(In reply to William Kenney from comment #5)
> Ran the test again to capture the error screen and didn't get the
> errors a second time.
> But I did get an error I've seen repeatedly:
> 
> Error: 'script' failed for memtest86+-5.01-10.mga6.x86_64

That's been occurring on EFI installs 

> Screen shot attached. After getting through this I ok'd the install of
> the proprietary video driver ( nvidia ) and the system got into an endless
> reboot after that was installed. I'll try again in another few days.

I can give you a work-around with the nvidia issue if you would like to try it.
Just drop a line to the qa-discuss@ml.mageia.org rather than adding more issues to this report.
Comment 8 William Kenney 2016-05-16 06:37:15 CEST
Thanks Charles. Lets see how this next set of isos looks
Comment 9 Frank Griffin 2016-05-16 15:24:54 CEST
Dup of https://bugs.mageia.org/show_bug.cgi?id=18413 ?

CC: (none) => ftg

Comment 10 William Kenney 2016-05-18 20:41:40 CEST
I've been attempting a 64-bit, Plasma boot.iso on real hardware install
every couple days and each time I come up with some failed transactions.
A few repeat but I think there are some that come and go. I'll try to
post what I get as I go along. I think we have two open bugs for
basically the same thing:

https://bugs.mageia.org/show_bug.cgi?id=18413

https://bugs.mageia.org/show_bug.cgi?id=18463

I suggest we mark one of this as a dup and use that to post what we get
as we go along.
Comment 11 William Kenney 2016-05-18 20:42:32 CEST
Created attachment 7807 [details]
M6 failed transactions during boot.iso install
Comment 12 Charles Edwards 2016-05-18 21:57:12 CEST
Many of the plasma|kde rpms were updated yesterday so I think those errors you got were simply transitory.

For the hylafax+-client error I have opened a bug report specific to it and
providing a solution.
https://bugs.mageia.org/show_bug.cgi?id=18484

I have run 2 successful boot.iso installs over the past 6 hrs.
I used the previously noted workaround for hylafax+-client.
The latest I did not choose plasma during pkg selection but I did just now install
task-plasma on the running system and am able to login to a working plasma desktop.
Comment 13 William Kenney 2016-05-19 00:04:45 CEST
(In reply to Charles Edwards from comment #12)

> Many of the plasma|kde rpms were updated yesterday so I think those errors
> you got were simply transitory.

Yes, I agree. I'll give it a go again tomorrow ( California time )

> For the hylafax+-client error I have opened a bug report specific to it and
> providing a solution.
> https://bugs.mageia.org/show_bug.cgi?id=18484

We have success when we have a clean install.

> The latest I did not choose plasma during pkg selection but I did just now
> install
> task-plasma on the running system and am able to login to a working plasma
> desktop.

I had a pretty good working system a couple weeks ago. We'll get there.
I've go two ( i586 & x86_64 ) Vbox M6 Clients installed from the last
live isos that are still cook'n along.
Comment 14 William Kenney 2016-05-19 18:46:38 CEST
Created attachment 7810 [details]
M6 failed operation during boot.iso install

Today the ( stage 2 ) xorg server would not even start. See attachment.
Comment 15 Marja Van Waes 2016-05-19 19:44:55 CEST
(In reply to Charles Edwards from comment #12)
> Many of the plasma|kde rpms were updated yesterday so I think those errors
> you got were simply transitory.
> 
> For the hylafax+-client error I have opened a bug report specific to it and
> providing a solution.
> https://bugs.mageia.org/show_bug.cgi?id=18484
> 

thanks :-)

(In reply to William Kenney from comment #14)
> Created attachment 7810 [details]
> M6 failed operation during boot.iso install
> 
> Today the ( stage 2 ) xorg server would not even start. See attachment.


stage2 is from last night, so is most likely affected by bug 18487

I'll close this bug as duplicate of bug 18413, which should be turned into a tracker, setting it to depend on the separate issues.

*** This bug has been marked as a duplicate of bug 18413 ***

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


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