vlc crashes when opening ".flv" files with it

Bug #1520977 reported by Abhilash Roy Gollamandala
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

vlc gives "Segmentation Fault" when run through terminal to access a "flv" video or will not open "vlc" when double clicked on the
flv video in filesystem or when dragged and dropped into an opened vlc, the vlc window disappears.

VLC output: (vlc pokemonxy_ep31.flv)

VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1~trusty1)
[00000000020d7118] core libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
Segmentation fault (core dumped)

My ubuntu: (lsb_release -a)

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
Uname: Linux 3.13.0-68-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Nov 30 00:44:49 2015
DistUpgraded: 2014-11-29 17:13:59,703 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3977]
InstallationDate: Installed on 2014-06-16 (531 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 20236
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic.efi.signed root=UUID=bd8ecfac-06ff-45bf-a245-a5a63a2c2221 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-11-29 (365 days ago)
dmi.bios.date: 11/19/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 78CN25WW(V2.03)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 00000000Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G500
dmi.modalias: dmi:bvnLENOVO:bvr78CN25WW(V2.03):bd11/19/2013:svnLENOVO:pn20236:pvrLenovoG500:rvnLENOVO:rnINVALID:rvr00000000NotDefined:cvnLENOVO:ct10:cvrLenovoG500:
dmi.product.name: 20236
dmi.product.version: Lenovo G500
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Nov 27 22:03:41 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 826
 vendor LGD
xserver.version: 2:1.15.1-0ubuntu2.7

Revision history for this message
Abhilash Roy Gollamandala (abhilashroy-g) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Abhilash Roy Gollamandala, thank you for reporting this and helping make Ubuntu better.

After VLC crashes, are there crash files in /var/crash?

tags: added: latest-bios-2.03
Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Abhilash Roy Gollamandala (abhilashroy-g) wrote :

Yes, yes. I found this file there: _usr_bin_vlc.1000.crash

I am attaching it.

Revision history for this message
penalvch (penalvch) wrote :

Abhilash Roy Gollamandala, thank you for reporting this and helping make Ubuntu better. However, your crash report is manually attached.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

If you do open this report, please feel free to subscribe me to it.

However, I'm closing this report since the process outlined above will deal with this issue more efficiently. Also, please do not attach your crash report manually to this report and reopen it. Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xorg (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Abhilash Roy Gollamandala (abhilashroy-g) wrote :

Hi, when I tried the second method. I got that "the bug cannot be reported as it is from a third-party package" kind of message.
I did follow the first method though.

Thanks for your help. Hope it will get solved soon.

Thank you.

Revision history for this message
penalvch (penalvch) wrote :

Abhilash Roy Gollamandala:
>"Hi, when I tried the second method. I got that "the bug cannot be reported as it is from a third-party package" kind of message."

This message is expected as you are using a third party version (i.e. PPA or self compiled, etc.) of VLC. The version that is supported in Trusty may be found at https://launchpad.net/ubuntu/+source/vlc .

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.