After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 345191 - AisleRiot craches when changing selecting new game
AisleRiot craches when changing selecting new game
Status: RESOLVED FIXED
Product: gnome-games-superseded
Classification: Deprecated
Component: general
2.14.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
: 346652 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-06-17 19:17 UTC by Karderio
Modified: 2012-01-31 23:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Karderio 2006-06-17 19:17:09 UTC
I'm currently using Ubuntu Dapper 6.06 LTS. I have tried to report a bug in the Ubuntu launchpad, but it refers me here. I have not tested this with a home built GNOME, as I am currently wrestling with GARNOME after a reinstall.

To reproduce : open AisleRiot, select a new game. The program just exits.

If I open it from the command line (type sol), here is the output :

***--------Output--------***

Backtrace:
In /usr/share/sol-games/sol.scm:
 480: 0* (if (defined? (quote card-guardian)) (letrec (# #) (catch # # ...)) ...)
 481: 1  (while (card-guardian))
In unknown file:
   ...
   ?: 2  [catch break #<procedure #f ()> #<procedure #f v>]
   ?: 3* [#<procedure #f ()>]
   ?: 4* [continue]
   ?: 5  (or (not (card-guardian)) (begin (begin) (continue)))
   ?: 6  (begin (begin) (continue))
   ?: 7* (begin)

<unnamed port>: In procedure begin in expression (begin):
<unnamed port>: missing or extra expression

***--------EndOutput--------***

Love, Karderio
Comment 1 Richard Hoelscher 2006-06-17 21:22:36 UTC
I've seen this too, a few days ago... It's odd, since selecting the game and confirming the dialog can work fine, while double-clicking to select it can trigger this bug. 
Comment 2 Callum McKenzie 2006-06-17 23:25:18 UTC
That crash _should_ have been fixed just before 2.15.3.

I'm a bit confused about the version claim of 2.14 because the code shown in the stack trace was only introduced in 2.15 to try and fix some issues with overly aggressive garbage collection.

Comment 3 Josselin Mouette 2006-06-20 19:31:39 UTC
I received a similar bug report at http://bugs.debian.org/374251 and can reproduce it with gnome-games 2.14.2. It only happens when the game opens with "Zebra" as the current game. Then, whenever switching games, I get the error:

In /usr/share/sol-games/sol.scm:
 480: 0* (if (defined? (quote card-guardian)) (letrec (# #) (catch # # ...)) ...)
 481: 1  (while (card-guardian))
In unknown file:
   ...
   ?: 2  [catch break #<procedure #f ()> #<procedure #f v>]
   ?: 3* [#<procedure #f ()>]
   ?: 4* [continue]
   ?: 5  (or (not (card-guardian)) (begin (begin) (continue)))
   ?: 6  (begin (begin) (continue))
   ?: 7* (begin)

<unnamed port>: In procedure begin in expression (begin):
<unnamed port>: missing or extra expression
Comment 4 William Astle 2006-06-23 21:52:32 UTC
I have the same problem. This is using a fully up to date Dropline GNOME distribution for Slackware. I have been able to duplicate the bug on two separate machines by selecting the "Poker" game. Once the Poker game is selected, it simply will not switch games, even after resetting the default game to Klondike in gconf. If, however, the program starts up using --variation=freecell (for example) it is possible to switch games. --variation=poker and --variation=klondike exhibit this crash behaviour.
Comment 5 Richard Hoelscher 2006-06-26 04:00:00 UTC
The claim about 2.14 is valid because unlike what we've been used to for years from lesser distros, those Ubuntu guys actually upgrade to 2.14.2 and so on soon after release.

Unfortunately, we didn't notice the earlier 2.14.2 release had a crasher once that sol.scm fix ("(while (card-guardian) #t)") landed in HEAD. I've made a commit with it over to the stable branch, and I think a 2.14.2.1 is justified.
Comment 6 Andreas Røsdal 2006-06-26 06:47:24 UTC
Richard, I agree with you that a 2.14.2.1 is justified.
However, 2.14.3 is due on August 2nd, which is pretty soon also.
Comment 7 Richard Hoelscher 2006-06-26 12:29:39 UTC
Andreas:

I definitely don't wan't to wait until 2.14.2, because if history is any indication, many distros never update by the time 2.stable.3 rolls around. Not to name any names.... but Fedora/Red Hat used to be really bad about this. They've updated to 2.14.2, which is out of the ordinary already, so maybe this won't be a big a problem as usual.

Releasing it in the next 24 hours or anything probably isn't absolutely needed either though. The severity isn't too bad, as long as nobody plays Zebra. :)
Comment 8 Richard Hoelscher 2006-07-06 12:24:52 UTC
*** Bug 346652 has been marked as a duplicate of this bug. ***
Comment 9 Robert Ancell 2012-01-31 23:22:21 UTC
This bug is being reassigned to the "general" component so we can close the aisleriot bugzilla component.  Apologies for the mass email!