lightdm failing to load

Raspberry Pi 2

lightdm failing to load

Postby nickarchpi2 » Mon Aug 01, 2016 2:03 pm

I have a fresh install of arch ARM on a Rpi2. Configured all the basics, sudo, locale, timezone etc. Installed and configured SMB and rtorrent all working fine.

I want to also run Kodi but I need to keep SMB running in the background and rtorrent. I use ssh to access the command line and rtorrent runs in GNU screen.

So, I believe I need a window manager to run Kodi. I have installed lightdm and lightdm-gtk-greeter. I've read the Archwiki on the Arch Linux site regarding setting up lightdm but when I enable lightdm and reboot it fails to load. I can still access the system by ssh to disable lightdm.

Desktops I have installed are LXDE.desktop openbox.desktop openbox-kde.desktop. I have also installed gnome-themes-standard.

Can anyone help me out with this. Here are some logs after running lightdm --test-mode --debug, systemctl status lightdm.service and journalctl -xe.

Code: Select all
$ lightdm --test-mode --debug
[+0.00s] DEBUG: Logging to /home/nick/.cache/lightdm/log/lightdm.log
[+0.01s] DEBUG: Starting Light Display Manager 1.18.2, UID=1001 PID=376
[+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Running in user mode
[+0.01s] DEBUG: Registered seat module xlocal
[+0.01s] DEBUG: Registered seat module xremote
[+0.01s] DEBUG: Registered seat module unity
[+0.04s] DEBUG: Monitoring logind for seats
[+0.04s] DEBUG: New seat added from logind: seat0
[+0.04s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.04s] DEBUG: Seat seat0: Starting
[+0.04s] DEBUG: Seat seat0: Creating greeter session
[+0.05s] 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
[+0.05s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.05s] DEBUG: User alarm added
[+0.05s] DEBUG: User elliot added
[+0.05s] DEBUG: User nick added
[+0.06s] DEBUG: Seat seat0: Creating display server of type x
[+0.07s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.07s] DEBUG: Seat seat0: Starting local X display
[+0.07s] DEBUG: DisplayServer x-0: Logging to /home/nick/.cache/lightdm/log/x-0.log
[+0.07s] DEBUG: DisplayServer x-0: Writing X server authority to /run/lightdm/root/:0
[+0.07s] WARNING: Error reading existing Xauthority: Failed to open file '/run/lightdm/root/:0': Permission denied
[+0.07s] WARNING: DisplayServer x-0: Failed to write authority: Failed to open X authority /run/lightdm/root/:0: Permission denied
[+0.07s] DEBUG: DisplayServer x-0: Launching X Server
[+0.07s] DEBUG: Launching process 383: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp
[+0.08s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.08s] WARNING: Could not enumerate user data directory /var/lib/lightdm-data: Error opening directory '/var/lib/lightdm-data': Permission denied
[+0.09s] DEBUG: Process 383 exited with return value 1
[+0.09s] DEBUG: DisplayServer x-0: X server stopped
[+0.09s] DEBUG: DisplayServer x-0: Removing X server authority /run/lightdm/root/:0
[+0.10s] DEBUG: Seat seat0: Display server stopped
[+0.10s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+0.10s] DEBUG: Seat seat0: Stopping
[+0.10s] DEBUG: Seat seat0: Stopping session
[+0.10s] DEBUG: Seat seat0: Session stopped
[+0.10s] DEBUG: Seat seat0: Stopped
[+0.10s] DEBUG: Required seat has stopped
[+0.10s] DEBUG: Stopping display manager
[+0.10s] DEBUG: Display manager stopped
[+0.10s] DEBUG: Stopping daemon
[+0.10s] WARNING: invalid unclassed pointer in cast to 'Logger'
[+0.10s] CRITICAL: logger_logv: assertion 'IS_LOGGER (self)' failed
[+0.10s] CRITICAL: g_dbus_connection_unregister_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
[+0.10s] DEBUG: Exiting with return value 1


Code: Select all
$ systemctl status lightdm.service
● lightdm.service - Light Display Manager
   Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit-hit) since Mon 2016-08-01 13:55:30 UTC; 3min 2s ago
     Docs: man:lightdm(1)
  Process: 343 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
 Main PID: 343 (code=exited, status=1/FAILURE)

Aug 01 13:55:30 arch systemd[1]: lightdm.service: Unit entered failed state.
Aug 01 13:55:30 arch systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 01 13:55:30 arch systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Aug 01 13:55:30 arch systemd[1]: Stopped Light Display Manager.
Aug 01 13:55:30 arch systemd[1]: lightdm.service: Start request repeated too quickly.
Aug 01 13:55:30 arch systemd[1]: Failed to start Light Display Manager.
Aug 01 13:55:30 arch systemd[1]: lightdm.service: Unit entered failed state.
Aug 01 13:55:30 arch systemd[1]: lightdm.service: Failed with result 'start-limit-hit'.


