goodtft / LCD-show

2.4" 2.8"3.2" 3.5" 5.0" 7.0" TFT LCD driver for the Raspberry PI 3B+/A/A+/B/B+/PI2/ PI3/ZERO/ZERO W
2.29k stars 781 forks source link

reedesktop.Accounts issue ? #151

Open Toshibass opened 5 years ago

Toshibass commented 5 years ago

Installed as per instructions, but I get screen with just a flashing curser the log says following continually :

Jul 6 18:41:44 raspberrypi systemd[1]: Started Light Display Manager. Jul 6 18:41:47 raspberrypi systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Jul 6 18:41:47 raspberrypi systemd[1]: lightdm.service: Unit entered failed state. Jul 6 18:41:47 raspberrypi systemd[1]: lightdm.service: Failed with result 'exit-code'. Jul 6 18:41:47 raspberrypi systemd[1]: lightdm.service: Service hold-off time over, scheduling restart. Jul 6 18:41:47 raspberrypi systemd[1]: Stopped Light Display Manager. Jul 6 18:41:47 raspberrypi systemd[1]: Starting Light Display Manager... Jul 6 18:41:48 raspberrypi lightdm[1162]: 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

Any idea how to fix this ?

Toshibass commented 5 years ago

This is tested on Zero and pi3b+ both fresh install of latest raspbian, same result... I tried sudo apt install accountsservice which gets rid of the message only, but result is same.

Jul 7 11:15:10 raspberrypi systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Jul 7 11:15:10 raspberrypi systemd[1]: lightdm.service: Unit entered failed state. Jul 7 11:15:10 raspberrypi systemd[1]: lightdm.service: Failed with result 'exit-code'. Jul 7 11:15:10 raspberrypi systemd[1]: lightdm.service: Service hold-off time over, scheduling restart. Jul 7 11:15:10 raspberrypi systemd[1]: Stopped Light Display Manager. Jul 7 11:15:10 raspberrypi systemd[1]: Starting Light Display Manager... Jul 7 11:15:11 raspberrypi systemd[1]: Started Light Display Manager.

result of : pi@raspberrypi:~/LCD-show $ sudo lightdm –-test-mode --debug [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.01s] DEBUG: Starting Light Display Manager 1.18.3, UID=0 PID=793 [+0.02s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.02s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.02s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.02s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.03s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.03s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.05s] DEBUG: Registered seat module xlocal [+0.05s] DEBUG: Registered seat module xremote [+0.06s] DEBUG: Registered seat module unity [+0.56s] DEBUG: Monitoring logind for seats [+0.58s] DEBUG: New seat added from logind: seat0 [+0.58s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.59s] DEBUG: Seat seat0: Starting [+0.59s] DEBUG: Seat seat0: Creating user session [+0.62s] DEBUG: Loading users from org.freedesktop.Accounts [+0.63s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+0.67s] DEBUG: Seat seat0: Creating display server of type x [+0.73s] DEBUG: Using VT 7 [+0.74s] DEBUG: Seat seat0: Starting local X display on VT 7 [+0.74s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log [+0.75s] DEBUG: DisplayServer x-1: Writing X server authority to /var/run/lightdm/root/:1 [+0.75s] DEBUG: DisplayServer x-1: Launching X Server [+0.76s] DEBUG: Launching process 798: /usr/bin/X :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch [+0.79s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1 [+0.79s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.81s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?

do you have appropriate permissions?...... I don't know, how do I fix this issue.