Judicator
Posts: 11
Joined: Sun Nov 27, 2011 10:55 pm

Can't Run Lightdm

Tue Mar 01, 2016 7:41 pm

When I try to run lightdm I get this error message:

** (lightdm:3547): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files

If I try to automatically run lightdm at start via raspi-config it keeps asking me name and password, basically it accepts them and after a couple of seconds of black screen it asks me again.

I have a PI model B, overclock doesn't matter.
Raspbian Jessie Lite
Version: February 2016
Release date: 2016-02-26
Kernel version: 4.1

What should I do?

User avatar
DougieLawson
Posts: 41962
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: Can't Run Lightdm

Tue Mar 01, 2016 8:37 pm

Ditch Jessie Lite in favour of full-fat Jessie. Work on removing things from Jessie rather than adding things to Jessie Lite.
Languages using left-hand whitespace for syntax are ridiculous

DMs sent on Twitter/LinkedIn will be answered next month.
Fake doctors - are all on my foes list.

The use of crystal balls and mind reading is prohibited.

Judicator
Posts: 11
Joined: Sun Nov 27, 2011 10:55 pm

Re: Can't Run Lightdm

Wed Mar 02, 2016 8:32 am

Thanks for your answer DougieLawson, I chose Lite because Full won't fit on my 4GB (3.8GB real) SD.
I'll buy a new one if there's no other way to fix this.

User avatar
DougieLawson
Posts: 41962
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: Can't Run Lightdm

Wed Mar 02, 2016 2:35 pm

The minimum size is 8GB now, unless you really want to run entirely headless.
Languages using left-hand whitespace for syntax are ridiculous

DMs sent on Twitter/LinkedIn will be answered next month.
Fake doctors - are all on my foes list.

The use of crystal balls and mind reading is prohibited.

Return to “Troubleshooting”