gnome-software crashed with SIGSEGV in g_io_channel_shutdown()

[Sufian Ahmad]

i tried to install wireshark but this error appear

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.26.3-2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 9 13:05:23 2018
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2018-01-09 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.26.3-2ubuntu1
ProcCmdline: /usr/bin/gnome-software --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7fcb7d52252f <g_io_channel_shutdown+111>: cmpq $0x0,0x8(%rdi)
 PC (0x7fcb7d52252f) ok
 source "$0x0" ok
 destination "0x8(%rdi)" (0x4030000000000008) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 g_io_channel_shutdown () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-software crashed with SIGSEGV in g_io_channel_shutdown()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1740151, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.