gnome-software crashed with SIGSEGV in gs_plugin_loader_set_network_status()

[Udara Madubhashana]

gnome-software crashed when launch

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-32.51-generic 4.4.15
Uname: Linux 4.4.0-32-generic x86_64
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sat Jul 23 11:23:59 2016
ExecutablePath: /usr/bin/gnome-software
ExecutableTimestamp: 1466154793
ProcCmdline: gnome-software
ProcCwd: /var/crash
SegvAnalysis:
 Segfault happened at: 0x55fd997da400 <gs_plugin_loader_set_network_status+48>: cmp %esi,0x68(%rbp)
 PC (0x55fd997da400) ok
 source "%esi" ok
 destination "0x68(%rbp)" (0x00000068) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 gs_plugin_loader_set_network_status ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-software crashed with SIGSEGV in gs_plugin_loader_set_network_status()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Yonatan (yonatan-redhat-bugs)]

Version-Release number of selected component:
gnome-software-3.18.2-2.fc23

Additional info:
reporter: libreport-2.6.3
backtrace_rating: 4
cmdline: gnome-software --local-filename=/var/cache/dnf/updates-96b7b648a31a001b/packages/wine-mono-4.5.6-4.fc23.noarch.rpm
crash_function: gs_plugin_loader_set_network_status
executable: /usr/bin/gnome-software
global_pid: 11123
kernel: 4.2.5-300.fc23.i686
runlevel: N 5
type: CCpp
uid: 0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gs_plugin_loader_set_network_status at gs-plugin-loader.c:3240
 #1 network_changed_cb at gs-application.c:164
 #2 gs_application_monitor_network at gs-application.c:175
 #3 gs_application_startup at gs-application.c:598
 #4 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:905
 #5 g_type_class_meta_marshalv at gclosure.c:1021
 #6 _g_closure_invoke_va at gclosure.c:864
 #9 g_application_register at gapplication.c:2015
 #10 gs_application_handle_local_options at gs-application.c:655
 #11 ffi_call_SYSV at ../src/x86/sysv.S:65

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093869
File: backtrace

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093870
File: cgroup

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093871
File: core_backtrace

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093872
File: dso_list

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093873
File: environ

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093874
File: exploitable

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093875
File: limits

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093876
File: maps

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093877
File: mountinfo

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093878
File: open_fds

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093879
File: proc_pid_status

[Yonatan (yonatan-redhat-bugs)]

Created attachment 1093880
File: var_log_messages

[Richard (richard-redhat-bugs)]

Interesting; is this reproducable?

[Apport retracing service (apport)]

StacktraceTop:
 gs_plugin_loader_set_network_status (plugin_loader=0x0, online=0) at gs-plugin-loader.c:3489
 network_changed_cb (app=0x55fd9b2b10e0, available=<optimized out>, monitor=<optimized out>) at gs-application.c:174
 gs_application_monitor_network (app=0x55fd9b2b10e0) at gs-application.c:190
 gs_application_startup (application=<optimized out>) at gs-application.c:824
 _g_closure_invoke_va () from /tmp/apport_sandbox_EGvkXJ/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

[Fedora (fedora-redhat-bugs)]

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 (fedora-redhat-bugs)]

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.