Created attachment 1305141 [details] Scoreboard After upgrading to F26 and gnome-2048-3.22.0-2.fc26.x86_64, the scoreboard is not in order any more and the highest scores are missing. There does seem to be some order with regard to the player names, though not alphabetical. In the attached screenshot, the first two scores belong to "player_F" while the others to "player_A".
I can't reproduce which makes this awkard to track. - If you run gnome-2048 in a terminal , does it spew anything unusual ? - what is your system locale ? - could you maybe share your (~/.local/share/gnome-2048/scores/grid4) perhaps with somewhat sanitized names ?
Created attachment 1305303 [details] grid4 scores (In reply to Yanko Kaneti from comment #1) > I can't reproduce which makes this awkard to track. > > - If you run gnome-2048 in a terminal , does it spew anything unusual ? No output whatsoever. > - what is your system locale ? en_US.utf8 > - could you maybe share your (~/.local/share/gnome-2048/scores/grid4) > perhaps with somewhat sanitized names ? I changed the names so that they are in the same alphabetical order and I kept the exclamation mark, that the second player had right after his name and a hyphen in the first player's name.
Thanks. Unfortunately I still can't reproduce, with your score file and with mine. Tried both rawhide and f26 fully updated. Maybe there is another score category file in the same directory ? or any other file there that might be confusing it ?
(In reply to Yanko Kaneti from comment #3) > Maybe there is another score category file in the same directory ? or any > other file there that might be confusing it ? Just a grid5 with a single score. I moved both files out of the directory and played a few games using the same player names. This time, the scores were displayed in descending order. I deleted the new file and restored the original ones. Problem gone. I checked my gsettings as well, but I didn't notice anything out of the ordinary.
Thanks for the report. Now that its gone on your end too I'll close this one as INSUFFICIENT_DATA and reopen if something like that comes up again... I have no idea what it might be.
(In reply to Yanko Kaneti from comment #5) > Thanks for the report. Now that its gone on your end too I'll close this one > as INSUFFICIENT_DATA and reopen if something like that comes up again... Sure, thanks for taking an interest.