|
Bugzilla – Full Text Bug Listing |
| Summary: | kdm doesn't allow logins due to keyboard error | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Henryk Hecht <nvbugs> |
| Component: | Other | Assignee: | Juergen Weigert <jw> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | c_maass, r.cabane, sndirsch, uli.2001 |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Henryk Hecht
2007-10-06 03:35:37 UTC
So does it help to add kbd to Required-Start of /etc/init.d/earlyxdm? Restart of machine required ... Unfortunately it makes no difference. I'm not positive kbd is actually getting started before earlyxdm, though. There's: <notice>startproc: execve (/opt/kde3/bin/kdm)... quite a ways above: setfont: putfont: 256,8x16: failed: -1 putfont: KDFONTOP: Invalid argument which was the bug alluded to above (bug #331529). Of course, the way the startup messages are buffered means that one cannot infer that kdm is actually getting started before kbd just because of the order of the messages...Also, I'm not sure what the difference between "service" and "$service" in Required-start is-the usage in the scripts themselves seems random. Changing S04earlyxdm to S12earlyxdm certainly made it start later. It still appears to start before the setfont message, and it still doesn't work. Sorry, I forgot to mention that after editing the init script you need to run insserv. Anyway, reassigning to kbd maintainer. I tried (manually) linking earlyxdm as S15earlyxdm, and xdm as S18xdm, which makes the latter not very early, and the latter almost the last thing to run. This eliminates the problem, which confirms the idea that it's probably a matter of sequencing. I also tried eliminating earlyxdm completely and leaving xdm at 15, which also worked. There seem to me to be a few possibilities: 1. bug #331529 is to blame. I don't know how to fix it, so I can't tell. I just find it suspicious that there is a problem with the kbd script (albeit with setfont) and then a problem with the keyboard. 2. kbd is hanging on something else 3. init blithely launches kbd, but does not wait fo the kbd script to finish before starting earlyxdm. I'm not sure if this is possible with the suse init system. 4. there is some other hidden dependency (not kbd). Nothing obvious stands out in rc5.d, though. I do not know how to further localize the problem, so I guess I'll just leave the symlinks as they are for now, a late login manager being preferable to starting it by hand each time. BTW I'm just having problems also. I did an update of the Xorg server & kdm. My versions are: xorg:core 7.2-135.2 & server: 7.2-143.2 kdm:3.5.8-2.2 What happens : I can start the X server from a console login by startx. I can launch kdm, the login screen appears, but I can't reach KDE at all; I tried to build kdrmrc from scratch, nothing changes. I can't find anything special in the logs. So I suspect a sequencing/timing problem. Should I file a bigreport ? I am now certain that this is related to bug #331529 (see comment #2 for that bug). What the causal relationship is, I do not know. Nor do I know if it's related to bug #302010, except that that one is supposedly fixed and this one certainly is not. *** Bug 336507 has been marked as a duplicate of this bug. *** Depending on one's point of view, this should probably be viewed either as depending on or being a duplicate of bug #335267; this and bug #331529 were different manifestations of the same problem, and the latter has been marked as a duplicate of bug #335267. The suggested workaround in that bug also worked for me, in case anyone is still having trouble with [kgx]dm. *** Bug 331671 has been marked as a duplicate of this bug. *** *** Bug 335261 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 302010 *** |