Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allegro in Ubuntu Jaunty is not compatible #3273

Closed
DorpsGek opened this issue Oct 19, 2009 · 3 comments
Closed

Allegro in Ubuntu Jaunty is not compatible #3273

DorpsGek opened this issue Oct 19, 2009 · 3 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

Gremnon opened the ticket and wrote:

The Allegro available in the Jaunty repositories is not up to date
The version of Allegro in the repository is 4.2.2, which has been confirmed not to work, exiting before loading with the debug output of:

ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC0D0 failed: No such file or directory
dbg: [driver] allegro: install_sound failed 'ALSA: snd_pcm_hw_params_set_format(pcm_handle, hwparams, format) : Invalid argument'
Error: Unable to load driver 'allegro'. The error was: Failed to set up Allegro sound

Status in Karmic repositories not known, but possibly it uses a newer version (Can someone using Karmic check this?)
Debian repository unknown as well, but most likely a newer version of Allegro is used there.

Unless users wish to download and compile Allegro from the official website, or there is a Jaunty .deb available, using Allegro on Ubuntu Jaunty and before is not possible.

Reported version: trunk
Operating system: Linux

This issue was imported from FlySpray: https://bugs.openttd.org/task/3273
@DorpsGek
Copy link
Member Author

Rubidium wrote:

What's the point of this report? There's hardly anything we can do about what Ubuntu packages and with what they like to link OpenTTD.

Besides that it's Allegro causing problems with PulseAudio (or vice versa), fixed in 4.2.3. No idea why they haven't packaged that yet because it's already 2 years old. Still, it's out of our hands.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3273#comment6855

@DorpsGek
Copy link
Member Author

Gremnon wrote:

Could be my mistake, I'm sure someone mentioned sending in a flyspray task about it.
Besides, if a third party .deb that works can be found, then perhaps it's worth linking to, or providing a download of it for users who want to use Allegro?

This comment was imported from FlySpray: https://bugs.openttd.org/task/3273#comment6857

@DorpsGek
Copy link
Member Author

peter1138 closed the ticket.

Reason for closing: Invalid

This comment was imported from FlySpray: https://bugs.openttd.org/task/3273

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DorpsGek