Ubuntu
gvfs package

gvfsd-smb-browse crashed with SIGABRT in talloc_abort()

Bug #1651130 reported by Thomas A. F. Thorne on 2016-12-19

14

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	gvfs (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

Had plugged in a Micro SD card. Closed the two file browser windows that automatically opened. Did an `lsblk` on the command line and noticed that no SD card was shown. A few seconds later an error report came up.

Now the report has complete the sd card is mounted once again. Things managed to recover without any physical intervention on my part.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gvfs-backends 1.28.2-1ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Dec 19 13:32:28 2016
ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
InstallationDate: Installed on 2015-03-12 (647 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 /org/gtk/gvfs/exec_spaw/39
ProcEnviron:
XDG_RUNTIME_DIR=<set>
SHELL=/bin/bash
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=en_GB.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
talloc_named_const () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
?? () from /usr/lib/x86_64-linux-gnu/libsamba-util.so.0
smbc_free_context () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
?? ()
Title: gvfsd-smb-browse crashed with SIGABRT in talloc_named_const()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark

Tags:

Revision history for this message

Thomas A. F. Thorne (tafthorne) wrote on 2016-12-19:

#1

Dependencies.txt Edit (10.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (33.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (65.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (980 bytes, text/plain; charset="utf-8")
Registers.txt Edit (693 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (12.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2016-12-19:

#2

StacktraceTop:
talloc_abort () from /tmp/apport_sandbox_9kV89N/usr/lib/x86_64-linux-gnu/libtalloc.so.2
talloc_named_const () from /tmp/apport_sandbox_9kV89N/usr/lib/x86_64-linux-gnu/libtalloc.so.2
talloc_stackframe_internal () from /tmp/apport_sandbox_9kV89N/usr/lib/x86_64-linux-gnu/libsamba-util.so.0
smbc_free_context () from /tmp/apport_sandbox_9kV89N/usr/lib/x86_64-linux-gnu/libsmbclient.so.0
g_vfs_backend_smb_browse_finalize (object=0x1b9f660) at gvfsbackendsmbbrowse.c:223

Revision history for this message

Apport retracing service (apport) wrote on 2016-12-19: Stacktrace.txt

#3

Stacktrace.txt Edit (4.0 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2016-12-19: StacktraceSource.txt

#4

StacktraceSource.txt Edit (4.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2016-12-19: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (14.5 KiB, text/plain)

Changed in gvfs (Ubuntu):
importance:	Undecided → Medium
summary:	- gvfsd-smb-browse crashed with SIGABRT in talloc_named_const() + gvfsd-smb-browse crashed with SIGABRT in talloc_abort()
tags:	removed: need-amd64-retrace

Revision history for this message

Thomas A. F. Thorne (tafthorne) wrote on 2016-12-28:

#6

I have come accross this problem again today. I was not doing anything with memory cards this time.

Revision history for this message

Thomas A. F. Thorne (tafthorne) wrote on 2019-08-07:

#7

Marking as non-private as it has been long enough I am comfortable that anything stored is no longer sensative. I do not think there is anything sensitive in there anyway.

I am back here now as I have just raised bug 1839247 however that only looks related by attributed package and nothing more. I know I am not running on the same hardware.

information type:

Private → Public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2021-07-19:

#8

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

Changed in gvfs (Ubuntu):
status:	New → Confirmed

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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