331529 – setfont fails on boot

Bug 331529 - setfont fails on boot

Summary: setfont fails on boot

Status:	RESOLVED DUPLICATE of bug 335267

Alias:	None

Product:	openSUSE 10.3
Classification:	openSUSE
Component:	Other (show other bugs)
Version:	Final
Hardware:	i586 openSUSE 10.3

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

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2007-10-06 03:41 UTC by Henryk Hecht
Modified:	2007-10-22 18:20 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 Henryk Hecht 2007-10-06 03:41:56 UTC

While booting:
Loading console font lat9w-16.psfu  -m trivial G0:loadable
setfont: putfont: 256,8x16:  failed: -1
putfont: KDFONTOP: Invalid argument

thus the "kbd" service fails.  Oddly, if one logs in and runs setfont by hand, it doesn't complain.

System was upgraded from 10.2 to 10.3.

Comment 1 Stefan Dirsch 2007-10-16 02:08:37 UTC

I'm wondering whether this isn't related to Bug #302010.

Comment 2 Henryk Hecht 2007-10-22 01:07:48 UTC

Possibly, certainly the symptoms are similar.  From my hasty reading of bug #302010, however, that problem should only occur when not using the framebuffer.  The machine I've found this on boots with the framebuffer enabled.  Moreover, 302010 is marked fixed, and I'm still seeing this problem even with all current patches.

It is definitely related to bug #331528, however.  If earlyxdm is elimited or moved well back in the boot process (see the above bug) then neither bug occurs.  With S04earlyxdm (which is the default on this machine) both bugs occur.

Comment 3 Stefan Dirsch 2007-10-22 03:40:33 UTC

Yes, bug 302010 only happens if framebuffer has been disabled.

Comment 4 Juergen Weigert 2007-10-22 18:20:53 UTC

I had no luck reproducing this up to now.
I believe it is a duplicate of bug #335267.

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