Bug 2252274

Summary: [abrt] xorg-x11-server-Xorg: dix_main(): Xorg killed by SIGABRT
Product: [Fedora] Fedora Reporter: fj.gaming
Component: xorg-x11-serverAssignee: Adam Jackson <ajax>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: ajax, bskeggs, fj.gaming, jexposit, ofourdan, rhughes, rstrode, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/51f32082adb5a2ecce514f3efc6d547c166810f
Whiteboard: abrt_hash:bd56765b57ff7f6a989a0c44fdfd1850bc516465;VARIANT_ID=xfce;
Fixed In Version: xorg-x11-server-21.1.13-3.fc42 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-09-27 19:45:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: backtrace none

Description fj.gaming 2023-11-30 14:32:10 UTC
Version-Release number of selected component:
xorg-x11-server-Xorg-1.20.14-26.fc39

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         Xorg killed by SIGABRT
journald_cursor: s=1fa6d53f23264872a64dc3f9ca2755d4;i=4163a;b=796bec76fa9e403bb29174627b9ffa25;m=2142088a0;t=60ae138ebbbbc;x=1eb373be5f6e3620
executable:     /usr/libexec/Xorg
cmdline:        /usr/libexec/Xorg -core -noreset :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
cgroup:         0::/system.slice/lightdm.service
rootdir:        /
uid:            0
kernel:         6.5.12-300.fc39.x86_64
package:        xorg-x11-server-Xorg-1.20.14-26.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: dix_main

Truncated backtrace:
Thread no. 1 (1 frames)
 #7 dix_main at ../../dix/main.c:196


Potential duplicate: bug 1898442

Comment 1 fj.gaming 2023-11-30 14:32:14 UTC
Created attachment 2002123 [details]
File: proc_pid_status

Comment 2 fj.gaming 2023-11-30 14:32:15 UTC
Created attachment 2002124 [details]
File: maps

Comment 3 fj.gaming 2023-11-30 14:32:17 UTC
Created attachment 2002125 [details]
File: limits

Comment 4 fj.gaming 2023-11-30 14:32:19 UTC
Created attachment 2002126 [details]
File: environ

Comment 5 fj.gaming 2023-11-30 14:32:20 UTC
Created attachment 2002127 [details]
File: open_fds

Comment 6 fj.gaming 2023-11-30 14:32:22 UTC
Created attachment 2002128 [details]
File: mountinfo

Comment 7 fj.gaming 2023-11-30 14:32:23 UTC
Created attachment 2002129 [details]
File: os_info

Comment 8 fj.gaming 2023-11-30 14:32:25 UTC
Created attachment 2002130 [details]
File: cpuinfo

Comment 9 fj.gaming 2023-11-30 14:32:27 UTC
Created attachment 2002131 [details]
File: core_backtrace

Comment 10 fj.gaming 2023-11-30 14:32:28 UTC
Created attachment 2002132 [details]
File: dso_list

Comment 11 fj.gaming 2023-11-30 14:32:30 UTC
Created attachment 2002133 [details]
File: backtrace

Comment 12 Hei 2024-02-24 01:51:58 UTC
I was trying to automatically mount a probably faulty HD that I use for torrents by edting fstab. The moment the system boot it failed completely. So i had to use a live OS in a thumbdrive to delete the lines i added to fstab and everything worked fine. I thought no HD could brake the system this way despite the fault. The worst case scenario for me was the HD not mounting at all, but without any harm to the system. Thank you.


reporter:       libreport-2.17.11
type:           CCpp
reason:         Xorg killed by SIGABRT
journald_cursor: s=7dc90a3c3d7d4443a01b0c7f1045688f;i=3b31;b=422f737ef328409eb8e37b5799f2a204;m=ffc4d6;t=611ea264d8e18;x=49f01325343e54ac
executable:     /usr/libexec/Xorg
cmdline:        /usr/libexec/Xorg -core -noreset :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
cgroup:         0::/system.slice/lightdm.service
rootdir:        /
uid:            0
kernel:         6.7.4-200.fc39.x86_64
package:        xorg-x11-server-Xorg-1.20.14-30.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: dix_main
comment:        I was trying to automatically mount a probably faulty HD that I use for torrents by edting fstab. The moment the system boot it failed completely. So i had to use a live OS in a thumbdrive to delete the lines i added to fstab and everything worked fine. I thought no HD could brake the system this way despite the fault. The worst case scenario for me was the HD not mounting at all, but without any harm to the system. Thank you.

Comment 13 Fedora Update System 2024-09-27 16:04:10 UTC
FEDORA-2024-2a319dc3e8 (tigervnc-1.14.0-6.fc42, xorg-x11-drv-amdgpu-23.0.0-5.fc42, and 11 more) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-2a319dc3e8

Comment 14 Fedora Update System 2024-09-27 19:45:21 UTC
FEDORA-2024-2a319dc3e8 (tigervnc-1.14.0-6.fc42, xorg-x11-drivers-2022-8.fc42, and 12 more) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.