You are not logged in.

#1 2019-10-12 22:37:33

gonzalo2099
Member
Registered: 2018-12-27
Posts: 13

lightDM black screen at start

Hello everyone, actually i'm using plasma desktop and i'm trying to change my DM from sddm to lightdm and i'm using plymouth, lightdm seems to start  but gives me a black screen and does not show me the login screen. I show my install process and maybe someone see my error:

$ sudo pacman -S lightdm lightdm-gtk-greeter
$ sudo systemctl disable sddm-plymouth
$ sudo nano /etc/lightdm/lightdm.conf ==> in " [Seat:*] "  i set from "#greeter-session=" to "greeter-session=lightdm-gtk-greeter"
$ sudo nano /etc/lightdm/lightdm.conf ==> in " [Seat:*] "  i set from "#user-session=" to "user-session=plasma"
$ sudo nano /etc/lightdm/lightdm-gtk-greeter.conf ==> and set "#background=" to  "background=/usr/share/backgrounds/gnome/Road.jpg"
$ sudo systemctl start lightdm
$ sudo systemctl enable lightdm-plymouth
$ sudo reboot

What i'm doing wrong????

Last edited by gonzalo2099 (2019-10-13 00:08:29)

Offline

#2 2019-10-12 23:10:38

loqs
Member
Registered: 2014-03-06
Posts: 8,785

Re: lightDM black screen at start

Can you reach a console with Ctrl + Alt F2?
Please post the contents of /var/log/lightdm/lightdm.log and /var/log/Xorg.0.log .
You can post from the console using the tip box from pastebin

Offline

#3 2019-10-12 23:20:20

gonzalo2099
Member
Registered: 2018-12-27
Posts: 13

Re: lightDM black screen at start

