vlc crashed with SIGSEGV in QMetaObject::activate()

Bug #475710 reported by dorpm
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vlc (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: vlc

it happened duriing switchiing dvb-t channels

ProblemType: Crash
Architecture: amd64
Date: Thu Nov 5 19:51:00 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/vlc
NonfreeKernelModules: nvidia
Package: vlc-nox 1.0.2-1ubuntu2
ProcCmdline: /usr/bin/vlc
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7fd0b700d32b: mov 0x8(%rax),%edx
 PC (0x7fd0b700d32b) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
 ?? () from /usr/lib/libQtDBus.so.4
 ?? () from /usr/lib/libQtDBus.so.4
 QMetaObject::activate(QObject*, int, int, void**) ()
 QObject::destroyed(QObject*) ()
 QObject::~QObject() () from /usr/lib/libQtCore.so.4
Title: vlc crashed with SIGSEGV in QMetaObject::activate()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout dip fuse lp lpadmin plugdev sambashare users vboxusers video
XsessionErrors: (polkit-gnome-authentication-agent-1:3531): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
dorpm (dorpmueller) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? () from /usr/lib/libQtDBus.so.4
?? () from /usr/lib/libQtDBus.so.4
QMetaObject::activate ()
QObject::destroyed () from /usr/lib/libQtCore.so.4
QObject::~QObject () from /usr/lib/libQtCore.so.4

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in vlc (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
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.