Red Hat Bugzilla – Bug 216248
--colour-blind option does not work
Last modified: 2007-11-30 17:11:49 EST
Description of problem:
Frozen Bubble doesn't initialize properly when using the --colour-blind option
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. enter "frozen-bubble --colour-blind" on the command line
[SDL Init] [Graphics.FATAL: Couldn't load
'/usr/share/frozen-bubble/gfx/balls/bubble-colourblind-1-mini.png' into a
Frozen Bubble uses bubbles with little geometrical symbols inside.
This problem appears to be present in upstream version as well. I tried to
contact upstream via theh e-mail address mentioned on the troubleshooting page
of the website http://www.frozen-bubble.org/ but the e-mail bounces with
"Relaying not allowed" error.
Reassigning to Matthias as he is the new frozen-bubble package maintainer.
Matthias, I'll update owners.list for this and put myself in the initial-CC as
I've taken a quick look and the problem seems to be that frozen-bubble tries to
open /usr/share/frozen-bubble/gfx/balls/bubble-colourblind-1-mini.png, which we
do not have, we only have bubble-colourblind-1.gif, but no matching
bubble-colourblind-1-mini.png, whereas the non colourblind version has both:
bubble-1.gif and bubble-1-mini.png .
I've rescaled the colourblind images and hand touched up (pixelated) the result.
I'll attach a tarbal with them here. FE CVS is currently down, so actually
pushing out a fixed version may take some time. In the mean time unpack the
attached tarball in /usr/share/frozen-bubble/gfx/balls and all should be well.
Matthias, will you do the further fixing once CVS is up, or shall I? And could
you please send the tarbal to upstream? Thanks.
Created attachment 141552 [details]
tarbal with missing images
Thanks for the quick response. I extracted the files from the tar file and
Frozen Bubble now works OK with the --colour-blind option.
FYI, upstream has already solved the problem, so it will be fixed in the next
maintenance release. No ETA yet, sorry.
The 2.1.0 update has been pushed today. The option is now working.