nautilus crashed with SIGSEGV in bacon_video_widget_properties_set_has_type()

Bug #1376609 reported by Per-Inge on 2014-10-02
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Medium
Unassigned

Bug Description

I think this bug is related to
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1212601

The bug happened when I copied a media file with strange Audio/Video properties in Utopic.
The Audio/Video properties are shown OK in Ubuntu 14.04.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: totem 3.10.1-1ubuntu6
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Oct 2 10:28:48 2014
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2013-05-04 (515 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: /usr/bin/nautilus --no-default-window
SegvAnalysis:
 Segfault happened at: 0x7f99de8fcb20 <bacon_video_widget_properties_set_has_type+32>: mov (%rbx),%rcx
 PC (0x7f99de8fcb20) ok
 source "(%rbx)" (0x3fa999999999999a) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 bacon_video_widget_properties_set_has_type () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so
 ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in bacon_video_widget_properties_set_has_type()
UpgradeStatus: Upgraded to utopic on 2014-04-28 (156 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Per-Inge (per-inge-hallin) wrote :
information type: Private → Public

StacktraceTop:
 bacon_video_widget_properties_set_has_type (props=0x3fa999999999999a, has_video=has_video@entry=0, has_audio=has_audio@entry=0) at bacon-video-widget-properties.c:213
 discovered_cb (discoverer=<optimized out>, info=0x330ab20, error=<optimized out>, props=0x32c6380) at totem-properties-view.c:290
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7fffec57e230, fn=0x7f99de8fbad0 <discovered_cb>, rvalue=0x7fffec57e190, avalue=avalue@entry=0x7fffec57e130) at ../src/x86/ffi64.c:525
 g_cclosure_marshal_generic (closure=0x356b5b0, return_gvalue=0x0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=0x0) at /build/buildd/glib2.0-2.41.5/./gobject/gclosure.c:1448

Changed in totem (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Vindicator (vindicator) wrote :

Same thing for me in Wily.
I am in the middle of transcoding an audio/video file that already had messed up data (timestamps, "past duration", whatever).
I'm guessing that since the video source and destination folders are open in Nautilus, thumbnail (re)creation is being attempted for the output file and it didn't like a sample location. Only a guess.

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

Other bug subscribers