MIA: /etc/lightdm/lightdm.conf.bunsen-orig

johnraff · 2016-12-12 08:34:18

Trying to implement xaos52's suggestion here in bunsen-configs.

Two questions, for anyone who's kind enough to give me a hand:

short question
1) Is there a file named lightdm.conf.bunsen-orig in your /etc/lightdm directory or not?
If not, is there a lightdm.conf.dpkg-new?

tricky question
2) If after reading the stuff below, you have any idea what might be going on, any thoughts would be most welcome!

bunsen-configs at the moment uses config-package-dev to divert lightdm.conf to lightdm.conf.bunsen-orig and divert lightdm-gtk-greeter.conf to lightdm-gtk-greeter.conf.bunsen-orig, while turning the original files into symlinks (eg lightdm.conf → lightdm.conf.bunsen).
This lets us add some custom configuration without having it overwritten by a package upgrade.

You can run

dpkg-divert --list | grep lightdm

to see the lightdm diverts on your system, and should see those symlinks in your /etc/lightdm directory. What I don't find, in any of my BunsenLabs systems, virtual or metal, i386 or amd64, is any *bunsen-orig files! I'm sure they were there when testing the bunsen-configs package, but all I have now is lightdm.conf.dpkg-new and lightdm-gtk-greeter.conf.dpkg-new.

This causes no issues as things are because the *.bunsen-orig files are just backups, but with the setup I want to introduce in the new bunsen-configs, which drops a config file in /usr/share/lightdm/lightdm.conf.d, then the diversion of lightdm.conf becomes unnecessary. The new package's postinst script (written automatically by config-package-dev) will remove the symlink and use dpkg-divert to remove the diversion, renaming lightdm.conf.bunsen-orig to lightdm.conf But, there's no lightdm.conf.bunsen-orig to restore! For a start, that means that the System>Login Settings menu item will have no lightdm.conf file to edit.

So in fact question (2) is two questions:
2a) Why have my *.bunsen-orig files become *.dpkg-new files (if that's what they are)? Was it dpkg during an upgrade of lightdm and lighdm-gtk-greeter, or does BL ship that way for some reason?

2b) What would be the best way to resore the original files?

apt-get install --reinstall lightdm{,-gtk-greeter}

would do it nicely, but package maintainer scripts aren't allowed to invoke apt or dpkg.
Otherwise, some logic in bunsen-configs.postinst like

[ ! -f lightdm.bunsen-orig ] && [ -f lightdm.dpkg-new ] && cp lightdm.dpkg-new lightdm.bunsen-orig || true

might work (assuming the dpkg-new file was OK) but that feels awfully hacky.

Any ideas?

Last edited by johnraff (2016-12-27 02:07:27)

martix · 2016-12-12 11:25:23

Well, I can only answer the short question: No and Yes. There is no lightdm.conf.bunsen-orig (only without "-orig") and yes, there is lightdm.conf.dpkg-new (also lightdm-gtk-greeter.conf.dpkg-new). I have "-orig" files in /etc and and /etc/dpkg/origins, but none in /etc/lightdm.
Edit: After the dpkg-divert command same result here as Sector11.

Last edited by martix (2016-12-12 13:02:16)

Sector11 · 2016-12-12 12:41:43

I have NO "-new" files.

Short 1) Yes!
Tricky 2)

 12 Dec 16 @ 09:37:22 ~
  $ dpkg-divert --list | grep lightdm
diversion of /etc/lightdm/lightdm.conf to /etc/lightdm/lightdm.conf.bunsen-orig by bunsen-configs
diversion of /etc/lightdm/lightdm-gtk-greeter.conf to /etc/lightdm/lightdm-gtk-greeter.conf.bunsen-orig by bunsen-configs
 
 12 Dec 16 @ 09:37:24 ~
  $

2a) - 2b) I'm sorry no help here. But a thought. What if someone made a custom change, would that affect anything. I recall tweaking lightdm config files a while back.

Horizon_Brave · 2016-12-12 17:24:39

Hey John, here's my short answer... I'll respond the trickier one, in a few:

I don't have the lightdm.conf.bunsen-orig but rather the lightdm.conf.dpkg-new exists.

Last edited by Horizon_Brave (2016-12-12 17:27:19)

Horizon_Brave · 2016-12-12 17:52:35

My question would also be was your lightdm.conf.bunsen-orig file removed and replaced with the dpgk-new file? or was it overwritten by something? Is there any dpkg process that appends a ".dpkg-new" extension to files? Is this behavior/ syntax seen anywhere else?

Also I notice there is a lightdm-gtk-greeter.conf.dpkg-new file as well? Is this expected to be there? Or has this appeared in a similar situation? Was there a lightdm-gtk-greeter.conf.bunsen-orig?

I wonder if it's some sort of dpkg-dev tool that gets called if a diverted package is overwritten or something?

