Description of problem: The login will always fail with lxdm and systemd Version-Release number of selected component (if applicable): lxdm-0.4.1 Searching the Internet has given this: https://bugzilla.redhat.com/show_bug.cgi?id=661600 In /etc/ lxdm/ lxdm.conf I therefore valid line: arg=/usr/bin/X -background vt1 and operation is correct. To be fully operational, it must also: - Fix the bug #2740 - Add a postscript in lxdm package: chksession-z - Validate numlock in /etc/lxdm/lxdm.conf
Created attachment 1164 [details] Modified package src.rpm I modified the package lxdm for my personal use. You cann adapt it to Mageia depo
Hi, thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC.
Keywords: (none) => Junior_job, PATCHCC: (none) => ennael1, fundawang, mageiaBlocks: (none) => 2120Depends on: (none) => 2740
Created attachment 1166 [details] Corrected package Attention, a line of patch numlock is WRONG. We must change the line as follows: numlock = 1 The correct package is attached I'm sorry
Attachment 1164 is obsolete: 0 => 1
For the record, I've now fixed bug #2740 in cauldron/mga2 and the suggested chksession in %post is no longer necessary. LXDM now seems to work fine on my system.
CC: (none) => anssi.hannula
I just did a minimal installation this morning (I choose customize desktop, in the next window I uncheck all the groups, in the next window I check "with X" and I uncheck documentation) After rebooting, I install task-xfce-minimal and lxdm. Two problems remain: - Unable to login - Numlock is not active for the login window (that is less serious) I think the proposed patch is necessary.
Can you please attach the proposed patch?
Created attachment 1179 [details] fix login and numlock Yes of course (It was contained in the package proposed)
Well, AFAICS enabling numlock always would cause problems on e.g. those laptops that have a numpad among the "normal" keys, causing login to easily fail. e.g. KDM doesn't touch numlock at all, so I wonder what breaks it for lxdm (i.e. why is it not already in the correct state, or does LXDM itself disable it). Thanks for the information that login doesn't work, I'll look into it.
(In reply to comment #8) > Well, AFAICS enabling numlock always would cause problems on e.g. those laptops > that have a numpad among the "normal" keys, causing login to easily fail. > > e.g. KDM doesn't touch numlock at all, so I wonder what breaks it for lxdm > (i.e. why is it not already in the correct state, or does LXDM itself disable > it). > > Thanks for the information that login doesn't work, I'll look into it. Good evening, I can not answer you, I have no laptop to test. If your side you can not test, you can leave open the activation of numlock.
I reproduced the issue on a minimal installation in virtualbox. I've added the arg= hunk of the patch, but selected vt8 instead of vt1. I've left the numlock state as is for now. I looked at LXDM source code and it indeed leaves it be when it is not configured, so something else should be setting it (unfortunately I don't immediately know what that should be). Closing as FIXED as the login issue has been fixed. Please reopen if that is not the case. Thanks for the report.
Status: NEW => RESOLVEDResolution: (none) => FIXED