Bug 27946 - With Breeze SDDM theme, typing a wrong password is not told to user
Summary: With Breeze SDDM theme, typing a wrong password is not told to user
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: Mageia 8
Assignee: KDE maintainers
QA Contact:
Keywords: UPSTREAM
Depends on:
Blocks: 17523
  Show dependency treegraph
Reported: 2020-12-27 16:40 CET by Aurelien Oudelet
Modified: 2022-01-17 19:09 CET (History)
1 user (show)

See Also:
Source RPM: breeze-5.20.4-1.mga8.src.rpm
Status comment:


Description Aurelien Oudelet 2020-12-27 16:40:24 CET
With Breeze SDDM theme, in French locale, when user enters a wrong password, it is  no longer told to him that. Design change?

1. Use french locale (not verified all other)
2. Choose Breeze as SDDM theme.
3. Try to log on by typing a wrong password.
4. See that black dots are " selected greyed" and dialog give no feedback.

No precise feedback when typing a wrong password.
You can see a subtle freeze but user can have later the control to retype the password.

A message telling a wrong password has been typed.

Reported upstream here: https://bugs.kde.org/show_bug.cgi?id=430860
Assigning to KDE Team
Comment 1 katnatek 2022-01-17 19:09:01 CET
I have a 32 bit laptop and a 64 bit desktop with Plasma, the only differences i can think is the laptop was installed from the DVD classic as minimal Plasma Desktop and the Desktop was installed above an Xfce installation from the live image installing the full task Plasma package and manually installing plasma-workspace and plasma-framework.

while in the laptop the wrong login message is not showed, in the desktop is showed
not sure what of all packages could be the responsible.

both machines are with a other sddm theme but i can test with breeze.

What kind of information you need from both machines to see if you found how to make it work?

CC: (none) => j.alberto.vc

Note You need to log in before you can comment on or make changes to this bug.