Bug 3715 - With lxdm MCC does not set autologin
Summary: With lxdm MCC does not set autologin
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: Junior_job, PATCH
: 5446 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-12-12 08:59 CET by Georges Eckenschwiller
Modified: 2012-09-09 14:56 CEST (History)
5 users (show)

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


Attachments
Fix autologin for lxdm and slim (495 bytes, patch)
2012-05-27 08:38 CEST, Derek Jennings
Details | Diff

Description Georges Eckenschwiller 2011-12-12 08:59:15 CET
I use lxdm as display manager and Xfce as desktop.

With lxdm MCC does not set autologin:
- I open MCC
- I select "Démarrage"
- I select "Configurer la connexion automatique"
- I check "Connexion automatique" and select user and desktop.

With lxdm, we must uncomment and modify the line" autologin="
Thierry Vignaud 2011-12-12 10:13:51 CET

CC: (none) => thierry.vignaud
Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => drakxtools

Comment 1 Georges Eckenschwiller 2011-12-14 18:21:47 CET
The config file is /etc/lxdm/lxdm.conf
Georges Eckenschwiller 2012-02-04 17:38:09 CET

Depends on: (none) => 4406

Thierry Vignaud 2012-02-08 18:17:32 CET

Depends on: 4406 => (none)

Comment 2 Marja Van Waes 2012-05-12 10:06:05 CEST
Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher.

Is this one still valid for Mageia 2 rc?

If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
If it wasn't assigned correctly, please assign back to Bug Squad and explain.
Comment 3 Georges Eckenschwiller 2012-05-12 11:38:36 CEST
The problem is still actual
Comment 4 Marja Van Waes 2012-05-26 13:05:27 CEST
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

Manuel Hiebel 2012-05-27 02:06:23 CEST

Keywords: NEEDINFO => (none)

Comment 5 Manuel Hiebel 2012-05-27 02:06:38 CEST
*** Bug 5446 has been marked as a duplicate of this bug. ***

CC: (none) => scsijon

Comment 6 Derek Jennings 2012-05-27 08:38:52 CEST
Created attachment 2382 [details]
Fix autologin for lxdm and slim

Currently if the DM is lxde or slim autologin will be disabled and the configuration file /etc/sysconfig/autologin removed. 

The attached patch permits autologin for lxdm or slim.

It works for me, I hope it works for you too.
Manuel Hiebel 2012-05-27 13:42:13 CEST

Keywords: (none) => Junior_job, PATCH

Comment 7 Georges Eckenschwiller 2012-06-08 11:29:58 CEST
I just tested modification of the file any.pm.
For me, it works also.
However, the method presents a very big inconvenience.
I can not stop or restart the computer from the panel. Only the "Logout" is proposed.

It is therefore preferable to modify the file lxdm.conf (or find another solution)

Keywords: Junior_job, PATCH => (none)

Comment 8 papoteur 2012-06-10 08:39:50 CEST
I had the problem with lxdm and for starting lxde.
paiou has proposed this solution, which works for me :
Replace
eq 'xdm')
with
=~ /xdm|lxdm|slim/ )
in lines 718 et 738 of file /usr/lib/libDrakX/any.pm (under root).
After that, installation of the package autologin is suggested and done.

CC: (none) => yves.brungard_mageia

Comment 9 papoteur 2012-06-16 22:25:23 CEST
There is still another issue.
The option "Halt" and "Reboot" are not available with the halt button.
Comment 10 Marja Van Waes 2012-07-06 15:06:01 CEST
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
Comment 11 Georges Eckenschwiller 2012-07-06 20:44:33 CEST
(In reply to comment #10)
I did not see update which corrects this problem.
Manuel Hiebel 2012-07-07 14:16:04 CEST

Keywords: (none) => Junior_job, PATCH

Comment 12 jon scsi 2012-07-09 08:35:11 CEST
(In reply to comment #10)
Will give it a go and see if it works for me, hopefully it's fixed properly for mageia 3.
Comment 13 Rubén Fernández 2012-07-24 16:03:06 CEST
papoteur, your troubles are caused by bug 5855, you all take a look at it. Everybody who autologins with LXDM will encounter it.

CC: (none) => ruben33en-mandriva

Rubén Fernández 2012-07-24 16:03:35 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=5855

Comment 14 Thierry Vignaud 2012-07-26 10:09:53 CEST
Just commited into Drakx (for Cauldron for now), but slight different:
    if (member($autologin->{dm}, qw(lxdm slim xdm))) {

Thankx for the fix!
Comment 15 Thomas Backlund 2012-09-09 14:19:47 CEST
Update pushed for mga2:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0188

CC: (none) => tmb

Comment 16 Manuel Hiebel 2012-09-09 14:56:00 CEST
seems it's ok in cauldron too, closing

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


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