Ubuntu
linphone package

linphone-3 crashed with SIGSEGV in sws_scale()

Bug #864657 reported by Sergei A. Beilin on 2011-10-02

This bug report is a duplicate of: Bug #603107: linphone-3 crashed with SIGSEGV in sws_scale(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linphone (Ubuntu)	New	Undecided	Unassigned

Bug Description

Upgraded to oneiric, installed linphone, and it crashes at startup.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: linphone 3.3.2-4.1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Oct 2 18:43:16 2011
ExecutablePath: /usr/bin/linphone-3
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: linphone-3
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=ru_RU.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fe4ca31adda: callq *%rax
PC (0x7fe4ca31adda) ok
source "*%rax" (0xc0244489489848c8) not located in a known VMA region (needed readable region)!
destination "(%rsp)" (0x7fffc275a000) ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: linphone
StacktraceTop:
?? () from /usr/lib/libswscale.so.2
sws_scale () from /usr/lib/libswscale.so.2
?? () from /usr/lib/libmediastreamer.so.0
ms_load_jpeg_as_yuv () from /usr/lib/libmediastreamer.so.0
static_image_preprocess () from /usr/lib/libmediastreamer.so.0
Title: linphone-3 crashed with SIGSEGV in sws_scale()
UpgradeStatus: Upgraded to oneiric on 2011-09-07 (25 days ago)
UserGroups: admin cdrom dialout floppy lpadmin plugdev sambashare

Tags:

Revision history for this message

Sergei A. Beilin (sbeilin) wrote on 2011-10-02:

XsessionErrors.txt Edit (3.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-10-02: 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 #864376, 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.