Bug 1099723

Summary: [abrt] network-manager-applet: _dbus_abort(): nm-applet killed by SIGABRT
Product: [Fedora] Fedora Reporter: dubultra
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, pessoft
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f773ba13dc6945de420f987978d104975ab39f33
Whiteboard: abrt_hash:508ac4ae9dec8197c62022ce6ac0aa8d6baecfd9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:44:40 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description dubultra 2014-05-21 04:16:00 UTC 
Description of problem:
connecting vpn and when i first power up and log into lxde i have to sudo setenforce 0 so that my vpn will connect without SElinux stopping it


ps. im looking to get rare and different old computers and really enjoy old server and networking equipment.  dubultra if you have any old computer parts or systems you want to sell

Version-Release number of selected component:
network-manager-applet-0.9.9.0-9.git20140123.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        nm-applet
crash_function: _dbus_abort
executable:     /usr/bin/nm-applet
kernel:         3.12.8-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _dbus_abort at dbus-sysdeps.c:94
 #3 _dbus_warn_check_failed at dbus-internals.c:290
 #4 dbus_message_iter_append_basic at dbus-message.c:2586
 #5 marshal_basic at dbus-gvalue.c:1452
 #6 marshal_map_entry at dbus-gvalue.c:1654
 #7 hashtable_foreach_with_values at dbus-gvalue-utils.c:586
 #8 g_hash_table_foreach at ghash.c:1526
 #9 hashtable_iterator at dbus-gvalue-utils.c:608
 #10 marshal_map at dbus-gvalue.c:1716
 #11 marshal_variant at dbus-gvalue.c:1805

Potential duplicate: bug 962321
Comment 1 dubultra 2014-05-21 04:16:04 UTC 
Created attachment 897806 [details]
File: backtrace
Comment 2 dubultra 2014-05-21 04:16:06 UTC 
Created attachment 897807 [details]
File: cgroup
Comment 3 dubultra 2014-05-21 04:16:07 UTC 
Created attachment 897808 [details]
File: core_backtrace
Comment 4 dubultra 2014-05-21 04:16:09 UTC 
Created attachment 897809 [details]
File: dso_list
Comment 5 dubultra 2014-05-21 04:16:10 UTC 
Created attachment 897810 [details]
File: environ
Comment 6 dubultra 2014-05-21 04:16:12 UTC 
Created attachment 897811 [details]
File: limits
Comment 7 dubultra 2014-05-21 04:16:13 UTC 
Created attachment 897812 [details]
File: maps
Comment 8 dubultra 2014-05-21 04:16:15 UTC 
Created attachment 897813 [details]
File: open_fds
Comment 9 dubultra 2014-05-21 04:16:16 UTC 
Created attachment 897814 [details]
File: proc_pid_status
Comment 10 dubultra 2014-05-21 04:16:18 UTC 
Created attachment 897815 [details]
File: var_log_messages
Comment 11 Jirka Klimes 2014-05-21 14:47:46 UTC 
There's a problem with D-Bus messages. nm-applet may pass invalid argument to dbus_g_method_return() or something.

If you are able to reproduce the issue, could you be more specific about what type of VPN do you use, how/where do you store password for it.
And please include log messages:
* for NM sudo journalctl -u NetworkManager.service
* for nm-applet, please start it in a terminal to see the messages it writes
Comment 12 Peter "Pessoft" Kolínek 2014-11-06 18:35:36 UTC 
Another user experienced a similar problem:

For unknown reason nm applet forgot user's password for OpenVPN connection's certificate. Attempt to reinsert the key via configuration menu and reattempt to connect VPN connection failed again and crashed the applet.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        nm-applet
crash_function: _dbus_abort
executable:     /usr/bin/nm-applet
kernel:         3.16.6-200.fc20.x86_64
package:        network-manager-applet-0.9.9.0-10.git20140123.fc20
reason:         nm-applet killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Fedora End Of Life 2015-05-29 11:54:43 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 14 Fedora End Of Life 2015-06-29 20:44:40 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.