Code: Select all
$ journalctl -xe
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 01 13:57:16 arch systemd[363]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 01 13:57:16 arch systemd[363]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 01 13:57:16 arch systemd[363]: Startup finished in 198ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required KERNEL_USEC microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 198606 microseconds.
Aug 01 13:57:16 arch systemd[1]: Started User Manager for UID 1001.
-- Subject: Unit user@1001.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user@1001.service has finished starting up.
--
-- The start-up result is done.
Aug 01 13:57:32 arch systemd[363]: Started D-Bus User Message Bus.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.


Edit..

I have got Kodi to run in standalone mode but I would still like to get lightdm to work so that I can also run a few other packages that do require a gui and window manager.
nickarchpi2
 
Posts: 18
Joined: Tue Mar 22, 2016 9:43 pm

Re: lightdm failing to load

Postby sdjf » Fri Aug 05, 2016 3:03 am

I would not try to get a service running until I knew that the command started by the service is working.

You have a lot of error messages, some of them permissions. You could try running with sudo, assuming that you are running as a different user than root. That could clear up your permission issues, although no guarantees.

I have never used kodi and have no idea how it works, so not sure I can be of much help, though. The first thing I ran into that looked like an issue to use a search engine to find was the inability to find plymouth. Have you looked up what that is?

Does kodi run outside of or inside of X, or is it just a different form of X?
sdjf
 
Posts: 178
Joined: Wed May 08, 2013 1:55 pm

Re: lightdm failing to load

Postby moonman » Fri Aug 05, 2016 5:23 am

Kodi for rpi(1-3) and imx6 devices comes with kodi.service and runs without X. This isn't really covered in the wiki.
Pogoplug V4 | GoFlex Home | Raspberry Pi B 512 | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | |[armv5] How to install my.pogoplug.com service | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3089
Joined: Sat Jan 15, 2011 3:36 am
Location: Calgary, Canada

Re: lightdm failing to load

Postby sdjf » Fri Aug 05, 2016 2:46 pm

Hmm, thanks moonman. @nickarchpi2, did you see the Arch Wiki page that supposedly tells how to start lightdm with kodi, and needs a user kodi?

https://wiki.archlinux.org/index.php/Kodi

@moonman maybe this means there is more than one way to start Kodi? Or would both Kodi and Xsession be running independently?
sdjf
 
Posts: 178
Joined: Wed May 08, 2013 1:55 pm

Re: lightdm failing to load

Postby moonman » Fri Aug 05, 2016 9:44 pm

Kodi can run with X as well, and AFAIK running without X is not supported on all devices. I thought this was the main reason OP wanted X. Maybe now OP can ditch the lightdm completely.
Pogoplug V4 | GoFlex Home | Raspberry Pi B 512 | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | |[armv5] How to install my.pogoplug.com service | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3089
Joined: Sat Jan 15, 2011 3:36 am
Location: Calgary, Canada

Re: lightdm failing to load

Postby nickarchpi2 » Sun Aug 07, 2016 1:01 pm

Apologies, I should have been more clear but I wasn't sure myself at time of post.

Kodi is running in standalone which doesn't require X.

I have instigated it to launch with the following command so that I do not need to set up a user 'Kodi' or use lightdm, seems a more lightweight option.

Code: Select all
kodi --standalone


Now that I know kodi works I have enabled the kodi.service to launch on boot with systemctl and it works fine.

It is possible to launch it in other ways using X but I have gone with standalone as a personal preference, in the arch wiki it has a few different ways to launch Kodi and advises to use only one method.

I haven't looked into my lightdm issues yet but I started the service using
Code: Select all
sudo systemctl enable lightdm.service
so not sure why permissions issues are present.
nickarchpi2
 
Posts: 18
Joined: Tue Mar 22, 2016 9:43 pm

Re: lightdm failing to load

Postby nickarchpi2 » Sun Aug 07, 2016 11:04 pm

I've decided to remove all the dm packages for now but get the following errors trying to remove lightdm and lightdm-gtk-greeter

Code: Select all
$ sudo pacman -Rs lightdm
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: lightdm-gtk-greeter: removing lightdm breaks dependency 'lightdm'
$ sudo pacman -Rs lightdm-gtk-greeter
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: lightdm-gtk-greeter-settings: removing lightdm-gtk-greeter breaks dependency 'lightdm-gtk-greeter'
nickarchpi2
 
Posts: 18
Joined: Tue Mar 22, 2016 9:43 pm


Return to Broadcom

Who is online

Users browsing this forum: No registered users and 2 guests