Home / ubuntu / Questions / 395955
Accepted
L. D. James
Asked: 2013-12-27 06:15:50 +0800 CST

How to run greeter/login script with lightdm

  • 772

Is there a workaround to run a lightdm script? The one in the docs doesn't work. Anything placed there will prevent X from working.

The script I would like to use is my KVM utility synergy. I thought for a while it was synergy that was causing the problems. However, I found that anytime there is a lightdm.conf file with anything on that line X will fail to load.

Example:

greeter-setup-script=/etc/lightdm/test.sh

The text.sh file is simply a shell command to indicate it ran:

test.sh:
#!/bin/bash
date >> /tmp/test.log

Thanks in advance for anyone who has any input, or as I mentioned a workaround so that I could have a resource that will run upon X startup before the user actually logs in.

scripts

3 Answers

  1. Best Answer

    During the past week I saw this problem many times doing my research and effort to fix it. It turns out that any entries placed in a "lightdm.conf" file for Ubuntu 13.10 will break lightdm.

    There is an entry in the lightdm.conf.d provided for this. I added my KVM script to:

    /etc/lightdm/lightdm.conf.d/50-unity-greeter.conf

    This works!

    • 3

  2. If you can't login normally because a file 50-unity-greeter.conf has been impaired, you can try this:

    • PressCtrl+F6
    • Input Login and your password
    • Type startx
    • Open any directory and go to a hardDisk and search greeter.

    When you see for example: unity-greeter_14.04.10-0ubuntu1_amd64.deb, or anything like greeter.deb, execute this file. reboot and that's all. This installer package will re-install all greeter files.

    • 1

  3. Where did you put your test.sh file? Likely that file is not in the PATH when lightdm tries to execute the script, so it can't find it. And because a session startup script fails, lightdm tries to switch back to greeter-session, which again tries to load that script and this goes on-and-on. Please use absolute path when you specify the script in lightdm.conf.

    If the above didn't solve it, then please paste the contents of the files in the /var/log/lightdm/ directory.

    • 0