You are not logged in.

#1 2017-10-25 14:24:50

phunni
Member
From: Bristol, UK
Registered: 2003-08-13
Posts: 770

Can't get lightdm to start any more (previously "Can't get X to ...")

For some reason, I can no longer get X to start on my desktop. 

After the system has booted, the screen goes black and I briefly get a mouse pointer flashing up on the screen.  It then disappears, leaving me with the black screen again.  This process repeats itself for about a minute with, I would estimate, around 10 seconds between mouse pointer appearances.  After about twenty attempts (this is a guess - I haven't counted), it simply stops with a dash (-) in the top left of the screen.  At this point, I am able to switch virtual consoles and try things.

At first, I thought it might have been a hardware error - especially since I was getting USB errors - 110, which, apparently, is something to do with power.  Searching around gave me the suggestion to power off, unplug all USB devices and power cables, plug them all back in again and power up.  I did this - with little expectation of it making any difference, but the USB errors did go away.  X, however, still will not start.

I opened the box up to see if there was anything obviously wrong, hardware wise, but found nothing.  dmesg contained lots of messages from nvidia-modeset:

[    5.218126] nvidia: loading out-of-tree module taints kernel.
[    5.218889] nvidia: module license 'NVIDIA' taints kernel.
[    5.311447] nvidia-nvlink: Nvlink Core is being initialized, major device number 246
[    5.311866] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[    5.326079] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  387.12  Thu Sep 28 19:30:23 PDT 2017
[    5.328288] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    5.328290] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
[    8.764333] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   10.466740] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   11.313670] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   12.699158] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   13.530590] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   14.899445] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   15.763613] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   17.131624] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   17.996399] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   20.380612] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   21.243521] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   22.596907] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   23.843546] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   25.247249] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   26.093496] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   27.446157] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   28.293462] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   29.664028] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   30.510084] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   32.846920] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   33.675940] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   35.046387] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   35.892532] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   37.246104] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   38.643436] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   40.042565] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   40.892448] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   42.262395] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   43.109939] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   44.528513] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   45.739907] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   47.110187] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   47.939005] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   49.327533] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   50.156774] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   51.527131] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   52.838970] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   54.209747] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   54.822239] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   56.192822] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   56.822239] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   58.175815] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   58.805543] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   60.172343] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   60.823043] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   62.174783] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   62.822970] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   64.174397] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   65.505441] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   66.891258] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   67.552093] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   68.956789] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   69.568742] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   71.988168] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   72.818687] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   74.172330] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   74.819522] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   76.188641] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   76.818621] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   78.638036] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   79.319442] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   80.671144] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   81.318598] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   82.671044] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   83.302757] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   84.620447] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   85.319341] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   86.704738] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   87.319358] nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
[   88.735439] nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0

and there was nothing in the Xorg log that suggested a problem to me:

[    87.412] 
X.Org X Server 1.19.5
Release Date: 2017-10-12
[    87.412] X Protocol Version 11, Revision 0
[    87.412] Build Operating System: Linux 4.9.54-1-lts x86_64 
[    87.412] Current Operating System: Linux kirstine 4.13.5-1-ARCH #1 SMP PREEMPT Fri Oct 6 09:58:47 CEST 2017 x86_64
[    87.412] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=863696d9-cb5c-49d4-a2ea-50b5188c0573 rw quiet
[    87.412] Build Date: 12 October 2017  09:59:53PM
[    87.413]  
[    87.413] Current version of pixman: 0.34.0
[    87.413] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    87.413] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    87.413] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 20 16:17:52 2017
[    87.413] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    87.413] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    87.413] (==) No Layout section.  Using the first Screen section.
[    87.413] (==) No screen section available. Using defaults.
[    87.413] (**) |-->Screen "Default Screen Section" (0)
[    87.413] (**) |   |-->Monitor "<default monitor>"
[    87.413] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[    87.413] (**) |   |-->Device "Nvidia Card"
[    87.413] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    87.413] (==) Automatically adding devices
[    87.413] (==) Automatically enabling devices
[    87.413] (==) Automatically adding GPU devices
[    87.413] (==) Automatically binding GPU devices
[    87.413] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    87.413] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[    87.413] 	Entry deleted from font path.
[    87.413] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[    87.413] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[    87.413] 	Entry deleted from font path.
[    87.413] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[    87.413] (==) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/OTF/,
	/usr/share/fonts/Type1/
[    87.413] (==) ModulePath set to "/usr/lib/xorg/modules"
[    87.413] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    87.413] (II) Loader magic: 0x5574c4586d60
[    87.413] (II) Module ABI versions:
[    87.413] 	X.Org ANSI C Emulation: 0.4
[    87.413] 	X.Org Video Driver: 23.0
[    87.413] 	X.Org XInput driver : 24.1
[    87.413] 	X.Org Server Extension : 10.0
[    87.414] (++) using VT number 7

