Bug 1631949

Summary: [abrt] libreport-gtk: ec_get_name(): report-gtk killed by SIGSEGV
Product: [Fedora] Fedora Reporter: James <james>
Component: libreportAssignee: abrt <abrt-devel-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: abrt-devel-list, jakub, michal.toman, mkutlak, mmarusak, msuchy, sajith
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c2e006736d3a950e71aa724daef3fd5ae0f7f79c
Whiteboard: abrt_hash:065728697fcc84054e17f8737ad2451b9b7f0144;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-27 09:41:51 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 James 2018-09-22 11:35:26 UTC 
Description of problem:
Was reporting a crash.

Version-Release number of selected component:
libreport-gtk-2.9.5-1.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        report-gtk -- /var/spool/abrt/ccpp-2018-09-22-12:16:06.547948-10802
crash_function: ec_get_name
executable:     /usr/bin/report-gtk
journald_cursor: s=fb335c7d96744ebcb3ab841d57acf40f;i=a8952;b=0b992d3387f8477eb1c44924e8c1fabc;m=b8214aff54;t=576741472c4f7;x=4e907953b44196ba
kernel:         4.18.5-200.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1402400001

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 ec_get_name at event_config.c:69
 #1 save_data_from_event_config_dialog at event_config_dialog.c:80
 #2 cdialog_run at config_dialog.c:99
 #3 libreport_show_event_config_dialog at event_config_dialog.c:391

Potential duplicate: bug 1498414
Comment 1 James 2018-09-22 11:35:43 UTC 
Created attachment 1485915 [details]
File: backtrace
Comment 2 James 2018-09-22 11:35:45 UTC 
Created attachment 1485916 [details]
File: cgroup
Comment 3 James 2018-09-22 11:35:46 UTC 
Created attachment 1485917 [details]
File: core_backtrace
Comment 4 James 2018-09-22 11:35:48 UTC 
Created attachment 1485918 [details]
File: cpuinfo
Comment 5 James 2018-09-22 11:35:50 UTC 
Created attachment 1485919 [details]
File: dso_list
Comment 6 James 2018-09-22 11:35:51 UTC 
Created attachment 1485920 [details]
File: environ
Comment 7 James 2018-09-22 11:35:52 UTC 
Created attachment 1485921 [details]
File: exploitable
Comment 8 James 2018-09-22 11:35:53 UTC 
Created attachment 1485922 [details]
File: limits
Comment 9 James 2018-09-22 11:35:55 UTC 
Created attachment 1485923 [details]
File: maps
Comment 10 James 2018-09-22 11:35:57 UTC 
Created attachment 1485924 [details]
File: mountinfo
Comment 11 James 2018-09-22 11:35:58 UTC 
Created attachment 1485925 [details]
File: open_fds
Comment 12 James 2018-09-22 11:35:59 UTC 
Created attachment 1485926 [details]
File: proc_pid_status
Comment 13 Sajith Sasidharan 2018-10-04 15:58:14 UTC 
*** Bug 1636168 has been marked as a duplicate of this bug. ***
Comment 14 Ben Cotton 2019-05-02 20:44:49 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 Miroslav Suchý 2019-05-27 09:41:51 UTC 
This has been fixed in upstream in commit
1db19d0eddbdc8914add5f44a59d7f2f154918ba