Bug 1667682

Summary: [abrt] 0ad: verify_crt(): pyrogenesis killed by SIGBUS
Product: [Fedora] Fedora Reporter: Mathieu Baudier <mbaudier>
Component: 0adAssignee: Paulo Andrade <paulo.cesar.pereira.de.andrade>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: 7d28c752, bioinfornatics, cheese, igor.raits, mail, paulo.cesar.pereira.de.andrade, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c62d78eaa7748ebeb5839ec5cb1826739b97de6b
Whiteboard: abrt_hash:321b6940d11d8af954c3a48bb729e069df6f889c;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:36: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: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Mathieu Baudier 2019-01-19 19:26:43 UTC
Description of problem:
0ad crashes when trying to use the multiplayer online hall

Version-Release number of selected component:
0ad-0.0.23b-1.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/pyrogenesis
crash_function: verify_crt
executable:     /usr/bin/pyrogenesis
journald_cursor: s=9009f1218c8748d58730f995a6bb90b4;i=234aa;b=265cf1c247df442e875f47fefb7389a0;m=5bb9a8f;t=57fd45e2c4a50;x=adbc97ccf77fee6d
kernel:         4.19.15-200.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 verify_crt at verify.c:633
 #1 _gnutls_verify_crt_status at verify.c:975
 #2 gnutls_x509_crt_verify at verify.c:1487
 #3 gloox::GnuTLSClient::verifyAgainstCAs at tlsgnutlsclient.cpp:227
 #4 gloox::GnuTLSClient::getCertInfo at tlsgnutlsclient.cpp:157
 #5 gloox::GnuTLSBase::handshake at tlsgnutlsbase.cpp:138
 #6 gloox::GnuTLSBase::decrypt at tlsgnutlsbase.cpp:70
 #7 gloox::ConnectionTCPClient::recv at connectiontcpclient.cpp:169
 #8 Frame() at ../../../source/main.cpp:403
 #9 RunGameOrAtlas(int, char const**) at ../../../source/main.cpp:634

Comment 1 Mathieu Baudier 2019-01-19 19:26:46 UTC
Created attachment 1521831 [details]
File: backtrace

Comment 2 Mathieu Baudier 2019-01-19 19:26:48 UTC
Created attachment 1521832 [details]
File: cgroup

Comment 3 Mathieu Baudier 2019-01-19 19:26:49 UTC
Created attachment 1521833 [details]
File: core_backtrace

Comment 4 Mathieu Baudier 2019-01-19 19:26:50 UTC
Created attachment 1521834 [details]
File: cpuinfo

Comment 5 Mathieu Baudier 2019-01-19 19:26:52 UTC
Created attachment 1521835 [details]
File: dso_list

Comment 6 Mathieu Baudier 2019-01-19 19:26:53 UTC
Created attachment 1521836 [details]
File: environ

Comment 7 Mathieu Baudier 2019-01-19 19:26:54 UTC
Created attachment 1521837 [details]
File: exploitable

Comment 8 Mathieu Baudier 2019-01-19 19:26:55 UTC
Created attachment 1521838 [details]
File: limits

Comment 9 Mathieu Baudier 2019-01-19 19:26:57 UTC
Created attachment 1521839 [details]
File: maps

Comment 10 Mathieu Baudier 2019-01-19 19:26:58 UTC
Created attachment 1521840 [details]
File: mountinfo

Comment 11 Mathieu Baudier 2019-01-19 19:27:00 UTC
Created attachment 1521841 [details]
File: open_fds

Comment 12 Mathieu Baudier 2019-01-19 19:27:01 UTC
Created attachment 1521842 [details]
File: proc_pid_status

Comment 13 rugk 2019-01-25 10:29:51 UTC
Upstream report here: https://trac.wildfiregames.com/ticket/5349

(and dupe of this issue is here: https://bugzilla.redhat.com/show_bug.cgi?id=1669448)

Comment 14 Ben Cotton 2019-05-02 19:58:06 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Ben Cotton 2019-05-28 23:36:44 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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

Comment 16 Ben Brian 2019-07-24 11:49:06 UTC
Due to bugs in gloox 1.0.14, fixed with update to 1.0.22, reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1732797