martix · 2016-12-12 18:03:54

Horizon_Brave wrote:

".dpkg-new" Is this behavior/ syntax seen anywhere else?

On my machine I have only those two files in the lightdm folder. lightdm.conf.dpkg.new was modified 04.11.2014, the other one 21.11.2014.

johnraff · 2016-12-13 08:41:44

About *.dpkg-new, according to this, those files are created if dpkg detects a user modification to a config file which requires one of those "...has been modified..." dialogs during an upgrade. I'm wondering why the *.bunsen-orig files have disappeared. They should still be there.

Going from Sector11's report we see that some users at least still have those *.bunsen-orig files, while others, like me, have lost them.

@Sector11 I wonder if you'd mind posting a ls -l for /etc/lightdm so we can see the modification dates you have? Here's mine:

john@bunsen1:~$ ls -l /etc/lightdm
total 40
-rw-r--r-- 1 root root   40 Nov  5  2014 keys.conf
lrwxrwxrwx 1 root root   19 Feb 16  2016 lightdm.conf -> lightdm.conf.bunsen
-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
-rw-r--r-- 1 root root 6374 Nov  5  2014 lightdm.conf.dpkg-new
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.dpkg-new
-rw-r--r-- 1 root root  452 Nov  5  2014 users.conf

johnraff · 2016-12-13 09:00:40

I just booted up a BL iso in live session, and those bunsen-orig files had been replaced by dpkg-new files there too!
So it's something that comes with the iso. OTOH, the /etc/os-release files were already present and correct. (The same kind of diversion is done there, by twoion's bunsen-os-release package.)

Maybe I've made a mistake in the packaging of bunsen-configs...

martix · 2016-12-13 09:46:57

The modification dates for the dpkg-new files is exactly one day later in both cases on your machine (same with keys.conf and users.conf). The other dates are completely different here (btw I have the same files in the folder, apart from the one dpkg-old).

-rw-r--r-- 1 root root   40 Nov  4  2014 keys.conf
lrwxrwxrwx 1 root root   19 Jul 18 12:45 lightdm.conf -> lightdm.conf.bunsen
-rw-r--r-- 1 root root 6413 Jul 21 23:46 lightdm.conf.bunsen
-rw-r--r-- 1 root root 6374 Nov  4  2014 lightdm.conf.dpkg-new
lrwxrwxrwx 1 root root   31 Jul 18 12:45 lightdm-gtk-greeter.conf -> lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1499 Apr 18  2016 lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1388 Nov 21  2014 lightdm-gtk-greeter.conf.dpkg-new
-rw-r--r-- 1 root root  452 Nov  4  2014 users.conf

Last edited by martix (2016-12-15 23:19:57)

Sector11 · 2016-12-13 11:25:54

Here you go:

 13 Dec 16 @ 08:23:33 ~
  $ ls -l /etc/lightdm
total 44
-rw-r--r-- 1 root root   40 Nov  4  2014 keys.conf
lrwxrwxrwx 1 root root   19 Jul  5  2015 lightdm.conf -> lightdm.conf.bunsen
-rw-r--r-- 1 root root 6453 Apr 19  2016 lightdm.conf.bunsen
-rw-r--r-- 1 root root 6408 Apr 18  2016 lightdm.conf.bunsen.dpkg-dist
-rw-r--r-- 1 root root 6374 Nov  4  2014 lightdm.conf.bunsen-orig
lrwxrwxrwx 1 root root   31 Jul  5  2015 lightdm-gtk-greeter.conf -> lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1519 Apr 19  2016 lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1499 Apr 18  2016 lightdm-gtk-greeter.conf.bunsen.dpkg-dist
-rw-r--r-- 1 root root 1388 Nov 21  2014 lightdm-gtk-greeter.conf.bunsen-orig
-rw-r--r-- 1 root root  452 Nov  4  2014 users.conf
 
 13 Dec 16 @ 08:29:23 ~
  $

martix · 2016-12-13 18:44:17

@Sector11
keys.conf and users.conf = same date, same size here
lightdm.conf.bunsen-orig = same date, same size as lightdm.conf.dpkg-new (time: 22:01)
lightdm-gtk-greeter.conf.bunsen-orig = same date, same size as lightdm-gtk-greeter.conf.dpkg-new (18:05)

johnraff · 2016-12-14 02:21:23

So it looks as if *.dpkg-new got substituted for *.bunsen-orig for some reason.
They have almost the same 2014 date - presumably that's the date that lightdm.conf was created by the lightdm devs, and far earlier than any BL stuff.

@Sector11 so now I'm curious why you managed to escape this. How did you install your BL system?

Last edited by johnraff (2016-12-14 02:22:06)

Sector11 · 2016-12-14 02:26:40

