Bug 2228173

Summary: [abrt] deluge-gtk: g_thread_abort(): python3.11 killed by SIGABRT
Product: [Fedora] Fedora Reporter: alod123
Component: delugeAssignee: Michael Cronenworth <mike>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: alod123, mike
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1ecc0cf0730f2e6dfdab58ed833b224aed6ed2c
Whiteboard: abrt_hash:940070c74b4801b59dd2eb1bade69e09f46bc43a;VARIANT_ID=xfce;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-28 13:39:17 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: backtrace none

Description alod123 2023-08-01 15:33:25 UTC 
Version-Release number of selected component:
deluge-gtk-2.1.1-2.fc38

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         python3.11 killed by SIGABRT
journald_cursor: s=de530b0de60d4414825f94bcb3e005e1;i=3d0e27;b=a63f8dcad5664473914765d3c72de111;m=331a56285f;t=601cd0a20b3d4;x=ae2e0922f241906d
executable:     /usr/bin/python3.11
cmdline:        /usr/bin/python3 /usr/bin/deluge-gtk $'magnet:?xt=urn:btih:9a90cc1cac99ceb9d7d2a5147493822be41a3411&dn=Baldurs.Gate.3.v4.1.83.2651-GOG&tr=http%3A%2F%2Ftracker.trackerfix.com%3A80%2Fannounce&tr=udp%3A%2F%2F9.rarbg.me%3A2740&tr=udp%3A%2F%2F9.rarbg.to%3A2720'
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
rootdir:        /
uid:            1000
kernel:         6.4.4-200.fc38.x86_64
package:        deluge-gtk-2.1.1-2.fc38
runlevel:       N 5
dso_list:       /usr/bin/python3.11 python3-3.11.4-1.fc38.x86_64 (Fedora Project) 1688161040
backtrace_rating: 4
crash_function: g_thread_abort

Truncated backtrace:
Thread no. 0 (6 frames)
 #4 g_thread_abort at ../glib/gthread-posix.c:88
 #5 g_private_set at ../glib/gthread-posix.c:1105
 #6 g_task_thread_setup at ../gio/gtask.c:1479
 #7 g_task_thread_pool_thread at ../gio/gtask.c:1529
 #9 g_thread_proxy at ../glib/gthread.c:831
 #11 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Comment 1 alod123 2023-08-01 15:33:29 UTC 
Created attachment 1981137 [details]
File: proc_pid_status
Comment 2 alod123 2023-08-01 15:33:30 UTC 
Created attachment 1981138 [details]
File: maps
Comment 3 alod123 2023-08-01 15:33:31 UTC 
Created attachment 1981139 [details]
File: limits
Comment 4 alod123 2023-08-01 15:33:33 UTC 
Created attachment 1981140 [details]
File: environ
Comment 5 alod123 2023-08-01 15:33:34 UTC 
Created attachment 1981141 [details]
File: open_fds
Comment 6 alod123 2023-08-01 15:33:36 UTC 
Created attachment 1981142 [details]
File: mountinfo
Comment 7 alod123 2023-08-01 15:33:37 UTC 
Created attachment 1981143 [details]
File: os_info
Comment 8 alod123 2023-08-01 15:33:39 UTC 
Created attachment 1981144 [details]
File: cpuinfo
Comment 9 alod123 2023-08-01 15:33:40 UTC 
Created attachment 1981145 [details]
File: core_backtrace
Comment 10 alod123 2023-08-01 15:33:42 UTC 
Created attachment 1981146 [details]
File: backtrace
Comment 11 Aoife Moloney 2024-05-28 13:39:17 UTC 
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.