[    87.414] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    87.414] (II) xfree86: Adding drm device (/dev/dri/card0)
[    87.416] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules"
[    87.416] (**) OutputClass "nvidia" setting /dev/dri/card0 as PrimaryGPU
[    87.418] (--) PCI:*(0:1:0:0) 10de:1287:3842:3731 rev 161, Mem @ 0xf4000000/16777216, 0xe0000000/134217728, 0xe8000000/33554432, I/O @ 0x0000b000/128, BIOS @ 0x????????/131072
[    87.418] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    87.418] (II) LoadModule: "glx"
[    87.418] (II) Loading /usr/lib/nvidia/xorg/libglx.so
[    87.424] (II) Module glx: vendor="NVIDIA Corporation"
[    87.424] 	compiled for 4.0.2, module version = 1.0.0
[    87.424] 	Module class: X.Org Server Extension
[    87.424] (II) NVIDIA GLX Module  387.12  Thu Sep 28 19:24:49 PDT 2017
[    87.424] (II) LoadModule: "nvidia"
[    87.425] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    87.425] (II) Module nvidia: vendor="NVIDIA Corporation"
[    87.425] 	compiled for 4.0.2, module version = 1.0.0
[    87.425] 	Module class: X.Org Video Driver
[    87.425] (II) NVIDIA dlloader X Driver  387.12  Thu Sep 28 18:57:27 PDT 2017
[    87.425] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    87.425] (II) Loading sub module "fb"
[    87.425] (II) LoadModule: "fb"
[    87.425] (II) Loading /usr/lib/xorg/modules/libfb.so
[    87.426] (II) Module fb: vendor="X.Org Foundation"
[    87.426] 	compiled for 1.19.5, module version = 1.0.0
[    87.426] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    87.426] (II) Loading sub module "wfb"
[    87.426] (II) LoadModule: "wfb"
[    87.426] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    87.426] (II) Module wfb: vendor="X.Org Foundation"
[    87.426] 	compiled for 1.19.5, module version = 1.0.0
[    87.426] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    87.426] (II) Loading sub module "ramdac"
[    87.426] (II) LoadModule: "ramdac"
[    87.426] (II) Module "ramdac" already built-in
[    87.426] (II) NVIDIA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    87.426] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[    87.426] (==) NVIDIA(0): RGB weight 888
[    87.426] (==) NVIDIA(0): Default visual is TrueColor
[    87.426] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    87.426] (II) Applying OutputClass "nvidia" options to /dev/dri/card0
[    87.427] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[    87.427] (**) NVIDIA(0): Enabling 2D acceleration
[    87.917] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[    87.917] (--) NVIDIA(0):     CRT-0 (boot)
[    87.917] (--) NVIDIA(0):     DFP-0
[    87.917] (--) NVIDIA(0):     DFP-1
[    87.919] (II) NVIDIA(0): NVIDIA GPU GeForce GT 730 (GK208) at PCI:1:0:0 (GPU-0)
[    87.919] (--) NVIDIA(0): Memory: 1048576 kBytes
[    87.919] (--) NVIDIA(0): VideoBIOS: 80.28.6a.00.30
[    87.919] (II) NVIDIA(0): Detected PCI Express Link width: 8X
[    87.948] (--) NVIDIA(GPU-0): NEC LCD73V (CRT-0): connected
[    87.948] (--) NVIDIA(GPU-0): NEC LCD73V (CRT-0): 400.0 MHz maximum pixel clock
[    87.948] (--) NVIDIA(GPU-0): 
[    87.948] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    87.948] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    87.948] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    87.949] (--) NVIDIA(GPU-0): 
[    87.949] (--) NVIDIA(GPU-0): DFP-1: disconnected
[    87.949] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[    87.949] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[    87.949] (--) NVIDIA(GPU-0): 
[    87.951] (==) NVIDIA(0): 
[    87.951] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[    87.951] (==) NVIDIA(0):     will be used as the requested mode.
[    87.951] (==) NVIDIA(0): 
[    87.951] (II) NVIDIA(0): Validated MetaModes:
[    87.951] (II) NVIDIA(0):     "CRT-0:nvidia-auto-select"
[    87.951] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
[    87.959] (--) NVIDIA(0): DPI set to (95, 96); computed from "UseEdidDpi" X config
[    87.959] (--) NVIDIA(0):     option
[    87.959] (--) Depth 24 pixmap format is 32 bpp
[    87.959] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect memory
[    87.959] (II) NVIDIA:     access.
[    87.977] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    87.977] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    87.977] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    87.977] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    87.977] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    87.977] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    87.977] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    87.977] (II) NVIDIA(0):     Config Options in the README.
[    87.993] (II) NVIDIA(0): Setting mode "CRT-0:nvidia-auto-select"
[    88.026] (==) NVIDIA(0): Disabling shared memory pixmaps
[    88.026] (==) NVIDIA(0): Backing store enabled
[    88.026] (==) NVIDIA(0): Silken mouse enabled
[    88.026] (==) NVIDIA(0): DPMS enabled
[    88.027] (WW) NVIDIA(0): Option "PrimaryGPU" is not used
[    88.027] (WW) NVIDIA(0): Option "NoLogo" is not used
[    88.027] (II) Loading sub module "dri2"
[    88.027] (II) LoadModule: "dri2"
[    88.027] (II) Module "dri2" already built-in
[    88.027] (II) NVIDIA(0): [DRI2] Setup complete
[    88.027] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    88.027] (--) RandR disabled
[    88.031] (II) Initializing extension GLX
[    88.032] (II) Indirect GLX disabled.
[    88.101] (II) config/udev: Adding input device Power Button (/dev/input/event15)
[    88.101] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    88.101] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    88.101] (**) Power Button: Applying InputClass "system-keyboard"
[    88.101] (**) Power Button: Applying InputClass "Keyboard Defaults"
[    88.101] (II) LoadModule: "libinput"
[    88.101] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    88.104] (II) Module libinput: vendor="X.Org Foundation"
[    88.104] 	compiled for 1.19.3, module version = 0.26.0
[    88.104] 	Module class: X.Org XInput Driver
[    88.104] 	ABI class: X.Org XInput driver, version 24.1
[    88.104] (II) Using input driver 'libinput' for 'Power Button'
[    88.104] (**) Power Button: always reports core events
[    88.104] (**) Option "Device" "/dev/input/event15"
[    88.104] (**) Option "_source" "server/udev"
[    88.104] (II) event15 - (II) Power Button: (II) is tagged by udev as: Keyboard
[    88.104] (II) event15 - (II) Power Button: (II) device is a keyboard
[    88.104] (II) event15 - (II) Power Button: (II) device removed
[    88.123] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input17/event15"
[    88.123] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    88.123] (**) Option "xkb_layout" "gb"
[    88.148] (II) event15 - (II) Power Button: (II) is tagged by udev as: Keyboard
[    88.148] (II) event15 - (II) Power Button: (II) device is a keyboard
[    88.148] (II) config/udev: Adding input device Power Button (/dev/input/event14)
[    88.148] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    88.148] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    88.148] (**) Power Button: Applying InputClass "system-keyboard"
[    88.148] (**) Power Button: Applying InputClass "Keyboard Defaults"
[    88.148] (II) Using input driver 'libinput' for 'Power Button'
[    88.148] (**) Power Button: always reports core events
[    88.148] (**) Option "Device" "/dev/input/event14"
[    88.148] (**) Option "_source" "server/udev"
[    88.149] (II) event14 - (II) Power Button: (II) is tagged by udev as: Keyboard
[    88.149] (II) event14 - (II) Power Button: (II) device is a keyboard
[    88.149] (II) event14 - (II) Power Button: (II) device removed
[    88.166] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input16/event14"
[    88.166] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    88.166] (**) Option "xkb_layout" "gb"
[    88.167] (II) event14 - (II) Power Button: (II) is tagged by udev as: Keyboard
[    88.167] (II) event14 - (II) Power Button: (II) device is a keyboard
[    88.167] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event12)
[    88.167] (II) No input driver specified, ignoring this device.
[    88.167] (II) This device may have been added with another device file.
[    88.168] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event13)
[    88.168] (II) No input driver specified, ignoring this device.
[    88.168] (II) This device may have been added with another device file.
[    88.169] (II) config/udev: Adding input device SIGMACH1P USB Keykoard (/dev/input/event0)
[    88.169] (**) SIGMACH1P USB Keykoard: Applying InputClass "evdev keyboard catchall"
[    88.169] (**) SIGMACH1P USB Keykoard: Applying InputClass "libinput keyboard catchall"
[    88.169] (**) SIGMACH1P USB Keykoard: Applying InputClass "system-keyboard"
[    88.169] (**) SIGMACH1P USB Keykoard: Applying InputClass "Keyboard Defaults"
[    88.169] (II) Using input driver 'libinput' for 'SIGMACH1P USB Keykoard'
[    88.169] (**) SIGMACH1P USB Keykoard: always reports core events
[    88.169] (**) Option "Device" "/dev/input/event0"
[    88.169] (**) Option "_source" "server/udev"
[    88.169] (II) event0  - (II) SIGMACH1P USB Keykoard: (II) is tagged by udev as: Keyboard
[    88.169] (II) event0  - (II) SIGMACH1P USB Keykoard: (II) device is a keyboard
[    88.169] (II) event0  - (II) SIGMACH1P USB Keykoard: (II) device removed
[    88.183] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/0003:1C4F:000E.0001/input/input2/event0"
[    88.183] (II) XINPUT: Adding extended input device "SIGMACH1P USB Keykoard" (type: KEYBOARD, id 8)
[    88.183] (**) Option "xkb_layout" "gb"
[    88.184] (II) event0  - (II) SIGMACH1P USB Keykoard: (II) is tagged by udev as: Keyboard
[    88.184] (II) event0  - (II) SIGMACH1P USB Keykoard: (II) device is a keyboard
[    88.184] (II) config/udev: Adding input device SIGMACH1P USB Keykoard (/dev/input/event1)
[    88.184] (**) SIGMACH1P USB Keykoard: Applying InputClass "evdev keyboard catchall"
[    88.184] (**) SIGMACH1P USB Keykoard: Applying InputClass "libinput keyboard catchall"
[    88.184] (**) SIGMACH1P USB Keykoard: Applying InputClass "system-keyboard"
[    88.184] (**) SIGMACH1P USB Keykoard: Applying InputClass "Keyboard Defaults"
[    88.184] (II) Using input driver 'libinput' for 'SIGMACH1P USB Keykoard'
[    88.184] (**) SIGMACH1P USB Keykoard: always reports core events
[    88.184] (**) Option "Device" "/dev/input/event1"
[    88.184] (**) Option "_source" "server/udev"
[    88.185] (II) event1  - (II) SIGMACH1P USB Keykoard: (II) is tagged by udev as: Keyboard
[    88.185] (II) event1  - (II) SIGMACH1P USB Keykoard: (II) device is a keyboard
[    88.185] (II) event1  - (II) SIGMACH1P USB Keykoard: (II) device removed
[    88.204] (II) libinput: SIGMACH1P USB Keykoard: needs a virtual subdevice
[    88.204] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.1/0003:1C4F:000E.0002/input/input3/event1"
[    88.204] (II) XINPUT: Adding extended input device "SIGMACH1P USB Keykoard" (type: MOUSE, id 9)
[    88.204] (**) Option "AccelerationScheme" "none"
[    88.204] (**) SIGMACH1P USB Keykoard: (accel) selected scheme none/0
[    88.204] (**) SIGMACH1P USB Keykoard: (accel) acceleration factor: 2.000
[    88.204] (**) SIGMACH1P USB Keykoard: (accel) acceleration threshold: 4
[    88.204] (II) event1  - (II) SIGMACH1P USB Keykoard: (II) is tagged by udev as: Keyboard
[    88.204] (II) event1  - (II) SIGMACH1P USB Keykoard: (II) device is a keyboard
[    88.205] (II) config/udev: Adding input device HID 1241:1177 (/dev/input/event2)
[    88.205] (**) HID 1241:1177: Applying InputClass "evdev pointer catchall"
[    88.205] (**) HID 1241:1177: Applying InputClass "libinput pointer catchall"
[    88.205] (II) Using input driver 'libinput' for 'HID 1241:1177'
[    88.205] (**) HID 1241:1177: always reports core events
[    88.205] (**) Option "Device" "/dev/input/event2"
[    88.205] (**) Option "_source" "server/udev"
[    88.260] (II) event2  - (II) HID 1241:1177: (II) is tagged by udev as: Mouse
[    88.260] (II) event2  - (II) HID 1241:1177: (II) device is a pointer
[    88.260] (II) event2  - (II) HID 1241:1177: (II) device removed
[    88.296] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.0/0003:1241:1177.0003/input/input4/event2"
[    88.296] (II) XINPUT: Adding extended input device "HID 1241:1177" (type: MOUSE, id 10)
[    88.296] (**) Option "AccelerationScheme" "none"
[    88.296] (**) HID 1241:1177: (accel) selected scheme none/0
[    88.296] (**) HID 1241:1177: (accel) acceleration factor: 2.000
[    88.296] (**) HID 1241:1177: (accel) acceleration threshold: 4
[    88.353] (II) event2  - (II) HID 1241:1177: (II) is tagged by udev as: Mouse
[    88.353] (II) event2  - (II) HID 1241:1177: (II) device is a pointer
[    88.354] (II) config/udev: Adding input device HID 1241:1177 (/dev/input/mouse0)
[    88.354] (II) No input driver specified, ignoring this device.
[    88.354] (II) This device may have been added with another device file.
[    88.354] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event8)
[    88.354] (II) No input driver specified, ignoring this device.
[    88.354] (II) This device may have been added with another device file.
[    88.354] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event9)
[    88.354] (II) No input driver specified, ignoring this device.
[    88.354] (II) This device may have been added with another device file.
[    88.355] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event10)
[    88.355] (II) No input driver specified, ignoring this device.
[    88.355] (II) This device may have been added with another device file.
[    88.355] (II) config/udev: Adding input device HDA Intel Line Out Side (/dev/input/event11)
[    88.355] (II) No input driver specified, ignoring this device.
[    88.355] (II) This device may have been added with another device file.
[    88.355] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event4)
[    88.355] (II) No input driver specified, ignoring this device.
[    88.355] (II) This device may have been added with another device file.
[    88.356] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event5)
[    88.356] (II) No input driver specified, ignoring this device.
[    88.356] (II) This device may have been added with another device file.
[    88.356] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event6)
[    88.356] (II) No input driver specified, ignoring this device.
[    88.356] (II) This device may have been added with another device file.
[    88.356] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event7)
[    88.356] (II) No input driver specified, ignoring this device.
[    88.356] (II) This device may have been added with another device file.
[    88.357] (II) config/udev: Adding input device PC Speaker (/dev/input/event16)
[    88.357] (II) No input driver specified, ignoring this device.
[    88.357] (II) This device may have been added with another device file.
[    88.357] (II) config/udev: Adding input device Speakup (/dev/input/event3)
[    88.357] (**) Speakup: Applying InputClass "evdev keyboard catchall"
[    88.357] (**) Speakup: Applying InputClass "libinput keyboard catchall"
[    88.357] (**) Speakup: Applying InputClass "system-keyboard"
[    88.357] (**) Speakup: Applying InputClass "Keyboard Defaults"
[    88.357] (II) Using input driver 'libinput' for 'Speakup'
[    88.357] (**) Speakup: always reports core events
[    88.357] (**) Option "Device" "/dev/input/event3"
[    88.357] (**) Option "_source" "server/udev"
[    88.358] (II) event3  - (II) Speakup: (II) is tagged by udev as: Keyboard
[    88.358] (II) event3  - (II) Speakup: (II) device is a keyboard
[    88.358] (II) event3  - (II) Speakup: (II) device removed
[    88.396] (**) Option "config_info" "udev:/sys/devices/virtual/input/input5/event3"
[    88.396] (II) XINPUT: Adding extended input device "Speakup" (type: KEYBOARD, id 11)
[    88.396] (**) Option "xkb_layout" "gb"
[    88.397] (II) event3  - (II) Speakup: (II) is tagged by udev as: Keyboard
[    88.397] (II) event3  - (II) Speakup: (II) device is a keyboard
[    88.401] (**) SIGMACH1P USB Keykoard: Applying InputClass "evdev keyboard catchall"
[    88.401] (**) SIGMACH1P USB Keykoard: Applying InputClass "libinput keyboard catchall"
[    88.401] (**) SIGMACH1P USB Keykoard: Applying InputClass "system-keyboard"
[    88.401] (**) SIGMACH1P USB Keykoard: Applying InputClass "Keyboard Defaults"
[    88.401] (II) Using input driver 'libinput' for 'SIGMACH1P USB Keykoard'
[    88.401] (**) SIGMACH1P USB Keykoard: always reports core events
[    88.401] (**) Option "Device" "/dev/input/event1"
[    88.401] (**) Option "_source" "_driver/libinput"
[    88.401] (II) libinput: SIGMACH1P USB Keykoard: is a virtual subdevice
[    88.401] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.1/0003:1C4F:000E.0002/input/input3/event1"
[    88.401] (II) XINPUT: Adding extended input device "SIGMACH1P USB Keykoard" (type: KEYBOARD, id 12)
[    88.401] (**) Option "xkb_layout" "gb"
[    88.964] (II) event15 - (II) Power Button: (II) device removed
[    88.980] (II) event14 - (II) Power Button: (II) device removed
[    88.996] (II) event0  - (II) SIGMACH1P USB Keykoard: (II) device removed
[    89.013] (II) event2  - (II) HID 1241:1177: (II) device removed
[    89.053] (II) event3  - (II) Speakup: (II) device removed
[    89.080] (II) event1  - (II) SIGMACH1P USB Keykoard: (II) device removed
[    89.092] (II) UnloadModule: "libinput"
[    89.092] (II) UnloadModule: "libinput"
[    89.092] (II) UnloadModule: "libinput"
[    89.092] (II) UnloadModule: "libinput"
[    89.092] (II) UnloadModule: "libinput"
[    89.092] (II) UnloadModule: "libinput"
[    89.092] (II) UnloadModule: "libinput"
[    89.222] (II) NVIDIA(GPU-0): Deleting GPU-0
[    89.233] (II) Server terminated successfully (0). Closing log file.

