gnome-mplayer crashed with SIGSEGV in g_source_remove()

Bug #212081 reported by cefc
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glib2.0 (Ubuntu)
Invalid
Medium
Unassigned
gnome-mplayer (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-mplayer

gnome-mplayer crashed with SIGSEGV in g_source_remove()

ProblemType: Crash
Architecture: amd64
Date: Sat Apr 5 12:57:02 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-mplayer
NonfreeKernelModules: nvidia
Package: gnome-mplayer 0.6.0-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: gnome-mplayer /home/username/data/video/username/【動畫】/【驚爆危機】/【驚爆危機~校園篇】/[reca][dmhy][fmp2][dvdrip][04][500k].rmvb
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=zh_TW.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-mplayer
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 g_source_remove () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 start_thread () from /lib/libpthread.so.0
Title: gnome-mplayer crashed with SIGSEGV in g_source_remove()
Uname: Linux 2.6.24-15-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags: apport-crash
Revision history for this message
cefc (cedriccefc2002) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_source_destroy_internal (source=0x98dd90,
IA__g_source_remove (tag=<value optimized out>)
launch_player (data=0x98c9d0) at thread.c:769
g_thread_create_proxy (data=0x98e3e0)
start_thread () from /lib/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in gnome-mplayer:
importance: Undecided → Medium
Changed in gnome-mplayer:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Could you try to get a valgrind log for the crash (you can follow the instructions on https://wiki.ubuntu.com/Valgrind)?

Changed in glib2.0:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in glib2.0:
status: Incomplete → 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.