Bug 245507

Summary:	per-application keyboard layout is forgotten
Product:	kxkb	Reporter:	Silver Salonen <silver.salonen>
Component:	general	Assignee:	Andriy Rysin <arysin>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:	4.5

Description Silver Salonen 2010-07-23 08:09:49 UTC

Version:           unspecified (using Devel) 
OS:                Linux

I have multiple keyboard layouts configured and I've set switching policy to application. The problem is that once I close an application (that I've switched keyboard layout for), the layout activated for the applicaion, is forgotten. When I open the application again, the default keyboard layout is used for that.

Reproducible: Always

Steps to Reproduce:
1) Enable multiple keyboard layouts
2) Set switching policy to 'Application'
3) Open an application
4) Switch the keyboard layout for that application to non-default
5) Close the application
6) Open the application again

Actual Results:  
Keyboard layout is now reset to default

Expected Results:  
Keyboard layout should be the same it was before closing the application

Comment 1 Silver Salonen 2010-07-27 08:53:11 UTC

This is still the case in KDE SC 4.4.95.

Comment 2 Andriy Rysin 2010-08-07 23:01:22 UTC

SVN commit 1160334 by rysin:

Fix saving layout per application (use winclass instead of pid)
BUG: 245507
FIXED-IN: 4.5


 M  +8 -8      layout_memory.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1160334

Comment 3 Andriy Rysin 2010-08-07 23:02:43 UTC

SVN commit 1160335 by rysin:

Fix saving layout per application (use winclass instead of pid)
BUG: 245507
FIXED-IN: 4.5


 M  +8 -8      layout_memory.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1160335

Comment 4 Silver Salonen 2010-08-12 07:57:49 UTC

I use KDE 4.5.0 now, but this still works the same way. Was it fixed after 4.5.0?

Comment 5 Andriy Rysin 2010-08-12 13:17:06 UTC

The push was fixed at 2010-08-07 23:02:43 which was before branch was tagged 4.5.0 so if your packages were built before that (i.e. before revision 1160334) then it won't have the fix.

Comment 6 Andriy Rysin 2010-08-18 03:25:03 UTC

So it this working ok after updating to 1160334 or later?

Comment 7 Silver Salonen 2010-08-18 08:06:28 UTC

Ah, yes, sry. It works now with re-built packages in openSUSE.