Bug 1115465

Summary: [abrt] nm-connection-editor: g_value_unset(): nm-connection-editor killed by SIGSEGV
Product: [Fedora] Fedora Reporter: leigh scott <leigh123linux>
Component: network-manager-appletAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dcbw, jklimes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8bb8617348ed5913a8f761fc0bee62433daa6670
Whiteboard: abrt_hash:e1e8cf901a7765b29fc8f8bcfc03e4de1592b10c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 21:26:19 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: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description leigh scott 2014-07-02 12:14:23 UTC
Description of problem:
Used forget network connection using control-center network panel.

Version-Release number of selected component:
nm-connection-editor-0.9.9.0-10.git20140123.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        nm-connection-editor
crash_function: g_value_unset
executable:     /usr/bin/nm-connection-editor
kernel:         3.15.2-1.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #1 g_value_unset at gvalue.c:274
 #4 marshal_dbus_message_to_g_marshaller at dbus-gproxy.c:1736
 #9 dbus_g_proxy_emit_remote_signal at dbus-gproxy.c:1789
 #10 dbus_g_proxy_manager_filter at dbus-gproxy.c:1356

Comment 1 leigh scott 2014-07-02 12:14:27 UTC
Created attachment 914145 [details]
File: backtrace

Comment 2 leigh scott 2014-07-02 12:14:29 UTC
Created attachment 914146 [details]
File: cgroup

Comment 3 leigh scott 2014-07-02 12:14:31 UTC
Created attachment 914147 [details]
File: core_backtrace

Comment 4 leigh scott 2014-07-02 12:14:34 UTC
Created attachment 914148 [details]
File: dso_list

Comment 5 leigh scott 2014-07-02 12:14:36 UTC
Created attachment 914149 [details]
File: environ

Comment 6 leigh scott 2014-07-02 12:14:38 UTC
Created attachment 914150 [details]
File: exploitable

Comment 7 leigh scott 2014-07-02 12:14:39 UTC
Created attachment 914151 [details]
File: limits

Comment 8 leigh scott 2014-07-02 12:14:41 UTC
Created attachment 914152 [details]
File: maps

Comment 9 leigh scott 2014-07-02 12:14:43 UTC
Created attachment 914153 [details]
File: open_fds

Comment 10 leigh scott 2014-07-02 12:14:45 UTC
Created attachment 914154 [details]
File: proc_pid_status

Comment 11 Fedora End Of Life 2015-05-29 12:16:50 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 12 Fedora End Of Life 2015-06-29 21:26:19 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.