Bug 18055

Summary:	System-hang at end of bootstrap with profile selection
Product:	Mageia	Reporter:	Juergen Harms <juergen.harms>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	High	CC:	juergen.harms, marja11
Version:	5
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakx-net-2.22-1.mga5	CVE:
Status comment:

Description Juergen Harms 2016-03-23 11:14:11 CET

Bootstrapping a Mageia partition with multiple profiles hangs if a profile is selected that does not correspond to the current profile (not the one marked by an *).

At the end of booting a system that has more than one profile configured, a message like

Select network profile: (1) default* (2) roaming

sollicits the user to select the profile he wants to initially use. If the user selects the "currently active" profile (the one marked by the *), everything goes well; if he selects another profile - when he needs a switch of profile to be made, the system becomes unresponsive and gets into a hang-like state.
In order to avoid the need to re-boot, the key combination "Left Alt + SysRq + i" will kill all current processes except init, and the desktop will be started.

It is probable that this problem also occurs in cauldron (Mageia-6), but I do not have a cauldron system to verify.

A second bug on draknetprofile will be filed immediately (missing "module" options"), the issues might be related.

Juergen Harms 2016-03-23 11:15:09 CET

Priority: Normal => High

Comment 1 Juergen Harms 2016-03-23 11:25:32 CET

I had a problem when submitting the bug, too much in a hurry - sorry

The problem is 100% reproducible

Steps to reproduce
1. Use draknetprofile to create an (at least) second profile
2. Reboot the system
3. When the key-in to specify a new profile comes, select the profile that is not the current profile (does not have  an *)

Source RPM: (none) => drakx-net-2.22-1.mga5

David Walser 2016-03-23 18:52:04 CET

Assignee: bugsquad => thierry.vignaud

Comment 2 Marja Van Waes 2018-04-24 18:55:14 CEST

Hi Juergen,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 3 Marja Van Waes 2018-10-06 13:13:54 CEST

CC'ing the new account of the reporter.

@ Jürgen,

Please reopen this report if it is still valid in a maintained Mageia version.

Resolution: (none) => OLD
Status: NEW => RESOLVED
CC: (none) => juergen.harms