Bug 15821

Summary:	Keyboardlayout not fully recognized until running any keyboard switch app (lxde, mate)
Product:	Mageia	Reporter:	Marc Krämer <mageia>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	nicolas.salguero, tarakbumba
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	MGA5TOO
Source RPM:		CVE:
Status comment:

Description Marc Krämer 2015-05-02 13:13:35 CEST

At least in LXDE after a restart of the system java applications, such as netbeans do not recognize keyboard strokes such as "Alt-Shift-O" (go to file).
This can be changed, running e.g. drakkeyboard & selecting another layout, save & reopen, reselect, save.

Or, by the desktop app of lxde, I had to deselect "system setting" and select it again & close the dialog. After this, all is fine.

Reproducible: 

Steps to Reproduce:

Comment 1 David Walser 2015-05-03 18:54:41 CEST

Can you reproduce this with other desktops, or is this only an LXDE problem?

Comment 2 Marc Krämer 2015-05-03 22:54:24 CEST

it's the same issue on mate desktop, icewm works.
I don't have more desktops installed.

Comment 3 David Walser 2015-05-04 16:19:01 CEST

If it works on IceWM then it's doubtful Java is to blame.

CC'ing LXDE and MATE maintainers.

CC: (none) => nicolas.salguero, tarakbumba
Source RPM: java-1.8.0-openjdk-1.8.0.45-6.b13.1.mga5.src.rpm => (none)

Samuel Verschelde 2015-06-06 15:16:11 CEST

Summary: Keyboardlayout not fully recognized until running any keyboard switch app => Keyboardlayout not fully recognized until running any keyboard switch app (lxde, mate)
Whiteboard: (none) => MGA5TOO

Comment 4 Nicolas Salguero 2016-03-02 11:10:10 CET

Hi,

Does resolution of bug 14622 helped for this bug too?

Best regards,

Nico.

Comment 5 Marc Krämer 2016-03-02 14:10:27 CET

no, it does not. I have this problem only on one machine, even though it disturbs me and I don't understand the differences. If I find some time, I will investigate this problem.

Comment 6 Samuel Verschelde 2016-11-01 12:43:30 CET

(In reply to M K from comment #5)
> no, it does not. I have this problem only on one machine, even though it
> disturbs me and I don't understand the differences. If I find some time, I
> will investigate this problem.

Have you been able to investigate it more? With the current information we have it will be very difficult to find a solution.

Keywords: (none) => NEEDINFO

Comment 7 Marc Krämer 2016-11-01 12:45:05 CET

thanks for the reminder, it looks like some update solved this issue - but unfortunately I don't know which. So I close this bug.

Status: NEW => RESOLVED
Resolution: (none) => INVALID