totem crashed with SIGSEGV in g_variant_unref()

Bug #828853 reported by Zijyfe Duufop
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
New
Undecided
Unassigned

Bug Description

don't know

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: totem 3.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Thu Aug 18 10:36:25 2011
ExecutablePath: /usr/bin/totem
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705)
LogAlsaMixer:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
ProcCmdline: /usr/bin/totem /media/Storage/Videos/Season\ 14\ -\ Complete/The\ Simpsons\ [14x05]\ Helter\ Shelter.avi
ProcCwd: /home/yehuda/Documents
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc00cbad4e9 <g_variant_unref+9>: lock xadd %eax,0x24(%rdi)
 PC (0x7fc00cbad4e9) ok
 source "%eax" ok
 destination "0x24(%rdi)" (0x00000024) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 g_variant_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/libtotem.so.0
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: totem crashed with SIGSEGV in g_variant_unref()
UpgradeStatus: Upgraded to oneiric on 2011-07-27 (21 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Zijyfe Duufop (zijifayd) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #827918, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
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.