swell-foop segfaults with error 4 in libclutter-glx-1.0.so.0.200.4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Games |
Expired
|
Medium
|
|||
gnome-games (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Binary package hint: gnome-games
swell-foop segfaults in libclutter-glx
How to reproduce the bug (takes up to a few minutes of messing about to grab the crash - apport does not catch it automatically):
1 Open swell-foop.
2. Configure Game-Preferences as follows:
Board size: Large
Number of colors: 3
Theme: Test Theme
Zealous Animation: OFF
3. Place the cursor over a block of squares that is close to but not on the edge of the game space, such that the block of squares is color highlighted.
4. Move the cursor off the game window crossing over another block of squares of the same color.
5. While the program is trying to highlight a new block of the same color as the currently highlighted block it segfaults just as the cursor moves out of the game window. Sometimes it takes several tries to get the timing just right, but with practice, I've gotten pretty good at making it happen.
=======
The gnome game swell-foop intermittently segfaults and leaves messages like this in the /var/log/messages:
May 3 18:43:54 stephen-desktop kernel: [258657.370101] seed[16935]: segfault at 14 ip b2d815c5 sp bff888a8 error 4 in libclutter-
Sometimes the game works without issue, but performance bogs down and then it dies unexpectedly. The machine was minimally loaded at the time.
ProblemType: BugDistroRelease: Ubuntu 10.04
Package: swell-foop 1:2.30.0-0ubuntu6
ProcVersionSign
Uname: Linux 2.6.32-
NonfreeKernelMo
Architecture: i386
Date: Mon May 3 18:52:23 2010Installatio
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=
Changed in gnome-games: | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in gnome-games: | |
status: | Unknown → New |
description: | updated |
Changed in gnome-games: | |
importance: | Unknown → Medium |
Changed in gnome-games: | |
status: | New → Expired |
And I'm getting the virtually the same error but in the 64-bit kernel and packages. Apport isn't catching any crash data at all.
May 6 21:49:06 tobuntu kernel: [18764.433690] seed[5837]: segfault at 20 ip 00007f740a014fd0 sp 00007fff20ff5bc8 error 4 in libclutter- glx-1.0. so.0.200. 4[7f7409fe8000+ f0000] glx-1.0. so.0.200. 4[7fe6a25a8000+ f0000] glx-1.0. so.0.200. 4[7f4d438e8000+ f0000] glx-1.0. so.0.200. 4[7f8eecfa8000+ f0000] glx-1.0. so.0.200. 4[7f7de5868000+ f0000]
May 6 21:51:45 tobuntu kernel: [18923.836285] seed[5843]: segfault at 20 ip 00007fe6a25d4fd0 sp 00007fff54121618 error 4 in libclutter-
May 6 21:53:18 tobuntu kernel: [19016.058094] seed[5849]: segfault at 20 ip 00007f4d43914fd0 sp 00007fff3d95c538 error 4 in libclutter-
May 6 22:28:52 tobuntu kernel: [21150.866792] seed[6821]: segfault at 20 ip 00007f8eecfd4fd0 sp 00007fff1b354358 error 4 in libclutter-
May 6 22:31:01 tobuntu kernel: [21279.514692] seed[6827]: segfault at 20 ip 00007f7de5894fd0 sp 00007fff41d773e8 error 4 in libclutter-
As you can see, this is easily repeatable. Where it crashes in the course of the game seems to depend on gameplay action of certain pattern(s) of squares being removed right after the mouseclick to make that move.
Is this is perhaps a problem communicating with the fglrx driver? If so, this is the only problem where the video driver may be involved that I'm having. But I noticed the original report refers to the fglrx driver too.
Sorry, the segfault messages are all the evidence of the crash I can get.
ProblemType: Bug 22-generic- AMD-64 dules: fglrx 9.04-dvd- amd64.iso - 21-Apr-2009 13:58 4.3G
DistroRelease: Ubuntu 10.04 AMD-64
Package: swell-foop 1:2.30.0-0ubuntu6
Kernel: Ubuntu Linux 2.6.32-
NonfreeKernelMo
Architecture: AMD-64
InstallationMedia: Ubuntu 9.04 "Jaunty Jackalope" - ubuntu-
SourcePackage: gnome-games