gnash crashed with signal 5 in g_logv()

Bug #122683 reported by Toby Smithe
4
Affects Status Importance Assigned to Milestone
gnash (Ubuntu)
Invalid
High
Mozilla Bugs

Bug Description

Binary package hint: gnash

Is this related to bug 122389?

ProblemType: Crash
Architecture: i386
Date: Wed Jun 27 22:00:55 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnash
NonfreeKernelModules: cdrom
Package: gnash 0.8.0~cvs20070611.1016-1ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/bin/gnash -v -x 35718365 -j 1 -k 1 -u http://video.google.com/proxy.swf -U http://video.google.com/videohosted?docid=-7269205919871967751 -P FlashVars=targetId=-7269205919871967751&functionName=pause -P PARAM= -P SRC=/proxy.swf -P align=middle -P bgcolor=#ffffff -P data=/proxy.swf -P height=1 -P id=VideoDataStore -P movie=/proxy.swf -P quality=best -P salign=TL -P scale=noScale -P width=1 -P wmode=window -
ProcCwd: /home/toby
ProcEnviron:
 PATH=/home/toby/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnash
StacktraceTop:
 g_logv () from /usr/lib/libglib-2.0.so.0
 g_log () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? ()
Title: gnash crashed with signal 5 in g_logv()
Uname: Linux leopard 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse games lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt scanner video

Tags: apport-crash
Revision history for this message
Toby Smithe (tsmithe) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_logv (log_domain=<value optimized out>, log_level=G_LOG_LEVEL_ERROR, format=0xb73ed5a0 "%s", args1=0xbfcd493c "hpO\b\003")
IA__g_log (log_domain=0xb73d10a3 "Gdk", log_level=G_LOG_LEVEL_ERROR, format=0xb73ed5a0 "%s") at /build/buildd/glib2.0-2.13.5/glib/gmessages.c:517
gdk_x_error (display=0x8126568, error=0xbfcd49e8) at /build/buildd/gtk+2.0-2.11.4/gdk/x11/gdkmain-x11.c:641
_XError (dpy=0x8126568, rep=0xbfcd4ac8) at ../../src/XlibInt.c:2907
_XReply (dpy=0x8126568, rep=0xbfcd4ac8, extra=1, discard=0) at ../../src/XlibInt.c:1833

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
John Vivirito (gnomefreak) wrote :

Thank you for your bug report,
Can you please provide step by step instrucions and links on what you did when it crashed?

Changed in gnash:
assignee: nobody → mozilla-bugs
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Toby Smithe (tsmithe) wrote :

Although I cannot remember the exact link, I do remember I was attempting to watch a Google Video (although I am aware that this is not fully supported; I was curious to what extent it was). Fortunately, the Apport report has saved the link for me:

ProcCmdline: /usr/bin/gnash -v -x 35718365 -j 1 -k 1 -u http://video.google.com/proxy.swf -U http://video.google.com/videohosted?docid=-7269205919871967751 -P FlashVars=targetId=-7269205919871967751&functionName=pause -P PARAM= -P SRC=/proxy.swf -P align=middle -P bgcolor=#ffffff -P data=/proxy.swf -P height=1 -P id=VideoDataStore -P movie=/proxy.swf -P quality=best -P salign=TL -P scale=noScale -P width=1 -P wmode=window -

The man page on gnash suggests that this means that I was looking at the video with the "real" URL of http://video.google.com/proxy.swf and a "base" URL of http://video.google.com/videohosted?docid=-7269205919871967751

Could someone clarify what the difference between "base" and "real" URLs are? (Although I am aware this isn't strictly linked with this bug report)

Revision history for this message
Alexander Sack (asac) wrote :

resetting crashers < 0.8.4.

Changed in gnash:
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.