gvfsd-trash crashed with SIGSEGV in trash_item_invoke_closure()

Bug #1811540 reported by Paul White
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Low
Unassigned

Bug Description

I started a live session using daily ISO 20190112 within KVM. I opened the Settings application, changed the Ubuntu dock icon size and when I closed Settings I saw a crash notification which led to the reporting of this bug report.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gvfs-daemons 1.38.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu18
Architecture: amd64
CasperVersion: 1.401
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 12 21:34:16 2019
Disassembly: => 0x50: Cannot access memory at address 0x50
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190112)
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.27 /org/gtk/gvfs/exec_spaw/1
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x50: Cannot access memory at address 0x50
 PC (0x00000050) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gvfsd-trash crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Paul White (paulw2u) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 trash_item_invoke_closure (closure=0x55a54708fda0) at ../daemon/trashlib/trashitem.c:304
 trash_root_thaw (root=0x55a54704df70) at ../daemon/trashlib/trashitem.c:304
 trash_dir_set_files (dir=dir@entry=0x7f06a8005de0, items=<optimized out>, items@entry=0x0) at ../daemon/trashlib/trashdir.c:115
 trash_dir_free (dir=0x7f06a8005de0) at ../daemon/trashlib/trashdir.c:413

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 gvfs (Ubuntu):
importance: Undecided → Medium
summary: - gvfsd-trash crashed with SIGSEGV in g_closure_invoke()
+ gvfsd-trash crashed with SIGSEGV in trash_item_invoke_closure()
tags: removed: need-amd64-retrace
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1811540

tags: added: iso-testing
Paul White (paulw2u)
information type: Private → Public
Changed in gvfs (Ubuntu):
importance: Medium → Low
Revision history for this message
Leó Kolbeinsson (leok) wrote :

Tested today build 25.02.19 daily tests and was unable to repeat the error--changing icon size worked well for me. This was tested Live on a Dell laptop not in a virtual machine.

Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

Changed to incomplete since not replicable. If the original poster could retest and if it's still a problem, provide clear steps and conditions to reproduce, that would be great. Thanks!

Changed in gvfs (Ubuntu):
status: New → Invalid
status: Invalid → Incomplete
Revision history for this message
Paul White (paulw2u) wrote :

Closing my own bug report as "Invalid" as I:

1) Didn't see the crash again
2) Don't have Ubuntu 19.04 installed
3) No longer have KVM set-up to test

Changed in gvfs (Ubuntu):
status: Incomplete → Invalid
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.