Bug 3649 - 2_a1: No console login: prompt in runlevel 3
Summary: 2_a1: No console login: prompt in runlevel 3
Status: RESOLVED DUPLICATE of bug 4170
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 2120
  Show dependency tree / graph
 
Reported: 2011-12-07 08:19 CET by Bit Twister
Modified: 2012-01-23 17:42 CET (History)
0 users

See Also:
Source RPM: systemd-37-17.mga2.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2011-12-07 08:19:11 CET 
Description of problem:

No console login: prompt  in runlevel 3 

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


How reproducible: Always


Steps to Reproduce:
1. clean install with updates applied
2. modify /boot/grub/menu.lst to have space 3 on end of line, remove splash=silent argument
3. reboot
4. wait for Started LSB: Network monitoring daemon.
5. hit Enter, note newline works, but no login prompt.


Workaround is to hit the Left Windows key until you find the Login: prompt.
Comment 1 Manuel Hiebel 2011-12-07 17:53:29 CET 
I guess you use systemd ?
Comment 2 Bit Twister 2011-12-07 20:09:46 CET 
(In reply to comment #1)
> I guess you use systemd ?

Yes. Mandriva 2011.0 also had the problem. They did seem to fix it as far as a real system goes. I think it is a race condition because VirtualBox has no prompt IIRC. Then again it exists on real hardware. My real system has lots of partitions on both drives and my VirtualBox has about 3 partitions on drive.
Manuel Hiebel 2011-12-07 21:15:06 CET

Blocks: (none) => 2120

Comment 3 Bit Twister 2011-12-20 00:48:04 CET 
Workaround/Solution:

cd /etc/systemd/system/getty.target.wants
ln -sf ../../../../lib/systemd/system/getty@.service getty@tty1.service

Source RPM: (none) => systemd-37-17.mga2.src.rpm

Comment 4 Manuel Hiebel 2012-01-23 17:42:42 CET 
dup of 4170 I guess

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.