Bug 12078

Summary:	xscreensaver.kss & kikbd problem.
Product:	[Retired] Red Hat Linux	Reporter:	Aleksey Nogin <aleksey>
Component:	xscreensaver	Assignee:	Bill Nottingham <notting>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	jwz, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-01-23 05:00:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Aleksey Nogin 2000-06-11 04:32:04 UTC

All other KDE screensavers make sure that kikbd is switched back to
"default" keyboard before locking the screen. Xscreensaver.kss does not do
that. As a result if the kikbd was switched into some other keyboard before
xscreensaver kiked in, there is no way to type in the password and to
unlock the screen (other than logging in using some other means and killing
xscreensaver).

Comment 1 Bill Nottingham 2000-06-11 19:13:43 UTC

I'm not sure I'm catching this; where do the kde
screensavers switch the keyboard mode/mapping?

Comment 2 Aleksey Nogin 2000-06-11 19:51:43 UTC

I am not sure who does it and how. But what I know is that when I have my
screensaver set to, for example, xrock.xss and I press the lock button on the
panel, kikbd switches to default keyboard just before the screenbecomes locked.
This does not happen with xcreensaver.kss.

Comment 3 Bill Nottingham 2002-11-11 20:46:11 UTC

At this point, this is probably not something we're going to look into inhouse.