Bug 10770 - after kernel upgrade 3.4.45 -> 3.4.52: impossible to boot into graphical modus
Summary: after kernel upgrade 3.4.45 -> 3.4.52: impossible to boot into graphical modus
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-07-15 13:35 CEST by Markus Mertens
Modified: 2013-11-23 16:15 CET (History)
1 user (show)

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments

Description Markus Mertens 2013-07-15 13:35:38 CEST
Description of problem:

After upgrading from kernel 3.4.45 to kernel 3.4.52 it is not possible anymore to boot directly into graphical modus. Screen messages on tty1 stop with "Failed to start Wait for Plymouth Boot Screen to Quit". The only way to continue is to switch to another tty, login as rot and run "init 5". Then booting into graphical modus on tty7 will finish. 


Version-Release number of selected component (if applicable):

kernel-server-3.4.45-1.mga2 (+ nvidia-current-kernel-3.4.45-server-1.mga2)
kernel-server-3.4.52-1.mga2 (+ nvidia-current-kernel-3.4.52-server-1.mga2)


How reproducible:

Always.


Steps to Reproduce:

1. upgrade from kernel-server-3.4.45 to kernel-server-3.4.52
2. reboot
3. when the boot process hangs on tty1 switch to another tty (e.g. Ctrl+Alt+F2)
4. login as root and run "init 5"
5. booting into graphical modus will finish on tty7
6. switch back to tty2 and logout root
7. continue working on tty7 as usual



Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2013-09-06 22:41:31 CEST
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

Keywords: (none) => Triaged
CC: (none) => stormi
Assignee: bugsquad => tmb
Source RPM: (none) => kernel

Comment 2 Manuel Hiebel 2013-10-22 12:18:59 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 3 Manuel Hiebel 2013-11-23 16:15:38 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 => RESOLVED
Resolution: (none) => OLD


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