xdg-desktop-portal crashed with SIGSEGV

[Vittorio Ballestra]

clicked : crashed

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: xdg-desktop-portal 0.8-2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Oct 5 11:36:53 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20130203-1
ExecutablePath: /usr/lib/xdg-desktop-portal/xdg-desktop-portal
InstallationDate: Installed on 2014-11-06 (1064 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50
ProcCmdline: /usr/lib/xdg-desktop-portal/xdg-desktop-portal
ProcEnviron:
 LANG=it_IT.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x562aef90d508: mov 0x8(%rax),%rcx
 PC (0x562aef90d508) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xdg-desktop-portal
StacktraceTop:
 ()
 ()
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: xdg-desktop-portal crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-10-01 (3 days ago)
UserGroups: adm cdrom davfs2 debian-tor dip docker lpadmin lxd plugdev sambashare sudo vboxusers

[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 #1691649, 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.