Siduction Forum

As the subject say, after du the computer boots in to runlevel 3.

32 bit, "Desktop: Xfce 4.10.2 (Gtk 2.24.18), Distro: siduction 13.1.0 Firestarter - xfce - (201305202236)"

Same here.

System: Kernel: 3.16-2.towo.3-siduction-amd64 x86_64 (64 bit) Desktop: KDE 4.14.1
           Distro: siduction 11.1 One Step Beyond - kde - (201112302141)

As I understand from irc, towo says that on this d-u you have to say yes to the new lightdm.conf  I choose no as usual.

I have solved my issue with the help of towo on irc.

In  /etc/lightdm you will find the new lightdm.conf as (if I remember right) lightdm.conf.dpkg.dist, remove or rename the old lightdm.conf and rename the new one (lightdm.conf.dpkg.dist) to lightdm.conf and reboot. This worked for me.

Quote from: vilde on 2014/09/19, 12:08:15
...towo says that on this d-u you have to say yes to the new lightdm.conf ...

Has worked here. One should make this warning prominent, as the savfe way is known as the opposite.

greets
ayla

That's odd, I said my usual no as lightdm updated, and, was able to boot fine.  On the laptop and the desktop.  Both are 64 bit. 

maybe we talk about the greeter conf?

Quote from: melmarker on 2014/09/20, 00:15:23
maybe we talk about the greeter conf?

No, it's lightdm.conf

The only prompt I got during the update was for lightdm.conf.  It's strange how it affects some and not others though.

GoinEasy9 - one should have a look at the diff - and maybe provide the diff. Saying so - i have build some isos with our configuration an upgrade some systems the good oldfashioned way - it works :D

So - without a proof, that our settings are bad we will change absolutely nothing at the moment.

If one encounter problems - please send us your lightdm.conf and the backup - it should be lightdm.conf.dpkg-old or so

Today I did a d-u on one of my own computers, I sad no to update the lightdm.conf but that didn't trigger the problem I had yesterday. The computer where the problem occurred was an older install (firestarter) than this computer 13.2.1 December) and the lightdm.conf was probably the original from the installation, never updated, I don't have access to that computer at home so I can't provide the files.

I've had the same issue... Thank you vilde for posting the solution!
As I set i3 as default I chose to keep the old conf. But that was the only change I remember...
The files, if anyone is interested:
http://paste.siduction.org/20140920141903 (http://paste.siduction.org/20140920141903) = old lightdm.conf
http://paste.siduction.org/20140920141936 (http://paste.siduction.org/20140920141936)  = new lightdm.conf
http://paste.siduction.org/20140920143007 (http://paste.siduction.org/20140920143007) = diff