[Solved] lightdm messed up...

Sector11 · 2017-01-24 17:02:28

With a recent update/dist-upgrade, there were changes to lightdm and my custom config file was over written.

I had it setup with a custom background and "login box", which had my user name already in place - type in my password and I'm in ...

However in trying to fix things I messed up lightdm and uninstalled it.
I now have the "stock" repo version of lightdm running.

I need help with these:
1. How do I get back the BL setup.
2. How do I set my own background.
3. Where do I add my user name (not password)

damo · 2017-01-24 17:15:37

Here are my config files...

/etc/lightdm/lightdm-gtk-greeter.conf

#
# background = Background file to use, either an image path or a color (e.g. #772953)
# theme-name = GTK+ theme to use
# icon-theme-name = Icon theme to use
# font-name = Font to use
# xft-antialias = Whether to antialias Xft fonts (true or false)
# xft-dpi = Resolution for Xft in dots per inch (e.g. 96)
# xft-hintstyle = What degree of hinting to use (none, slight, medium, or hintfull)
# xft-rgba = Type of subpixel antialiasing (none, rgb, bgr, vrgb or vbgr)
# show-indicators = semi-colon ";" separated list of allowed indicator modules. Built-in indicators include "~a11y", "~language", "~session", "~power". Unity indicators can be represented by short name (e.g. "sound", "power"), service file name, or absolute path
# show-clock (true or false)
# clock-format = strftime-format string, e.g. %H:%M
# keyboard = command to launch on-screen keyboard
# position = main window position: x y
# default-user-image = Image used as default user icon, path or #icon-name
# screensaver-timeout = Timeout (in seconds) until the screen blanks when the greeter is called as lockscreen
#
[greeter]
#background=/usr/share/images/bunsen/login/bl-login-background
theme-name=Bunsen-lightdm
icon-theme-name=Bunsen-lightdm
font-name=Sans Bold 10
xft-antialias=true
#xft-dpi=
xft-hintstyle=hintslight
xft-rgba=rgb
show-indicators=~language;~session;~power
show-clock=true
clock-format=%H:%M          %a, %b %d
#keyboard=
position=10% 35%
#screensaver-timeout=
#default-user-image=/usr/share/icons/bunsen.png

/etc/lightdm/lightdm.conf

