Bug 1054646

Summary:	Sigil does not follow keyboard layout switching
Product:	[Fedora] Fedora	Reporter:	Nicholas Kudriavtsev <nkudriavtsev>
Component:	sigil	Assignee:	Hans de Goede <hdegoede>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	20	CC:	dan, hdegoede
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-22 14:20:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nicholas Kudriavtsev 2014-01-17 08:02:02 UTC

Description of problem: Sigil does not follow keyboard layout switching


Version-Release number of selected component (if applicable): 0.7.4-1.fc20


How reproducible:
Start Sigil

Steps to Reproduce:
1. Type something in current keyboard layout (1) in Sigil's window.
2. Switch keyboard layout (gnome-shell shows new layout (2) in the indicator).
3. Type something in layout 2.

Actual results:
Sigil inputs characters from layout 1

Expected results:
Sigil shall input characters from layout 2

Additional info:
I have builded Sigil 0.7.4 in Fedora 19 with the same keyboard bug.

Comment 1 Dan Horák 2014-05-01 16:42:37 UTC

maybe this is related, I see it when starting sigil from command line

[dan@eagle ~]$ sigil
Error:    cz:75:19: illegal escape sequence in string literal
Error:    cz:75:19: syntax error
Error:    Couldn't process include statement for 'cz(qwerty)'
Error:    Abandoning symbols file "(unnamed)"
Error:    Failed to compile xkb_symbols
Error:    Failed to compile keymap
Warning: Qt: Failed to compile a keymap

and as a result I can't type anything

Comment 2 Nicholas Kudriavtsev 2014-05-07 13:29:31 UTC

I have no output in console.

Comment 3 Nicholas Kudriavtsev 2014-07-20 12:28:36 UTC

Qt5 5.3.1-4 fixed the error.

Comment 4 Dan Horák 2014-07-22 14:20:13 UTC

Thanks for testing, was a bug in qt5 instead.