Bug 24959 - xdm display manager broken - won't allow login (except root)
Summary: xdm display manager broken - won't allow login (except root)
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: High major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 7RC
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2019-06-15 21:50 CEST by Tony Blackwell
Modified: 2020-08-26 11:39 CEST (History)
3 users (show)

See Also:
Source RPM: xdm
CVE:
Status comment:


Attachments

Description Tony Blackwell 2019-06-15 21:50:32 CEST
Description of problem:
as per title - normal user logins always fail

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


How reproducible:always


Steps to Reproduce:
1.enable Xorg display manager and try to log in

(Side-effect: autologin to a particular user also fails if Xorg display manager in use)

Work around:
Enable a different display manager - all the others work
Comment 1 Tony Blackwell 2019-06-15 22:39:50 CEST
... this in context of using xfce

Whiteboard: (none) => 7RC

Tony Blackwell 2019-06-15 22:40:54 CEST

Priority: Normal => High

Comment 2 Tony Blackwell 2019-06-15 22:54:11 CEST
fixed bug label - too early in morning for this...

Summary: xorg display manager broken - won't allow login (except root) => xdm display manager broken - won't allow login (except root)

Comment 3 Tony Blackwell 2019-06-15 23:32:04 CEST
This was on an "HP Compaq 8200 ultraslim desktop" using integrated graphics - ageing a bit now, but at least UEFI.  Problem is quite reproducible on this unit if XDM in use.  However Ben in qa has just "not confirmed' this with his xfce login succeeding.
Comment 4 Marja Van Waes 2019-06-16 13:19:44 CEST
@ Shlomi

assigning to you, since you are the registered xdm maintainer. I can't remember having seen you touch it, though. Feel free to assign back and drop maintainership if xdm isn't yours at all!

Source RPM: (none) => xdm
Assignee: bugsquad => shlomif
CC: (none) => marja11

Comment 5 Shlomi Fish 2019-06-16 14:06:03 CEST
(In reply to Marja Van Waes from comment #4)
> @ Shlomi
> 
> assigning to you, since you are the registered xdm maintainer. I can't
> remember having seen you touch it, though. Feel free to assign back and drop
> maintainership if xdm isn't yours at all!

Done. I think I adopted xdm because I felt sorry for it, but I'm not using it.

Assignee: shlomif => bugsquad

Comment 6 Martin Whitaker 2019-06-16 16:09:49 CEST
@Tony, does your normal user have a password? xdm doesn't work with a blank password.

CC: (none) => mageia

Comment 7 Tony Blackwell 2019-06-16 22:04:19 CEST
Normal (and all) users have passwords.
XDM for me accepts name entry, but in the split-second of clicking the enter key after putting in the password, it re-spawns the blank name entry field.  Note that this is for me: Ben apparently gets sessions up for 90 sec before they die - hence his bug 24961
Comment 8 Martin Whitaker 2019-06-17 09:38:46 CEST
Please install xdm-1.1.12-3, which will fix the reset after ~90 seconds. Then create a new user and try to log in as that user from xdm. If that fails, use Ctrl-Alt-F3 to switch to a tty, log in as that user, and save a copy of ~/.xsession-errors, /var/log/Xorg.0.log, and the journal.log created by running (as root)

  journalctl -b > journal.log

and after you've switched back to a working DM, attach those three files here.
Marja Van Waes 2019-06-19 12:08:34 CEST

Keywords: (none) => NEEDINFO

Comment 9 Aurelien Oudelet 2020-08-19 22:05:58 CEST
Does this bug is still valid?

Version in this bug report is xdm-1.1.12-3.mga7 and currently is 1.1.12-4.mga8.

Closing it on 26-08-2020 if no answers.

Status: NEW => UNCONFIRMED
CC: (none) => ouaurelien
Ever confirmed: 1 => 0

Comment 10 Aurelien Oudelet 2020-08-26 11:39:11 CEST
Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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


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