Hello, if I click on the MCC icon, a dialog pops-up to ask me the superuser password. My superuser password contains the character "ô". It is not take into account by the password dialog. I mean that if I type ô, it counts as 2 characters (2 points appear), probably because it is considered as "^o" And so my password is not recognised. Could you fix it? Reproducible: Steps to Reproduce:
Hardware: i586 => All
what for polkit agent are you using (as this popup depends on it/desktop) ?
I do not know which polkit agent I am using. If I type rpm -qa | grep polkit, I get lib64mate-polkit1_0-1.6.1-2.mga4 lib64polkit1_0-0.112-2.mga4 polkit-desktop-policy-0.112-2.mga4 lib64polkit-qt-core-1_1-0.103.0-3.mga4 polkit-kde-agent-1-0.99.0-6.mga4 polkit-0.112-2.mga4 lib64polkit-qt-agent-1_1-0.103.0-3.mga4 mate-polkit-1.6.1-2.mga4 In addition, I use KDE SC.
CC: (none) => balcaen.john, lmenut, mageiaAssignee: bugsquad => mageiaSummary: password dialog does not manage complexe characters => password dialog does not manage complexe characters (kde)
(In reply to Manuel Hiebel from comment #1) > what for polkit agent are you using (as this popup depends on it/desktop) ? Bug summary indicates that Olivier uses KDE when this issue occurs. Right? If it is that' s a problem with either polkit-kde-agent or directly polkit. Since, mate-polkit has "OnlyShowIn=MATE;XFCE;LXDE;OPENBOX;Old;" array in /etc/xdg/autostart/polkit-mate-authentication-agent-1.desktop file and it shouldn't run on KDE. Olivier, would you mind to run ps ax | polkit from commandline and paste results here?
CC: (none) => tarakbumba
I guess you meant ps ax | grep polkit If so, I got 1356 ? Ssl 0:00 /usr/lib/polkit-1/polkitd --no-debug 3069 ? Sl 0:00 /usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1 10674 pts/1 D+ 0:00 grep --color polkit
I sought on bugs.kde.org for this bug and I did not find any bug which looks like to this issue. So I open a new one at https://bugs.kde.org/show_bug.cgi?id=343794 Let us see what the KDE's devs say.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you 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. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Version: 4 => CauldronWhiteboard: (none) => MGA5TOO
Assignee: mageia => kde
CC: lmenut => (none)
Please reopen if this bug is still valid on current cauldron
Status: NEW => RESOLVEDCC: (none) => mageiaResolution: (none) => FIXED