| Summary: | sddm-kcm - password enters in wrong (invisible) user's field when logging in with maui theme | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Barry Jackson <zen25000> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | eatdirt, mageia, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | sddm-kcm | CVE: | |
| Status comment: | |||
| Bug Depends on: | |||
| Bug Blocks: | 17523 | ||
|
Description
Barry Jackson
2016-07-29 12:36:56 CEST
Barry Jackson
2016-07-29 12:37:29 CEST
Summary:
sddm-kcm - password enters in wrong (invisible) user's field when logging in with sddm-kcm maui theme =>
sddm-kcm - password enters in wrong (invisible) user's field when logging in with maui theme
Barry Jackson
2016-07-29 12:55:53 CEST
Severity:
normal =>
major
Marja Van Waes
2016-07-30 19:55:46 CEST
CC:
(none) =>
marja11
Samuel Verschelde
2016-08-25 16:24:58 CEST
Assignee:
mageia =>
kde is it still valid with plasma 5.8.6 ? CC:
(none) =>
mageia I don't know as the Maui theme is not offered now by the systemsettings tool (under startup/shutdown -> sddm) What is annoying is that the default Mageia background is not offered either, so having changed to one of the three offered, it is not possible to return to the Mageia default. Any ideas? Under /etc/sddm/themes/ I have: breeze, elarun, maldives, maui, mga-coffee, mga-maui and numix yet only breeze, elarun and maldives are available in systemsettings -> startup/shutdown -> login screen. This seems really broken. Upping to critical. Severity:
major =>
critical I have managed to get back to the default sddm login screen by manually editing /etc/sddm.conf to point to mga-coffee, so tomorrow I will edit it again to test maui and mga-maui for this original bug. for mga-coffee: file:///usr/share/sddm-kcm/main.qml:36:5: QML Image: Cannot open: file:///usr/share/sddm/themes/mga-coffee/maldives.jpg i think this is why it is not visible. so the problem is with your themes and not with sddm_kcm Severity:
critical =>
normal Where do you see that message? I have mga-coffee working fine now it's in /etc/sddm.conf with: kcmshell5 kcm_sddm Right - there is a mention of maldives.jpg in /usr/share/sddm/themes/mga-coffee/metadata.desktop [SddmGreeterTheme] Name=Maldives Description=Maldives Theme Author=Abdurrahman AVCI Copyright=(c) 2013, Abdurrahman AVCI License=CC-BY-SA Type=sddm-theme Version=0.1 Website=https://github.com/sddm/sddm #Screenshot=maldives.jpg Screenshot=default.jpg MainScript=Main.qml ConfigFile=theme.conf TranslationsDirectory=translations Email=abdurrahmanavci@gmail.com Theme-Id=maldives Theme-API=2.0 This looks wrong to be in mga-coffee cc_ing eatdirt CC:
(none) =>
eatdirt Oops sorry - ignore the edit Original had only Screenshot=maldives.jpg I am on it, I completely omitted the .desktop file at first, I am fixing it. Should be fixed in incoming sddm. Thanks Chris, That now works and I can select between breeze, elarun, maldives and mga-coffee themes in systemsettings and they all work. However, in /usr/share/sddm/themes/ we still have maui, mga-maui and numix themes which appear to be in various states of breakage and do not show in systemsettings. This bug was really about an issue in the maui theme which is currently not selectable. If those that do not work are now obsolete, should they not be removed from the package and git, or if they are not obsolete can they be fixed? Good, I'll have a look to the other themes then! thanks! Barry, are you sure that maui, mga-maui are not coming from some older install? I don't have them, that's my /usr/share/sddm/themes: ls /usr/share/sddm/themes/ breeze/ elarun/ maldives/ mga-coffee/ and urpmq -l sddm | grep themes does not show them neither. /usr/share/sddm/themes /usr/share/sddm/themes/elarun /usr/share/sddm/themes/elarun/Main.qml /usr/share/sddm/themes/elarun/README /usr/share/sddm/themes/elarun/angle-down.png /usr/share/sddm/themes/elarun/elarun.jpg /usr/share/sddm/themes/elarun/images /usr/share/sddm/themes/elarun/images/background.png /usr/share/sddm/themes/elarun/images/lock.png /usr/share/sddm/themes/elarun/images/login_active.png /usr/share/sddm/themes/elarun/images/login_normal.png /usr/share/sddm/themes/elarun/images/rectangle.png /usr/share/sddm/themes/elarun/images/rectangle_overlay.png /usr/share/sddm/themes/elarun/images/session_normal.png /usr/share/sddm/themes/elarun/images/system_hibernate.png /usr/share/sddm/themes/elarun/images/system_reboot.png /usr/share/sddm/themes/elarun/images/system_shutdown.png /usr/share/sddm/themes/elarun/images/system_suspend.png /usr/share/sddm/themes/elarun/images/system_switch_user.png /usr/share/sddm/themes/elarun/images/user_icon.png /usr/share/sddm/themes/elarun/metadata.desktop /usr/share/sddm/themes/elarun/theme.conf /usr/share/sddm/themes/maldives /usr/share/sddm/themes/maldives/LICENSE /usr/share/sddm/themes/maldives/Main.qml /usr/share/sddm/themes/maldives/README /usr/share/sddm/themes/maldives/angle-down.png /usr/share/sddm/themes/maldives/background.jpg /usr/share/sddm/themes/maldives/maldives.jpg /usr/share/sddm/themes/maldives/metadata.desktop /usr/share/sddm/themes/maldives/rectangle.png /usr/share/sddm/themes/maldives/theme.conf /usr/share/sddm/themes/mga-coffee /usr/share/sddm/themes/mga-coffee/Main.qml /usr/share/sddm/themes/mga-coffee/README /usr/share/sddm/themes/mga-coffee/angle-down.png /usr/share/sddm/themes/mga-coffee/metadata.desktop /usr/share/sddm/themes/mga-coffee/mgacoffee.png /usr/share/sddm/themes/mga-coffee/mgangle.png /usr/share/sddm/themes/mga-coffee/theme.conf (In reply to Chris Denice from comment #14) > Barry, are you sure that maui, mga-maui are not coming from some older > install? > I just checked in a clean VM upgrade from 5.1 and I see the same as you, so they must be relics from a bygone age on my main system. This bug was from last July! I did a urpmi --replacepkgs --replacefiles sddm the other day which I expected to put it back to current default, but it would not remove stuff it hadn't installed of course. OK in that case lets close this now as invalid :) Status:
NEW =>
RESOLVED |