|
Bugzilla – Full Text Bug Listing |
| Summary: | after upgrading 11.0 rc1 to 11.0 final goldmaster - setfont putfont failed - kdfontop invalid argument | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | andreas bittner <abittner> |
| Component: | KDE3 | Assignee: | Stephan Kulow <coolo> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
andreas bittner
2008-06-19 10:47:10 UTC
thats normal, it is because kdm is started before /etc/init.d/kbd completed. preload bug no, not a bug, that's a feature. What's $KBD_TTY in /etc/sysconfig/keyboard ? in /etc/sysconfig/keyboard i have: KBD_TTY="tty1 tty2 tty3 tty4 tty5 tty6" i am using an usb mouse/keyboard combination on this system. but it was the same hardware with 11.0 rc1. there werent any errors there. i just booted this box again and i had these same errors during boot again. i thought it was still because of the upgrade, but it seems as the errors come up each time. cheers. it's very weird in any case, there were no changes from what I remember between rc1 and final in that area. Does "chkconfig earlyxdm off" help the problem? i booted the 11.0 testsystem up today and these messages didnt show up during todays booting. the other day they showed up during every boot. also: just some moments ago several kde-related updates and other patches have been offered and installed by the suse updater applet in kde4. will report back when i see those errors again. there havent been any changes since the last time i used the testmachine and todays first reboot. so i really dont know why the messages have dissapeared or why the appear in the first place when there were no changes between rc1 and goldmaster as you say. maybe its some racing conditions, timing issues or something during the booting process. cheers. *** This bug has been marked as a duplicate of bug 335267 *** |