just verified, still valid with most recent cauldron.
gnome-shell-3.3.92-2.mga2

CC: (none) => herbert

should be fixed with gdm 3.4.0.1 (reason that upstream made 3.4.0.1)

I just don't know what issues I created by upgrading to 3.4.0.1...

Please reopen if it doesn't work with gdm 3.4.0.1 (obviously, restart first).

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

still not working in latest Cauldron, maybe you forgot to submit the package?

urpmi gdm
Package gdm-3.2.1.1-5.mga2.x86_64 is already installed

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

just a build error; has been resubmitted since. Please retry when it is available.

just tested with the gdm-3.4.0.1-1.mga2 package you uploaded, but the result is the same - i.e. doesn't work.

does it work for you? how did you test it?

Didn't try, just noticed the following upstream report:
https://bugzilla.gnome.org/show_bug.cgi?id=672773

as a workaround you can use drakboot for the autologin it should work (since it's the case with the live)

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

I have the same problem with lxdm.
I configure the autologin in MCC, but the new configuration is not recorded. When I restart the drakboot just after the precedent configuration, new settings are not kept.
Yves

CC: (none) => yves.brungard_mageia

(In reply to comment #9)
> I have the same problem with lxdm.
> I configure the autologin in MCC, but the new configuration is not recorded.
> When I restart the drakboot just after the precedent configuration, new
> settings are not kept.
> Yves

not the same, see bug 3715

but since there was no change in cauldron I guess that this bug of gdm is still valid

hello
my computer with Mageia2 64b do not use autologin with kdm .
with gdm, autologin is good, but that first session is wrong : for example mcc do not start in graphic mode.

I see some log :
( user fischer, autologin on )

Authentification + Messages 
---( first )boot
Jun 19 08:21:53 localhost systemd-logind[698]: New session c1 of user fischer. 
Jun 19 08:21:53 localhost systemd-logind[698]: Linked /tmp/.X11-unix/X0 to /run/user/fischer/X11-display. 
Jun 19 08:21:53 localhost kdm: :0[1007]: pam_tcb(kdm-np:session): Session opened for fischer by (uid=0) 
Jun 19 08:22:16 localhost sshd[1850]: Server listening on 0.0.0.0 port 22. 
Jun 19 08:22:19 localhost polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.106 [/usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) 
Jun 19 08:24:23 localhost polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.106, object path /org/kde/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) 
Jun 19 08:24:24 localhost kdm: :0[1007]: pam_tcb(kdm-np:session): Session closed for fischer 
Jun 19 08:24:33 localhost kdm: :0[3211]: pam_succeed_if(kdm:auth): no condition detected; module succeeded 
Jun 19 08:24:33 localhost kdm: :0[3211]: pam_succeed_if(kdm:auth): requirement "user ingroup nopasswdlogin" not met by user "fischer" 
Jun 19 08:24:34 localhost kdm: :0[3211]: pam_tcb(kdm:auth): Authentication passed for fischer from (uid=0) 
Jun 19 08:24:34 localhost systemd-logind[698]: New session 2 of user fischer. 
Jun 19 08:24:34 localhost kdm: :0[3211]: pam_tcb(kdm:session): Session opened for fischer by fischer(uid=0) 
Jun 19 08:25:07 localhost polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session2 (system bus name :1.135 [/usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) 
Jun 19 08:30:44 localhost userhelper[3876]: running '/usr/sbin/urpmi.update --update' with root privileges on behalf of 'fischer' 
Jun 19 08:30:51 localhost userhelper[3918]: running '/usr/sbin/urpmi.update Core Backports Testing' with root privileges on behalf of 'fischer' 
Jun 19 08:30:53 localhost userhelper[3932]: running '/usr/sbin/urpmi.update Nonfree Backports' with root privileges on behalf of 'fischer' 
Jun 19 08:30:54 localhost userhelper[3947]: running '/usr/sbin/urpmi.update Nonfree Backports Testing' with root privileges on behalf of 'fischer' 
Jun 19 08:30:55 localhost userhelper[3961]: running '/usr/sbin/urpmi.update Tainted Backports' with root privileges on behalf of 'fischer' 
Jun 19 08:30:57 localhost userhelper[3975]: running '/usr/sbin/urpmi.update Tainted Backports Testing' with root privileges on behalf of 'fischer' 

etc :  session 2 ( with manual password ) is good

CC: (none) => christian-maryse.fischer

(In reply to comment #11)
> hello
> my computer with Mageia2 64b do not use autologin with kdm .
> with gdm, autologin is good, but that first session is wrong : for example mcc
> do not start in graphic mode.
> 

@ hristian

This bug is about gdm auto login failing.

You're problem is with kdm, do you maybe have this issue:
https://bugs.mageia.org/show_bug.cgi?id=4197#c22

OK I have a problem with automatic login kdm, but with gdm and XDM too :

When automatic login start from gdm to kde , kde4 session seem good but  :
 Mcc do not start in graphic mode.
+ (2 minutes later ) a splash error complain to paswword: : " Le mot de passe n'est pas valable, veuillez essayer de nouveau" : that is from  consolehelper-g 
13 clicks for erase that !

With XDM to kde : autologin do not work.

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

The problem is always present, but the conditions being different, I thought of making a new report 11476

CC: (none) => paiiou

Closing as OLD. The original issue has not been confirmed since Marja asked about it. Please open a new bug report or refer to existing ones if you have issues with autologin.

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