Bug 10089

Summary:	Dead keys won't work for pt-BR layout because of XMODIFIERS env var
Product:	Mageia	Reporter:	Ivan Filgueiras <ivan.reche>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	High	CC:	fundawang, mageia, olav
Version:	3
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	gnome-settings-daemon	CVE:
Status comment:

Description Ivan Filgueiras 2013-05-14 03:31:10 CEST

Using Mageia 3, the dead keys won't work if XMODIFIERS is set to "@im=none", which seems to be the default value in my system's configuration. If I unset this env var, everything works normally. Affected applications from a brief test included GNU Emacs and Skype. This is a grave issue for Brazillians users.

I don't know what information would be useful to add, so I'll wait for someone to request it.

Reproducible: 

Steps to Reproduce:

Comment 1 Ivan Filgueiras 2013-05-14 17:26:12 CEST

This seems to be exactly the same issue as this one:

https://bugzilla.redhat.com/show_bug.cgi?id=917130

I'd love to provide a patch but I don't know which would be a correct solution.

Comment 2 Ivan Filgueiras 2013-05-15 01:03:18 CEST

I've increased the priority as this might drive away brazillian users.

Priority: Normal => High

Comment 3 Manuel Hiebel 2013-05-24 23:26:35 CEST

seems something resolved for gnome 3.8

CC: (none) => fundawang, mageia, olav
Source RPM: (none) => gnome-settings-daemon

Comment 4 Ivan Filgueiras 2013-05-25 00:32:54 CEST

But will Gnome 3.8 make it to Mageia 3 or will we need to backport something?

Comment 5 Marja Van Waes 2015-03-31 16:03:37 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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