At this point I'm stumped - any suggestions on what to try/explore next would be very gratefully appreciated!

Last edited by phunni (2017-10-25 20:41:04)

Offline

#2 2017-10-25 14:32:43

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,789

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

Your X server is exiting normally.  This means that your desktop environment is exiting.
What is your desktop environment?
How are you starting X?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2017-10-25 18:31:34

seth
Member
Registered: 2012-09-03
Posts: 51,213

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

And to be sure: the posted log file is 5 days old - is it the correct one?

Log file: "/var/log/Xorg.0.log", Time: Fri Oct 20 16:17:52 201

Offline

#4 2017-10-25 20:40:16

phunni
Member
From: Bristol, UK
Registered: 2003-08-13
Posts: 770

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

Thanks - I looked a little closer and it seems like it's lightdm that's failing to start, although I can't find anything helpful in those logs either except that it says that it's failing to start a greeter, but doesn't say ( as far as I can see) why...

It tried running "lightdm --test-mode --debug" - it only let me run as root - and here's the output:

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.22.0, UID=0 PID=613
[+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: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory)
[+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 618: /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.02s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.14s] DEBUG: Seat seat0 changes active session to 
[+1.46s] DEBUG: Got signal 10 from process 618
[+1.46s] DEBUG: XServer 0: Got signal from X server :0
[+1.46s] DEBUG: XServer 0: Connecting to XServer :0
[+1.46s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[+1.46s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+1.46s] DEBUG: Session pid=634: Started with service 'lightdm-greeter', username 'lightdm'
[+1.48s] DEBUG: Session pid=634: Authentication complete with return value 0: Success
[+1.48s] DEBUG: Seat seat0: Session authenticated, running command
[+1.48s] DEBUG: Session pid=634: Running command /usr/bin/lightdm-gtk-greeter
[+1.48s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+1.48s] DEBUG: Session pid=634: Logging to /var/log/lightdm/seat0-greeter.log
[+1.49s] DEBUG: Activating VT 7
[+1.69s] DEBUG: Greeter connected version=1.22.0 api=1 resettable=false
[+2.28s] DEBUG: Greeter closed communication channel
[+2.28s] DEBUG: Session pid=634: Exited with return value 1
[+2.28s] DEBUG: Seat seat0: Session stopped
[+2.28s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+2.28s] DEBUG: Seat seat0: Stopping
[+2.28s] DEBUG: Seat seat0: Stopping display server
[+2.28s] DEBUG: Sending signal 15 to process 618
[+2.54s] DEBUG: Process 618 exited with return value 0
[+2.54s] DEBUG: XServer 0: X server stopped
[+2.54s] DEBUG: Releasing VT 7
[+2.54s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
[+2.54s] DEBUG: Seat seat0: Display server stopped
[+2.54s] DEBUG: Seat seat0: Stopped
[+2.54s] DEBUG: Required seat has stopped
[+2.54s] DEBUG: Stopping display manager
[+2.54s] DEBUG: Display manager stopped
[+2.54s] DEBUG: Stopping daemon
[+2.55s] DEBUG: Exiting with return value 1

As far as I can make out lightdm.log contains exactly the same.

Here are the relevant congfigs:

lightdm.conf (pretty sure it's just the default):

#
# General configuration
#
# start-default-seat = True to always start one seat if none are defined in the configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the system location
# guest-account-script = Script to be run to setup guest account
# logind-check-graphical = True to on start seats that are marked as graphical by logind
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# sessions-directory = Directory to find sessions
# remote-sessions-directory = Directory to find remote sessions
# greeters-directory = Directory to find greeters
# backup-logs = True to move add a .old suffix to old log files when opening new ones
# dbus-service = True if LightDM provides a D-Bus service to control it
#
[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7 # Setting this to a value < 7 implies security issues, see FS#46799
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#logind-check-graphical=false
#log-directory=/var/log/lightdm
run-directory=/run/lightdm
#cache-directory=/var/cache/lightdm
#sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#greeters-directory=$XDG_DATA_DIRS/lightdm/greeters:$XDG_DATA_DIRS/xgreeters
#backup-logs=true
#dbus-service=true

#
# Seat configuration
#
# Seat configuration is matched against the seat name glob in the section, for example:
# [Seat:*] matches all seats and is applied first.
# [Seat:seat0] matches the seat named "seat0".
# [Seat:seat-thin-client*] matches all seats that have names that start with "seat-thin-client".
#
# type = Seat type (local, xremote, unity)
# pam-service = PAM service to use for login
# pam-autologin-service = PAM service to use for autologin
# pam-greeter-service = PAM service to use for greeters
# xserver-backend = X backend to use (mir)
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xmir-command = Xmir server command to run (can also contain arguments e.g. Xmir -special-option)
# xserver-config = Config file to pass to X server
# xserver-layout = Layout to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xserver-share = True if the X server is shared for both greeter and session
# xserver-hostname = Hostname of X server (only for type=xremote)
# xserver-display-number = Display number of X server (only for type=xremote)
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
# unity-compositor-command = Unity compositor command to run (can also contain arguments e.g. unity-system-compositor -special-option)
# unity-compositor-timeout = Number of seconds to wait for compositor to start
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login option
# greeter-show-remote-login = True if the greeter should offer a remote login option
# user-session = Session to load for users
# allow-user-switching = True if allowed to switch users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# greeter-wrapper = Wrapper script to run greeter with
# guest-wrapper = Wrapper script to run guest sessions with
# display-setup-script = Script to run when starting a greeter session (runs as root)
# display-stopped-script = Script to run after stopping the display server (runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as root)
# session-cleanup-script = Script to run when quitting a user session (runs as root)
# autologin-guest = True to log in as guest by default
# autologin-user = User to log in with by default (overrides autologin-guest)
# autologin-user-timeout = Number of seconds to wait before loading default user
# autologin-session = Session to load for automatic login (overrides user-session)
# autologin-in-background = True if autologin session should not be immediately activated
# exit-on-failure = True if the daemon should exit if this seat fails
#
[Seat:*]
#type=local
#pam-service=lightdm
#pam-autologin-service=lightdm-autologin
#pam-greeter-service=lightdm-greeter
#xserver-backend=
#xserver-command=X
#xmir-command=Xmir
#xserver-config=
#xserver-layout=
#xserver-allow-tcp=false
#xserver-share=true
#xserver-hostname=
#xserver-display-number=
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
#unity-compositor-command=unity-system-compositor
#unity-compositor-timeout=60
#greeter-session=example-gtk-gnome
#greeter-hide-users=false
#greeter-allow-guest=true
#greeter-show-manual-login=false
#greeter-show-remote-login=true
#user-session=default
#allow-user-switching=true
#allow-guest=true
#guest-session=
session-wrapper=/etc/lightdm/Xsession
#greeter-wrapper=
#guest-wrapper=
#display-setup-script=
#display-stopped-script=
#greeter-setup-script=
#session-setup-script=
#session-cleanup-script=
#autologin-guest=false
#autologin-user=
#autologin-user-timeout=0
#autologin-in-background=false
#autologin-session=
#exit-on-failure=false

#
# XDMCP Server configuration
#
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# listen-address = Host/address to listen for XDMCP connections (use all addresses if not present)
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
# hostname = Hostname to report to XDMCP clients (defaults to system hostname if unset)
#
# The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn.  Alternatively
# it can be a word and the first 7 characters are used as the key.
#
[XDMCPServer]
#enabled=false
#port=177
#listen-address=
#key=
#hostname=

#
# VNC Server configuration
#
# enabled = True if VNC connections should be allowed
# command = Command to run Xvnc server with
# port = TCP/IP port to listen for connections on
# listen-address = Host/address to listen for VNC connections (use all addresses if not present)
# width = Width of display to use
# height = Height of display to use
# depth = Color depth of display to use
#
[VNCServer]
#enabled=false
#command=Xvnc
#port=5900
#listen-address=
#width=1024
#height=768
#depth=8

lightdm-gtk-greeter.conf:

# LightDM GTK+ Configuration
# Available configuration options listed below.
#
# Appearance:
#  theme-name = GTK+ theme to use
#  icon-theme-name = Icon theme to use
#  background = Background file to use, either an image path or a color (e.g. #772953)
#  user-background = false|true ("true" by default)  Display user background (if available)
#  transition-duration = Length of time (in milliseconds) to transition between background images ("500" by default)
#  transition-type = ease-in-out|linear|none  ("ease-in-out" by default)
#
# Fonts:
#  font-name = Font to use
#  xft-antialias = false|true  Whether to antialias Xft fonts
#  xft-dpi = Resolution for Xft in dots per inch (e.g. 96)
#  xft-hintstyle = none|slight|medium|hintfull  What degree of hinting to use
#  xft-rgba = none|rgb|bgr|vrgb|vbgr  Type of subpixel antialiasing
#
# Login window:
#  active-monitor = Monitor to display greeter window (name or number). Use #cursor value to display greeter at monitor with cursor. Can be a semicolon separated list
#  position = x y ("50% 50%" by default)  Login window position
#  default-user-image = Image used as default user icon, path or #icon-name
#  hide-user-image = false|true ("false" by default)
#
# Panel:
#  panel-position = top|bottom ("top" by default)
#  clock-format = strftime-format string, e.g. %H:%M
#  indicators = semi-colon ";" separated list of allowed indicator modules. Built-in indicators include "~a11y", "~language", "~session", "~power", "~clock", "~host", "~spacer". Unity indicators can be represented by short name (e.g. "sound", "power"), service file name, or absolute path
#
# Accessibility:
#  a11y-states = states of accessibility features: "name" - save state on exit, "-name" - disabled at start (default value for unlisted), "+name" - enabled at start. Allowed names: contrast, font, keyboard, reader.
#  keyboard = command to launch on-screen keyboard (e.g. "onboard")
#  keyboard-position = x y[;width height] ("50%,center -0;50% 25%" by default)  Works only for "onboard"
#  reader = command to launch screen reader (e.g. "orca")
#
# Security:
#  allow-debugging = false|true ("false" by default)
#  screensaver-timeout = Timeout (in seconds) until the screen blanks when the greeter is called as lockscreen
#
# Template for per-monitor configuration:
#  [monitor: name]
#  background = overrides default value
#  user-background = overrides default value
#  laptop = false|true ("false" by default) Marks monitor as laptop display
#  transition-duration = overrides default value
#
[greeter]
background=/opt/0901wallpaper-4_1024.jpg
#user-background=
theme-name=Adwaita-dark
icon-theme-name=Adwaita
#font-name=
xft-antialias=true
#xft-dpi=
#xft-hintstyle=
#xft-rgba=
#indicators=
#clock-format=
#keyboard=
#reader=
#position=
#screensaver-timeout=

Offline

#5 2017-10-26 06:30:14

HiImTye
Member
From: Halifax, NS, Canada
Registered: 2012-05-09
Posts: 1,072

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

[+1.48s] DEBUG: Session pid=634: Logging to /var/log/lightdm/seat0-greeter.log

any information in this log file?

Offline

#6 2017-10-26 08:12:51

phunni
Member
From: Bristol, UK
Registered: 2003-08-13
Posts: 770

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

HiImTye wrote:
[+1.48s] DEBUG: Session pid=634: Logging to /var/log/lightdm/seat0-greeter.log

any information in this log file?

No, sorry, I meant to say. Despite what the above logs say, the last date mentioned in that log is from 2016.

I have confirmed that the date on the computer is correct.

Offline

#7 2017-10-26 15:15:52

phunni
Member
From: Bristol, UK
Registered: 2003-08-13
Posts: 770

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

For completeness - here is that log:

** (process:634): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
** Message: Starting lightdm-gtk-greeter 2.0.2 (Oct 17 2016, 14:22:50)
** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf

** (lightdm-gtk-greeter:637): WARNING **: [PIDs] Failed to execute command: upstart
Failed to launch bus: Failed to connect to session bus
(lightdm-gtk-greeter:637): Gtk-WARNING **: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Adwaita/16x16/status/image-missing.png: Unrecognised image file format (gdk-pixbuf-error-quark, 3)

Offline

#8 2017-10-26 16:54:59

HiImTye
Member
From: Halifax, NS, Canada
Registered: 2012-05-09
Posts: 1,072

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

alternately, are there any messages in the journal? if it says it's logging to a file and the file mentioned is basically empty, then it's likely it's logging to the journal.

Offline

#9 2017-11-01 21:25:08

phunni
Member
From: Bristol, UK
Registered: 2003-08-13
Posts: 770

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

HiImTye wrote:

alternately, are there any messages in the journal? if it says it's logging to a file and the file mentioned is basically empty, then it's likely it's logging to the journal.

Genius idea - don't know why I didn't think of that myself.  Yes, there is some stuff that looks like it might be relevant in the journal:

Nov 01 21:15:21 kirstine kernel: NVRM: Your system is not currently configured to drive a VGA console
                                 on the primary VGA device. The NVIDIA Linux graphics driver
                                 requires the use of a text-mode VGA console. Use of other console
                                 drivers including, but not limited to, vesafb, may result in
                                 corruption and stability problems, and is not supported.
Nov 01 21:15:21 kirstine kernel: nvidia-modeset: Allocated GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0
Nov 01 21:15:22 kirstine lightdm[623]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Nov 01 21:15:22 kirstine lightdm[623]: pam_systemd(lightdm-greeter:session): Cannot create session: Already running in a session
Nov 01 21:15:22 kirstine systemd[1]: Created slice system-systemd\x2dcoredump.slice.
-- Subject: Unit system-systemd\x2dcoredump.slice has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit system-systemd\x2dcoredump.slice has finished starting up.
-- 
-- The start-up result is RESULT.
Nov 01 21:15:22 kirstine systemd[1]: Started Process Core Dump (PID 632/UID 0).
-- Subject: Unit systemd-coredump@0-632-0.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-coredump@0-632-0.service has finished starting up.
-- 
-- The start-up result is RESULT.
Nov 01 21:15:23 kirstine systemd-coredump[633]: Removed old coredump core.lightdm-gtk-gre.620.0c8598d70403468fa1708c4c75cd5fac.3476.1509568120000000.lz4.
Nov 01 21:15:23 kirstine lightdm[623]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Nov 01 21:15:23 kirstine systemd-coredump[633]: Process 626 (lightdm-gtk-gre) of user 620 dumped core.
                                                
                                                Stack trace of thread 626:
                                                #0  0x00007f9e3f8b48a0 raise (libc.so.6)
                                                #1  0x00007f9e3f8b5f09 abort (libc.so.6)
                                                #2  0x00007f9e40978c06 g_assertion_message (libglib-2.0.so.0)
                                                #3  0x00007f9e4097b774 g_assertion_message_error (libglib-2.0.so.0)
                                                #4  0x00007f9e41c682f1 n/a (libgtk-3.so.0)
                                                #5  0x00007f9e41c68a45 n/a (libgtk-3.so.0)
                                                #6  0x00007f9e41c68b96 n/a (libgtk-3.so.0)
                                                #7  0x00007f9e41c68d98 n/a (libgtk-3.so.0)
                                                #8  0x00007f9e41c7ca1f n/a (libgtk-3.so.0)
                                                #9  0x00007f9e41bdccc3 n/a (libgtk-3.so.0)
                                                #10 0x00007f9e41be0f12 n/a (libgtk-3.so.0)
                                                #11 0x00007f9e41c7d1d4 n/a (libgtk-3.so.0)
                                                #12 0x00007f9e41d4a311 n/a (libgtk-3.so.0)
                                                #13 0x00007f9e41d4a5ac n/a (libgtk-3.so.0)
                                                #14 0x00007f9e41d49a01 gtk_widget_get_preferred_height (libgtk-3.so.0)
                                                #15 0x00007f9e41cbc693 n/a (libgtk-3.so.0)
                                                #16 0x00007f9e41bdccc3 n/a (libgtk-3.so.0)
                                                #17 0x00007f9e41be0f12 n/a (libgtk-3.so.0)
                                                #18 0x00007f9e41cbc3b7 n/a (libgtk-3.so.0)
                                                #19 0x00007f9e41d49d0d n/a (libgtk-3.so.0)
                                                #20 0x00007f9e41d4a5ac n/a (libgtk-3.so.0)
                                                #21 0x00007f9e41d4a8b5 gtk_widget_get_preferred_height_and_baseline_for_width (libgtk-3.so.0)
                                                #22 0x00007f9e41cb9af5 n/a (libgtk-3.so.0)
                                                #23 0x00007f9e41bdccc3 n/a (libgtk-3.so.0)
                                                #24 0x00007f9e41be0f12 n/a (libgtk-3.so.0)
                                                #25 0x00007f9e41cba1b7 n/a (libgtk-3.so.0)
                                                #26 0x00007f9e41d49d0d n/a (libgtk-3.so.0)
                                                #27 0x00007f9e41d4a5ac n/a (libgtk-3.so.0)
                                                #28 0x00007f9e41d4a8b5 gtk_widget_get_preferred_height_and_baseline_for_width (libgtk-3.so.0)
                                                #29 0x00007f9e41d4a311 n/a (libgtk-3.so.0)
                                                #30 0x00007f9e41d4a5ac n/a (libgtk-3.so.0)
                                                #31 0x00007f9e41d4a8b5 gtk_widget_get_preferred_height_and_baseline_for_width (libgtk-3.so.0)
                                                #32 0x00007f9e41d4a9fc n/a (libgtk-3.so.0)
                                                #33 0x00007f9e41cdd349 n/a (libgtk-3.so.0)
                                                #34 0x00007f9e41ca6671 n/a (libgtk-3.so.0)
                                                #35 0x00007f9e40c536f5 g_closure_invoke (libgobject-2.0.so.0)
                                                #36 0x00007f9e40c66ae2 n/a (libgobject-2.0.so.0)
                                                #37 0x00007f9e40c6aefe g_signal_emit_valist (libgobject-2.0.so.0)
                                                #38 0x00007f9e40c6c920 g_signal_emit (libgobject-2.0.so.0)
                                                #39 0x00007f9e41cdd995 n/a (libgtk-3.so.0)
                                                #40 0x00007f9e41cdda88 n/a (libgtk-3.so.0)
                                                #41 0x00007f9e41cddb86 n/a (libgtk-3.so.0)
                                                #42 0x00007f9e40c6bc01 g_signal_emit_valist (libgobject-2.0.so.0)
                                                #43 0x00007f9e40c6c920 g_signal_emit (libgobject-2.0.so.0)
                                                #44 0x00007f9e41e0747c gtk_widget_realize (libgtk-3.so.0)
                                                #45 0x00007f9e41e0ae79 gtk_widget_set_parent (libgtk-3.so.0)
                                                #46 0x00007f9e41b8412c n/a (libgtk-3.so.0)
                                                #47 0x00007f9e40c51e0a g_cclosure_marshal_VOID__OBJECTv (libgobject-2.0.so.0)
                                                #48 0x00007f9e40c6bc01 g_signal_emit_valist (libgobject-2.0.so.0)
                                                #49 0x00007f9e40c6c920 g_signal_emit (libgobject-2.0.so.0)
                                                #50 0x00007f9e41bd5616 gtk_container_add (libgtk-3.so.0)
                                                #51 0x000056360319e8fb n/a (lightdm-gtk-greeter)
                                                #52 0x00005636031a0948 greeter_background_connect (lightdm-gtk-greeter)
                                                #53 0x0000563603198b34 main (lightdm-gtk-greeter)
                                                #54 0x00007f9e3f8a0f6a __libc_start_main (libc.so.6)
                                                #55 0x0000563603199e8a _start (lightdm-gtk-greeter)
                                                
                                                Stack trace of thread 627:
                                                #0  0x00007f9e3f96bd4b __poll (libc.so.6)
                                                #1  0x00007f9e40984ed3 n/a (libglib-2.0.so.0)
                                                #2  0x00007f9e40984fae g_main_context_iteration (libglib-2.0.so.0)
                                                #3  0x00007f9e40985002 n/a (libglib-2.0.so.0)
                                                #4  0x00007f9e409791eb n/a (libglib-2.0.so.0)
                                                #5  0x00007f9e3fc3e08a start_thread (libpthread.so.0)
                                                #6  0x00007f9e3f97624f __clone (libc.so.6)
-- Subject: Process 626 (lightdm-gtk-gre) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 626 (lightdm-gtk-gre) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Nov 01 21:15:23 kirstine kernel: nvidia-modeset: Freed GPU:0 (GPU-2b9cecb2-ef44-9cd4-7497-3deb42ef0869) @ PCI:0000:01:00.0

Shed any light?

The VGA console nvidia thing at the top looks interesting, I'm going to try and google that first up - if you have clearer insights = please feel free to share them!

Offline

#10 2017-11-01 21:39:55

seth
Member
Registered: 2012-09-03
Posts: 51,213

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

I'd rather worry about the greeter crash.
Do you have a custom /etc/lightdm/lightdm-gtk-greeter.conf ?

https://wiki.archlinux.org/index.php/GR … ramebuffer

Offline

#11 2017-11-01 21:49:57

phunni
Member
From: Bristol, UK
Registered: 2003-08-13
Posts: 770

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

seth wrote:

I'd rather worry about the greeter crash.
Do you have a custom /etc/lightdm/lightdm-gtk-greeter.conf ?

https://wiki.archlinux.org/index.php/GR … ramebuffer

Not really, there's an example above which is what I'm using - except that I've since commented out the theme related stuff, so I'm only specifying a background.

I've tried changing to the WebKit greeter and that will start and allow me to log in. If, however, I then go into XFCE (which is what my wife uses) all the icons are missing...

Edit:  Logging as myself and into Openbox (which seemed to work) I started gimp and, when I tried to open an image, I was greeted with an error about png not being supported.  This rang a vague bell with some of the lightdm messages as well.  I then went to start my terminal emulator (terminator) and it didn't start, so I started it from a different terminal and it failed to load complaining about pngs and pixbufs.  I'm beginning to think that this whole problem has been caused by something breaking support for various image formats - possibly just png - which are ubiquitous enough for me to believe that would break some things fairly badly.

I'm not sure how to investigate further.  I did quickly run "pacman -Q | grep png" and got more or less what I'd expected which was a few packages for both lib32 and 64 bit.

Last edited by phunni (2017-11-01 22:00:56)

Offline

#12 2017-11-01 22:03:00

seth
Member
Registered: 2012-09-03
Posts: 51,213

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

Probably what knocks out the greeter as well?

pacman -Qkk adwaita-icon-theme

Offline

#13 2017-11-07 18:41:41

phunni
Member
From: Bristol, UK
Registered: 2003-08-13
Posts: 770

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

adwaita-icon-theme: 5647 total files, 0 altered files

Although that might be a red herring since I've tweaked the icon theme in use while trying to figure out what's wrong with the greeter.  It does look like some fundamental thing (such as a corrupted cache of some sort) has broken support for certain image files...

Edit: here's what my wife's desktop looks like now:  https://i.imgur.com/qO0LGhE.png

There should be icons in the bar at the bottom (although they still work if you click on them - assuming you can remember which action was where!) and there should also be some images at the top to show system stats.

Last edited by x33a (2017-11-07 19:18:46)

Offline

#14 2017-11-07 19:19:43

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

Hi phunni, you are an old enough member to know the rules around posting images: https://wiki.archlinux.org/index.php/Co … s_and_code

I have edited the image link for you.

Offline

#15 2017-11-07 19:37:15

phunni
Member
From: Bristol, UK
Registered: 2003-08-13
Posts: 770

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

x33a wrote:

Hi phunni, you are an old enough member to know the rules around posting images: https://wiki.archlinux.org/index.php/Co … s_and_code

I have edited the image link for you.

You're quite right - my apologies. Thanks for fixing it.

Offline

#16 2017-11-07 21:49:50

seth
Member
Registered: 2012-09-03
Posts: 51,213

Re: Can't get lightdm to start any more (previously "Can't get X to ...")

Does the icon view demo in gtk-demo work?
If not,

strace gtk-demo 2>&1 | grep icon > ~/wtf.txt

(it's likely gonna be some text ...)

Offline

Board footer

Powered by FluxBB