Bug 16733 - Can only login to 1st-defined user. All other users get "Login failed"
Summary: Can only login to 1st-defined user. All other users get "Login failed"
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-10 18:33 CEST by Maurice Batey
Modified: 2017-07-13 21:09 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Maurice Batey 2015-09-10 18:33:16 CEST
Description of problem:

  After booting full Cauldron-updated 64-bit KDE Mageia-5,
cannot login to any user except first-defined.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

1. Define a 2nd user

2. Reboot

3. Try to login to 2nd user: get "Login failed"

N.B. Same problem if define 3rd user; can still only login to 1st-defined user.
       Also, if login as user #1, then try to switch to login to another user, it will only login user #1 again.


Reproducible: 

Steps to Reproduce:
Maurice Batey 2015-09-10 18:33:32 CEST

CC: (none) => maurice

Comment 1 Rémi Verschelde 2015-09-10 18:43:20 CEST
This could be related to bug 16668; it would be interested to check if it happens with other DM than sddm.

@Maurice: Note that you don't need to add yourself in CC, as bug reporter you will always be notified of all bug activity.
Comment 2 Maurice Batey 2015-09-10 18:50:05 CEST
> you don't need to add yourself in CC

  Noted! :-)
Comment 3 Maurice Batey 2015-09-10 18:59:43 CEST
Tried login on IceWm, but same login problem.
Samuel Verschelde 2015-09-11 09:23:19 CEST

Assignee: bugsquad => mageia

Comment 4 Rémi Verschelde 2016-01-19 11:26:35 CET
Does this issue still occur in current cauldron?

Blocks: (none) => 17523

Comment 5 Maurice Batey 2016-01-19 19:09:42 CET
Still same problem, I'm afraid!

(1) After adding new user, note that 'Status' at end of entry says "Expired".

(2) Reboot and try login new user:  "Login failed".
Comment 6 Rémi Verschelde 2016-01-19 19:16:28 CET
Thanks, it seems not to be related to Plasma or SDDM then. If I understand correctly, when you create a new user in the MCC it is shown as "Expired" directly? If so the bug is in the MCC or libuser.

CC: (none) => thierry.vignaud
Blocks: 17523 => (none)
Assignee: mageia => pkg-bugs
Summary: At Plasma login, can only login to 1st-defined user. All other users get "Login failed" => Can only login to 1st-defined user. All other users get "Login failed"

Comment 7 Maurice Batey 2016-01-19 19:20:32 CET
Issue still valid, I'm afraid:

[mab@netbook ~]$ kmail
kmail: symbol lookup error: /lib64/libKF5AkonadiCore.so.5: undefined symbol: _ZTIN7Akonadi8Protocol7CommandE
[mab@netbook ~]$
Comment 8 Rémi Verschelde 2016-01-19 19:23:11 CET
(In reply to Maurice Batey from comment #7)
> Issue still valid, I'm afraid:
> 
> [mab@netbook ~]$ kmail
> kmail: symbol lookup error: /lib64/libKF5AkonadiCore.so.5: undefined symbol:
> _ZTIN7Akonadi8Protocol7CommandE
> [mab@netbook ~]$

I believe you wanted to comment on bug 16726 :)
Comment 9 Marja Van Waes 2016-01-19 19:45:57 CET
this might be the same as bug 17504

CC: (none) => marja11

Comment 10 Maurice Batey 2016-01-19 20:42:02 CET
Looks like it...
Comment 11 Maurice Batey 2016-01-19 20:47:50 CET
> I believe you wanted to comment on bug 16726 :)

  Oops, yes! Will copy it over there.
Comment 12 Maurice Batey 2016-01-19 20:50:02 CET
 > Will copy it over there.

  Mm - I see t hat that's already been done. Thank you. :-)
Comment 13 Maurice Batey 2016-07-10 12:48:40 CEST
Same problem with Mageia-6-sta1 Plasma 5.7.0.

Login to 2nd user still fails; entry marked "Expired'.
Comment 14 Maurice Batey 2016-08-17 22:29:39 CEST
With new install of Aug.13.2016 Mga6-RC, a second user can now be added and can login (once the 'Locked' account status is cleared in MCC/System/Users).

Looks as though this one can be closed - if it is normal to find the new user account Locked.
Comment 15 Rémi Verschelde 2016-08-29 11:08:14 CEST
(In reply to Maurice Batey from comment #14) 
> Looks as though this one can be closed - if it is normal to find the new
> user account Locked.

That doesn't sound normal to me, but maybe it's already tracked in another bug report?
Comment 16 Alan Secker 2016-11-13 14:58:14 CET
Today, after downloading the latest updates, I created a new user via the mcc.
As usual I could not access it upon rebooting.
Booting in using the 1st user I ran:

# passwd -f <new-user>

assigning the same password as before. On rebooting I could gain access as the new user.

As an aside, I couldn't see /etc/shadow.locked at any time. HTH.

CC: (none) => alan

Comment 17 Maurice Batey 2017-07-13 19:09:57 CEST
No longer a problem!
Comment 18 Rémi Verschelde 2017-07-13 21:09:04 CEST
Closing.

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


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