Bug 2219399

Summary: [abrt] remmina: thread_pool_work_func(): remmina killed by SIGABRT
Product: [Fedora] Fedora Reporter: crippton
Component: remminaAssignee: Jonathan Wright <jonathan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: crippton, jonathan, negativo17, pahan, philip.wyett
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9df96e3e96ed2fc17c66c811e9e64613e899dbe
Whiteboard: abrt_hash:709eac192fd1d0ea4666c8c77300c861395b6486;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-28 13:19:18 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: var_log_messages
none
File: backtrace none

Description crippton 2023-07-03 13:31:54 UTC 
Version-Release number of selected component:
remmina-1.4.31-1.fc38

Additional info:
reporter:       libreport-2.17.10
type:           CCpp
reason:         remmina killed by SIGABRT
journald_cursor: s=b2026275f7e844638e56f6c701482333;i=b401d5;b=5ff00e17ed6442d49d780cf737a24fe1;m=2a0da6decc;t=5ff63a4758c95;x=d124ca4da4e9bc9e
executable:     /usr/bin/remmina
cmdline:        remmina
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.3.8-200.fc38.x86_64
package:        remmina-1.4.31-1.fc38
runlevel:       N 5
dso_list:       /usr/bin/remmina remmina-1.4.31-1.fc38.x86_64 (Fedora Project) 1687201973
backtrace_rating: 4
crash_function: thread_pool_work_func

Truncated backtrace:
Thread no. 0 (3 frames)
 #8 thread_pool_work_func at /usr/src/debug/freerdp-2.10.0-1.fc38.x86_64/winpr/libwinpr/pool/pool.c:92
 #9 thread_launcher at /usr/src/debug/freerdp-2.10.0-1.fc38.x86_64/winpr/libwinpr/thread/thread.c:530
 #11 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Comment 1 crippton 2023-07-03 13:32:09 UTC 
Created attachment 1973869 [details]
File: proc_pid_status
Comment 2 crippton 2023-07-03 13:32:11 UTC 
Created attachment 1973870 [details]
File: maps
Comment 3 crippton 2023-07-03 13:32:13 UTC 
Created attachment 1973871 [details]
File: limits
Comment 4 crippton 2023-07-03 13:32:15 UTC 
Created attachment 1973872 [details]
File: environ
Comment 5 crippton 2023-07-03 13:32:17 UTC 
Created attachment 1973873 [details]
File: open_fds
Comment 6 crippton 2023-07-03 13:32:19 UTC 
Created attachment 1973874 [details]
File: mountinfo
Comment 7 crippton 2023-07-03 13:32:30 UTC 
Created attachment 1973875 [details]
File: os_info
Comment 8 crippton 2023-07-03 13:32:42 UTC 
Created attachment 1973876 [details]
File: cpuinfo
Comment 9 crippton 2023-07-03 13:32:45 UTC 
Created attachment 1973878 [details]
File: core_backtrace
Comment 10 crippton 2023-07-03 13:32:47 UTC 
Created attachment 1973879 [details]
File: var_log_messages
Comment 11 crippton 2023-07-03 13:32:50 UTC 
Created attachment 1973880 [details]
File: backtrace
Comment 12 Aoife Moloney 2024-05-28 13:19:18 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.