lxdm -- The LXDE Login Manager

[ghostbunny]

Hi AS,

i looked in this scripts, maybe i didn't understand all but i think the place where the start of the things in the different runlevels is defined is /etc/rc.d/rc.

But i also have to say i have the same problem (50% cpu load for X) when i try to use xdm or slim and here it is also solved by removing the K09dm file from rc3.d.

so probably xdm and slim have the same side effect.

The condition to start lxdm, is that it should be defined in /etc/sysconfig/desktop as DISPLAYMANAGER=lxdm, alternatively, if DISPLAYMANAGER is not defined, it look at DESKTOP, allowing for the same values.

this is already done when i choose lxdm in pcc.

And lxdm was starting before without the change in /etc/rc.d/rc3.d but in this case i got a high cpu load for X

But here now the 32bit rpm and srpm:
links removed until i have a solution

The 32bit rpm don't removes the entry in /etc/rc3.d it renames it to BK09dm.bak.
On deinstallation it will get his original name back.

[AS]

The 32bit rpm don't removes the entry in /etc/rc3.d it renames it to BK09dm.bak.
On deinstallation it will get his original name back.

Hi ghostbunny,

may be I've not explained myself very well: dm is the service script responsible for starting and stopping the display manager, and it should do that even when using lxdm. The real script is placed in /etc/rc.d/init.d, symlinks exists in /etc/init.d;
additionally a symlink exists in /etc/rc3.d if the service is enabled in runlevel 3.

All the above means that if you want to disable a service at runlevel 3, all you need to do is remove the symbolic link in /etc/rc3.d, and you don't need to do it manually, because there are utilities made to do it:

Code: [Select]

chkconfig --level 3 dm off   # disable dm at runlevel 3
service dm stop               # turn off (kill) dm service

If the above need to be fixed, this should be done in the corresponding package, which is initscripts, otherwise your changes will be overwritten upon initscripts reinstall/updates.

How is it started lxdm if not from /etc/rc.d/init.d/dm ?

Guess you are meeting problems because you start lxdm, while the script /etc/rc.d/init.d/dm is trying to start lxdm or another dm (may be a non existent dm ? ) at the same time ... 

About runlevel 3, a short recap of run levels standards:
0: shutdown / power off
1: single user
2: multiuser without network services
3: multiuser with network services
4: unused
5: multiuser with newtork services and X server running
6: reboot

So, you are correct when you say that dm should not be enabled at runlevel 3, still should not be an issue for itself, other than running the display manager when it is not supposed to run.

Hope the above clarify a bit my previous answer.

AS

[ghostbunny]

Ok, thanks for clarification.

If the above need to be fixed, this should be done in the corresponding package, which is initscripts, otherwise your changes will be overwritten upon initscripts reinstall/updates.

Related to my post which started with wwwoooooohhhhhoooooo is it possible that we get problems with other app if we disable the dm script on rlvl (runlevel) 3?

Maybe one question: What is the order for entering the rlvls on a normal start?

How is it started lxdm if not from /etc/rc.d/init.d/dm ?

lxdm is also started by this script, i don't know why but it is started on rlvl 3 like every other DM i tested if i don't do the change in rc3.d. Seems like if i use gdm and X that they does not care about this but in combination with lxdm/xdm/slim it seems to conflict with X. with the change the other DMs are launched on rlvl 4 or 5 i'm not sure but it should be 5 everything is working well.

When i searched the web related to this i found things like X is starting to fast for lxdm on rlvl 3 but in this case the guys in the articles modded /etc/inittab but i wasn't able to translate the hack on the pclos inittab so i tryed it directly by moving the dm script from rlvl 3.

[ghostbunny]

Little not to LXDM Config i placed in the menu.

I think this is designed for the *ubunties which use sudo. if you start this as normal user everything is grey out and you can't do anything except closing the app. If you start it as root you can do some simple modifications but root is still the only user for setting up a autologin.

If you want to have a autologin for a normal user you have to modify /etc/lxdm/lxdm.conf manualy with a editor of your choice.

[daniel]

get your package not working under 64 bit... Will later see what's wrong, because i get only a black screen, and with my previous the default login mask, but no start of lxde session 

[ghostbunny]

i think the lxdm-greeter stuff isnt found.

take a look in /etc/lxdm/lxdm.conf

Code: [Select]

## greeter used to welcome the user
greeter=/usr/share/lxdm/lxdm-greeter-gtk

check whether this thing is there

[daniel]

it is there...

[ghostbunny]

sh*t

i will try my second system where i didn't made the changes linke on my other system.

[ghostbunny]

gggrrr it wont work on my clear system. have to find out the changes i made on the other system


edit:

edit i found several mistakes.

/etc/lxdm/Xsession

change everying with xprofile to profile we dont have xprofile

but with this changes i got two terminals after login and the keyboard does not work and i cant change the Session only Default is available i think that's the real problem on 32bit


i need a break i will try the next changes tomorrow

[daniel]

Translate -DE

@ Ghostbunny

Sage mal hast Du schon irgendwelche Fortschritte erlangt?