I get this on my Ubuntu 18.04, nVidia equipped machine. 390 binary nVidia driver. I have 3 displays attached in case that matters.
$ lambdarogue
An unhandled exception occurred at $00000000005809AD:
EInOutError: Invalid input
$00000000005809AD
1 Like
Interesting… if you have the time, could you test the non-snap version of the game and tell me if you get the same error? (https://mariodonick.itch.io/lambdarogue-the-book-of-stars) Thanks!
Thanks for testing, glad it works!
Abitrolly, could you test the latest version, please?
FWIW the game works fine on my Intel laptop. I suspect this may be weirdness on my nVidia machine.
1 Like
The “real agenda” is to get more exposure of my game using the snap store. And according to the snapcraft website, this is one reason why one should use snaps. At least that is how snapcraft is advertising for using snaps. I apologize if links to other sites are unwanted.
However, if an error message occurs where it is unclear if it is caused by the binary itself, or by my snap, I of course want to check this, and the easiest way for that is to link to the place where one can get the non-snap version.
2 Likes
to give another data point, it runs fine on my 16.04 triple head setup with nvidia and the 384 binary driver … (same as popeys but one LTS behind)
2 Likes
The same ALSA error with 1.7.0.1.
1 Like
Thanks for testing. Being a bit clueless right now… why does it work for some and for others not…
1 Like
I rebooted, and now it works, so ignore my error report! Thanks for snapping the game! 
(I have a habit of updating my system and not rebooting for days or weeks at a time. I clearly didn’t reboot over Christmas, sorry about the bum-steer).
1 Like
No idea. It is Ubuntu 18.10 here with snap/snapd 2.36.3
For abitrolly (and others who might have ALSA errors with my snap), I’m going to try the suggestion from the following thread:
I’d be surprised if that is needed or helps. If this is using SDL, it will use pulseaudio by default (or that can be forced by passing an environment variable). The alsa errors in the terminal can usually be ignored. Is there an actual problem with audio playback or is it just error messages in the terminal?
1 Like
Don’t know. According to abitrolly’s error output:
Error: SDL Mixer could not be initialized.
Maybe the binary stops then?
Note I use SDL 1.2, not 2.0, so I don’t know if it really uses pulseaudio by default. However, your hint about forcing it via an environment variable might do the trick. In my next update to the snap, I’ll set “SDL_AUDIODRIVER” to “pulse” (which is the valid value for SDL 1.2), and then we’ll see what happens. 
Why use SDL 1.2 instead of SDL 2.0?
Because this game is 12 years old and I don’t see a need for rewriting large parts which work fine.
For C it might make sense, but for FreePascal I doubt it. SDL2 itself is not easy.
https://twitter.com/realbisqwit/status/869459175927148544?lang=en
Running SDL_AUDIODRIVER=pulse lamdarodue removes ALSA error message, but Error: SDL Mixer could not be initialized. is still there. Does it work on your system?
as a data point: on my Ubuntu 18.10 system I’m able to run the application fine, with no errors about alsa or the mixer… Audio works without issue.