Bug 1390016

Summary: fillets executable needs to be linked against compat-lua-libs (5.1)
Product: [Fedora] Fedora Reporter: The Source <thesource>
Component: fillets-ngAssignee: Nikolay Nikolov <nickysn>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: amigadave, bjorn, ivo, matthias
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-25 15:13:50 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:
Embargoed:
Attachments:
Description Flags
spec file for new packages
none
Source RPM for new build
none
Saved game none

Description The Source 2016-10-30 20:33:37 UTC
Description of problem:
Some level scripts from fillets-ng-data are incompatible with lua newer that 5.1 (electromagnet level crashes on start, first mate's cabin level crashes when trying to play wall move animation), please rebuild fillets package against compat-lua instead.

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

fillets-ng-1.0.1-11.fc24.x86_64
fillets-ng-data-1.0.1-5.fc24.noarch

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 The Source 2016-11-02 07:45:21 UTC
I just built fillets from src.rpm ignoring lua-5.2 patch and linking executable against lua-5.1, everything works just fine, no crashes on those levels.

Comment 2 The Source 2016-11-02 09:06:54 UTC
Created attachment 1216403 [details]
spec file for new packages

Comment 3 The Source 2016-11-02 09:07:48 UTC
Created attachment 1216404 [details]
Source RPM for new build

Could you please review this files?

Comment 4 The Source 2016-11-23 18:16:18 UTC
Still a problem in fedora 25

Comment 5 Fedora End Of Life 2017-11-16 18:37:02 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 The Source 2017-12-04 06:36:10 UTC
Fedora 27, still here

Comment 7 Ben Cotton 2018-11-27 17:57:04 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2018-11-30 18:34:54 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 9 The Source 2018-11-30 19:21:23 UTC
Still bugged in fedora 29

Comment 10 Ben Cotton 2019-10-31 20:23:09 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 The Source 2019-11-12 18:35:20 UTC
The problem is still present in F31

Comment 12 Ben Cotton 2020-11-03 14:57:57 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 The Source 2020-11-03 17:13:51 UTC
Still bugged in F33, guess nobody cares.

Comment 14 Fedora Admin user for bugzilla script actions 2020-11-22 14:53:02 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 15 Fedora Admin user for bugzilla script actions 2021-05-27 00:09:34 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 16 The Source 2021-05-31 12:23:17 UTC
Latest update fillets-ng-1.0.1-26.fc34.x86_64 fillets-ng-data-1.0.1-15.fc34.noarch still has the issue.

Comment 17 Nikolay Nikolov 2021-05-31 12:42:18 UTC
Can you provide steps to reproduce (probably with save game files, i.e. archive of the ~/.fillets-ng/ directory), because I don't know which are the broken levels (I still haven't reached them, I guess, since I still haven't finished this game)?

Comment 18 The Source 2021-05-31 13:41:00 UTC
Created attachment 1788316 [details]
Saved game

Attached my .fillets-ng contents. How to reproduce:
Method 1. Load level "Electromagnet", it crashes on start.
Method 2. Load level "First mate's cabin", select large fish, swim up to the top of the level and push the ceiling (by yourself or by some object).

Comment 19 Björn Persson 2021-10-12 08:26:31 UTC
Would some stack traces help with fixing these crashes?

main.cpp:117: ERROR script failure; error='/usr/share/fillets-ng/script/cabin1/code.lua:142: bad argument #2 to 'game_setScreenShift' (number has no integer representation)
stack traceback:
	[C]: in function `game_setScreenShift'
	/usr/share/fillets-ng/script/cabin1/code.lua:142: in function `subupdate'
	/usr/share/fillets-ng/script/cabin1/code.lua:380: in function `prog_update'
	/usr/share/fillets-ng/script/share/level_start.lua:81: in function `script_update'
	[string "script_update()"]:1: in main chunk'

main.cpp:117: ERROR script failure; error='/usr/share/fillets-ng/script/share/level_creation.lua:61: bad argument #3 to 'model_setAnim' (number has no integer representation)
stack traceback:
	[C]: in function `model_setAnim'
	/usr/share/fillets-ng/script/share/level_creation.lua:61: in function `setAnim'
	/usr/share/fillets-ng/script/share/level_start.lua:28: in function `updateAnim'
	/usr/share/fillets-ng/script/electromagnet/code.lua:88: in function `subupdate'
	/usr/share/fillets-ng/script/electromagnet/code.lua:299: in function `prog_update'
	/usr/share/fillets-ng/script/share/level_start.lua:81: in function `script_update'
	[string "script_update()"]:1: in main chunk'

Comment 20 Fedora Update System 2021-10-17 02:32:57 UTC
FEDORA-2021-d4eed8a50d has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d4eed8a50d

Comment 21 Fedora Update System 2021-10-17 02:47:45 UTC
FEDORA-2021-44740dd685 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-44740dd685

Comment 22 Fedora Update System 2021-10-17 03:01:14 UTC
FEDORA-2021-79af36bf2b has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-79af36bf2b

Comment 23 Fedora Update System 2021-10-17 18:32:27 UTC
FEDORA-2021-d4eed8a50d has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d4eed8a50d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d4eed8a50d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 24 Fedora Update System 2021-10-17 22:10:51 UTC
FEDORA-2021-79af36bf2b has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-79af36bf2b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-79af36bf2b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 25 Fedora Update System 2021-10-17 22:19:10 UTC
FEDORA-2021-44740dd685 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-44740dd685`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-44740dd685

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 26 Fedora Update System 2021-10-25 15:13:50 UTC
FEDORA-2021-44740dd685 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 27 Fedora Update System 2021-10-25 15:17:52 UTC
FEDORA-2021-79af36bf2b has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 28 Fedora Update System 2021-10-29 23:07:18 UTC
FEDORA-2021-d4eed8a50d has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.