You are not logged in.

Pages: 1 2

#1 2013-07-25 02:43:08

nef131
Member
Registered: 2013-07-24
Posts: 23

[SOLVED] Display manager

I am new to Arch. I have installed Arch, X, Mate (as the DE) and Lightdm as the display manager.  Lightdm will only start in X, with the sudo lightdm command. From there, you can get into Mate.

Mate seems to work just fine. However, it would be nice to be able to boot successfully to a display manager and then into a desktop environment.

Before Lightdm, I had installed gdm with xfce. Gdm starts up properly but will not properly start either xfce or Mate. Gdm goes to a screen that is akin to the login screen but with nothing else. I just tried slim, which will not start up, either on boot up or from x.

I am not sure what to post for logs on this. In any event, my computer is an old Dell Dimension 2400, with a pentium 4 processor, intel graphics and 2 gb of memory. I am not sure what log would be helpful here but, if someone could help me with my issue, it would be appreciated.

My x-0-greeter.log reads:

** (process:290): 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

(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_shell_parse_argv: assertion `command_line != NULL' failed

** (lightdm-gtk-greeter:331): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory

** (lightdm-gtk-greeter:331): WARNING **: Failed to load user image: Failed to open file '/home/allen/.face': Permission denied

** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XKeyboardLayouts

** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XHasMessages

(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed

(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed

(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed

** (lightdm-gtk-greeter:331): WARNING **: Unexpected accounts property type for XHasMessages: (null)

(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed

** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XKeyboardLayouts

** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XHasMessages

(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed

(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed

(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed

** (lightdm-gtk-greeter:331): WARNING **: Unexpected accounts property type for XHasMessages: (null)

(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed

That seems to include some errors. The x-0.log reads:

X.Org X Server 1.14.2
Release Date: 2013-06-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.9.7-1-ARCH i686 
Current Operating System: Linux archbox 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:52:05 CEST 2013 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5eec6b5e-dd19-4f9d-8e3b-39b950052c48 ro quiet
Build Date: 01 July 2013  10:52:25AM
 
Current version of pixman: 0.30.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 24 22:13:55 2013
(==) Using config directory: "/etc/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(II) AIGLX: Suspending AIGLX clients for VT switch
setversion 1.4 failed

The lightdm.log reads:

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=532
[+0.00s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Using Xephyr for X servers
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Adding default seat
[+0.00s] DEBUG: Starting seat
[+0.00s] DEBUG: Starting new display for greeter
[+0.00s] DEBUG: Starting local X display
[+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.02s] DEBUG: Using VT 7
[+0.02s] DEBUG: Activating VT 7
[+0.03s] DEBUG: Logging to /var/log/lightdm/x-2.log
[+0.03s] DEBUG: Writing X server authority to /run/lightdm/root/:2
[+0.03s] DEBUG: Launching X Server
[+0.03s] DEBUG: Launching process 536: /usr/bin/Xephyr :2 -auth /run/lightdm/root/:2 -nolisten tcp vt7 -novtswitch
[+0.06s] DEBUG: Waiting for ready signal from X server :2
[+0.06s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.06s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0

The log from slim reads:

slim: waiting for X server to begin accepting connections.
slim: pam_authentication(): Authentication failure

slim: waiting for X server to shut down



slim: waiting for X server to begin accepting connections.

The xorg.0.log reads:

[     6.928] 
X.Org X Server 1.14.2
Release Date: 2013-06-25
[     6.928] X Protocol Version 11, Revision 0
[     6.928] Build Operating System: Linux 3.9.7-1-ARCH i686 
[     6.928] Current Operating System: Linux archbox 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:52:05 CEST 2013 i686
[     6.929] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5eec6b5e-dd19-4f9d-8e3b-39b950052c48 ro quiet
[     6.929] Build Date: 01 July 2013  10:52:25AM
[     6.929]  
[     6.929] Current version of pixman: 0.30.0
[     6.929] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     6.929] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     6.929] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 24 22:13:55 2013
[     6.958] (==) Using config directory: "/etc/X11/xorg.conf.d"
[     6.978] (==) No Layout section.  Using the first Screen section.
[     6.978] (==) No screen section available. Using defaults.
[     6.978] (**) |-->Screen "Default Screen Section" (0)
[     6.978] (**) |   |-->Monitor "<default monitor>"
[     6.985] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[     6.985] (==) Automatically adding devices
[     6.985] (==) Automatically enabling devices
[     6.985] (==) Automatically adding GPU devices
[     7.000] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[     7.000] 	Entry deleted from font path.
[     7.000] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[     7.000] 	Entry deleted from font path.
[     7.000] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[     7.000] 	Entry deleted from font path.
[     7.000] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[     7.000] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[     7.000] 	Entry deleted from font path.
[     7.000] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[     7.000] (==) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/
[     7.000] (==) ModulePath set to "/usr/lib/xorg/modules"
[     7.000] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     7.005] (II) Loader magic: 0x8258620
[     7.005] (II) Module ABI versions:
[     7.005] 	X.Org ANSI C Emulation: 0.4
[     7.005] 	X.Org Video Driver: 14.1
[     7.005] 	X.Org XInput driver : 19.1
[     7.005] 	X.Org Server Extension : 7.0
[     7.006] (II) xfree86: Adding drm device (/dev/dri/card0)
[     7.007] (--) PCI:*(0:0:2:0) 8086:2562:1028:0160 rev 1, Mem @ 0xe8000000/134217728, 0xfeb80000/524288
[     7.008] Initializing built-in extension Generic Event Extension
[     7.008] Initializing built-in extension SHAPE
[     7.008] Initializing built-in extension MIT-SHM
[     7.008] Initializing built-in extension XInputExtension
[     7.008] Initializing built-in extension XTEST
[     7.008] Initializing built-in extension BIG-REQUESTS
[     7.008] Initializing built-in extension SYNC
[     7.008] Initializing built-in extension XKEYBOARD
[     7.008] Initializing built-in extension XC-MISC
[     7.008] Initializing built-in extension SECURITY
[     7.008] Initializing built-in extension XINERAMA
[     7.008] Initializing built-in extension XFIXES
[     7.008] Initializing built-in extension RENDER
[     7.008] Initializing built-in extension RANDR
[     7.008] Initializing built-in extension COMPOSITE
[     7.008] Initializing built-in extension DAMAGE
[     7.008] Initializing built-in extension MIT-SCREEN-SAVER
[     7.008] Initializing built-in extension DOUBLE-BUFFER
[     7.008] Initializing built-in extension RECORD
[     7.008] Initializing built-in extension DPMS
[     7.008] Initializing built-in extension X-Resource
[     7.008] Initializing built-in extension XVideo
[     7.008] Initializing built-in extension XVideo-MotionCompensation
[     7.008] Initializing built-in extension XFree86-VidModeExtension
[     7.008] Initializing built-in extension XFree86-DGA
[     7.008] Initializing built-in extension XFree86-DRI
[     7.008] Initializing built-in extension DRI2
[     7.008] (II) LoadModule: "glx"
[     7.027] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     7.042] (II) Module glx: vendor="X.Org Foundation"
[     7.042] 	compiled for 1.14.2, module version = 1.0.0
[     7.042] 	ABI class: X.Org Server Extension, version 7.0
[     7.042] (==) AIGLX enabled
[     7.042] Loading extension GLX
[     7.042] (==) Matched intel as autoconfigured driver 0
[     7.042] (==) Matched intel as autoconfigured driver 1
[     7.042] (==) Matched vesa as autoconfigured driver 2
[     7.042] (==) Matched modesetting as autoconfigured driver 3
[     7.043] (==) Matched fbdev as autoconfigured driver 4
[     7.043] (==) Assigned the driver to the xf86ConfigLayout
[     7.043] (II) LoadModule: "intel"
[     7.044] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[     7.098] (II) Module intel: vendor="X.Org Foundation"
[     7.098] 	compiled for 1.14.2, module version = 2.21.12
[     7.098] 	Module class: X.Org Video Driver
[     7.098] 	ABI class: X.Org Video Driver, version 14.1
[     7.098] (II) LoadModule: "vesa"
[     7.098] (WW) Warning, couldn't open module vesa
[     7.098] (II) UnloadModule: "vesa"
[     7.098] (II) Unloading vesa
[     7.098] (EE) Failed to load module "vesa" (module does not exist, 0)
[     7.098] (II) LoadModule: "modesetting"
[     7.099] (WW) Warning, couldn't open module modesetting
[     7.099] (II) UnloadModule: "modesetting"
[     7.099] (II) Unloading modesetting
[     7.099] (EE) Failed to load module "modesetting" (module does not exist, 0)
[     7.099] (II) LoadModule: "fbdev"
[     7.099] (WW) Warning, couldn't open module fbdev
[     7.099] (II) UnloadModule: "fbdev"
[     7.099] (II) Unloading fbdev
[     7.099] (EE) Failed to load module "fbdev" (module does not exist, 0)
[     7.099] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
	i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
	E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
	965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
	4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
	Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
	Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
	Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
	Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
	Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
	Ivybridge Server (GT2), HD Graphics, HD Graphics 4600,
	Haswell Desktop (GT3), HD Graphics, HD Graphics 4600,
	Haswell Mobile (GT3), HD Graphics, HD Graphics P4600/P4700,
	Haswell Server (GT3), Haswell (GT1), Haswell (GT2), Haswell (GT3),
	HD Graphics, Haswell (GT2), Haswell (GT3), Haswell SDV Desktop (GT1),
	Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT3),
	Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
	Haswell SDV Mobile (GT3), Haswell SDV Server (GT1),
	Haswell SDV Server (GT2), Haswell SDV Server (GT3),
	Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
	Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
	Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
	Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4400,
	HD Graphics 5000, Haswell ULT Server (GT1), Haswell ULT Server (GT2),
	Iris(TM) Graphics 5100, Haswell ULT (GT1), Haswell ULT (GT2),
	Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4200,
	Iris(TM) Graphics 5100, Haswell CRW Desktop (GT1), HD Graphics 4600,
	Iris(TM) Pro Graphics 5200, Haswell CRW Mobile (GT1),
	HD Graphics 4600, Iris(TM) Pro Graphics 5200,
	Haswell CRW Server (GT1), Haswell CRW Server (GT2),
	Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
	Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
	Iris(TM) Pro Graphics 5200, ValleyView PO board
[     7.101] (++) using VT number 7

[     7.101] (II) intel(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[     7.101] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[     7.101] (==) intel(0): RGB weight 888
[     7.101] (==) intel(0): Default visual is TrueColor
[     7.101] (--) intel(0): Integrated Graphics Chipset: Intel(R) 845G
[     7.101] (**) intel(0): Relaxed fencing disabled
[     7.102] (**) intel(0): Wait on SwapBuffers? enabled
[     7.102] (**) intel(0): Triple buffering? enabled
[     7.102] (**) intel(0): Framebuffer tiled
[     7.102] (**) intel(0): Pixmaps tiled
[     7.102] (**) intel(0): 3D buffers tiled
[     7.102] (**) intel(0): SwapBuffers wait enabled
[     7.103] (==) intel(0): video overlay key set to 0x101fe
[     7.303] (II) intel(0): Output VGA1 has no monitor section
[     7.443] (II) intel(0): EDID for output VGA1
[     7.443] (II) intel(0): Manufacturer: DEL  Model: 3142  Serial#: 894121267
[     7.443] (II) intel(0): Year: 1999  Week: 29
[     7.443] (II) intel(0): EDID Version: 1.2
[     7.443] (II) intel(0): Analog Display Input,  Input Voltage Level: 0.700/0.300 V
[     7.443] (II) intel(0): Sync:  Separate
[     7.443] (II) intel(0): Max Image Size [cm]: horiz.: 32  vert.: 24
[     7.443] (II) intel(0): Gamma: 2.27
[     7.443] (II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[     7.443] (II) intel(0): First detailed timing is preferred mode
[     7.443] (II) intel(0): redX: 0.645 redY: 0.321   greenX: 0.285 greenY: 0.600
[     7.443] (II) intel(0): blueX: 0.142 blueY: 0.057   whiteX: 0.283 whiteY: 0.298
[     7.443] (II) intel(0): Supported established timings:
[     7.443] (II) intel(0): 720x400@70Hz
[     7.443] (II) intel(0): 640x480@60Hz
[     7.443] (II) intel(0): 640x480@75Hz
[     7.443] (II) intel(0): 800x600@60Hz
[     7.443] (II) intel(0): 800x600@75Hz
[     7.443] (II) intel(0): 1024x768@60Hz
[     7.443] (II) intel(0): 1024x768@75Hz
[     7.443] (II) intel(0): 1280x1024@75Hz
[     7.443] (II) intel(0): Manufacturer's mask: 0
[     7.443] (II) intel(0): Supported standard timings:
[     7.443] (II) intel(0): #0: hsize: 1024  vsize 768  refresh: 85  vid: 22881
[     7.443] (II) intel(0): #1: hsize: 800  vsize 600  refresh: 85  vid: 22853
[     7.443] (II) intel(0): #2: hsize: 640  vsize 480  refresh: 85  vid: 22833
[     7.443] (II) intel(0): Supported detailed timing:
[     7.443] (II) intel(0): clock: 94.5 MHz   Image Size:  306 x 230 mm
[     7.444] (II) intel(0): h_active: 1024  h_sync: 1072  h_sync_end 1168 h_blank_end 1376 h_border: 0
[     7.444] (II) intel(0): v_active: 768  v_sync: 769  v_sync_end 772 v_blanking: 808 v_border: 0
[     7.444] (II) intel(0): Serial No: 5322DE5K5379
[     7.444] (II) intel(0): Monitor name: DELL M780
[     7.444] (II) intel(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 85 kHz,
[     7.444] (II) intel(0): EDID (in hex):
[     7.444] (II) intel(0): 	00ffffffffffff0010ac423133354b35
[     7.444] (II) intel(0): 	1d0901020820187fea1269a552499924
[     7.444] (II) intel(0): 	0e484ca54b0061594559315901010101
[     7.444] (II) intel(0): 	010101010101ea240060410028303060
[     7.444] (II) intel(0): 	130032e61000001e000000ff00353332
[     7.444] (II) intel(0): 	324445354b353337390a000000fc0044
[     7.444] (II) intel(0): 	454c4c204d3738300a202020000000fd
[     7.444] (II) intel(0): 	0032a01e55ff000a20202020202000e3
[     7.444] (II) intel(0): Printing probed modes for output VGA1
[     7.444] (II) intel(0): Modeline "1024x768"x85.0   94.50  1024 1072 1168 1376  768 769 772 808 +hsync +vsync (68.7 kHz eP)
[     7.444] (II) intel(0): Modeline "1280x1024"x75.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[     7.444] (II) intel(0): Modeline "1024x768"x75.1   78.80  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.1 kHz e)
[     7.444] (II) intel(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[     7.444] (II) intel(0): Modeline "800x600"x85.1   56.25  800 832 896 1048  600 601 604 631 +hsync +vsync (53.7 kHz e)
[     7.444] (II) intel(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[     7.444] (II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[     7.444] (II) intel(0): Modeline "640x480"x85.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz e)
[     7.444] (II) intel(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[     7.444] (II) intel(0): Modeline "640x480"x60.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[     7.444] (II) intel(0): Modeline "720x400"x70.1   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[     7.444] (II) intel(0): Output VGA1 connected
[     7.444] (II) intel(0): Using exact sizes for initial modes
[     7.444] (II) intel(0): Output VGA1 using initial mode 1024x768
[     7.444] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[     7.444] (II) intel(0): Kernel page flipping support detected, enabling
[     7.444] (==) intel(0): DPI set to (96, 96)
[     7.444] (II) Loading sub module "fb"
[     7.444] (II) LoadModule: "fb"
[     7.444] (II) Loading /usr/lib/xorg/modules/libfb.so
[     7.458] (II) Module fb: vendor="X.Org Foundation"
[     7.458] 	compiled for 1.14.2, module version = 1.0.0
[     7.458] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     7.458] (II) Loading sub module "dri2"
[     7.458] (II) LoadModule: "dri2"
[     7.458] (II) Module "dri2" already built-in
[     7.458] (==) Depth 24 pixmap format is 32 bpp
[     7.466] (II) intel(0): [DRI2] Setup complete
[     7.466] (II) intel(0): [DRI2]   DRI driver: i915
[     7.466] (II) intel(0): Allocated new frame buffer 1024x768 stride 4096, tiled
[     7.478] (II) UXA(0): Driver registered support for the following operations:
[     7.478] (II)         solid
[     7.478] (II)         copy
[     7.478] (II)         composite (RENDER acceleration)
[     7.478] (II)         put_image
[     7.478] (II)         get_image
[     7.478] (==) intel(0): Backing store disabled
[     7.478] (==) intel(0): Silken mouse enabled
[     7.478] (II) intel(0): Initializing HW Cursor
[     7.478] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[     7.480] (==) intel(0): DPMS enabled
[     7.480] (==) intel(0): Intel XvMC decoder disabled
[     7.480] (II) intel(0): Set up overlay video
[     7.480] (II) intel(0): direct rendering: DRI2 Enabled
[     7.480] (==) intel(0): hotplug detection: "enabled"
[     7.540] (--) RandR disabled
[     7.689] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[     7.689] (II) AIGLX: enabled GLX_INTEL_swap_event
[     7.689] (II) AIGLX: enabled GLX_ARB_create_context
[     7.689] (II) AIGLX: enabled GLX_ARB_create_context_profile
[     7.689] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[     7.689] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[     7.689] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[     7.689] (II) AIGLX: Loaded and initialized i915
[     7.689] (II) GLX: Initialized DRI2 GL provider for screen 0
[     7.690] (II) intel(0): Setting screen physical size to 270 x 203
[     7.924] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[     7.924] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[     7.924] (II) LoadModule: "evdev"
[     7.925] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[     7.943] (II) Module evdev: vendor="X.Org Foundation"
[     7.943] 	compiled for 1.14.2, module version = 2.8.1
[     7.943] 	Module class: X.Org XInput Driver
[     7.943] 	ABI class: X.Org XInput driver, version 19.1
[     7.943] (II) Using input driver 'evdev' for 'Power Button'
[     7.943] (**) Power Button: always reports core events
[     7.943] (**) evdev: Power Button: Device: "/dev/input/event3"
[     7.943] (--) evdev: Power Button: Vendor 0 Product 0x1
[     7.943] (--) evdev: Power Button: Found keys
[     7.943] (II) evdev: Power Button: Configuring as keyboard
[     7.943] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[     7.943] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     7.943] (**) Option "xkb_rules" "evdev"
[     7.943] (**) Option "xkb_model" "pc104"
[     7.943] (**) Option "xkb_layout" "us"
[     7.980] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[     7.980] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[     7.980] (II) Using input driver 'evdev' for 'Power Button'
[     7.980] (**) Power Button: always reports core events
[     7.980] (**) evdev: Power Button: Device: "/dev/input/event2"
[     7.980] (--) evdev: Power Button: Vendor 0 Product 0x1
[     7.980] (--) evdev: Power Button: Found keys
[     7.980] (II) evdev: Power Button: Configuring as keyboard
[     7.981] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2"
[     7.981] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[     7.981] (**) Option "xkb_rules" "evdev"
[     7.981] (**) Option "xkb_model" "pc104"
[     7.981] (**) Option "xkb_layout" "us"
[     7.981] (II) config/udev: Adding drm device (/dev/dri/card0)
[     7.982] (II) config/udev: Adding input device OM (/dev/input/event1)
[     7.982] (**) OM: Applying InputClass "evdev pointer catchall"
[     7.982] (II) Using input driver 'evdev' for 'OM'
[     7.982] (**) OM: always reports core events
[     7.982] (**) evdev: OM: Device: "/dev/input/event1"
[     7.982] (--) evdev: OM: Vendor 0x4f3 Product 0x232
[     7.982] (--) evdev: OM: Found 3 mouse buttons
[     7.982] (--) evdev: OM: Found scroll wheel(s)
[     7.982] (--) evdev: OM: Found relative axes
[     7.982] (--) evdev: OM: Found x and y relative axes
[     7.982] (II) evdev: OM: Configuring as mouse
[     7.982] (II) evdev: OM: Adding scrollwheel support
[     7.982] (**) evdev: OM: YAxisMapping: buttons 4 and 5
[     7.982] (**) evdev: OM: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[     7.982] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/input/input1/event1"
[     7.982] (II) XINPUT: Adding extended input device "OM" (type: MOUSE, id 8)
[     7.982] (II) evdev: OM: initialized for relative axes.
[     7.983] (**) OM: (accel) keeping acceleration scheme 1
[     7.983] (**) OM: (accel) acceleration profile 0
[     7.983] (**) OM: (accel) acceleration factor: 2.000
[     7.983] (**) OM: (accel) acceleration threshold: 4
[     7.983] (II) config/udev: Adding input device OM (/dev/input/mouse0)
[     7.983] (II) No input driver specified, ignoring this device.
[     7.983] (II) This device may have been added with another device file.
[     7.984] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[     7.984] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[     7.984] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[     7.984] (**) AT Translated Set 2 keyboard: always reports core events
[     7.984] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[     7.984] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[     7.984] (--) evdev: AT Translated Set 2 keyboard: Found keys
[     7.984] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[     7.984] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[     7.984] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[     7.984] (**) Option "xkb_rules" "evdev"
[     7.984] (**) Option "xkb_model" "pc104"
[     7.984] (**) Option "xkb_layout" "us"
[     7.985] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[     7.985] (II) No input driver specified, ignoring this device.
[     7.985] (II) This device may have been added with another device file.
[    29.826] (II) AIGLX: Suspending AIGLX clients for VT switch
[    53.275] (II) AIGLX: Resuming AIGLX clients after VT switch
[    53.426] (II) intel(0): EDID vendor "DEL", prod id 12610
[    53.427] (II) intel(0): Using EDID range info for horizontal sync
[    53.427] (II) intel(0): Using EDID range info for vertical refresh
[    53.427] (II) intel(0): Printing DDC gathered Modelines:
[    53.427] (II) intel(0): Modeline "1024x768"x0.0   94.50  1024 1072 1168 1376  768 769 772 808 +hsync +vsync (68.7 kHz eP)
[    53.427] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    53.427] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    53.427] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    53.427] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    53.427] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    53.427] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    53.427] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    53.427] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    53.427] (II) intel(0): Modeline "800x600"x0.0   56.25  800 832 896 1048  600 601 604 631 +hsync +vsync (53.7 kHz e)
[    53.427] (II) intel(0): Modeline "640x480"x0.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz e)
[    53.433] setversion 1.4 failed
[    57.450] (II) intel(0): EDID vendor "DEL", prod id 12610
[    57.450] (II) intel(0): Using hsync ranges from config file
[    57.450] (II) intel(0): Using vrefresh ranges from config file
[    57.450] (II) intel(0): Printing DDC gathered Modelines:
[    57.450] (II) intel(0): Modeline "1024x768"x0.0   94.50  1024 1072 1168 1376  768 769 772 808 +hsync +vsync (68.7 kHz eP)
[    57.450] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    57.450] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    57.450] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    57.450] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    57.450] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    57.450] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    57.450] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    57.450] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    57.450] (II) intel(0): Modeline "800x600"x0.0   56.25  800 832 896 1048  600 601 604 631 +hsync +vsync (53.7 kHz e)
[    57.450] (II) intel(0): Modeline "640x480"x0.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz e)
[    57.590] (II) intel(0): EDID vendor "DEL", prod id 12610
[    57.590] (II) intel(0): Using hsync ranges from config file
[    57.590] (II) intel(0): Using vrefresh ranges from config file
[    57.590] (II) intel(0): Printing DDC gathered Modelines:
[    57.590] (II) intel(0): Modeline "1024x768"x0.0   94.50  1024 1072 1168 1376  768 769 772 808 +hsync +vsync (68.7 kHz eP)
[    57.590] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    57.590] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    57.590] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    57.590] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    57.590] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    57.590] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    57.590] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    57.590] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    57.590] (II) intel(0): Modeline "800x600"x0.0   56.25  800 832 896 1048  600 601 604 631 +hsync +vsync (53.7 kHz e)
[    57.590] (II) intel(0): Modeline "640x480"x0.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz e)
[    57.763] (II) intel(0): EDID vendor "DEL", prod id 12610
[    57.763] (II) intel(0): Using hsync ranges from config file
[    57.763] (II) intel(0): Using vrefresh ranges from config file
[    57.763] (II) intel(0): Printing DDC gathered Modelines:
[    57.763] (II) intel(0): Modeline "1024x768"x0.0   94.50  1024 1072 1168 1376  768 769 772 808 +hsync +vsync (68.7 kHz eP)
[    57.763] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    57.763] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    57.763] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    57.763] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    57.763] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    57.763] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    57.763] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    57.763] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    57.763] (II) intel(0): Modeline "800x600"x0.0   56.25  800 832 896 1048  600 601 604 631 +hsync +vsync (53.7 kHz e)
[    57.763] (II) intel(0): Modeline "640x480"x0.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz e)
[    57.903] (II) intel(0): EDID vendor "DEL", prod id 12610
[    57.903] (II) intel(0): Using hsync ranges from config file
[    57.903] (II) intel(0): Using vrefresh ranges from config file
[    57.903] (II) intel(0): Printing DDC gathered Modelines:
[    57.903] (II) intel(0): Modeline "1024x768"x0.0   94.50  1024 1072 1168 1376  768 769 772 808 +hsync +vsync (68.7 kHz eP)
[    57.903] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    57.903] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    57.903] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    57.903] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    57.903] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    57.903] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    57.903] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    57.903] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    57.903] (II) intel(0): Modeline "800x600"x0.0   56.25  800 832 896 1048  600 601 604 631 +hsync +vsync (53.7 kHz e)
[    57.903] (II) intel(0): Modeline "640x480"x0.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz e)

No doubt I have missed the pertinent log.

Last edited by nef131 (2013-07-31 12:47:23)

Offline

#2 2013-07-25 02:54:57

Oxyd
Member
From: Czech Republic
Registered: 2008-01-17
Posts: 167

Re: [SOLVED] Display manager

nef131 wrote:

Lightdm will only start in X, with the sudo lightdm command. From there, you can get into Mate.

Mate seems to work just fine. However, it would be nice to be able to boot successfully to a display manager and then into a desktop environment.

“sudo systemctl enable lightdm.service” should make LightDM start on boot and allow you to log in.

nef131 wrote:

Before Lightdm, I had installed gdm with xfce. Gdm starts up properly but will not properly start either xfce or Mate. Gdm goes to a screen that is akin to the login screen but with nothing else.

“Akin to login screen”? smile What does that look like? If it is a login screen, what happens when you type your username and password? If it isn't a login screen, what is it?

Offline

#3 2013-07-25 06:08:42

shmibs
Member
Registered: 2012-09-11
Posts: 93
Website

Re: [SOLVED] Display manager

if all you're going to do with this machine is boot directly into a single environment, and you don't have any need for theatrics, you'd be better off without a display manager at all. if you copy /etc/skel/.bash_profile to ~/.bash_profile, paste this line:

[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx

into the very end of it, and then create a file called ~/.xinitrc containing only this line:

exec mate-session

you will be automatically sent into a mate session as soon as you log in at the first console (you can still log into others normally) without any of the hassle of waiting for lightdm to start up.
(wiki source)

[site] | [dotfiles] | あたしたち、人間じゃないの？

Offline

#4 2013-07-25 11:22:52

nef131
Member
Registered: 2013-07-24
Posts: 23

Re: [SOLVED] Display manager

Oxyd,

Thank you for your reply. I should have noted in my original post that I enabled lightdm. Please note that I received an error message (which, if I recall, reads, that the file already exists) on enabling so I used "sudo systemctl -f enable lightdm" which enables it, so far as I can tell. The same thing happens with gdm, by the way, and it, as I noted, starts up upon booting. It just does not reach Mate or xcfe.

In answer to your question, the screen for gdm is a normal login screen. It shows the user name, which you click on, then you type in your password. After that, you get the same page, only with nothing on it. The page is plain gray.


shmibs,

Thank you for your idea. I really wanted to be able to have a greeter. However, if all else fails, I shall follow your suggestion.

Offline

#5 2013-07-25 12:19:07

nef131
Member
Registered: 2013-07-24
Posts: 23

Re: [SOLVED] Display manager

Never mind. I fixed it. Thanks for the help, both of you!!!

Offline

#6 2013-07-25 16:51:32

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,140

Re: [SOLVED] Display manager

@nef131,
Welcome to Arch! While I am pleased you fixed it, saying that and disappearing is really not OK on these forums because it renders this thread useless to anybody else with the same problem. What you need to do is explain how you fixed it and then to mark your thread [solved] by editing your original post and tagging the subject line. Please see the forum etiquette for further information but basically it boils down to the idea that you should contribute to the community if you expect to take from it smile.

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#7 2013-07-26 01:42:49

nef131
Member
Registered: 2013-07-24
Posts: 23

Re: [SOLVED] Display manager

cfr,

You have my apology. What I did was, re-run sudo systemctl -f enable lightdm and then, while in Mate, I ran sudo systemctl enable lightdm.

That worked until I switched to xfce. Now, I am back to square one. So, it is premature to mark this all solved.

Offline

#8 2013-07-26 02:45:45

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,140

Re: [SOLVED] Display manager

Why did you repeat it within Mate? I'm not sure I'm following this.

How many display managers do you have installed? Are you positive that you are only trying to enable and use one of them?

EDIT: Why do you need xorg-server-xephyr? You need to be much clearer about what you are trying to do and what exactly you have done. How are you trying to set things up? What commands did you use to do so? For example, what did you use to "install... X"?

Also, did you follow the Beginners' Guide and, if so, did you follow the instructions there for installing and testing X?

Last edited by cfr (2013-07-26 02:56:05)

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#9 2013-07-26 03:45:44

nef131
Member
Registered: 2013-07-24
Posts: 23

Re: [SOLVED] Display manager

cfr: "Why did you repeat it within Mate? I'm not sure I'm following this."

This was not done for a good reason. I saw the comment from Oxyd to run sudo systemctl enable lightdm. Recall that I had, in X, run sudo systemctl enable lightdm but received an error message that the file exists. I read in the guide that such occurs sometimes when changing display managers. The guide recommends to run sudo systemctl -f enable lightdm. I just thought it was possible that running the command sudo systemctl enable lightdm again, while in Mate, might somehow work.

cfr: "How many display managers do you have installed? Are you positive that you are only trying to enable and use one of them?"

I started with gdm, at the time, this last weekend, when I first installed Arch. It would not load any DE. So, I thought that I somehow did something wrong. So, that led me to try lightdm, which I familiar with from my other computers that run Ubuntu. Lightdm worked from X (sudo lightdm), as I mentioned. But, I wondered if I had done something wrong, so I tried Slim, which simply does not load at all, so far as I can tell.

Now, I think I have figured out, in my non-expert sort of way  smile , that there is a configuration problem with the lightdm greeter and that lightdm itself actually starts up. After my last post, I re-enabled lightdm, this time as previously done for Mate, but in xfce (which is the DE I actually want to use on my rather dated computer). I came to the totally blank, black screen, which previously I had thought to be a failure. This time, however, I started clicking in the center of the screen. Amazingly, there was something there after clicking a bunch of times. I, just to see what would happen, typed in my password, even though what popped up did not look like a greeter, and I entered xfce just fine.

So, for whatever reason, the greeter page does not load any background or proper menus. If you click in the center again and again, more and more of a menu (but without any information on it) and a place to type appears.

I note that if I log out of xfce, I come to a normal greeter page. But, if I thereafter reboot, I come to the blank page, from which, after I click around in the center a bit, I can enter xfce.

In answer to your other question, I do not recall why xorg-server-xephyr was installed. I am sorry that my answer sounds foolish but, presumably, it had to do with one of the things above described.

So far as how I am installing things, I am following what appears, to the letter, in the Arch guides for installing programs. Install: sudo pacman -S packagename.  Service enabling: sudo systemctl enable nameofservice.service . etc., etc., etc. I have installed some packages from aur, following the tutorial for doing so.

Lastly, when I installed Arch, I not only followed the Beginner's Guide but, before doing anything, I read it thoroughly, along with the other guides and documentation on Arch's very thorough website. I also read an outside tutorial.

Offline

#10 2013-07-26 13:02:55

nef131
Member
Registered: 2013-07-24
Posts: 23

Re: [SOLVED] Display manager

cfr: "Why do you need xorg-server-xephyr?"

I just looked back at what I did. In the ArchWiki for Lightdm, It says to do so in order to test lightdm. 

Testing

First, install xorg-server-xephyr from the official repositories.

Then, run LightDM as an X application:

$ lightdm --test-mode --debug

Offline

#11 2013-07-26 14:22:49

henk
Member
From: Weert, Netherlands
Registered: 2013-01-01
Posts: 334

Re: [SOLVED] Display manager

My suggestion to you would be to start with a clean sheet regarding your displaymanagers.
You have installed gdm, slim and lightdm, and I may presume you have enabled all the services.

First make a choice which displaymanager you really want to use.
Disable the other two services. You can go even as far as to remove them.

gdm and lightdm won't start xfce by default. You need to change their configuration files to start xfce4.
Slim uses .xinitrc to start a session. You can copy a .xinitrc file from /etc/skel to your home directory
(this can be done for both root and user) and uncomment the session you want to start.

Offline

#12 2013-07-26 18:38:54

Oxyd
Member
From: Czech Republic
Registered: 2008-01-17
Posts: 167

Re: [SOLVED] Display manager

nef131 wrote:

but in xfce (which is the DE I actually want to use on my rather dated computer). I came to the totally blank, black screen, which previously I had thought to be a failure. This time, however, I started clicking in the center of the screen. Amazingly, there was something there after clicking a bunch of times. I, just to see what would happen, typed in my password, even though what popped up did not look like a greeter, and I entered xfce just fine.

So, for whatever reason, the greeter page does not load any background or proper menus. If you click in the center again and again, more and more of a menu (but without any information on it) and a place to type appears.

I note that if I log out of xfce, I come to a normal greeter page. But, if I thereafter reboot, I come to the blank page, from which, after I click around in the center a bit, I can enter xfce.

The display manager shouldn't be affected by your DE of choice at all, until you actually submit your username and password and it attempts to launch the DE.

Can you post the output of “pacman -Qs lightdm” (i.e. which greeter(s) you have installed), “cat /etc/lightdm/lightdm.conf” and “cat /etc/lightdm/lightdm-gtk-greeter.conf”?

Last edited by Oxyd (2013-07-26 18:46:18)

Offline

#13 2013-07-26 21:05:11

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,140

Re: [SOLVED] Display manager

"I did what it said in the wiki" leaves too many questions. The wiki says lots of things.

Did you test X following the Beginners' Guide?

What commands did you use to install X according to that guide?

I second henk's suggestion: disable and stop all of the display managers you have installed (sudo systemctl disable <service>; sudo systemctl stop <service>), and uninstall the ones you don't want. Now check that you can start X OK without a display manager, using whatever DE/WM you want to use. If that works, enable the display manager of your choice, edit the config file if required and try rebooting.

I recommend uninstalling xorg-server-xephyr. I think it is just complicating things as lightdm seems to be trying to start a nested X session with it (as far as I can tell - I'm not familiar with this sort of software so my interpretation of your log might be mistaken) and I think you should go for simple, simple, simple and add complexity later if you turn out to need/want it.

I still don't know, though, whether you *need* to run nested X server. I'm assuming not given your last post but not knowing what you are really trying to do, it is difficult to be sure of this. If this is needed, try doing without it initially and adding that step later. If that's not possible for some reason obviously ignore my suggestion above about uninstalling the nesting software.

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#14 2013-07-27 05:06:45

nef131
Member
Registered: 2013-07-24
Posts: 23

Re: [SOLVED] Display manager

Oxyd,

The current state of things, after removing gdm, slim and reinstalling lightdm, is that nothing has changed. In any event, below is the results of pacman -Qs lightdm:

[allen@archbox ~]$ pacman -Qs lightdm
local/lightdm 1:1.6.0-5 (lightdm)
    A lightweight display manager
local/lightdm-gtk3-greeter 1:1.6.0-1
    GTK+ greeter for LightDM
[allen@archbox ~]$

The result of is cat /etc/lightdm/lightdm.conf:

[allen@archbox ~]$ cat /etc/lightdm/lightdm.conf
#
# 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
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# xsessions-directory = Directory to find X sessions
# remote-sessions-directory = Directory to find remote sessions
# xgreeters-directory = Directory to find X greeters
#
[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#log-directory=/var/log/lightdm
run-directory=/run/lightdm
#cache-directory=/var/cache/lightdm
#xsessions-directory=/usr/share/xsessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#xgreeters-directory=/usr/share/xgreeters

#
# Seat defaults
#
# type = Seat type (xlocal, xremote)
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xserver-layout = Layout to pass to X server
# xserver-config = Config file to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# 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)
# 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-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
# display-setup-script = Script to run when starting a greeter session (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)
# exit-on-failure = True if the daemon should exit if this seat fails
#
[SeatDefaults]
#type=xlocal
#xserver-command=X
#xserver-layout=
#xserver-config=
#xserver-allow-tcp=false
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
#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-guest=true
#guest-session=UNIMPLEMENTED
session-wrapper=/etc/lightdm/xsession
#display-setup-script=
#greeter-setup-script=
#session-setup-script=
#session-cleanup-script=
#autologin-guest=false
#autologin-user=
#autologin-user-timeout=0
#autologin-session=UNIMPLEMENTED
pam-service=lightdm-autologin
#exit-on-failure=false

#
# Seat configuration
#
# Each seat must start with "Seat:".
# Uses settings from [SeatDefaults], any of these can be overriden by setting them in this section.
#
#[Seat:0]

#
# XDMCP Server configuration
#
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
#
# 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
#key=

#
# 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
# 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
#width=1024
#height=768
#depth=8

The result of cat /etc/lightdm/lightdm-gtk-greeter.conf is :

[allen@archbox ~]$ cat /etc/lightdm/lightdm-gtk-greeter.conf
#
# background = Background file to use, either an image path or a color (e.g. #772953)
# theme-name = GTK+ theme to use
# icon-theme-name = Icon theme to use
# font-name = Font to use
# xft-antialias = Whether to antialias Xft fonts (true or false)
# xft-dpi = Resolution for Xft in dots per inch (e.g. 96)
# xft-hintstyle = What degree of hinting to use (none, slight, medium, or full)
# xft-rgba = Type of subpixel antialiasing (none, rgb, bgr, vrgb or vbgr)
# show-language-selector (true or false)
# show-indicators = semi-colon ";" separated list of allowed indicator modules (e.g. libsoundmenu.so)
# show-clock (true or false)
# clock-format = strftime-format string, e.g. %H:%M
# keyboard = command to launch on-screen keyboard
#
[greeter]
#background=
#theme-name=
#icon-theme-name=
#font-name=
#xft-antialias=
#xft-dpi=
#xft-hintstyle=
#xft-rgba=
#show-language-selector=
#show-indicators=
#show-clock=
#clock-format=
#keyboard=

Cfr: "Did you test X following the Beginners' Guide?"

Yes. I tested X. I believe that I followed the Beginner's Guide to the letter. Of course, I am new to Arch, so it is possible I misunderstood something. I believe what I did was to enter the following command to install X: pacman -S xorg-server xorg-server-utils xorg-xinit and then, as provided in the guide, I installed mesa.

I have, per your suggestion, removed xorg-server-xephyr. I note, however, that the guide for installing lightdm indicates that the package should be installed initially, in order to test to see if lightdm works. In any event, removing it does not alter how the system starts up.

You are correct that I am starting the computer directly to lightdm - and not starting lightdm from X - but lightdm leaves a blank page, as I noted. I can click around on the blank page and stuff pops up. On looking at Oxyd's suggested outputs, I wonder if my problem is that nearly everything in the configuration file has been commented out.

Offline

#15 2013-07-27 09:41:16

Padfoot
Member
Registered: 2010-09-03
Posts: 381

Re: [SOLVED] Display manager

Looking at your lightdm-gtk-greeter.conf you have not configured your greeter at all. No background colour or image, no gtk theme, no icon theme etc.

Your greeter config should look something similar to this:

background=/etc/lightdm/wallpaper/Arch_Linux_Bluewave.png
theme-name=MediterraneanNight
icon-theme-name=Faenza-Xfce
font-name=Sans Regular 11
xft-antialias=true
xft-dpi=96
xft-hintstyle=slight
xft-rgba=rgb
show-language-selector=false
show-indicators=false
show-clock=true
clock-format=%a %d %b %H:%M
keyboard=

Configure the greeter and reboot.

Last edited by Padfoot (2013-07-27 09:41:47)

Offline

#16 2013-07-27 11:46:05

clfarron4
Member
From: London, UK
Registered: 2013-06-28
Posts: 2,163
Website

Re: [SOLVED] Display manager

Seconding what Padfoot said. I'm going to admit that I was lazy when I decided to go for lightdm and built the lightdm-ubuntu package with all the dependencies. Only thing is that if you decide to go for lightdm-ubuntu after playing with lightdm first, you have to purge the lightdm configuration files when you uninstall lightdm, otherwise there are going to be ownership conflicts galore.

Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository

Offline

#17 2013-07-27 19:55:07

nef131
Member
Registered: 2013-07-24
Posts: 23

Re: [SOLVED] Display manager

Thank you all. I have themed lightdm but, unfortunately, it only shows the theming, etc. when I log out.

I note that on actual boot up, I come to a blank, black page. There is a "pointer" that appears like a straight line in the middle - as if I were on a fill in form. If you move the pointer around, it turns into an ordinary pointer with an arrow on it. Moreover, if you click at the top of the screen and keep clicking around, part of a top panel forms. If you click in the middle of the screen, sort of a menu forms, but the lettering is not normal. This is exactly as was the case before I "themed" lightdm. I wonder whether I should give up on lightdm and try a different display manager.

Below, is the output from cat /etc/lightdm/lightdm-gtk-greeter.conf, which I checked from inside Mate:

[allen@archbox ~]$ cat /etc/lightdm/lightdm-gtk-greeter.conf
#
# background = Background file to use, either an image path or a color (e.g. #772953)
# theme-name = GTK+ theme to use
# icon-theme-name = Icon theme to use
# font-name = Font to use
# xft-antialias = Whether to antialias Xft fonts (true or false)
# xft-dpi = Resolution for Xft in dots per inch (e.g. 96)
# xft-hintstyle = What degree of hinting to use (none, slight, medium, or full)
# xft-rgba = Type of subpixel antialiasing (none, rgb, bgr, vrgb or vbgr)
# show-language-selector (true or false)
# show-indicators = semi-colon ";" separated list of allowed indicator modules (e.g. libsoundmenu.so)
# show-clock (true or false)
# clock-format = strftime-format string, e.g. %H:%M
# keyboard = command to launch on-screen keyboard
#
[greeter]
background=#772953
theme-name=xfce-curve
icon-theme-name=Quid
font-name=Verdana
xft-antialias=true
xft-dpi=96
xft-hintstyle=slight
xft-rgba=rgb
show-language-selector=false
show-indicators=false
show-clock=true
#clock-format=%a %d %b %H:%M
keyboard=

Is it possible that there is something not right with the way the graphics driver starts up? That does not make sense to me because, after I am on either Mate or XFCE, my graphics are normal. I do note that Flash is less responsive than it was under Windows XP but everything else is as good or better than when I used Windows. I note that when I had Zorin lite on this computer, the display manager worked well but, again, Flash was not great.

Offline

#18 2013-07-27 20:57:09

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,140

Re: [SOLVED] Display manager

Have you tried explicitly setting greeter-session in lightdm.conf? I know you are using the default greeter so I assume this shouldn't be necessary but presumably it couldn't hurt.

What does pam-service=lightdm-autologin do, by the way?

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#19 2013-07-27 22:02:19

progandy
Member
Registered: 2012-05-17
Posts: 5,203

Re: [SOLVED] Display manager

What does pam-service=lightdm-autologin do, by the way?

This selects another pam configuration. lightdm-autologin is the same as lightdm, but it won't require the user to enter his password. It will open the session without it.
Edit: I guess the setting should be called autologin-pam-service I think. pam-service is a bit confusing since it does not change the configuration for the manual login.

Last edited by progandy (2013-07-27 22:04:16)

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Offline

#20 2013-07-28 03:53:54

nef131
Member
Registered: 2013-07-24
Posts: 23

Re: [SOLVED] Display manager

cfr: "Have you tried explicitly setting greeter-session in lightdm.conf?"

I tried doing so but it results in not being able to log in without ctl alt f2, logging in via tty, starting X and removing the entry. I am not sure that I am doing this the correct way. I set the line in lightdm.conf that begins "#greeter-session=" to read " greeter-session=lightdm-gtk3-greeter ". If there is something else to set, I missed it.

Again, I wonder whether the issue here relates somehow to initiating graphics. "Normally" - if you can call it that - when I boot up to the black page and I click around, eventually enough becomes visible so that I can log in or change, for example, what DE to load. I am reminded of an old computer that overwhelms its graphics, and that changes what is seen very slowly, by clicking here and there.

Another thought I have is to try a different display manager. Perhaps there is one that will just work. I am not wedded to lightdm although, having tried pretty hard here - as have all of you who have posted -, I am not thrilled with the idea of giving up.

Offline

#21 2013-07-28 08:36:47

henk
Member
From: Weert, Netherlands
Registered: 2013-01-01
Posts: 334

Re: [SOLVED] Display manager

In lightdm.conf it should be 

greeter-session=lightdm-gtk-greeter

From my lightdm.conf:

[SeatDefaults]
#type=xlocal
#xserver-command=X
#xserver-layout=
#xserver-config=
#xserver-allow-tcp=false
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
greeter-session=lightdm-gtk-greeter
greeter-hide-users=false
#greeter-allow-guest=true
greeter-show-manual-login=true
#greeter-show-remote-login=true
#user-session=Xfce Session
#allow-guest=true
#guest-session=UNIMPLEMENTED
session-wrapper=/etc/lightdm/xsession

lightdm-greeter-gtk.conf:

[greeter]
background=/etc/xdg/Login/login05.jpg
theme-name=Greybird-lightdm
#icon-theme-name=
font-name=Droid Sans 10
xft-antialias=true
xft-dpi=96
xft-hintstyle=slight
xft-rgba=rgb
#show-language-selector=
#show-indicators=
show-clock=true
#clock-format=
#keyboard=

Just curious, what are the contents of your /etc/lightdm/ directory? Maybe you are missing something.

Offline

#22 2013-07-28 19:32:04

nef131
Member
Registered: 2013-07-24
Posts: 23

Re: [SOLVED] Display manager

henk,

Thank you for your post. I set lightdm, as per your suggestion. My lightdm lightdm-greeter-gtk.conf remains as previously set per recommendation, as earlier posted.

Here is what occured. The first time, I was booted to the same blank screen. After clicking around a bit, much of what lightdm would look like appeared. However, on the second boot up, I came to what had been from prior posts.

Here is what is in my lightdm folder:

[allen@archbox ~]$ ls /etc/lightdm
keys.conf                     lightdm-gtk-greeter.conf.pacsave  users.conf
lightdm-gtk-greeter.conf      lightdm.conf                      xsession
lightdm-gtk-greeter.conf.bak  lightdm.conf.bak

I had backed upon my files before making change, which is what the.bak files are. I think .pacsave is the form used by Arch when you uninstall a program, as I did, before, per suggestion, starting over with the process.

Offline

#23 2013-07-29 03:26:46

henk
Member
From: Weert, Netherlands
Registered: 2013-01-01
Posts: 334

Re: [SOLVED] Display manager

Regarding pacsave files you will have to read up on this:
https://wiki.archlinux.org/index.php/Pa … save_Files
If you pay attention to the pacman output during an update, you will notice that pacman
informs you of the fact when a file is being saved as pacsave.

Offline

#24 2013-07-29 12:50:17

nef131
Member
Registered: 2013-07-24
Posts: 23

Re: [SOLVED] Display manager

henk,

Thank you for pointing me to the information about pacsave. I do not recall being so informed but, being new at this, I might have read the notice without realizing what it means.

Offline

#25 2013-07-29 21:17:43

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,140

Re: [SOLVED] Display manager

Did you correct the value of greeter-session?

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

Pages: 1 2

Board footer

Powered by FluxBB