#
# General configuration
#
# start-default-seat = True to always start one seat if none are defined in the configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the system location
# guest-account-script = Script to be run to setup guest account
# logind-load-seats = True to automatically set up multi-seat configuration from logind
# logind-check-graphical = True to on start seats that are marked as graphical by logind
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# sessions-directory = Directory to find sessions
# remote-sessions-directory = Directory to find remote sessions
# greeters-directory = Directory to find greeters
#
[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#logind-load-seats=false
#logind-check-graphical=false
#log-directory=/var/log/lightdm
#run-directory=/var/run/lightdm
#cache-directory=/var/cache/lightdm
#sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#greeters-directory=/usr/share/lightdm/greeters:/usr/share/xgreeters

#
# Seat defaults
#
# type = Seat type (xlocal, xremote)
# xdg-seat = Seat name to set pam_systemd XDG_SEAT variable and name to pass to X server
# pam-service = PAM service to use for login
# pam-autologin-service = PAM service to use for autologin
# pam-greeter-service = PAM service to use for greeters
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xserver-layout = Layout to pass to X server
# xserver-config = Config file to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xserver-share = True if the X server is shared for both greeter and session
# xserver-hostname = Hostname of X server (only for type=xremote)
# xserver-display-number = Display number of X server (only for type=xremote)
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
# unity-compositor-command = Unity compositor command to run (can also contain arguments e.g. unity-system-compositor -special-option)
# unity-compositor-timeout = Number of seconds to wait for compositor to start
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login option
# greeter-show-remote-login = True if the greeter should offer a remote login option
# user-session = Session to load for users
# allow-user-switching = True if allowed to switch users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# greeter-wrapper = Wrapper script to run greeter with
# guest-wrapper = Wrapper script to run guest sessions with
# display-setup-script = Script to run when starting a greeter session (runs as root)
# display-stopped-script = Script to run after stopping the display server (runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as root)
# session-cleanup-script = Script to run when quitting a user session (runs as root)
# autologin-guest = True to log in as guest by default
# autologin-user = User to log in with by default (overrides autologin-guest)
# autologin-user-timeout = Number of seconds to wait before loading default user
# autologin-session = Session to load for automatic login (overrides user-session)
# autologin-in-background = True if autologin session should not be immediately activated
# exit-on-failure = True if the daemon should exit if this seat fails
#
[SeatDefaults]
#type=xlocal
#xdg-seat=seat0
#pam-service=lightdm
#pam-autologin-service=lightdm-autologin
#pam-greeter-service=lightdm-greeter
#xserver-command=X
#xserver-layout=
#xserver-config=
#xserver-allow-tcp=false
#xserver-share=true
#xserver-hostname=
#xserver-display-number=
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
#unity-compositor-command=unity-system-compositor
#unity-compositor-timeout=60
#greeter-session=example-gtk-gnome
greeter-hide-users=true
#greeter-allow-guest=true
#greeter-show-manual-login=false
#greeter-show-remote-login=true
#user-session=default
#allow-user-switching=true
#allow-guest=true
#guest-session=
#session-wrapper=lightdm-session
#greeter-wrapper=
#guest-wrapper=
#display-setup-script=
#display-stopped-script=
#greeter-setup-script=
session-setup-script=/usr/lib/bunsen/configs/bl-user-setup
#session-cleanup-script=
#autologin-guest=false
autologin-user=damo
#autologin-user-timeout=0
#autologin-in-background=false
#autologin-session=UNIMPLEMENTED
#exit-on-failure=false

#
# Seat configuration
#
# Each seat must start with "Seat:".
# Uses settings from [SeatDefaults], any of these can be overriden by setting them in this section.
#
#[Seat:0]

#
# XDMCP Server configuration
#
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
#
# The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn.  Alternatively
# it can be a word and the first 7 characters are used as the key.
#
[XDMCPServer]
#enabled=false
#port=177
#key=

#
# VNC Server configuration
#
# enabled = True if VNC connections should be allowed
# command = Command to run Xvnc server with
# port = TCP/IP port to listen for connections on
# width = Width of display to use
# height = Height of display to use
# depth = Color depth of display to use
#
[VNCServer]
#enabled=false
#command=Xvnc
#port=5900
#width=1024
#height=768
#depth=8

Sector11 · 2017-01-24 18:15:54

Thanks damo, will give those a try.

/etc/lightdm/lightdm-gtk-greeter.conf did not exist.

will compare changes with /etc/lightdm/lightdm.conf and the original.
===================

Other than missing my background, and not having my user name (that's an easy fix) it's:

TWO THUMBS UP! Thank you!

ohnonot · 2017-01-25 07:37:37

Sector11 wrote:

With a recent update/dist-upgrade, there were changes to lightdm and my custom config file was over written.

for future reference, wouldn't it be better to copy e.g. lightdm-*.conf to lightdm-*-s11.conf and work on that? i don't think an update would overwrite those files.

Head_on_a_Stick · 2017-01-25 07:45:03

Sector11 wrote:

With a recent update/dist-upgrade, there were changes to lightdm and my custom config file was over written.

Did APT ask you what to do with the configuration files during the upgrade?

It should ask if you want to replace the old files or not and it will even offer the option to compare the old and new files.

Sector11 · 2017-01-25 14:39:50

ohnonot wrote:

Sector11 wrote:
With a recent update/dist-upgrade, there were changes to lightdm and my custom config file was over written.
for future reference, wouldn't it be better to copy e.g. lightdm-*.conf to lightdm-*-s11.conf and work on that? i don't think an update would overwrite those files.

Yea, like so many files I have these now have an: s11_lightdm* version - now.
And dates won't bother them.

Sector11 · 2017-01-25 14:54:29

Head_on_a_Stick wrote:

Sector11 wrote:
With a recent update/dist-upgrade, there were changes to lightdm and my custom config file was over written.
Did APT ask you what to do with the configuration files during the upgrade?
It should ask if you want to replace the old files or not and it will even offer the option to compare the old and new files.

No not even a hint that anything was happening as far as apt was concerned.
LOG:

Log started: 2017-01-24  00:43:08
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 170111 files and directories currently installed.)
Preparing to unpack .../bunsen-common_8.9-1_all.deb ...
Unpacking bunsen-common (8.9-1) over (8.8.1-2) ...
Preparing to unpack .../bunsen-configs_8.8.1-1_all.deb ...
Unpacking bunsen-configs (8.8.1-1) over (8.7.2-1) ...
Preparing to unpack .../bunsen-faenza-icon-theme_8.2-1_all.deb ...
Unpacking bunsen-faenza-icon-theme (8.2-1) over (8.1.1-3) ...
Preparing to unpack .../bunsen-images_8.7-1_all.deb ...
Unpacking bunsen-images (8.7-1) over (8.5-1) ...
Preparing to unpack .../bunsen-images-extra_8.7-1_all.deb ...
Unpacking bunsen-images-extra (8.7-1) over (8.5-1) ...
Preparing to unpack .../bunsen-pipemenus_8.10-1_all.deb ...
Unpacking bunsen-pipemenus (8.10-1) over (8.9.3-1) ...
Preparing to unpack .../bunsen-utilities_8.8-1_all.deb ...
Unpacking bunsen-utilities (8.8-1) over (8.7.1-1) ...
Preparing to unpack .../bunsen-welcome_8.14-1_all.deb ...
Unpacking bunsen-welcome (8.14-1) over (8.11.1-1) ...
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for bamfdaemon (0.2.118-1) ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for mime-support (3.58) ...
Setting up bunsen-common (8.9-1) ...
Setting up bunsen-configs (8.8.1-1) ...
Removing 'diversion of /etc/lightdm/lightdm.conf to /etc/lightdm/lightdm.conf.bunsen-orig by bunsen-configs'
Setting up bunsen-faenza-icon-theme (8.2-1) ...
Setting up bunsen-images (8.7-1) ...
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
Found Debian GNU/Linux (7.10) on /dev/sda1
Found Debian GNU/Linux (8.2) on /dev/sda6
done
Setting up bunsen-images-extra (8.7-1) ...
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
Found Debian GNU/Linux (7.10) on /dev/sda1
Found Debian GNU/Linux (8.2) on /dev/sda6
done
Setting up bunsen-pipemenus (8.10-1) ...
Setting up bunsen-utilities (8.8-1) ...
Installing new version of config file /etc/bl-exit/bl-exitrc ...
Setting up bunsen-welcome (8.14-1) ...
Log ended: 2017-01-24  00:44:08

There was no: "Keep old" type notification that is a normal default when a config file has been edited.

Obvuously:

Removing 'diversion of /etc/lightdm/lightdm.conf ... ... ...

was a hint that flew by to fast to hardly notice.

Sector11 · 2017-01-25 15:06:37

Side Q: How can I get a screenie of lightdm in action?

damo · 2017-01-25 15:31:10

Sector11 wrote:

Side Q: How can I get a screenie of lightdm in action?

Mr Google says How to capture a screenshot of the LightDM greeter screen. Not a trivial process

Or trivial if you are running it in a VM

Sector11 · 2017-01-25 16:18:21

OH didn't see that one, guess Mr Startpage didn't like it, but I did search before posting the Q.

I was hoping for a better way, and I have imagemagick so I'll try that.

I'm going with the fact he made an OOPS!

As soon as you have pressed Enter for the above command, press Ctrl+Alt+F7 to switch back to VT7.

How does on switch back to a VT we haven't been to:

As soon as you have pressed Enter for the above command, press Ctrl+Alt+F2 to switch back to VT2.

That works.

In progress!

damo · 2017-01-25 16:53:27

The graphical desktop is on VT7, showing the ldm login screen. So you switch to another tty to run the script, then back to 7 for it to take the scrot.

Sector11 · 2017-01-25 16:59:51

OK, I tried that as well, BUT, since the bash script has a "sleep 30" command in it - I cannot do a [Ctrl]+[Alt]+[anything] until the sleep is done. I end up with ~/images/ldm-greeter.png that is a 1920x1080 black .png image

{grumble grumble ....}

Sector11 · 2017-01-25 17:08:19

FREAKING TYPO ALERT! HUSTON: TYPO ALERT!

:8 I'm red faced here. :8

BUT, my lightdm is back the way I like it.

We can go through the entire Periodic Table and that wallpaper will still reflect Bunsen in a state of "OK, what next?"

=== EDIT ===
HUGE thanks damo!

Last edited by Sector11 (2017-01-25 17:13:33)

ohnonot · 2017-01-26 07:22:29

damo wrote:

Mr [censored] says How to capture a screenshot of the LightDM greeter screen. Not a trivial process

wow, that's convoluted.
iirc slim had a configurable hotkey, or even a built-in screenshot function.
maybe lightdm can also execute a configurable command on keypress?

whatever happened to slim?
8.(

damo · 2017-01-26 10:17:28

Several login managers have a scrot capability. And SLiM development stopped, so many distros dropped it IIRC. Visually, SLiM was wonderfully tweakable - I even made a slim themes manager script

Sector11 · 2017-01-26 14:40:40

As of March, 2016, SLiM seems to be abandoned. It is not fully compatible with systemd. [1]

However

As of September, 2016, GhostBSD 10.3 replaced GDM with SLiM.[2]

It was a #! thing... so sad.

johnraff · 2017-01-27 04:52:43

The recent upgrade of bunsen-configs removed the diversion of /etc/lightdm/lightdm.conf to /etc/lightdm.conf.bunsen as you noticed. (BL tweaks are now in /usr/share/lightdm/lightdm.conf.d/50_bunsen.conf) but the old /etc/lightdm.conf.bunsen is still around so you can copy any personal tweaks from there to /etc/lightdm/lightdm.conf. @Sector11 that's what you did I guess? An alternative is to add /usr/share/lightdm/lightdm.conf.d/60_user.conf and put any tweaks there. They will be overruled by an uncommented setting in /etc/lightdm/lightdm.conf (so leave it all commented), but the advantage is no dpkg messages on upgrades.

Sector11 · 2017-01-27 14:44:23

Well, my configuration dates back to the 'alpha' release of Bunsen. Not sure how things were done then but I know I tweaked lightdm to my liking, this upgrade messed with those settings.

I have no /etc/lightdm.conf.bunsen - even after the update. This is what is here:
/etc/lightdm/keys.conf
/etc/lightdm/lightdm.conf --» (recreated & tweaked with damo's files)
/etc/lightdm/lightdm.conf_orig --» everything commented out.
/etc/lightdm/lightdm-gtk-greeter.conf --» (recreated and tweaked with damo's files)
/etc/lightdm/users.conf

and in /usr/share/lightdm/ just this:

/usr/share/lightdm/lightdm.conf.d/01_debian.conf

johnraff · 2017-01-28 03:39:52

@Sector11 that's not right. Here's what I've got:

john@bunsen1:~$ ls -l /etc/lightdm
total 40
-rw-r--r-- 1 root root   40 Nov  5  2014 keys.conf
-rw-r--r-- 1 root root 6374 Nov  5  2014 lightdm.conf
-rw-r--r-- 1 root root 6409 Apr 18  2016 lightdm.conf.bunsen
-rw-r--r-- 1 root root 6416 Apr 11  2016 lightdm.conf.bunsen.dpkg-old
lrwxrwxrwx 1 root root   31 Feb 16  2016 lightdm-gtk-greeter.conf -> lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1499 Jun  1  2016 lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1388 Nov 22  2014 lightdm-gtk-greeter.conf.bunsen-orig
-rw-r--r-- 1 root root  452 Nov  5  2014 users.conf
john@bunsen1:~$ ls -l /usr/share/lightdm/lightdm.conf.d
total 8
-rw-r--r-- 1 root root 377 Nov  7  2013 01_debian.conf
-rw-r--r-- 1 root root 146 Jan 22 20:53 50_bunsen.conf

lightdm.conf.bunsen.dpkg-old is a dpkg leftover of no importance, but note the old lightdm.conf.bunsen is still around, even though it's no longer used.

How about your dpkg diverts situation?

john@bunsen1:~$ dpkg-divert --list bunsen-configs
diversion of /etc/lightdm/lightdm-gtk-greeter.conf to /etc/lightdm/lightdm-gtk-greeter.conf.bunsen-orig by bunsen-configs

Have you got the latest bunsen-configs (8.8.1-1) installed?

dpkg can sometimes be a bit mysterious in the way it works, because it puts the highest priority on keeping the user's modified conffiles under /etc, so sometimes rejects changes that packages try to make.

Sector11 · 2017-01-28 10:43:00

 28 Jan 17 @ 07:36:43 ~
  $ ls -l /etc/lightdm
total 28
-rw-r--r-- 1 root root   40 Nov  4  2014 keys.conf
-rw-r--r-- 1 root root 6419 Jan 27 11:25 lightdm.conf
-rw-r--r-- 1 root root 6374 Nov  4  2014 lightdm.conf_orig
-rw-r--r-- 1 root root 1555 Jan 26 10:06 lightdm-gtk-greeter.conf
-rw-r--r-- 1 root root  452 Nov  4  2014 users.conf
 
 28 Jan 17 @ 07:37:08 ~
  $ ls -l /usr/share/lightdm/lightdm.conf.d
total 4
-rw-r--r-- 1 root root 378 Jan 24 13:17 01_debian.conf
 
 28 Jan 17 @ 07:37:20 ~
  $ dpkg-divert --list bunsen-configs
diversion of /etc/lightdm/lightdm-gtk-greeter.conf to /etc/lightdm/lightdm-gtk-greeter.conf.bunsen-orig by bunsen-configs
 
 28 Jan 17 @ 07:37:38 ~
  $ list bunsen-configs
Alias for: apt list -a filename
Listing... Done
bunsen-configs/unknown,now 8.8.1-1 all [installed]

 
 28 Jan 17 @ 07:37:51 ~
  $

That's what I have. As you can see my lightdm files are one day older then your originals.

#1 2017-01-24 17:02:28

[Solved] lightdm messed up...

#2 2017-01-24 17:15:37

Re: [Solved] lightdm messed up...

#3 2017-01-24 18:15:54

Re: [Solved] lightdm messed up...

#4 2017-01-25 07:37:37

Re: [Solved] lightdm messed up...

#5 2017-01-25 07:45:03

Re: [Solved] lightdm messed up...

#6 2017-01-25 14:39:50

Re: [Solved] lightdm messed up...

#7 2017-01-25 14:54:29

Re: [Solved] lightdm messed up...

#8 2017-01-25 15:06:37

Re: [Solved] lightdm messed up...

#9 2017-01-25 15:31:10

Re: [Solved] lightdm messed up...

#10 2017-01-25 16:18:21

Re: [Solved] lightdm messed up...

#11 2017-01-25 16:53:27

Re: [Solved] lightdm messed up...

#12 2017-01-25 16:59:51

Re: [Solved] lightdm messed up...

#13 2017-01-25 17:08:19

Re: [Solved] lightdm messed up...

#14 2017-01-26 07:22:29

Re: [Solved] lightdm messed up...

#15 2017-01-26 10:17:28

Re: [Solved] lightdm messed up...

#16 2017-01-26 14:40:40

Re: [Solved] lightdm messed up...

#17 2017-01-27 04:52:43

Re: [Solved] lightdm messed up...

#18 2017-01-27 14:44:23

Re: [Solved] lightdm messed up...

#19 2017-01-28 03:39:52

Re: [Solved] lightdm messed up...

#20 2017-01-28 10:43:00

Re: [Solved] lightdm messed up...

Board footer