totem crashed with SIGSEGV in g_str_hash()

Bug #1738025 reported by Paul White
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/b6bdd53dfb82772c52f94ada5dd629fb48ba155e

---

I had nautilus open to display media files on a NAS drive. I double clicked on a file and waited for totem to open. It didn't. I was then prompted to report the problem. nautilus seems to be working correctly as I can navigate the NAS drive without problem.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.8-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 13 15:41:15 2017
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-11-07 (35 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/totem --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f1c4e3871f0 <g_str_hash>: movsbl (%rdi),%edx
 PC (0x7f1c4e3871f0) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 g_str_hash () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () 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
Title: totem crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

StacktraceTop:
 g_str_hash (v=0x0) at ../../../../glib/ghash.c:1882
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x55f9f9785f60) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x55f9f9785f60, key=key@entry=0x0) at ../../../../glib/ghash.c:1153
 _g_daemon_vfs_mountspec_get_uri_scheme (spec=0x55f9f979b470) at gdaemonvfs.c:531
 g_daemon_file_has_uri_scheme (file=0x55f9fa2fe190, uri_scheme=0x7f1c4a041461 "mms") at gdaemonfile.c:136

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
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 totem (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
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.