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 108734 - AisleRiot crashes after finishing game
AisleRiot crashes after finishing game
Status: RESOLVED DUPLICATE of bug 89822
Product: gnome-games-superseded
Classification: Deprecated
Component: general
2.0.x
Other other
: Normal critical
: ---
Assigned To: Rosanna Yuen
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2003-03-18 13:11 UTC by Edward S. Marshall
Modified: 2012-01-31 23:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Edward S. Marshall 2003-03-19 00:38:57 UTC
Package: gnome-games
Severity: normal
Version: 2.0.3
Synopsis: AisleRiot crashes after finishing game
Bugzilla-Product: gnome-games
Bugzilla-Component: aisleriot
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
Upon successful completion of the game, a dialog appears with the one
button ("New Game"). After clicking it, a new deck is displayed, and the
game abruptly crashes.

Steps to reproduce the problem:
1. Win.
2. Click "New Game" in the resulting dialog.
3. Boom.

Actual Results:
Game crashes.

Expected Results:
I go on to win another game. :-)

How often does this happen?
Every time.

Additional Information:
This kind of thing also seems to happen when I double-click on the cards
too quickly (for example, if I'm nearing the end of the game, and just
have to click my way through a few stacks of cards to win, I go pretty
quickly, and if I don't make myself slow down, the game crashes while
I'm clicking through them...a double click followed by a double click
without moving the mouse seems to do the trick). Weird. ;-)



Debugging Information:

Backtrace was generated from '/usr/bin/sol'




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-03-18 19:38 -------

The original reporter (esm@logic.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, zana@webwynk.net.

Comment 1 Elijah Newren 2003-03-20 21:21:14 UTC
Thanks for the bug report. Without a stack trace from the crash it's
very hard to determine what caused the crash. Can you try to get us
one?  Note that you may have to run AisleRiot as root in order to get
one (or, run gdb as root and attach it to the appropriate process
after AisleRiot crashes).  For more information on obtaining stack
traces in general, please see
http://bugzilla.gnome.org/getting-traces.cgi .
Comment 2 Edward S. Marshall 2003-03-22 19:33:54 UTC
I've done a little more digging (you have no idea how sick of playing
solitaire I am right now ;-), and it's not actually dumping core. I
have no idea why bug-buddy popped up for it at the time I submitted
the report...

What I'm getting at a terminal is the following output at the time of
the crash:

ERROR: In procedure car:
ERROR: Wrong type argument in position 1: ()

So, a problem with the guile bits? I'm afraid my Scheme-fu is too weak
to tell you much more. :-P

I realized that I didn't submit with OS information. This is Red Hat
8.0, with their gnome-games-2.0.3-2 package.
Comment 3 Edward S. Marshall 2003-03-22 19:37:39 UTC
One last update; I did a search through Red Hat's bug database, and
they've got an issue open for this one too:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=78824

Hope this helps. :-)
Comment 4 Elijah Newren 2003-03-22 19:51:02 UTC
Reopening, marking severity->critical, setting version->2.0.x, adding
GNOMEVER2.0 and bugsquad keywords, and putting RedHat 8.0 in the OS
Details.
Comment 5 Elijah Newren 2003-03-22 19:51:32 UTC
...and marking as new.  (I wish I could reopen and mark as new in one
step)
Comment 6 Callum McKenzie 2003-06-04 09:59:46 UTC
Its a duplicate of bug #89822 and is fixed in the 2.3 series.

*** This bug has been marked as a duplicate of 89822 ***
Comment 7 Robert Ancell 2012-01-31 23:27:39 UTC
This bug is being reassigned to the "general" component so we can close the aisleriot bugzilla component.  Apologies for the mass email!