Bug 25133

Ricard
You need to give us some specific information, since the problem you describe would effect everybody - but clearly does not. You have said this is an installer problem - but is it? There is no login during installation or upgrade except to define it. You say that the password 'can be observed', but it is normally hidden.
Please say:
* Is the problem during, or after installation (reboot)?
* What ISO you are trying to install, or installed Mageia from.
* What display manager is involved (SDDM, GDM, LightDM, LXDM).
* Does this happen at login to the session from the DM?
* Does it happen when unlocking the screensaver?
* What keyboard layout you have, and is it correctly defined? [Mageia control centre - Hardware - Keyboard]

CC: (none) => lewyssmith
Whiteboard: (none) => NEEDINFO

See also
 https://bugs.mageia.org/show_bug.cgi?id=25168
in case it is the same problem.

* Is the problem during, or after installation (reboot)?
	-occurs after installation, at each login or exit of the screen saver

* What ISO you are trying to install, or installed Mageia from.
	-iso mageia 7

* What display manager is involved (SDDM, GDM, LightDM, LXDM).
	Sddm 0.18.1-3.mga7
		-not installed
			GDM,  LightDM,  LXDM
* Does this happen at login to the session from the DM?
	- yes

* Does it happen when unlocking the screensaver?
	-yes

* What keyboard layout you have, and is it correctly defined? [Mageia control centre - Hardware â Keyboard]
	- yes everything in spanish
		Hardware â Keyboard: generic | pc 104 keys
						number block without changes

without problems in the programs kmail, libreoffice, kwrite, etc.


--------

Regarding the previous comment:

	I think so, it would be necessary to know if you put any "_" in the passwords

I have already tried several keyboard configurations, local configuration all in Spanish. There is no error in konsole or tty3-5. DM only.

Today I had a moment to update kernel and several more. Now I have not had any problem setting the password. I have activated the screen saver several times and have not had any problems. For now I will wait a couple of days and if everything works fine close the notice

(In reply to Ricard Alfe from comment #5)
> Today I had a moment to update kernel and several more. Now I have not had
> any problem setting the password. I have activated the screen saver several
> times and have not had any problems. For now I will wait a couple of days
> and if everything works fine close the notice
Thank you for this encouraging news, from an unexpected direction!
If you are able to close the bug in a few days, please use WORKSFORME as the RESOLVED category.
TIA

ok, close bug

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

*** Bug 25168 has been marked as a duplicate of this bug. ***

CC: (none) => gerard.muratorio

There is clearly a problem experienced by both MURATORIO bug 25168
and Ricard here, who also replied on the other bug
So I am re-opening this bug and marking the other as a duplicate (it can be re-opened if necessary).

Muratorio (32-bit) started with LightDM-Xfce, with automatic login, and describes the problem in:
 https://bugs.mageia.org/show_bug.cgi?id=25168#c9
C11 of that bug says that with SDDM-Plasma the problem has not yet shown.
> the keyboard is  a AT Translated Set 2   [language?]
Yet Ricard (Spanish k/b) reported this bug using SDDM, and no mention of automatic login. Despite comments 5 (23 July) and 7 (25 July), 
> To me the error has reappeared (27 July)
 https://bugs.mageia.org/show_bug.cgi?id=25168#c15
We need to think how to persue this.

Summary: login error by automatic correction => login password error
Whiteboard: NEEDINFO => (none)
Resolution: WORKSFORME => (none)
Status: RESOLVED => REOPENED

nobody has permission to autologin, the sessions are all with login, as well as screen savers. MSEC is configured as fileserver with analysis and accurate verifications. Keyboard mark hp sdm4700p, all the premises in Spanish, spelling correction settings activated in Spanish. There is no error in tty only in sddm. The mistake with Muratorio I think is different. Mine only affects if "_" lowercase for some reason becomes "_" uppercase giving password error

(In reply to Lewis Smith from comment #9)
> There is clearly a problem experienced by both MURATORIO bug 25168
> and Ricard here, who also replied on the other bug
> So I am re-opening this bug and marking the other as a duplicate (it can be
> re-opened if necessary).

If KDE team does not reassign this report to BugSquad, then the other report should be reopened.
> 
<snip>
> Yet Ricard (Spanish k/b) reported this bug using SDDM, and no mention of
> automatic login. Despite comments 5 (23 July) and 7 (25 July), 
> > To me the error has reappeared (27 July)
>  https://bugs.mageia.org/show_bug.cgi?id=25168#c15
> We need to think how to persue this.

(In reply to Ricard Alfe from comment #10)
> nobody has permission to autologin, the sessions are all with login, as well
> as screen savers. MSEC is configured as fileserver with analysis and
> accurate verifications. Keyboard mark hp sdm4700p, all the premises in
> Spanish, spelling correction settings activated in Spanish. There is no
> error in tty only in sddm. The mistake with Muratorio I think is different.
> Mine only affects if "_" lowercase for some reason becomes "_" uppercase
> giving password error

CC'ing KDE team.

Ricard, just in case there is some useful info in it, could you please attach log.txt that is the result of running, as root:
   
  journalctl -a --since="YYYY-MM-DD hh:mm" --until="YYYY-MM-DD hh:mm" > log.txt

and adjust the since and until times to before and right after you last hit this bug.

For the "before" time, maybe starting with the line in which "kernel: Linux version" appears, would be best

Source RPM: xdm 1.1.12-3.mga7 ???? => sddm-0.18.1-3.mga7
CC: (none) => marja11
Summary: login password error => SDDM sometimes replaces _a in passwords with _A
Assignee: bugsquad => kde

My log after cleaning firewall or msec errors with file names is 76 megabytes. Can I upload it to the network?

journalctl -a --since="2019-07-01 00:00" --until="2019-08-04 11:45" > log.txt

You can compress the file using the command xz; just enter:

 xz log.txt

and it will replace it with the compressed log.txt.xz , attach that.

CC: (none) => fri

ok. 2.2 M
forgives. how do i upload

I have seen where to upload it but it is limited to 1M, I divide it into 3 parts?

(In reply to Ricard Alfe from comment #12)
> My log after cleaning firewall or msec errors with file names is 76
> megabytes. Can I upload it to the network?
> 
> journalctl -a --since="2019-07-01 00:00" --until="2019-08-04 11:45" > log.txt

I wasn't clear enough, sorry :-(

For the --since time, please use the last time when the line which contains "kernel: Linux version" appears before the until time.

Sorry, I saw that the log had the data for 2 months. I cut it, I upload it

Created attachment 11236 [details]
log systemctl

The same comment in the two bugs concerned.

@Ricard     re bug 25133
@ MURATORIO re bug 25168
Please can you install the package 'ibus-gtk' and report back.

Without any known explanation, this has resolved obscure bugs (for example bug 25707, and others elsewhere) with a Spanish element.

*** Bug 25168 has been marked as a duplicate of this bug. ***

Did proposal fix provided above (by Lewis Comment#19) work some?

Does bug still affect you?

CC: (none) => ouaurelien
Keywords: (none) => NEEDINFO

Hi,
This bug is against our Installer DrakX.

@Developers/Packagers: Feel free to reassign to correct person.
Also, if you are working on this, please change the status of this bug to "Assigned".
Feel free to close this if already fixed.

@All
Thanks making DrakX even better.

Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

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