vlc crashed with SIGSEGV in QBrush::QBrush()

Bug #268686 reported by Progressive
8
Affects Status Importance Assigned to Milestone
gtk-qt-engine (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: vlc

Apport claims the program crashed, but at least the instance that was showing on my screen was fine. Maybe it was a zombie from my previous session.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/vlc
Package: vlc-nox 0.8.6.release.h-1ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/vlc
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: vlc
StacktraceTop:
 QBrush::QBrush () from /usr/lib/libQtGui.so.4
 QPalette::detach () from /usr/lib/libQtGui.so.4
 QPalette::setBrush () from /usr/lib/libQtGui.so.4
 ?? ()
 ?? ()
Title: vlc crashed with SIGSEGV in QBrush::QBrush()
Uname: Linux 2.6.27-2-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
Progressive (vbgraphix2003) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:QBrush::QBrush () from /usr/lib/libQtGui.so.4
QPalette::detach () from /usr/lib/libQtGui.so.4
QPalette::setBrush () from /usr/lib/libQtGui.so.4
?? () from /usr/lib/gtk-2.0/2.10.0/engines/libqt4engine.so
?? () from /usr/lib/gtk-2.0/2.10.0/engines/libqt4engine.so

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

The crash is actually in gtk-qt-engine.

Changed in vlc:
importance: Undecided → Low
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

The latest vlc can't trigger this any more since vlc uses Qt now, so I'm closing this bug.

Changed in gtk-qt-engine:
status: New → Invalid
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.