Bug 11746

There's no need to install autologin rpm if lightdm is used. Drakboot is pretty broken currently as autologin will be disabled every time drakboot is started and even if it would work there's no autologin support for lightdm in drakboot. It's in my TODO, though.

To get autologin work properly with lightdm, you have to edit /etc/lightdm/lightdm.conf.d/50-mageia.conf by hand and add autologin=<user> under [SeatDefaults].

CC: (none) => jani.valimaa

Created attachment 4522 [details]
Experimental/WIP patch for lightdm support in drakboot

You can try with this experimental/WIP patch. Cd to /usr/lib/libDrakX and apply it with 'patch -p2' and run drakboot.

(In reply to Jani Välimaa from comment #1)
> To get autologin work properly with lightdm, you have to edit
> /etc/lightdm/lightdm.conf.d/50-mageia.conf by hand and add autologin=<user>
> under [SeatDefaults].

Currently 50-mageia.conf isn't tagged as conf file so it will be replaced with default one when lightdm is updated next time. Better to place your own .conf file with higher number to /etc/lightdm/lightdm.conf.d/. I should probably create a new .conf file for autologin when finishing autologin support for lightdm. I'll add all this to my TODO.

I tested the patch.
However, it is necessary to add to it an additional line
autologin-user-timeout=0
A value other than zero does not work according to my tries.

I found:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/902852
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682473

I think of a last thing to be planned in the modified patch:
Allow to invalidate autologin from MCC

(In reply to Georges Eckenschwiller from comment #5)
> I think of a last thing to be planned in the modified patch:
> Allow to invalidate autologin from MCC

I am sorry.
autologin-user-timeout perturbed my tests.
The invalidation by CCM works perfectly.

Wrong package

CC: (none) => thierry.vignaud
Source RPM: drakconf-12.44-1 => drakxtools

Wrong summary

Summary: autologin not working => autologin not working with lighdm

The problem remains present.

I had tested the patch of Jani Välimaa.
It worked correctly, in the installation and in the removal.

Since my tests, Jani added the file 
/etc/lightdm/lightdm.conf.d/50-mageia-xfce.conf
It is necessary to modify the patch as a consequence?

It is also necessary to add the line
autologin-user-timeout=0

I do not know who has to make what

(In reply to Georges Eckenschwiller from comment #9)
> 
> It is also necessary to add the line
> autologin-user-timeout=0
> 

Are you sure? Default value of 0 should be used if it's not explicitly set to some other value. I've never altered the default value and autologin has worked without any problems.

I had the problem during my first tries.
The search on the Internet seemed to confirm.

But I have just redone a new test.
The line is NOT necessary

(In reply to Georges Eckenschwiller from comment #9)
> 
> Since my tests, Jani added the file 
> /etc/lightdm/lightdm.conf.d/50-mageia-xfce.conf
> It is necessary to modify the patch as a consequence?
>

That file comes from xfce4-session (and probably will be moved to mageia-xfce4-config after mga4 release). It's just used to pre-select Xfce session in lightdm-gtk-greeter when booting system first time after install (see bug 11613).

We already ship /etc/lightdm/lightdm.conf.d/50-mageia.conf with lightdm for mageia specific settings,but better option would be creating a whole new file (e.x. 50-mageia-autologin.conf) for autologin purposes and ship it with lightdm with %config(noreplace) tag. This way we can alter mageia specific settings later without affecting existing autologin settings.

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

CC: (none) => magnux77

(In reply to Jani Välimaa from comment #12)
> (In reply to Georges Eckenschwiller from comment #9)
> > 
> > Since my tests, Jani added the file 
> > /etc/lightdm/lightdm.conf.d/50-mageia-xfce.conf
> > It is necessary to modify the patch as a consequence?
> >
> 
> That file comes from xfce4-session (and probably will be moved to
> mageia-xfce4-config after mga4 release). It's just used to pre-select Xfce
> session in lightdm-gtk-greeter when booting system first time after install
> (see bug 11613).
> 
> We already ship /etc/lightdm/lightdm.conf.d/50-mageia.conf with lightdm for
> mageia specific settings,but better option would be creating a whole new
> file (e.x. 50-mageia-autologin.conf) for autologin purposes and ship it with
> lightdm with %config(noreplace) tag. This way we can alter mageia specific
> settings later without affecting existing autologin settings.

do you think this can be fixed for the RC ?

CC: (none) => mageia

I can submit my changes to drakx git repo (and to lightdm).

Pushed changes to drakx git repo. However I don't know the correct procedure to create a new release so I'll leave it for someone who knows how to do it. Updated NEWS file, partially though.

Added also autologin file to lightdm, so when pushing new drakxtools also push lightdm.

Please note that autologin support isn't working 100%. Lightdm autologins to selected users last used session and not to session selected in drakboot as autologin-session setting isn't implemented yet in lightdm. Last used session is fetched via accountsservice (from file /var/lib/AccountsService/users/$USER). It might be good idea to add this info to errata.

commit 687d11bf2825b8143fc682e98dd09a189ebeeccc
Author: Thierry Vignaud <thierry.vignaud@...>
Date:   Tue Jan 7 22:00:35 2014 +0100

    perl_checker cleanups including fixing wrong variable name (mga#11746)
---
 Commit Link:
   http://gitweb.mageia.org/software/drakx/commit/?id=687d11bf2825b8143fc682e98dd09a189ebeeccc

The wrong variable name caused settings not being read correctly when starting drakboot. Thx tv for fixing it.

Is new drakxtools release planned anytime soon? I've already asked for a freeze push for lightdm.

If I do not deceive, there is only a package drakxtools to be updated?

Thanks to all.
Autologin works now perfectly with Xfce, both in the activation and in the deactivation

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