Sure, here is /var/log/lightdm/lightdm.log

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=8643
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.00s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.01s] DEBUG: XServer 0: Launching X Server
[+0.01s] DEBUG: Launching process 8659: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.01s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close requested) 
[+0.49s] DEBUG: Got signal 10 from process 8659
[+0.49s] DEBUG: XServer 0: Got signal from X server :0
[+0.49s] DEBUG: XServer 0: Connecting to XServer :0
[+0.49s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 
[+0.49s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.49s] DEBUG: Session pid=9029: Started with service 'lightdm-greeter', username 'lightdm'
[+0.50s] DEBUG: Session pid=9029: Authentication complete with return value 0: Success
[+0.50s] DEBUG: Seat seat0: Session authenticated, running command
[+0.50s] DEBUG: Session pid=9029: Running command /usr/bin/lightdm-gtk-greeter
[+0.50s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.50s] DEBUG: Session pid=9029: Logging to /var/log/lightdm/seat0-greeter.log
[+0.51s] DEBUG: Activating VT 7
[+0.52s] DEBUG: Activating login1 session c5
[+0.52s] DEBUG: Seat seat0 changes active session to c5
[+0.52s] DEBUG: Session c5 is already active
[+0.52s] DEBUG: Greeter closed communication channel
[+0.52s] DEBUG: Session pid=9029: Exited with return value 1
[+0.52s] DEBUG: Seat seat0: Session stopped
[+0.52s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+0.52s] DEBUG: Seat seat0: Stopping
[+0.52s] DEBUG: Seat seat0: Stopping display server
[+0.52s] DEBUG: Sending signal 15 to process 8659
[+0.72s] DEBUG: Process 8659 exited with return value 0
[+0.72s] DEBUG: XServer 0: X server stopped
[+0.72s] DEBUG: Releasing VT 7
[+0.72s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
[+0.72s] DEBUG: Seat seat0: Display server stopped
[+0.72s] DEBUG: Seat seat0: Stopped
[+0.72s] DEBUG: Required seat has stopped
[+0.72s] DEBUG: Stopping display manager
[+0.72s] DEBUG: Display manager stopped
[+0.72s] DEBUG: Stopping daemon
[+0.72s] DEBUG: Exiting with return value 1

Last edited by gonzalo2099 (2019-10-12 23:55:42)

Offline

#4 2019-10-12 23:27:05

loqs
Member
Registered: 2014-03-06
Posts: 8,785

Re: lightDM black screen at start

The contents of /var/log/lightdm/x-0-greeter.log please.  Also use code tags for logs,  commands,  their output e.t.c.

Offline

#5 2019-10-12 23:37:08

gonzalo2099
Member
Registered: 2018-12-27
Posts: 13

Re: lightDM black screen at start

here it is seat0-greeter.log


Error writing X authority: Failed to open X authority /var/lib/lightdm/.Xauthority: No such file or directory

Last edited by gonzalo2099 (2019-10-12 23:56:03)

Offline

#6 2019-10-12 23:45:55

loqs
Member
Registered: 2014-03-06
Posts: 8,785

Re: lightDM black screen at start

See the https://bbs.archlinux.org/help.php#bbcode link below the reply box to see how to use code tags.
Please post the output of the following in code tags and add code tags to your previous posts.

systemctl status systemd-tmpfiles-setup.service
cat /usr/lib/tmpfiles.d/lightdm.conf
# stat /var/lib/lightdm/ /var/lib/lightdm/.Xauthority

Offline

#7 2019-10-13 00:01:06

gonzalo2099
Member
Registered: 2018-12-27
Posts: 13

Re: lightDM black screen at start

systemctl status systemd-tmpfiles-setup.service

● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
   Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
   Active: active (exited) since Sun 2019-10-13 01:43:35 CEST; 13min ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 489 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=73)
 Main PID: 489 (code=exited, status=73)

cat /usr/lib/tmpfiles.d/lightdm.conf

d /run/lightdm 0711 lightdm lightdm -
d /var/cache/lightdm 0711 root lightdm -
d /var/lib/lightdm 1770 lightdm lightdm -
d /var/lib/lightdm-data 1770 lightdm lightdm -
d /var/log/lightdm 0711 root lightdm -

# stat /var/lib/lightdm/ /var/lib/lightdm/.Xauthority

stat: cannot stat '/var/lib/lightdm/': No such file or directory
stat: cannot stat '/var/lib/lightdm/.Xauthority': No such file or directory

Offline

#8 2019-10-13 00:08:33

loqs
Member
Registered: 2014-03-06
Posts: 8,785

Re: lightDM black screen at start

systemd-tmpfiles wrote:

EXIT STATUS
       On success, 0 is returned. If the configuration was syntactically
       invalid (syntax errors, missing arguments, ...), so some lines had to
       be ignored, but no other errors occurred, 65 is returned (EX_DATAERR
       from /usr/include/sysexits.h). If the configuration was syntactically
       valid, but could not be executed (lack of permissions, creation of
       files in missing directories, invalid contents when writing to /sys/
       values, ...), 73 is returned (EX_CANTCREAT from
       /usr/include/sysexits.h). Otherwise, 1 is returned (EXIT_FAILURE from
       /usr/include/stdlib.h).

What is the output of the following

journalctl -u systemd-tmpfiles-setup.service -b

Offline

#9 2019-10-13 00:11:06

gonzalo2099
Member
Registered: 2018-12-27
Posts: 13

Re: lightDM black screen at start

journalctl -u systemd-tmpfiles-setup.service -b

Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
No journal files were opened due to insufficient permissions.

Offline

#10 2019-10-13 16:19:57

loqs
Member
Registered: 2014-03-06
Posts: 8,785

Re: lightDM black screen at start

As commands output states the user you ran the command as does not have access to the system journal.
What is the output from executing the command as root?

# journalctl -u systemd-tmpfiles-setup.service -b

Offline

#11 2019-10-13 20:04:43

gonzalo2099
Member
Registered: 2018-12-27
Posts: 13

Re: lightDM black screen at start

here is:

-- Logs begin at Sun 2019-10-13 21:59:29 CEST, end at Sun 2019-10-13 22:01:54 CEST. --
oct 13 21:59:35 laptop systemd[1]: Starting Create Volatile Files and Directories...
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib/colord.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/lock.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/lock.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/cache.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/cache.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib/mpd.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/sudo.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/systemd/netif.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/systemd/netif.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib/systemd.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/cache.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log/journal.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log/journal.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log/journal.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log/journal.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /var during canonicalization of /var/log/journal/remote.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /sys during canonicalization of /sys/devices/system/cpu/microcode.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal/5f78f12b7ca64c5c82dd638b35fb38a1.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal/5f78f12b7ca64c5c82dd638b35fb38a1.
oct 13 21:59:35 laptop systemd-tmpfiles[492]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal/5f78f12b7ca64c5c82dd638b35fb38a1/system.journal.
oct 13 21:59:35 laptop systemd[1]: Started Create Volatile Files and Directories.

Offline

#12 2019-10-13 20:10:39

loqs
Member
Registered: 2014-03-06
Posts: 8,785

Re: lightDM black screen at start

What is the output of

stat /

Offline

#13 2019-10-14 00:27:47

gonzalo2099
Member
Registered: 2018-12-27
Posts: 13

Re: lightDM black screen at start

  File: /
  Size: 122             Blocks: 0          IO Block: 4096   directory
Device: 1bh/27d Inode: 256         Links: 1
Access: (0755/drwxr-xr-x)  Uid: ( 1001/ UNKNOWN)   Gid: ( 1001/ UNKNOWN)
Access: 2019-10-14 00:11:10.343164140 +0200
Modify: 2019-10-14 00:09:04.137113044 +0200
Change: 2019-10-14 00:09:04.137113044 +0200
 Birth: 2019-10-13 22:41:18.366270441 +0200

Offline

#14 2019-10-14 00:39:50

loqs
Member
Registered: 2014-03-06
Posts: 8,785

Re: lightDM black screen at start

/ Should be owned root:root.

# chown root:root /

You can use the following to detect such issues as there may be others:

# pacman -Qkk

Once ownership has been corrected does systemd-tmpfiles-setup.service run correctly?

Offline

#15 2019-10-14 02:43:57

gonzalo2099
Member
Registered: 2018-12-27
Posts: 13

Re: lightDM black screen at start

yes, that fixes all problems, thank you so much !!!!!!

Offline

#16 2019-10-14 02:45:28

gonzalo2099
Member
Registered: 2018-12-27
Posts: 13

Re: lightDM black screen at start

yes, that fixes all problems, thank you so much !!!!!!

Offline

Board footer

Powered by FluxBB