totem crashed with SIGSEGV in g_mount_spec_get()

Bug #1860235 reported by El jinete sin cabeza
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gvfs
New
Unknown
gvfs (Ubuntu)
Triaged
Low
Unassigned
totem (Ubuntu)
Triaged
Low
Unassigned

Bug Description

https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace
https://gitlab.gnome.org/GNOME/gvfs/issues/446

---

This happened to me when I opened nautilus and accessed my NAS through smb. And press double click on file and totem crash.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: totem 3.34.1-2ubuntu1
Uname: Linux 5.4.12-050412-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 17 19:08:13 2020
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2018-12-02 (412 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/bin/totem --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=es_CL:es
 LANG=es_CL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ff6dc45dd09 <g_mount_spec_get+57>: mov (%rbx),%rdi
 PC (0x7ff6dc45dd09) ok
 source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
 () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18
 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18
Title: totem crashed with SIGSEGV in g_mount_spec_get()
UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Revision history for this message
El jinete sin cabeza (ejsc-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_mount_spec_get (spec=spec@entry=0x560d463e9e60, key=key@entry=0x7ff6dc4624cc "type") at ../common/gmountspec.c:422
 g_mount_spec_get_type (spec=spec@entry=0x560d463e9e60) at ../common/gmountspec.c:432
 _g_daemon_vfs_mountspec_get_uri_scheme (spec=0x560d463e9e60) at ../client/gdaemonvfs.c:529
 g_daemon_file_has_uri_scheme (file=0x7ff6d402b730, uri_scheme=0x7ff6e252c711 "itms") at ../client/gdaemonfile.c:136
 totem_pl_parser_is_itms_feed (file=file@entry=0x7ff6d402b730) at ../plparse/totem-pl-parser-podcast.c:744

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 totem (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
El jinete sin cabeza (ejsc-deactivatedaccount) wrote :
information type: Private → Public
description: updated
Changed in totem:
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in totem (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
Revision history for this message
El jinete sin cabeza (ejsc-deactivatedaccount) wrote :
description: updated
no longer affects: totem
Changed in gvfs:
status: Unknown → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. Though since there have only been a couple dozen instances of this crash in the past 5 years I think Low priority is most appropriate. Sounds like it relates to using totem over SMB mounts?..

Changed in gvfs (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
status: Confirmed → Triaged
Changed in totem (Ubuntu):
status: Confirmed → Triaged
Changed in gvfs (Ubuntu):
importance: Medium → Low
Changed in totem (Ubuntu):
importance: Medium → Low
Revision history for this message
El jinete sin cabeza (ejsc-deactivatedaccount) wrote :

Yes, I work with smb on a NAS.

description: updated
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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