Bug 104917

Created attachment 137137 [details]
Xorg.0.log

rpm -q xorg-x11-server-Xorg
xorg-x11-server-Xorg-1.19.6-2.fc27.i686

If it helps here's a gdb:

gdb  /usr/libexec/Xorg /var/lib/systemd/coredump/core.Xorg.42.e441588487b74ca5893135fe695cd1aa.27146.1517597898000000
GNU gdb (GDB) Fedora 8.0.1-33.fc27
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/libexec/Xorg...Reading symbols from /usr/lib/debug/usr/libexec/Xorg-1.19.6-2.fc27.i386.debug...done.
done.
[New LWP 27146]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Core was generated by `/usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -backgroun'.
Program terminated with signal SIGABRT, Aborted.
#0  0xb7f54cf9 in __kernel_vsyscall ()

Still happening in Fedora 28:
gdb /usr/libexec/Xorg core.Xorg.0.6448cdc2272644f0a25242a1c2562d9f.24277.1528138755000000                              GNU gdb (GDB) Fedora 8.1-15.fc28
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/libexec/Xorg...Reading symbols from /usr/lib/debug/usr/libexec/Xorg-1.19.6-8.fc28.i386.debug...done.
done.
[New LWP 24277]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Core was generated by `/usr/libexec/Xorg -core -noreset :0 -seat seat0 -auth /var/run/lightdm/root/:0'.
Program terminated with signal SIGABRT, Aborted.
#0  0xb7f8fd21 in __kernel_vsyscall ()


Jun  4 14:59:15 curie systemd-coredump[24265]: Process 24263 (Xorg) of user 0 dumped core.#012#012Stack trace of thread 24263:#012#0  0x000000
00b7fbcd21 __kernel_vsyscall (linux-gate.so.1)#012#1  0x00000000b77cae52 raise (libc.so.6)#012#2  0x00000000b77b482f abort (libc.so.6)#012#3  
0x00000000081ed409 OsAbort (Xorg)#012#4  0x00000000081f32a6 AbortServer (Xorg)#012#5  0x00000000081f3c84 FatalError (Xorg)#012#6  0x0000000008
07b8b7 dix_main (Xorg)#012#7  0x000000000806439f main (Xorg)#012#8  0x00000000b77b6191 __libc_start_main (libc.so.6)#012#9  0x00000000080643e2
 _start (Xorg)

That shows the X server is calling FatalError and killing itself.
Please attach the relevant Xorg logs so we can see what
error message the FatalError is printing when doing that.

Oh, never mind, I missed that Xorg.0.log was provided in a earlier comment.

It shows you've configured to use the "radeon" driver, but that Xorg can't
find any devices that driver supports in the system.

Created attachment 140022 [details]
Xorg.log

newer Xorg.log