I'm a diehard ... installed the very first Bunsen Alpha ISO release and have been updating it ever since.

Other then I tweaked lightdm to start with my username and all I have to add is my password.

Nothing else that I can think of that would affect anything here.

johnraff · 2016-12-14 02:51:49

^Maybe that's why it worked for you. The dpkg diverts brought in by bunsen-configs probably arrived after that alpha install, and the package did its job OK.

Something odd seems to have happened during the later iso building, but I've no idea why at the moment.

I've done the same tweak as you btw - 'greeter-hide-users=false', right? Do you remember if that caused dpkg to bring up the "modified" dialogue when bunsen-configs was upgraded? And did you choose to keep your modifications, or to accept the package file change, then go in and edit the file again by hand afterwards?

SMALL UPDATE: I've just tried with the newest i386_20160710 iso in a VM:

live: lightdm.conf is NOT a symlink to lightdm.conf.bunsen as it should be, but a file (with the bunsen contents though). lightdm.conf.bunsen-orig is missing, and there is a lightdm.conf.dpkg-new
(lightdm-gtk-greeter.conf is a symlink, though.

installed: Situation as reported before: symlinks are setup OK, but the backup *.bunsen-orig files are missing, replaced by *.dpkg-new files, dates same Nov. 5 & 22 2014 as in my real metal system.
'apt-get install --reinstall lightdm' brings back the missing lightdm.conf.bunsen-orig (same size and date as lightdm.conf.dpkg-new).

Last edited by johnraff (2016-12-14 03:10:03)

Sector11 · 2016-12-14 03:19:10

let me do this ... start with a repeat:

 14 Dec 16 @ 00:05:08 ~
  $ ls -l /etc/lightdm
total 44
-rw-r--r-- 1 root root   40 Nov  4  2014 keys.conf
lrwxrwxrwx 1 root root   19 Jul  5  2015 lightdm.conf -> lightdm.conf.bunsen
-rw-r--r-- 1 root root 6453 Apr 19  2016 lightdm.conf.bunsen
-rw-r--r-- 1 root root 6408 Apr 18  2016 lightdm.conf.bunsen.dpkg-dist
-rw-r--r-- 1 root root 6374 Nov  4  2014 lightdm.conf.bunsen-orig
lrwxrwxrwx 1 root root   31 Jul  5  2015 lightdm-gtk-greeter.conf -> lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1519 Apr 19  2016 lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1499 Apr 18  2016 lightdm-gtk-greeter.conf.bunsen.dpkg-dist
-rw-r--r-- 1 root root 1388 Nov 21  2014 lightdm-gtk-greeter.conf.bunsen-orig
-rw-r--r-- 1 root root  452 Nov  4  2014 users.conf
 
 14 Dec 16 @ 00:05:11 ~
  $

Copy and paste from thunar with two comments:

/etc/lightdm/keys.conf
/etc/lightdm/lightdm.conf «««« it is a simlink
/etc/lightdm/lightdm.conf.bunsen
/etc/lightdm/lightdm.conf.bunsen.dpkg-dist
/etc/lightdm/lightdm.conf.bunsen-orig
/etc/lightdm/lightdm-gtk-greeter.conf «««« it is a simlink
/etc/lightdm/lightdm-gtk-greeter.conf.bunsen
/etc/lightdm/lightdm-gtk-greeter.conf.bunsen.dpkg-dist
/etc/lightdm/lightdm-gtk-greeter.conf.bunsen-orig
/etc/lightdm/users.conf

I changed:

lightdm-gtk-greeter.conf
background=/media/5/Walls-Play/Wallpapers/BunsenLabs/BunsenLabs-bunsennoise.jpg

The next change was:

 14 Dec 16 @ 00:08:57 ~
  $ ftxt sector11 /etc/lightdm/
find text in files ie ftxt filepattern path
/etc/lightdm/lightdm.conf.bunsen
117:#        autologin-user=sector11
 
 14 Dec 16 @ 00:12:07 ~
  $

If I recall correctly once after that I was asked the usual question about keeping what I have or update to the new regarding something about lightdm. I always select "Keep" for any files that apt asks about.

Other than that, I can say honestly: I have no idea. Sorry.

martix · 2016-12-14 10:38:04

johnraff wrote:

Something odd seems to have happened during the later iso building.

Seems like it... Anyone maybe with -orig files who installed the official release (i.e. NOT alpha)?

Btw I installed the official release and changed only autologin.

tknomanzr · 2016-12-15 02:16:34

My oldest install is Oct. 5 2015 apparently, and it shows the dpkg-new as below. This is my testing laptop and I am guessing the last thing I put on it would be RC2. Sadly, I dont have anything left of the very early stuff as the other laptop is still running #! and the desktop would be a very recent BL install.

tknomanzr@test:~$ ls -l /etc/lightdm
total 32
-rw-r--r-- 1 root root   40 Nov  4  2014 keys.conf
lrwxrwxrwx 1 root root   19 Oct  5  2015 lightdm.conf -> lightdm.conf.bunsen
-rw-r--r-- 1 root root 6416 Jan 11  2016 lightdm.conf.bunsen
-rw-r--r-- 1 root root 6374 Nov  4  2014 lightdm.conf.dpkg-new
lrwxrwxrwx 1 root root   31 Oct  5  2015 lightdm-gtk-greeter.conf -> lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1526 Nov 14  2015 lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1388 Nov 21  2014 lightdm-gtk-greeter.conf.dpkg-new
-rw-r--r-- 1 root root  452 Nov  4  2014 users.conf
tknomanzr@test:~$

Head_on_a_Stick · 2016-12-15 19:54:26

Sorry for the delay but here is the output from a freshly installed system:

empty@TheLab:~$ ls -l /etc/lightdm
total 40
-rw-r--r-- 1 root root   40 Nov  4  2014 keys.conf
lrwxrwxrwx 1 root root   19 Dec 15 19:26 lightdm.conf -> lightdm.conf.bunsen
-rw-r--r-- 1 root root 6408 Apr 18  2016 lightdm.conf.bunsen
-rw-r--r-- 1 root root 6374 Nov  4  2014 lightdm.conf.bunsen-orig
lrwxrwxrwx 1 root root   31 Dec 15 19:26 lightdm-gtk-greeter.conf -> lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1499 Apr 18  2016 lightdm-gtk-greeter.conf.bunsen
-rw-r--r-- 1 root root 1388 Nov 21  2014 lightdm-gtk-greeter.conf.bunsen-orig
-rw-r--r-- 1 root root  452 Nov  4  2014 users.conf

The key difference here is that this system was installed using debootstrap(8) and the bunsen-netinstall script rather than the ISO image and it appears to be configured as expected.

johnraff · 2016-12-21 08:19:34

Thanks for the input everyone.

UPDATE:

The issue starts with the iso - that was already suggested by the results you posted, and confirmed as I watched a new live-build running and saw:
config files with suffix .dpkg-new being created as new packages were added at dpkg's unpack stage,
and then being renamed without the .dpkg-new extension at the configure stage.

This was working correctly for several packages EXCEPT the lightdm and lightdm-gtk-greeter files, and the generated live-build chroot directory reflected this, as did the system installed from the generated .iso file.

In a normal running system purging, then reinstalling lightdm, lightdm-gtk-greeter and bunsen-configs in any order, or all together sets things up as they should be, as does a simple 'apt-get install --reinstall' of the lightdm packages.

I have found an old (2008) dpkg bug that looks exactly like this (diverted conffiles not renamed properly): https://bugs.debian.org/cgi-bin/bugrepo … bug=476899
but that was fixed with dpkg version 1.15.0 and Jessie now ships with 1.17.27. Could it be that live-build's chroot is using an old version of dpkg?

Anyway, I think a patch can be added to the live-build configs to iron this out of the next BL iso.
The question is, what to do for existing users?

1) Add a check and an apt-get call to reinstall lightdm and lightdm-gtk-greeter to bl-welcome? That's clean and lets dpkg fix things, but users would have to run bl-welcome.

