Bug 1027749

Created attachment 821020 [details]
File: backtrace

Created attachment 821021 [details]
File: cgroup

Created attachment 821022 [details]
File: core_backtrace

Created attachment 821023 [details]
File: dso_list

Created attachment 821024 [details]
File: environ

Created attachment 821025 [details]
File: exploitable

Created attachment 821026 [details]
File: limits

Created attachment 821027 [details]
File: maps

Created attachment 821028 [details]
File: open_fds

Created attachment 821029 [details]
File: proc_pid_status

Created attachment 821030 [details]
File: var_log_messages

Jeremy, are you able to reproduce?

> Nov 07 11:12:18 localhost.localdomain NetworkManager[1086]: <warn> No agents were available for this request.
means that there is no secret agent (NM applet) to provide secrets.
Do you run gnome-shell or other DE? Was there a crash of the shell/applet?

> Nov 07 11:12:37 localhost.localdomain NetworkManager[1086]: nm_secret_agent_get_description: assertion 'NM_IS_SECRET_AGENT (agent)' failed
is the problem. We use an invalid agent object and crash later.

Would you install NetworkManager-debuginfo package, so that we can have more information if you are able to reproduce.

Installed NetworkManager-debuginfo-0.9.9.0.15
Currently on NetworkManager-0.9.9.0-15

Not reproducing for me at present...  fixed in this version, maybe?

I didn't check on the shell before; it could have been gnome-shell.
Current is xfce4-terminal.  I don't use any IDE.

*** Bug 1030193 has been marked as a duplicate of this bug. ***

Another user experienced a similar problem:

Booting into XFCE session after laptop got roughly switched off due to electricity breakdown and no battery inserted.

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/sbin/NetworkManager --no-daemon
crash_function: nm_secret_agent_get_secrets
executable:     /usr/sbin/NetworkManager
kernel:         3.11.10-301.fc20.i686+PAE
package:        NetworkManager-0.9.9.0-20.git20131003.fc20
reason:         NetworkManager killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            0

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.

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.