gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnash-commit] [bug #36953] player fails to open library file due to pat


From: anonymous
Subject: [Gnash-commit] [bug #36953] player fails to open library file due to path concatenation issues
Date: Wed, 25 Jul 2012 20:21:51 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3

URL:
  <http://savannah.gnu.org/bugs/?36953>

                 Summary: player fails to open library file due to path
concatenation issues
                 Project: Gnash - The GNU Flash player
            Submitted by: None
            Submitted on: dc 25 jul 2012 20:21:51 UTC
                Category: None
                Severity: 3 - Normal
                 Release: 0.8.8
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Hi there!

I just want to inform of a problem that I'v found in the gnash player.

When playing certain swf interactive video which opens in turn other swf
videos stored in another directory I never get to play the "subfolder videos"
although if I go manually to the subfolder and then I open that file it plays
fine.

With the verbose argument i can see the following errors:

"ERROR: failed to open 'file:///tmp/foo\bar.swf'; can't create movie
ERROR: Couldn't load library movie 'file:///tmp/foo\bar.swf'
"

In first sight I saw that actually the folder in which the videos were stored
was named "FOO" and not "foo"...

So it seems to me that obviously there's a path misunderstanding between the
UNIX style and the windows style for which the video was originally made.

I can rename the folder easy enough to "foo" (with non capital letters), but
the concatenation of the path is made with the windows backslash path
separator character.. and thus the file is not found...

I don't know if that's a problem of the swf file itself, that was poorly
created and has the paths hard-coded or where the source of the problem lies,
but anyway I think it should be pretty easy for you to solve that "bug" by
considering that scenario and treating it appropriately.

Sorry for my bad English and thanks for all your efforts.






    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?36953>

_______________________________________________
  Missatge enviat a través de/per Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]