2) Add a fix to bunsen-configs? That would automatically fix the issue with the next package upgrade, but package maintainer scripts aren't allowed to call apt or dpkg, so it would have to be the hackier way of copying lightdm.conf.dpkg-new to lightdm.conf.bunsen-orig, trusting that dpkg-new is OK as a default config file (it probably is).

3) Just post the fix on the forum and let people do it themselves?

damo · 2016-12-21 08:42:37

Are there any problems for the user if the files have been named incorrectly, and is it mainly a question of tidying loose ends? So....

johnraff wrote:

....
3) Just post the fix on the forum and let people do it themselves

#1 2016-12-12 08:34:18

MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#2 2016-12-12 11:25:23

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#3 2016-12-12 12:41:43

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#4 2016-12-12 17:24:39

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#5 2016-12-12 17:52:35

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#6 2016-12-12 18:03:54

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#7 2016-12-13 08:41:44

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#8 2016-12-13 09:00:40

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#9 2016-12-13 09:46:57

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#10 2016-12-13 11:25:54

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#11 2016-12-13 18:44:17

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#12 2016-12-14 02:21:23

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#13 2016-12-14 02:26:40

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#14 2016-12-14 02:51:49

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#15 2016-12-14 03:19:10

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#16 2016-12-14 10:38:04

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#17 2016-12-15 02:16:34

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#18 2016-12-15 19:54:26

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#19 2016-12-21 08:19:34

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

#20 2016-12-21 08:42:37

Re: MIA: /etc/lightdm/lightdm.conf.bunsen-orig

Board footer