vlc crashed with SIGSEGV in QWidget::actions()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vlc (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
vlc:
Installed: 2.1.2-2build2
Candidate: 2.1.2-2build2
Version table:
*** 2.1.2-2build2 0
500 http://
100 /var/lib/
action that provoc the crash of vlc: trying to move it's window with shortcuts (ctrl+alt+num on numpad) when in fullscreen.
Expected : fullscreen goes off and vlc window is in the corner you choosed.
Happened: Full screen didn't pop, screen of vlc stay black then vlc exit on segv when tryied to resize.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: vlc-nox 2.1.2-2build2
ProcVersionSign
Uname: Linux 3.13.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Apr 11 00:01:13 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/vlc
InstallationDate: Installed on 2014-04-08 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140408)
ProcCmdline: vlc
SegvAnalysis:
Segfault happened at: 0x7f92256f4d97 <_ZNK7QWidget7a
PC (0x7f92256f4d97) ok
source "0x1b8(%rdx)" (0x6492a867a9a0
destination "%rdx" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
QWidget::actions() const () from /usr/lib/
QMenu::clear() () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: vlc crashed with SIGSEGV in QWidget::actions()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1280889, 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.