Bug 1701590 - [abrt] gnome-terminal: std::__replacement_assert(): gnome-terminal-server killed by SIGABRT
Summary: [abrt] gnome-terminal: std::__replacement_assert(): gnome-terminal-server kil...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: 30
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:5637a3220fb76118c95d8477e49...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-19 18:23 UTC by Giacomo Longo
Modified: 2020-05-26 16:28 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 16:28:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (21.78 KB, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details
File: cgroup (399 bytes, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details
File: core_backtrace (9.23 KB, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details
File: cpuinfo (1.33 KB, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details
File: dso_list (9.72 KB, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details
File: environ (901 bytes, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details
File: limits (1.29 KB, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details
File: maps (57.77 KB, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details
File: mountinfo (5.41 KB, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details
File: open_fds (1.26 KB, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details
File: proc_pid_status (1.33 KB, text/plain)
2019-04-19 18:24 UTC, Giacomo Longo
no flags Details

Description Giacomo Longo 2019-04-19 18:23:57 UTC
Version-Release number of selected component:
gnome-terminal-3.32.1-1.fc30

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-terminal-server
crash_function: std::__replacement_assert
executable:     /usr/libexec/gnome-terminal-server
journald_cursor: s=df27f9b9c3bd4ef591b9d5f4cc541346;i=5a3b;b=5110d1ce02ce46a8b3abadd871f03ab1;m=db5f9dbf;t=586d5b4444dd0;x=f8581f2e159b6bcf
kernel:         5.0.7-300.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 Giacomo Longo 2019-04-19 18:24:02 UTC
Created attachment 1556547 [details]
File: backtrace

Comment 2 Giacomo Longo 2019-04-19 18:24:03 UTC
Created attachment 1556548 [details]
File: cgroup

Comment 3 Giacomo Longo 2019-04-19 18:24:05 UTC
Created attachment 1556549 [details]
File: core_backtrace

Comment 4 Giacomo Longo 2019-04-19 18:24:07 UTC
Created attachment 1556550 [details]
File: cpuinfo

Comment 5 Giacomo Longo 2019-04-19 18:24:08 UTC
Created attachment 1556551 [details]
File: dso_list

Comment 6 Giacomo Longo 2019-04-19 18:24:11 UTC
Created attachment 1556552 [details]
File: environ

Comment 7 Giacomo Longo 2019-04-19 18:24:13 UTC
Created attachment 1556553 [details]
File: limits

Comment 8 Giacomo Longo 2019-04-19 18:24:15 UTC
Created attachment 1556554 [details]
File: maps

Comment 9 Giacomo Longo 2019-04-19 18:24:17 UTC
Created attachment 1556555 [details]
File: mountinfo

Comment 10 Giacomo Longo 2019-04-19 18:24:19 UTC
Created attachment 1556556 [details]
File: open_fds

Comment 11 Giacomo Longo 2019-04-19 18:24:21 UTC
Created attachment 1556557 [details]
File: proc_pid_status

Comment 12 Christian Persch 2019-04-20 17:45:27 UTC
Fixed upstream on git master and 0-56 branch.

Comment 13 Peter 2019-05-05 17:47:17 UTC
Similar problem has been detected:

Crashed while using two terminal windows

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-terminal-server
crash_function: std::__replacement_assert
executable:     /usr/libexec/gnome-terminal-server
journald_cursor: s=954fbd276fad4f2b80c1d315cad87316;i=18b3;b=77facd72048d417aaf6d5a823fa25495;m=6c780000;t=58827861352c9;x=545b82281e0d704a
kernel:         5.0.10-300.fc30.x86_64
package:        gnome-terminal-3.32.1-1.fc30
reason:         gnome-terminal-server killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Ben Cotton 2020-04-30 21:24:54 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'.

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 30 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 2020-05-26 16:28:08 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.


Note You need to log in before you can comment on or make changes to this bug.