(In reply to Alan Coopersmith from comment #5)
> Oh, never mind, I missed that Xorg.0.log was provided in a earlier comment.
> 
> It shows you've configured to use the "radeon" driver, but that Xorg can't
> find any devices that driver supports in the system.

Where would I unset that and what can I set it to?

I found it I had:
20-radeon.conf 
Section "Device"
        Identifier      "default"
        Driver          "radeon"
EndSection

So I removed it. Tried lightdm again. Now getting this:

Jun  4 15:39:31 curie systemd-coredump[25314]: Process 25312 (Xorg) of user 0 dumped core.#012#012Stack trace of thread 25312:#012#0  0x00000000b7f1ad21 __kernel_vsyscall (linux-gate.so.1)#012#1  0x00000000b7728e52 __libc_signal_restore_set (libc.so.6)#012#2  0x00000000b771282f __GI_abort (libc.so.6)#012#3  0x00000000081ed409 OsAbort (Xorg)#012#4  0x00000000080bd79c ddxGiveUp (Xorg)#012#5  0x00000000080bd845 AbortDDX (Xorg)#012#6  0x00000000081f3284 AbortServer (Xorg)#012#7  0x00000000081f3c84 FatalError (Xorg)#012#8  0x00000000081ea38f OsSigHandler (Xorg)#012#9  0x00000000b7f1ad38 __kernel_rt_sigreturn (linux-gate.so.1)#012#10 0x00000000b7ba3340 pci_device_next (libpciaccess.so.0)#012#11 0x00000000b7ba3419 pci_device_find_by_slot (libpciaccess.so.0)#012#12 0x00000000b7ba5494 pci_device_vgaarb_init (libpciaccess.so.0)#012#13 0x00000000080d8368 xf86VGAarbiterInit (Xorg)#012#14 0x00000000080b01eb xf86BusConfig (Xorg)#012#15 0x00000000080bf457 InitOutput (Xorg)#012#16 0x000000000807b364 dix_main (Xorg)#012#17 0x000000000806439f main (Xorg)#012#18 0x00000000b7714191 __libc_start_main (libc.so.6)#012#19 0x00000000080643e2 _start (Xorg)

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Core was generated by `/usr/libexec/Xorg -core -noreset :0 -seat seat0 -auth /var/run/lightdm/root/:0'.
Program terminated with signal SIGABRT, Aborted.
#0  0xb7f1ad21 in __kernel_vsyscall ()


[876663.337] (EE) Backtrace:
[876663.337] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x136) [0x81ea456]
[876663.338] (EE) 1: ? (?+0x136) [0xb7f1ae6d]
[876663.339] (EE) 2: /lib/libpciaccess.so.0 (pci_device_next+0xf0) [0xb7ba3340]
[876663.340] (EE) 3: /lib/libpciaccess.so.0 (pci_device_find_by_slot+0x59) [0xb7ba3419]
[876663.340] (EE) 4: /lib/libpciaccess.so.0 (pci_device_vgaarb_init+0xc4) [0xb7ba5494]
[876663.341] (EE) 5: /usr/libexec/Xorg (xf86ConfigPciEntity+0x40b8) [0x80dc408]
[876663.341] (EE) 6: /usr/libexec/Xorg (xf86BusConfig+0xeb) [0x80b01eb]
[876663.342] (EE) 7: /usr/libexec/Xorg (InitOutput+0x9d7) [0x80bf457]
[876663.342] (EE) 8: /usr/libexec/Xorg (InitFonts+0x2a4) [0x807b3b4]
[876663.342] (EE) 9: /usr/libexec/Xorg (miPolyFillRect+0x164) [0x80644d4]
[876663.343] (EE) 10: /lib/libc.so.6 (__libc_start_main+0xf1) [0xb7714191]
[876663.343] (EE) 11: /usr/libexec/Xorg (_start+0x32) [0x8064414]
[876663.343] (EE) 
[876663.344] (EE) Segmentation fault at address 0x0
[876663.344] (EE) 
Fatal server error:
[876663.344] (EE) Caught signal 11 (Segmentation fault). Server aborting
[876663.344] (EE)

What you can set it to depends on what graphics card/device you have in the
system.  I don't see any indication in your Xorg.log of what that might be.

(In reply to Alan Coopersmith from comment #9)
> What you can set it to depends on what graphics card/device you have in the
> system.  I don't see any indication in your Xorg.log of what that might be.

09:0d.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV100 [Radeon 7000 / Radeon VE]

Please attach the corresponding dmesg output.

Created attachment 140033 [details]
dmesg log

Perhaps a clue in here?

[Fri May 25 12:08:27 2018] pci 0000:09:0d.0: vgaarb: setting as boot VGA device
[Fri May 25 12:08:27 2018] pci 0000:09:0d.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[Fri May 25 12:08:27 2018] pci 0000:09:0d.0: vgaarb: bridge control possible
[Fri May 25 12:08:27 2018] vgaarb: loaded

[Fri May 25 12:08:30 2018] [drm] radeon kernel modesetting enabled.
[Fri May 25 12:08:30 2018] [drm] initializing kernel modesetting (RV100 0x1002:0x5159 0x1028:0x016C 0x00).
[Fri May 25 12:08:30 2018] radeon 0000:09:0d.0: VRAM: 128M 0x00000000D0000000 - 0x00000000D7FFFFFF (16M used)
[Fri May 25 12:08:30 2018] radeon 0000:09:0d.0: GTT: 512M 0x00000000B0000000 - 0x00000000CFFFFFFF
[Fri May 25 12:08:30 2018] [drm] Detected VRAM RAM=128M, BAR=128M
[Fri May 25 12:08:30 2018] [drm] RAM width 32bits DDR
[Fri May 25 12:08:30 2018] [TTM] Zone  kernel: Available graphics memory: 424444 kiB
[Fri May 25 12:08:30 2018] [TTM] Zone highmem: Available graphics memory: 1679744 kiB
[Fri May 25 12:08:30 2018] [TTM] Initializing pool allocator
[Fri May 25 12:08:30 2018] [TTM] Initializing DMA pool allocator
[Fri May 25 12:08:30 2018] [drm] radeon: 16M of VRAM memory ready
[Fri May 25 12:08:30 2018] [drm] radeon: 512M of GTT memory ready.
[Fri May 25 12:08:30 2018] [drm] GART: num cpu pages 131072, num gpu pages 131072
[Fri May 25 12:08:30 2018] [drm] PCI GART of 512M enabled (table at 0x0000000035C80000).
[Fri May 25 12:08:30 2018] radeon 0000:09:0d.0: WB disabled
[Fri May 25 12:08:30 2018] radeon 0000:09:0d.0: fence driver on ring 0 use gpu addr 0x00000000b0000000 and cpu addr 0x7a045d80
[Fri May 25 12:08:30 2018] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[Fri May 25 12:08:30 2018] [drm] Driver supports precise vblank timestamp query.
[Fri May 25 12:08:30 2018] [drm] radeon: irq initialized.
[Fri May 25 12:08:30 2018] [drm] Loading R100 Microcode
[Fri May 25 12:08:30 2018] [drm] radeon: ring at 0x00000000B0001000
[Fri May 25 12:08:30 2018] [drm] ring test succeeded in 1 usecs
[Fri May 25 12:08:30 2018] [drm] ib test succeeded in 0 usecs
[Fri May 25 12:08:30 2018] [drm] No TV DAC info found in BIOS
[Fri May 25 12:08:30 2018] [drm] Radeon Display Connectors
[Fri May 25 12:08:30 2018] [drm] Connector 0:
[Fri May 25 12:08:30 2018] [drm]   VGA-1
[Fri May 25 12:08:30 2018] [drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[Fri May 25 12:08:30 2018] [drm]   Encoders:
[Fri May 25 12:08:30 2018] [drm]     CRT1: INTERNAL_DAC1
[Fri May 25 12:08:30 2018] [drm] Connector 1:
[Fri May 25 12:08:30 2018] [drm]   VGA-2
[Fri May 25 12:08:30 2018] [drm]   DDC: 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c
[Fri May 25 12:08:30 2018] [drm]   Encoders:
[Fri May 25 12:08:30 2018] [drm]     CRT2: INTERNAL_DAC2
[Fri May 25 12:08:30 2018] [drm] Connector 2:
[Fri May 25 12:08:30 2018] [drm]   DVI-I-1
[Fri May 25 12:08:30 2018] [drm]   HPD1
[Fri May 25 12:08:30 2018] [drm]   DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[Fri May 25 12:08:30 2018] [drm]   Encoders:
[Fri May 25 12:08:30 2018] [drm]     CRT2: INTERNAL_DAC2
[Fri May 25 12:08:30 2018] [drm]     DFP1: INTERNAL_TMDS1

Still no idea what's wrong. Please also attach all files in /etc/X11/xorg.conf.d/ and /usr/share/X11/xorg.conf.d/ (if there are any symlinks, attach the real files they resolve to, and mention the symlink name in the comment when attaching it).

Created attachment 140034 [details]
xorg conf files requested

tar archive of conf files from  /etc/X11/xorg.conf.d/ and /usr/share/X11/xorg.conf.d/

(In reply to Michel Dänzer from comment #13)
> Still no idea what's wrong. Please also attach all files in
> /etc/X11/xorg.conf.d/ and /usr/share/X11/xorg.conf.d/ (if there are any
> symlinks, attach the real files they resolve to, and mention the symlink
> name in the comment when attaching it).

I take it the config files didn't help? Is there any other debug/verbose logging that I can enable?

Helli Michel do you need any more logs from me? Or are the backtraces I put accidentally in  https://bugs.freedesktop.org/show_bug.cgi?id=81678 sufficient?

So.. bug 81678 has been eventually fixed in libpciaccess. 
If you build yourself xorg (after having installed the latest git of that tool) is anything changing?

(In reply to mirh from comment #17)
> So.. bug 81678 has been eventually fixed in libpciaccess. 
> If you build yourself xorg (after having installed the latest git of that
> tool) is anything changing?

LightDM seems to start without errors. GDM still throws these debug logs:

Jan 14 09:13:51 curie gnome-session-binary[4317]: DEBUG(+): GsmManager: CanShutdown called
Jan 14 09:13:51 curie journal[4356]: g_dir_open_with_errno: assertion 'path != NULL' failed
Jan 14 09:13:51 curie journal[4356]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed

Jan 14 09:13:56 curie journal[4439]: failed to get edid: unable to get EDID for output
Jan 14 09:13:56 curie journal[4356]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jan 14 09:13:57 curie journal[4439]: unable to get EDID for xrandr-VGA-0: unable to get EDID for output
Jan 14 09:13:58 curie journal[4356]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 29]: reference to undefined property "MetaWindowX11"
journal[4428]: Service not used for 60 seconds. Shutting down..

(In reply to RobbieTheK from comment #18)
> LightDM seems to start without errors. GDM still throws these debug logs:

Those look like GDM/gnome-shell issues, nothing X related (recent versions of GDM use Wayland instead of X by default).