Ubuntu
totem package

totem crashed with SIGABRT in _g_log_abort()

Bug #1197507 reported by Jo-Erlend Schinstad on 2013-07-03

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Totem	Fix Released	Critical	gnome-bugs #708647
	totem (Ubuntu)	Fix Released	High	Unassigned

Bug Description

Tried to open a video file and Totem crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: totem 3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Wed Jul 3 17:07:56 2013
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2013-06-26 (6 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
MarkForUpload: True
ProcCmdline: totem /home/username/Nedlastinger/Weeds\ Season\ 8\ 720p\ HD\ [CARG]/Weeds\ S08E01\ Messy.mkv
ProcEnviron:
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=nb_NO.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: totem
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: totem crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Related branches

lp://staging/ubuntu/trusty-proposed/totem

Revision history for this message

Jo-Erlend Schinstad (joerlend.schinstad-deactivatedaccount) wrote on 2013-07-03:

Dependencies.txt Edit (11.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (863 bytes, text/plain; charset="utf-8")
GstreamerVersions.txt Edit (5.9 KiB, text/plain; charset="utf-8")
LogAlsaMixer.txt Edit (4.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (119.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (827 bytes, text/plain; charset="utf-8")
Registers.txt Edit (741 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (994 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (24.5 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (60.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-07-03:

StacktraceTop:
_g_log_abort () at /build/buildd/glib2.0-2.37.3/./glib/gmessages.c:255
g_assertion_message (domain=domain@entry=0x7ffef6035707 "Totem", file=file@entry=0x7ffef603a65d "totem-fullscreen.c", line=line@entry=310, func=func@entry=0x7ffef603a900 <__PRETTY_FUNCTION__.57919> "totem_fullscreen_show_popups", message=<optimized out>) at /build/buildd/glib2.0-2.37.3/./glib/gtestutils.c:2075
g_assertion_message_expr (domain=domain@entry=0x7ffef6035707 "Totem", file=file@entry=0x7ffef603a65d "totem-fullscreen.c", line=line@entry=310, func=func@entry=0x7ffef603a900 <__PRETTY_FUNCTION__.57919> "totem_fullscreen_show_popups", expr=expr@entry=0x7ffef603a770 "fs->priv->is_fullscreen != FALSE") at /build/buildd/glib2.0-2.37.3/./glib/gtestutils.c:2086
totem_fullscreen_show_popups (fs=0x7ffef6e5a4b0, show_cursor=<optimized out>) at totem-fullscreen.c:310
totem_object_action_remote (totem=0x7ffef6cb8190, cmd=17009, cmd@entry=TOTEM_REMOTE_COMMAND_REPLACE, url=0x0) at totem-object.c:3147

Revision history for this message

Apport retracing service (apport) wrote on 2013-07-03: Stacktrace.txt

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

Revision history for this message

Apport retracing service (apport) wrote on 2013-07-03: ThreadStacktrace.txt

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

Changed in totem (Ubuntu):
importance:	Undecided → Medium
summary:	- totem crashed with SIGABRT in raise() + totem crashed with SIGABRT in _g_log_abort()
tags:	removed: need-amd64-retrace

Revision history for this message

Sebastien Bacher (seb128) wrote on 2013-11-15:

error report on https://errors.ubuntu.com/problem/50cf188a55f6058ae5d708a6284b575e43df2b4d

The issue is fixed in git with
https://git.gnome.org/browse/totem/commit/?h=gnome-3-8&id=5086168b4062c3fa07258dc517f8f94f1303bee5

information type:	Private → Public
Changed in totem (Ubuntu):
status:	New → Fix Committed
importance:	Medium → High

Bug Watch Updater (bug-watch-updater) on 2013-11-15

Changed in totem:
importance:	Unknown → Critical
status:	Unknown → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-11-15:

This bug was fixed in the package totem - 3.8.2-0ubuntu2

---------------
totem (3.8.2-0ubuntu2) trusty; urgency=low

  [ Jeremy Bicha ]
  * debian/control.in:
    - Don't build-depend on scrollkeeper

  [ Sebastien Bacher ]
  * debian/patches/git_no_assert_on_start.patch:
    - "main: Fix possible assertion on startup" (lp: #1197507)
-- Sebastien Bacher <email address hidden> Fri, 15 Nov 2013 16:02:30 +0100

Changed in totem (Ubuntu):
status:	Fix Committed → Fix Released

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

gnome-bugs #708647
[RESOLVED FIXED] Edit

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

Ubuntutotem package

totem crashed with SIGABRT in _g_log_abort()

Bug Description

Related branches

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
totem package