Description of problem: System boots only in Rescue Mode Version-Release number of selected component (if applicable): Mageia 3.0 How reproducible: This is your job Steps to Reproduce: 1.) on Bootscreen you see mageia and when you will startet mageia 3.0 an black screen startet and the laptop works and works and works, but no login start you don't can log in your system, than you must made an hard reset or POWER OFF and start with the rescue shell than you must type systemctl default and mageia startet with the login screen 2.)than on Bootscreen when you type esc it don't work you never see the start and what daemons are run or not run and where the system stopped and you have an interrupped holy crap.. 3.) when megeia start over the systemctl default with the rescueshell and you make than when your desktop kde or gnome work an reboot you have the same problems 4.) when you are finish with this session and make an shutdown and then you will start mageia new you have the same problems too... 5.) why can not see all the logfiles in /var/log please read to this prob the README in var/log this is sry BULLSHIT you don't see lastlog 6.) and why so many daemons work on an standard installation this is BULLSHIT 7.) Please EXCUSE MY BAD ENGLISH but the Prob is the same, you have the highrisk to loose data or your complete system when you mast made often an hard reset and must put in the rescue shell to start your system holy crap Regards Reproducible: Steps to Reproduce:
install rsyslog if you want old log system or give a try to journalctl for the new one.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD