Bug 1574797
| Summary: | [abrt] cone: std::__replacement_assert(): cone killed by SIGABRT | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stephen Haffly <hafflys> | ||||||||||||||||||||||||
| Component: | cone | Assignee: | Mosaab Alzoubi <moceap> | ||||||||||||||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||
| Version: | 29 | CC: | matthias.andree, moceap, nforro, rbarlow, steve, vkngbrsrkr | ||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/99a2824bb17190a2d21e7f04965d20a5bbd36fb0 | ||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:e8664f31523c01a00dcd0613db3b78b752172d4d; | ||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||
| Last Closed: | 2019-11-27 23:34:46 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
Stephen Haffly
2018-05-04 04:42:14 UTC
Created attachment 1431004 [details]
File: backtrace
Created attachment 1431005 [details]
File: cgroup
Created attachment 1431006 [details]
File: core_backtrace
Created attachment 1431007 [details]
File: cpuinfo
Created attachment 1431008 [details]
File: dso_list
Created attachment 1431009 [details]
File: environ
Created attachment 1431010 [details]
File: limits
Created attachment 1431011 [details]
File: maps
Created attachment 1431012 [details]
File: mountinfo
Created attachment 1431013 [details]
File: open_fds
Created attachment 1431014 [details]
File: proc_pid_status
*** Bug 1582843 has been marked as a duplicate of this bug. *** Similar problem has been detected:
Open terminal
Enter command "cone"
program crashes and this appears in the terminal window:
/usr/include/c++/8/bits/stl_vector.h:932: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) [with _Tp = char; _Alloc = std::allocator<char>; std::vector<_Tp, _Alloc>::reference = char&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.
Aborted (core dumped)
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: /usr/libexec/cone
crash_function: std::__replacement_assert
executable: /usr/libexec/cone
journald_cursor: s=a2deba363446405d9a2d04cab5994865;i=6924;b=cda643a697e649c2afaceefd235e65ce;m=748dceac;t=5703fdcc10614;x=8b84d5eb5bdd693b
kernel: 4.17.3-200.fc28.x86_64
package: cone-0.96.2-3.fc28
reason: cone killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Similar problem has been detected: cone crashes when started after a clean install. To reproduce: $ sudo dnf install cone $ cone reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/cone crash_function: std::__replacement_assert executable: /usr/libexec/cone journald_cursor: s=8d522c44788a4700add2728fd0901325;i=5bd8;b=63320f4d149a4879afa465bf80645b24;m=3b4ebe02f;t=5767a45ad3051;x=529a9df1f3a20c65 kernel: 4.18.8-200.fc28.x86_64 package: cone-0.96.2-3.fc28 reason: cone killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 This problem continues with Fedora 29 x86_64. What is happening and how do I fix it? *** Bug 1763534 has been marked as a duplicate of this bug. *** This upstream commit fixes the crash (among other things): https://sourceforge.net/p/courier/courier.git/ci/6c59480c2f87ea7a8de0be21c22312c8fbf88e27 and is also part of upstream release 1.0: https://sourceforge.net/projects/courier/files/cone/1.0/ This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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. Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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. |