ActionScript error on startup in Fluxbox

[confluence]

Hello, everyone.  I bought Botanicula through the Humble Bundle, and installed it from the 64-bit .deb.

As I mentioned in one of the sticky topics, when I start the game in Fluxbox, the window manager I normally use, I get this ActionScript error:

TypeError: Error #1009: Cannot access a property or method of a null object reference.
        at BotaniculaLinux/invokeHandler()[/Users/macbookpro/Documents/flex/BotaniculaLinux/src/BotaniculaLinux.as:369]
        at flash.events::EventDispatcher/dispatchEventFunction()
        at flash.events::EventDispatcher/dispatchEvent()
        at flash.desktop::NativeApplication/dispatchEvent()
        at Runtime/dispatchInvokeEventUnderProfile()
        at runtime::AppRunner/onComplete()

Then I just get a black screen, and the game doesn't run.  However, if I log into GNOME and try to run the game in GNOME, it runs without any problems.  This is a bit inexplicable -- I don't know why a flash game would depend on the window manager.  I have played through the entire game in GNOME, but obviously I'd rather not have to switch window managers whenever I want to replay it -- so I would like to try to debug this issue.  Since the source code is not public, I can't check the relevant line myself -- could the developers perhaps have a look?

[mr_scientist]

bump

Today purchased game from humble-bundle. Was hoping that this problem was fixed.

But... still no resuts.

[Alex]

Today purchased game from humble-bundle. Was hoping that this problem was fixed.
But... still no resuts.

Are you having the same problem ("black screen, and the game doesn't run")?

[confluence]

Sorry about the thread necromancy, but I thought you'd like to know that I have successfully run Botanicula after encountering this error, just by trying to launch it again a few times. Today it started with no error on the third try, and I remember this happening to me before, the last time I replayed it (about a year ago).

So it's possible that the error is triggered by some system resource not existing, which is created the first few times you try to launch it. At least that's my best guess.

The very first time I encountered the problem I was able to run the game by switching to a GNOME session (which is obviously not ideal).

If you have this problem, click "continue", shut the window, and try again. It sounds daft, but it worked for me.