In KDE 4 and KDE applications, the Belgian keyboard layout does not have "dead keys". So it is impossible to type characters that need to be accented by way of the umlaut or circonflex characters, or to form characters that have some other punctuation marks on top of them - e.g. a tilde. This problems does not exist in LXDE - I have not tested any other desktop environments.
CC: (none) => stryder
We have KDE 4.7 in cauldron, so in which version is this bug ?
You did check the advanced option in keyboard configuration kcm to see if there no option here for that purpose ?
CC: (none) => balcaen.john
I'm thinking about configuring the compose touche.
For example here with the compose key set to the left win touch the combination of windows left key+(AltGr+key2)+n give me the ñ
The compose key is set to to the right hand Win-key here (as the left Win-key is set up as a Meta key), but it too has no effect in KDE. It does work normally in a character mode login console and in LXDE. I have even added an explicit keyboard section in xorg.conf, with the right hand Win-key defined as the compose key, but again, all to no avail. In KDE, that is. Like I said, everything works in LXDE. Together with bug #3317 and #3318, this leads me to suspect that there is something very wrong with the KDE packages as they are set up in Mageia. LXDE behaves normally, and I also don't see the same KDE problems in Sabayon. I can only guess at the source of the problems, but it could be that there is some file somewhere with incorrect ownership and/or SUID bit, or some badness in dbus.
Well i'm not able to reproduce either bug #3317 (on both arch) , neither #3318 (on both arch)or this one. To configure the win-key you should better use systemsettings keybord ( kcmshell4 kcm_keyboard in command line )instead of adding a configuration in xorg.conf (this is how i set up it since i don't have a right winkey on my keyboard)
I tried it via System Settings first, but it didn't work. That's why I resorted to adding a section to xorg.conf, but that too does not work. Like KDE has a mind of its own. :-/
@ Aragorn Do you still have the same issue in current cauldron?
Keywords: (none) => NEEDINFOCC: (none) => marja11
Marja, this is a Mageia 1 bug, not a Cauldron bug. Please see my comments on bug #3317 as for the reason of this confusion.
(In reply to comment #9) > Marja, this is a Mageia 1 bug, not a Cauldron bug. Please see my comments on > bug #3317 as for the reason of this confusion. @ Aragorn No problem :) Changing version to 1 Can you please try whether the problem exists, too, when logging in as xguest? @ John Is kdebase4-workspace the correct package?
Version: Cauldron => 1Source RPM: (none) => kdebase4-workspace-2:4.6.5-1.4.mga1
@Marja: I have not installed the xguest package here because of security concerns. I don't want any blank password accounts on this system, and to the best of my knowledge the xguest can only log in via a display manager, i.e. a graphical login screen. I am not using a displaymanager - and prefer not to - but instead I log in the old UNIX way, i.e. via a character mode virtual console, and I start the X server manually via "startx". The problem does however seem limited to KDE. I have tried starting an XFCE session, and everything works normally there. I have also had this problem across multiple installations of Mageia 1, so it was not an isolated thing as a result of some particular selection I've made during installation.
(In reply to comment #0) > In KDE 4 and KDE applications, the Belgian keyboard layout does not have "dead > keys". So it is impossible to type characters that need to be accented by way > of the umlaut or circonflex characters, or to form characters that have some > other punctuation marks on top of them - e.g. a tilde. > > This problems does not exist in LXDE - I have not tested any other desktop > environments. (In reply to comment #11) > I am not using a displaymanager - and prefer not to - but instead I log in the > old UNIX way, i.e. via a character mode virtual console, and I start the X > server manually via "startx". > > The problem does however seem limited to KDE. I have tried starting an XFCE > session, and everything works normally there. I have also had this problem > across multiple installations of Mageia 1, so it was not an isolated thing as a > result of some particular selection I've made during installation. @ AL13N AFAIK, you have a Belgian keyboard. Can you reproduce this bug? If so, does it make any difference how X is started
Keywords: NEEDINFO => (none)CC: (none) => alien
yes, actually; i noticed it only with the ~ key though, i don't use " or ^ much, as i tend to leave those accented chars out, (unless formal things) i did notice with the ~ key, because i usually need to add a space for it give the homedir sign; otherwise i can make nice ñ ... oh wait, i don't have this in mageia 1 ; only in latest cauldron. i can confirm that this is only on KDE, not on tty...
(In reply to comment #13) > yes, actually; i noticed it only with the ~ key though, i don't use " or ^ > much, as i tend to leave those accented chars out, (unless formal things) > > i did notice with the ~ key, because i usually need to add a space for it give > the homedir sign; otherwise i can make nice ñ ... > > oh wait, i don't have this in mageia 1 ; only in latest cauldron. i can confirm > that this is only on KDE, not on tty... Thanks, AL13N assigning to John, who probably won't be able to do anything without a Belgian keyboard :( I didn't look upstream, because I'm sure John already looked there before commenting on this bug :)
Assignee: bugsquad => balcaen.john
perhaps, i or the original user can be of assistance in tracking down this issue. i have personally no idea how KDE is doing keyboard stuff that is different than tty; if i knew more about this, i could try and find out
Just to be sure did you also try by adding a belgium layout in systemsettings (for the keyboard setup) ?
no, I just installed like I always did, should I? tell me what I can do to test this...
Well since it seems kde does not choose directly the correct keyboard layout so if when choosing the be layout it's ok we can start thinking how to correctly setup this one by default.
@John: Yes, I have tried to set the correct keyboard layout both with drakkeyboard (or whatever it's called) and with the KDE System Settings.
i just thought of something... at home i have a PS2 keyb on cauldron (via VM) bugged at home i have a PS2 keyb on mga1 (via VM) OK at work i have a usb keyb on mga1 (physical) OK @Aragorn, what do you have? @mikala: is there a reason KDE doesn't use the system keyboard configs? is that configurable?
@ALI3N: This is a Cherry G81-3000 BE keyboard, connected via a PS/2 port. As reported, there are no layout problems in PCLinuxOS and Sabayon, and there are no problems either in Mageia 1 with LXDE. It does appear to be specific to the KDE 4 implementation in Mageia 1. Additionally, Mageia 1 runs on the bare metal here, not in a virtual machine. I am currently using it as my production workstation.
maybe it's rather the type of keyboard or something... like PS/2 keyb in any case, my keyboard is some kind of logitec access keyb ... in any case, i'm intersted in why/how KDE actually does the keyb thing...
CC: (none) => bert.ram.aerts
I also have a Belgian keyboard: on a Dell Inspiron 1720 Notebook. With Mageia 1 x86_64 on internal harddisk. And also Mageia 2 x86_64 cauldron on USB harddisk. In LibreOffice ö´`~ can not be entered, I simply can not enter these special characters. That's why I added another keyboard layout in the KDE config tool. Belgian with the last option of no dead keys. This allows me to enter ´`~ but still I can not compose characters tlike ö.
(In reply to comment #23) > I also have a Belgian keyboard: on a Dell Inspiron 1720 Notebook. > With Mageia 1 x86_64 on internal harddisk. > And also Mageia 2 x86_64 cauldron on USB harddisk. > > In LibreOffice ö´`~ can not be entered, I simply can not enter these special > characters. That's why I added another keyboard layout in the KDE config tool. > Belgian with the last option of no dead keys. This allows me to enter ´`~ but > still I can not compose characters tlike ö. But when you make the characters with accents in a console and crtl+shift+c and ctrl+v them to LibreOffice, they get pasted correctly? Does it make any difference which font you use?
eh no, afaik we can't make them in a console, we can make them in the tty. however, how can you copy paste from tty??? that's not really a usable workaround. it would gladly have this fixed, i don't know what exactly caused the regression, but it can be irritating. the dead keys should be usable. i wonder if germans or skandinavians has this problem as well?
(In reply to comment #25) > eh no, afaik we can't make them in a console, we can make them in the tty. > however, how can you copy paste from tty??? that's not really a usable > workaround. I had noticed that with the default font in LibreOffice, when I type a umlaut + o, the dots are too far on the right, but in the Konsole they are put neatly where they should be, but then when I copy and paste the letter into LO, the dots are too far to the right again. Picking another font fixed that. Somehow I mixed that up with what was written in this report, sorry. > > it would gladly have this fixed, i don't know what exactly caused the > regression, but it can be irritating. the dead keys should be usable. > > i wonder if germans or skandinavians has this problem as well? I have a Dutch keyboard with dead keys, and using them I can make letters like ô,ä,é,ì,ç,ñÂ, and after playing with xmodmap Ä and ÂÄ are possible, too. I'm writing this using Mageia 1, 64 bits. Do you see any dead keys in the list when you do: xmodmap -pke a dead umlaut should be visible as dead_diaerisis, ~ as dead_tilde, ` as dead_grave and the thing above á as dead_acute
(In reply to comment #23) > I also have a Belgian keyboard: on a Dell Inspiron 1720 Notebook. > With Mageia 1 x86_64 on internal harddisk. > And also Mageia 2 x86_64 cauldron on USB harddisk. > > In LibreOffice ö´`~ can not be entered, I simply can not enter these special > characters. That's why I added another keyboard layout in the KDE config tool. > Belgian with the last option of no dead keys. This allows me to enter ´`~ but > still I can not compose characters tlike ö. The only tools that work correctly are XEmacs and this Firefox. Here I can type ö ó ò ~ which are letters combined with dead keys. LibreOffice, Emacs, terminal, Mathematica all don't function as it should. For me this has never worked, not in Mageia 1 and not in Cauldron which is almost Mageia 2. This is not a regression.
There are similar reports in KDE bugzilla https://bugs.kde.org/show_bug.cgi?id=216098 https://bugs.kde.org/show_bug.cgi?id=290571 https://bugs.kde.org/show_bug.cgi?id=106538 Does it make a difference which language/locale settings you use?
(In reply to comment #28) Thanks for the link > https://bugs.kde.org/show_bug.cgi?id=216098 It says: "I found a better solution (although not perfect, I think): I changed my locale to US English and country United States. $ locale LANG=en_US.UTF-8 This way dead keys work and all my programs are in English." > Does it make a difference which language/locale settings you use? Yes, dead keys work when in "Mageia Control Center / System / Manage localisation for your system" I change {country Belgium, language English} to {country United Kingdom, language English}. This gives [bert@Dell1720Mageia2 ~]$ locale LANG=en_GB.UTF-8 And now all applications that I tried support dead keys: I can compose ë! As it is the Mageia locale setting, I think the problem with dead keys and en_BE as locale needs to be solved at Mageia side, not KDE... Anyway, I now have a workaround and have still the Belgian settings as in KDE / Common Appearance and Behaviour / Locale the Country is Belgium.
Great to hear that, Bert :) Out of curiousness: did you have one or more of the Belgian languages installed as extra language(s) on your system, or not?
(In reply to comment #30) > Great to hear that, Bert :) > > Out of curiousness: did you have one or more of the Belgian languages installed > as extra language(s) on your system, or not? No I do not have Dutch, French or German installed. I'm used to English as language to interact with computers ;-)
I tried to do exactly the same in Mageia 1 x86_64. When in "Mageia Control Center / System / Manage localisation for your system" I change {country Belgium, language English} to {country United Kingdom, language English}. This still gives [bert@Dell1720Mageia2 ~]$ locale LANG=en_BE.UTF-8 iso the expected en_GB. Why is the same trick of Mageia Cauldron not working in Mageia 1 ???
(In reply to comment #32) > I tried to do exactly the same in Mageia 1 x86_64. > > When in "Mageia Control Center / System / Manage > localisation for your system" I change {country Belgium, language English} to > {country United Kingdom, language English}. This still gives > [bert@Dell1720Mageia2 ~]$ locale > LANG=en_BE.UTF-8 > iso the expected en_GB. > > Why is the same trick of Mageia Cauldron not working in Mageia 1 ??? Did you choose Europe-GB English when you installed Mageia 1 and not US English instead?
(In reply to comment #33) > Did you choose Europe-GB English when you installed Mageia 1 and not US English > instead? I have following languages installed in Mageia 1 x86_64: [bert@Dell1720Mageia1 ~]$ rpm -aq | grep locale locales-fr-2.12.1-3.mga1 locales-en-2.12.1-3.mga1 locales-br-2.12.1-3.mga1 locales-nl-2.12.1-3.mga1 locales-2.12.1-3.mga1 Even when I select language Dutch and country Belgium, I still get [bert@Dell1720Mageia1 ~]$ locale LANG=en_BE.UTF-8 How can it be that Mageia Control Center can not change this setting?
(In reply to comment #34) > (In reply to comment #33) > > > Did you choose Europe-GB English when you installed Mageia 1 and not US English > > instead? > > I have following languages installed in Mageia 1 x86_64: > > [bert@Dell1720Mageia1 ~]$ rpm -aq | grep locale > locales-fr-2.12.1-3.mga1 > locales-en-2.12.1-3.mga1 > locales-br-2.12.1-3.mga1 > locales-nl-2.12.1-3.mga1 > locales-2.12.1-3.mga1 > > Even when I select language Dutch and country Belgium, I still get > [bert@Dell1720Mageia1 ~]$ locale > LANG=en_BE.UTF-8 > > How can it be that Mageia Control Center can not change this setting? Did you already install those languages when you installed Mageia 1? If not: I've had issues that have led to me installing all the languages the owner of a system might need, including at least the language of its keyboard and the language of the country he's in, when installing Mageia. If you didn't already do this while installing, you might want to Upgrade your Mageia 1 install with the Mageia 1 DVD, pick a Belgian language language in the first language choice screen and tick the boxes for the extra ones in the Multiple languages screen. cc'ing tv
CC: (none) => thierry.vignaud
(In reply to comment #34) > How can it be that Mageia Control Center can not change this setting? Mageia 1 x86_64 I used localedrake directly from the command line not as root but as normal user. This time selection of {English, United Kingdom} was successfull. (Previous times I used "Mageia Control Center / System / Manage localisation for your system" which is as root and it never succeeded.) Conclusion: Belgian Azerty keyboard works well with {English, United Kingdom} locale en_GB but not as {English, Belgium} locale en_BE. Can this Mageia issue be solved?
(In reply to comment #36) > (In reply to comment #34) > > > How can it be that Mageia Control Center can not change this setting? > > Mageia 1 x86_64 > I used localedrake directly from the command line not as root but as normal > user. This time selection of {English, United Kingdom} was successfull. > > (Previous times I used "Mageia Control Center / System / Manage > localisation for your system" which is as root and it never succeeded.) > > Conclusion: Belgian Azerty keyboard works well with {English, United Kingdom} > locale en_GB but not as {English, Belgium} locale en_BE. > > Can this Mageia issue be solved? I can confirm that this method works. I now also have dead keys working again on my Belgian AZERTY keyboard. ;-)
that's all very nice, but that means we can't select Belgium nor a belgian language... so, i'm thinking that the belgian keyboard tables or belgium locales are broken?
(In reply to comment #38) > that's all very nice, but that means we can't select Belgium nor a belgian > language... > > so, i'm thinking that the belgian keyboard tables or belgium locales are > broken? I'm not sure. If you hadn't already selected Belgium and Belgian language while installing Mageia, can you then please try with the method Anssi mentioned here: https://bugs.mageia.org/show_bug.cgi?id=1063#c18 > The manual way to switch to a new locale and internationalization right now is > to install locales-xx, then enable it in draklocale, and then reinstall needed > packages to get the new translation files, by using e.g. Eric Piel's script: > https://bzattachment.mandriva.com/attachment.cgi?id=8509 I think those "translation files" include more than just translations
Keywords: (none) => NEEDINFO
i wonder if this could be similar to bug 3791
(In reply to comment #40) > i wonder if this could be similar to bug 3791 As Christian answered there: no it isn't. Had you selected both Belgium and a Belgian language while installing Mageia?
yes
(In reply to comment #42) > yes :( And you already had the CRDA issue too. Maybe you should consider moving to another country :þ
Keywords: NEEDINFO => (none)
:(
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Everything works now since I have adopted the same method as AL13N, i.e. I have set my locale to GB. Have not felt a need to change to anything else. ;-)
i didn't use that method. i just don't have any dead keys now :-(... does anyone have a fix instead of a workaround? perhaps we need to ask neoclust or mikala or such and put them in CC and request for a new idea?
(In reply to comment #47) > i didn't use that method. i just don't have any dead keys now :-(... > > does anyone have a fix instead of a workaround? > > perhaps we need to ask neoclust or mikala or such and put them in CC and > request for a new idea? This bug is already assigned to mikala :þ cc'ing neoclust :)
CC: (none) => nicolas.lecureuil
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX
Same issue in Mageia 2 so bug reopened.
Status: RESOLVED => REOPENEDVersion: 1 => 2Resolution: WONTFIX => (none)
reproduced in Mageia 3 RC. firefox: dead keys work libreoffice: dead keys don't work at all konsole: dead keys aren't dead: they show ^ and ` etc... and don't wait for the next key.
(changing version as it seems still valid on mga3, eol of mga2)
Version: 2 => 3Source RPM: kdebase4-workspace-2:4.6.5-1.4.mga1 => kdebase4-workspace
mga2 isn't EOL... is it?
In Mageia 3 x86_64 I have no problems with dead keys of Belgian keyboard. [bert@Dell7720Mageia3 ~]$ locale LANG=en_BE.UTF-8 And in all applications dead keys work fine.
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: REOPENED => RESOLVEDResolution: (none) => OLD