Bug 2388184

Summary: [abrt] gnome-session: __syscall_cancel_arch(): gnome-session-binary killed by SIGABRT
Product: [Fedora] Fedora Reporter: Jan Vlug <jan.public>
Component: gnome-sessionAssignee: GNOME SIG Unassigned <gnome-sig>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: gnome-sig, jan.public, jeremy.linton, mclasen, rhughes, rstrode
Target Milestone: ---Keywords: AutomationTriaged
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5abff1d564916e0f7930e6e46dca91a738ca2150;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-10-16 21:12:44 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: cgroup
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: backtrace none

Description Jan Vlug 2025-08-13 09:00:02 UTC 
Description of problem:
This happened during a dnf upgrade. The gnome session crashed.

Version-Release number of selected component:
gnome-session-48.0-1.fc42

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-session-binary killed by SIGABRT
journald_cursor: s=2af8a8f819304b1ab2a3f8188572b998;i=58b3e9f;b=3741383d5b7d4c2b95703c606c0adce8;m=1243c01131;t=63c3b4b3d4182;x=6629e0fd8b38d737
executable:     /usr/libexec/gnome-session-binary
cmdline:        /usr/libexec/gnome-session-binary --systemd-service --session=gnome
rootdir:        /
uid:            1000
kernel:         6.15.9-201.fc42.x86_64
backtrace_rating: 4
crash_function: __syscall_cancel_arch
comment:        This happened during a dnf upgrade. The gnome session crashed.
package:        gnome-session-48.0-1.fc42

Truncated backtrace:
Thread no. 4 (10 frames)
 #0 __syscall_cancel_arch at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
 #1 __internal_syscall_cancel at cancellation.c:49
 #2 __syscall_cancel at cancellation.c:75
 #3 ppoll at ../sysdeps/unix/sysv/linux/ppoll.c:42
 #5 g_main_context_poll_unlocked at ../glib/gmain.c:4632
 #6 g_main_context_iterate_unlocked at ../glib/gmain.c:4309
 #7 g_main_context_iteration at ../glib/gmain.c:4379
 #8 dconf_gdbus_worker_thread at ../gdbus/dconf-gdbus-thread.c:82
 #9 g_thread_proxy at ../glib/gthread.c:893
 #11 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Comment 1 Jan Vlug 2025-08-13 09:00:05 UTC 
Created attachment 2103424 [details]
File: proc_pid_status
Comment 2 Jan Vlug 2025-08-13 09:00:06 UTC 
Created attachment 2103425 [details]
File: maps
Comment 3 Jan Vlug 2025-08-13 09:00:08 UTC 
Created attachment 2103426 [details]
File: limits
Comment 4 Jan Vlug 2025-08-13 09:00:09 UTC 
Created attachment 2103427 [details]
File: cgroup
Comment 5 Jan Vlug 2025-08-13 09:00:11 UTC 
Created attachment 2103428 [details]
File: environ
Comment 6 Jan Vlug 2025-08-13 09:00:12 UTC 
Created attachment 2103429 [details]
File: open_fds
Comment 7 Jan Vlug 2025-08-13 09:00:14 UTC 
Created attachment 2103430 [details]
File: mountinfo
Comment 8 Jan Vlug 2025-08-13 09:00:15 UTC 
Created attachment 2103431 [details]
File: os_info
Comment 9 Jan Vlug 2025-08-13 09:00:16 UTC 
Created attachment 2103432 [details]
File: backtrace
Comment 10 Fedora Admin user for bugzilla script actions 2025-08-13 09:10:13 UTC 
Bug reports for this component on Red Hat Bugzilla are not actively monitored. Please consider reporting your issue directly to GNOME at https://gitlab.gnome.org/GNOME/ to improve the chances that your issue will be resolved. This issue should only be kept open if it:

1. Relates to Fedora packaging or integration with other Fedora components
2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions

If this issue isn't needed for either of these two reasons, please:

 * create an issue with GNOME
 * add a link to the GNOME issue here
 * close this issue as CLOSED/UPSTREAM

Thank you!
Comment 11 Jeremy Linton 2025-10-16 21:12:44 UTC 

*** This bug has been marked as a duplicate of bug 2402621 ***