462609 – Check login capability on virtual text terminals

Bug 462609 - Check login capability on virtual text terminals

Summary: Check login capability on virtual text terminals

Status:	RESOLVED DUPLICATE of bug 463582

Alias:	None

Product:	openSUSE 11.1
Classification:	openSUSE
Component:	X11 Applications (show other bugs)
Version:	Final
Hardware:	x86-64 openSUSE 11.1

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2008-12-26 21:39 UTC by Markus Elfring
Modified:	2009-02-13 13:57 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

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

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

Description Markus Elfring 2008-12-26 21:39:17 UTC

I can switch to the virtual terminals by the keyboard shortcuts Strg+Alt+F1 to F6 from my KDE3 session. But these text consoles do not provide login prompts as I was used to this feature in openSUSE 11.0.
How should the login be reactivated by the display manager?

Comment 1 Marcus Meissner 2009-01-13 08:52:30 UTC

the number might be reduced to be just on console 1, but it should be there.

is the boot process finished? what is displayed on console 1?

Comment 2 Markus Elfring 2009-01-13 18:09:31 UTC

(In reply to comment #1)
> is the boot process finished?

Yes, since a few minutes. Today my third boot try was successful because of an unpleasant issue with binfmt_misc mount (bug #463582).



> what is displayed on console 1?

I see the usual startup messages. The cursor is blinking behind the text "Starting jexec services".

Comment 3 Markus Elfring 2009-01-22 18:31:34 UTC

Morgan Cox mentioned a similar observation in the issue "System gets stuck on jexec" (bug #461199).

Comment 4 Cyril Hrubis 2009-02-13 13:57:05 UTC

Duplicate.

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