xdg-desktop-portal-gtk crashed with SIGSEGV in g_path_is_absolute()

Bug #1716026 reported by Cristian Aravena Romero
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xdg-desktop-portal-gtk (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Hi,

I'm working with gnome-builder -> flatpak

Regards,
--
Cristian

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: xdg-desktop-portal-gtk 0.7-2
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Sep 8 14:42:59 2017
ExecutablePath: /usr/lib/xdg-desktop-portal/xdg-desktop-portal-gtk
InstallationDate: Installed on 2017-07-05 (64 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/lib/xdg-desktop-portal/xdg-desktop-portal-gtk
SegvAnalysis:
 Segfault happened at: 0x7f6501b3fd07 <g_path_is_absolute+7>: cmpb $0x2f,(%rdi)
 PC (0x7f6501b3fd07) ok
 source "$0x2f" ok
 destination "(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: xdg-desktop-portal-gtk
StacktraceTop:
 g_path_is_absolute () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 gtk_file_chooser_set_current_folder () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
Title: xdg-desktop-portal-gtk crashed with SIGSEGV in g_path_is_absolute()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_path_is_absolute (file_name=file_name@entry=0x4 <error: Cannot access memory at address 0x4>) at ../../../../glib/gfileutils.c:2119
 canonicalize_filename (filename=filename@entry=0x4 <error: Cannot access memory at address 0x4>) at ../../../../gio/glocalfile.c:209
 _g_local_file_new (filename=0x4 <error: Cannot access memory at address 0x4>) at ../../../../gio/glocalfile.c:307
 gtk_file_chooser_set_current_folder (chooser=0xcdc00cabf0, filename=filename@entry=0x4 <error: Cannot access memory at address 0x4>) at ././gtk/gtkfilechooser.c:908
 handle_open (object=<optimized out>, invocation=0x7f64e80119c0, arg_handle=<optimized out>, arg_app_id=<optimized out>, arg_parent_window=<optimized out>, arg_title=<optimized out>, arg_options=0x7f64e8019190) at src/filechooser.c:458

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xdg-desktop-portal-gtk (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Cristian Aravena Romero (caravena) wrote :
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xdg-desktop-portal-gtk (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.