721441 – During boot couldn't open /dev/tty1 /dev/tty2 etc.

Bug 721441 - During boot couldn't open /dev/tty1 /dev/tty2 etc.

Summary: During boot couldn't open /dev/tty1 /dev/tty2 etc.

Status:	RESOLVED DUPLICATE of bug 720486

Alias:	None

Product:	openSUSE 12.1
Classification:	openSUSE
Component:	Basesystem (show other bugs)
Version:	Factory
Hardware:	x86-64 SUSE Other

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

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2011-09-30 10:05 UTC by Freek de Kruijf
Modified:	2011-10-10 19:33 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 Freek de Kruijf 2011-09-30 10:05:48 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0

During booting of openSUSE 12.1 factory with only the repositories oss and non-oss and starting with System V, I got the message "Loading keymap Couldn't open /dev/tty1 /dev/tty2 /dev/tty3 /dev/tty4 /dev/tty5 /dev/tty6"

Reproducible: Always

Steps to Reproduce:
1.Update openSUSE 12.1 M5 from the factory repositories
2.boot using System V and press Esc to see the messages
3.
Actual Results:  
This message is displayed

Expected Results:  
No display of this message

Comment 1 Freek de Kruijf 2011-09-30 10:06:53 UTC

I forgot to mention this is a system running in VirtualBox 4.1.2.

Comment 2 Freek de Kruijf 2011-10-01 15:47:49 UTC

However it is also present on a real system after updating the M5 system with the current Beta1 repositories.

Comment 3 Hans-Peter Holler 2011-10-01 16:43:46 UTC

It's /bin/loadkeys from package kbd-1.15.3.
It does no longer accept more than one argument with option -C as 1.15.2 did.

Comment 4 Hans-Peter Holler 2011-10-10 19:33:12 UTC

dupe of and resolved with #720486

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