Bug 1034132

Summary:	gcompris water cycle doesn't recognize all possible actions
Product:	[Fedora] Fedora	Reporter:	Rolle <rolle.hoffmann>
Component:	gcompris	Assignee:	Hans de Goede <hdegoede>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	gwync, hdegoede
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gcompris-13.11-2.fc20	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-05 10:36:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Rolle 2013-11-25 10:18:29 UTC

Description of problem:
in gcompris the water cycle (and maybe other sub games too) doesn't recognize all possible stations to click.
It isn't possible to finish the water cycle.

Version-Release number of selected component (if applicable):
Fedora 20 beta

How reproducible:
always

Steps to Reproduce:
1. start gcompris
2. go in the third category (on the left side) to the physical experiments
3. start the 3rd SubGame (water cycle)
4. click the sun, afterwards the clouds, and so on
5. the power plant on water to generate electricity doesn't reacts -> so the water cycle isn't possible to fulfill.
6. sometimes the sun isn't even clickable

Actual results:
sometimes the sun and always the power plant to generate electricity isn't clickable

Expected results:
all stations on water cycle must be clickable to fulfill the task

Additional info:

Comment 1 Hans de Goede 2013-11-26 13:45:50 UTC

Thanks for the bug-report. It took me some hours, but I've managed to pinpoint and fix the bug both in the water cycle and in the related renewable energy activities. Expect an updated package fixing this soon.

Comment 2 Rolle 2013-11-26 14:19:56 UTC

Thank you very much. I'm happy to see this solved. I think these educational programs are very fine. Thank for your great job.
I have one more question. Is this patch only landed in the Fedora-universe or is the patch sended to the original gcompris-Authors?

Comment 3 Hans de Goede 2013-11-26 14:21:28 UTC

Hi,

(In reply to Rolle from comment #2)
> Thank you very much. I'm happy to see this solved. I think these educational
> programs are very fine. Thank for your great job.
> I have one more question. Is this patch only landed in the Fedora-universe
> or is the patch sended to the original gcompris-Authors?

I've also send the patch to the upstream authors.

Regards,

Hans

Comment 4 Fedora Update System 2013-11-26 18:07:53 UTC

gcompris-13.11-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/FEDORA-2013-21848/gcompris-13.11-2.fc19

Comment 5 Fedora Update System 2013-11-26 18:22:20 UTC

gcompris-13.11-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/FEDORA-2013-21969/gcompris-13.11-2.fc20

Comment 6 Fedora Update System 2013-11-27 04:37:57 UTC

Package gcompris-13.11-2.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gcompris-13.11-2.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-21848/gcompris-13.11-2.fc19
then log in and leave karma (feedback).

Comment 7 Rolle 2013-12-04 15:50:29 UTC

I tested the fix.
All works fine. Great job.
Thank you.

For me the bug report can be closed.

Comment 8 Fedora Update System 2013-12-05 10:36:01 UTC

gcompris-13.11-2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2013-12-14 02:49:42 UTC

gcompris-13.11-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.