Bug 99026

Summary:	Keyboard not working when booting straight into runlevel 5
Product:	[Unmaintained] kdm	Reporter:	Peter Vollebregt <peter.vollebregt>
Component:	general	Assignee:	kdm bugs tracker <kdm-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	Hermann.Zheboldov, mslinux2003, sven.burmeister
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Peter Vollebregt 2005-02-10 13:26:45 UTC

Version:            (using KDE KDE 3.3.92)
Installed from:    SuSE RPMs
OS:                Linux

Via apt (gwdg server) i installed the latest beta version (....3.3.92-1_1586 SuSE RPM's). When booting straight into runlevel 5 the kdm login manager comes up but it is impossible to type in anything via the keyboard (although the mouse is working). When passing the login dialog the keyboard is also not working in kde.

The workarounds are 
- to launch into runlevel 3 and then to launch kdm
- use another manager (gdm or xdm)

Checking the existing bugs i noticed the common error about vt7, but i have a vt7 call in my .Xservers file and i have also a ServerVTs=-7 call  in my kdmrc file. 

Note that several other people reported the same error on SuSE's suse-kde@suse.com mailing list.

Comment 1 Oswald Buddenhagen 2005-02-10 13:54:17 UTC

this _has_ to be the same problem.
you probably have several kdmrc files and kdm uses "the other one". suse makes a mess of this for years.


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

Comment 2 Peter Vollebregt 2005-02-10 14:59:28 UTC

OK this solved it

/opt/kde3/share/config/kdm/kdmrc contained the line ServerVTs=-7 in section GENERAL. /etc/opt/kde3/share/config/kdm/kdmrc did not and was used. Symlinking the first to the last solved the issue.

Still this seems to be a weak point (given murphy's law that says that when something can go wrong it will go wrong). Can KDE remove the possibility?

Comment 3 Oswald Buddenhagen 2005-02-10 15:21:01 UTC

> Can KDE remove the possibility?
>
no. the default config generated by kde just works. if suse screws up the packages, i don't care. i told them three years ago, two years ago, etc.  if they maintain that doing some black magic instead of just using upstream upgrade tools is better for backwards compatibility with some ancient suse release, it is _their_ [customers'] problem, _not_ mine.

Comment 4 Daniel Eckl 2005-02-10 18:32:32 UTC

Hmmmm, that's very unsatisfying for customers like me, but I have to give full acknowledge to you.

Comment 5 Oswald Buddenhagen 2005-02-11 08:33:28 UTC

*** Bug 99068 has been marked as a duplicate of this bug. ***

Comment 6 Oswald Buddenhagen 2005-02-11 12:23:22 UTC

*** Bug 99105 has been marked as a duplicate of this bug. ***

Comment 7 Gianluigi Belli 2005-02-12 16:13:36 UTC

same conditions and same problems but aren't solved symlinking the kdmrc.
In boot.smg i found "Failed services in runlevel 5: kbd" and the error is "putfont: PIO_FONT: Invalid argument"

Comment 8 Hermann Zheboldov 2005-02-15 11:22:33 UTC

I have the same situation as Gianluigi

Comment 9 Elmar Eberhardt 2005-02-15 11:38:59 UTC

actually it seems like suse already fixed the problem (and the next one too 99093) - just download another 150MB...
Anyway - problems like this will make me use more Debian and Gentoo...

Comment 10 Hermann Zheboldov 2005-02-15 11:59:00 UTC

To Elmar

For may opinon these problems are not the cornerstone for refusing to use SuSE

Comment 11 S. Burmeister 2005-02-15 12:36:35 UTC

@Elmar, do you get this problem with a stable KDE, or just the betas? If stable, the official packages, or 3.3.2? Betas are not meant to work perfectly, so if you want that, use debian stable.