Bug 18391 - [6sta1] "Failed to get cgroup: no media found"
Summary: [6sta1] "Failed to get cgroup: no media found"
Status: RESOLVED DUPLICATE of bug 18216
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL:
Whiteboard:
Keywords: 6sta1
Depends on:
Blocks:
 
Reported: 2016-05-07 06:25 CEST by Ben McMonagle
Modified: 2016-05-07 15:26 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Ben McMonagle 2016-05-07 06:25:01 CEST
Description of problem:"Failed to get cgroup: no media found
starting system 229" is displayed immediately after choosing "Mageia" from grub boot menu


Version-Release number of selected component (if applicable):
Mageia-6-sta1-i586-DVD.iso
DATE.txt: Tue May  3 12:34:47 CEST 2016


How reproducible:every time


Steps to Reproduce:
1.install any DE from above .iso and reboot.
2.choose "Boot Mageia 5
3. a black screen is presented with: Failed to get cgroup: no media found
starting system 229
Ben McMonagle 2016-05-07 06:25:18 CEST

Keywords: (none) => 6sta1

Comment 1 Marja Van Waes 2016-05-07 09:34:19 CEST
That error has also been present in 64bit cauldrons for quite a while (some months, iinm), too, now. Everything seems to work fine, though

CC: (none) => marja11
Assignee: bugsquad => mageia

Marja Van Waes 2016-05-07 09:34:29 CEST

Hardware: i586 => All

Comment 2 Dimitrios Glentadakis 2016-05-07 13:23:14 CEST
I have the same problem twice in Cauldron 64bit in Virtualbox. After, i cannot login in graphical mode.

CC: (none) => dglent

Comment 3 Marja Van Waes 2016-05-07 15:26:35 CEST
(In reply to Dimitrios Glentadakis from comment #2)
> After, i
> cannot login in graphical mode.

Please file a bug report for that issue if it doesn't already exist (you'll probably want to first check your "journalctl -ab output to see what goes wrong).

The "Failed to get cgroup: no media found
starting system 229" error was already reported before in bug 18216, closing this one as duplicate

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

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


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