Ubuntu
frozen-bubble package

Hiscore list mirrors on new entry - patch included

Bug #180244 reported by Jørgen Elgaard Larsen on 2008-01-04

Affects		Status	Importance	Assigned to	Milestone
	frozen-bubble (Ubuntu)	Invalid	Low	Unassigned

Bug Description

Binary package hint: frozen-bubble

When a highscore is made
* in mp_training mode,
* with chain reaction is enabled, and
* there are more than 19 entries in the highscore already,
then the highscore list is duplicated from the highscore list _without_ chain reaction.

The error is found in the file "frozen-bubble", in the end of sub handle_new_hiscores(), at line 4744 in the current version of frozen-bubble (version 2.1.0-1 for amd64).

The error can be fixed by applying this patch:

4744,4745d4743
< my @high = ordered_mptrain_highscores();
< pop @high;
4746a4745,4746
> my @high = ordered_mptrain_highscores_chainreaction();
> pop @high;
4748a4749,4750
> my @high = ordered_mptrain_highscores();
> pop @high;

Revision history for this message

Jørgen Elgaard Larsen (jel-solfisk) wrote on 2008-01-04:

Patch to the file frozen-bubble for correcting highscore bug Edit (259 bytes, text/plain)

I'd better attach the patch file as an attachment :-)

Revision history for this message

Mb (mb-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote on 2008-02-02:

Can you submit this change to Debian please?

Revision history for this message

Hew (hew) wrote on 2008-08-03:

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest Ubuntu release? Thanks in advance.

Changed in frozen-bubble:
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

Hew (hew) wrote on 2008-12-22:

I have looked through the frozen-bubble 2.2.0 source and, assuming this bug still exists, I can't find which file or lines this patch would apply to.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!