Bug 1084250

Summary: fillets-ng fails to start
Product: [Fedora] Fedora Reporter: Ferdinand Badescu <fb.commerce>
Component: fillets-ngAssignee: Matthias Saou <matthias>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 20CC: bruno, lnie, lukas.marek, matthias
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: fillets-ng-1.0.1-7.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1220396 (view as bug list) Environment:
Last Closed: 2015-05-26 03:14:31 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:
Bug Depends On:    
Bug Blocks: 1220396    

Description Ferdinand Badescu 2014-04-04 03:05:52 UTC
Description of problem:
$ rpm -q fillets-ng
fillets-ng-1.0.1-2.fc20.x86_64

$ fillets
main.cpp:117: ERROR script failure; error='/usr/share/fillets-ng/script/init.lua:5: attempt to index global 'string' (a nil value)
stack traceback:
	/usr/share/fillets-ng/script/init.lua:5: in main chunk'


Version-Release number of selected component (if applicable):
1.0.1-2.fc20

How reproducible:
Every time

Steps to Reproduce:
1. Open a terminal
2. Type 'fillets' at the prompt
3.

Actual results:
Error message (see 'Description of problem:' above)

Expected results:
The game runs.

Additional info:
Fedora 20, 64-bit, Intel i5-3570K, 8GB SDRAM, ASUS P8Z7 Motherboard, Z77 Chipset.

Comment 1 Ferdinand Badescu 2014-04-04 03:08:33 UTC
Correction: ASUS P8Z77-V Motherboard

Comment 2 Lukas Marek 2014-05-22 14:00:42 UTC
Probably related:

http://sourceforge.net/p/fillets/bugs/7/

Comment 3 Bruno Wolff III 2015-05-09 00:39:34 UTC
There is a lua compat package for 5.1 now. Using that might be a simple way to get fillets-ng working again.

Comment 4 Bruno Wolff III 2015-05-09 01:44:28 UTC
It looks like this will probably work. I was able to do the first level with a test build. There could potentially be some gotchas due too differences between 5.1 and 5.0. Expect test builds to be showing up soon.

Comment 5 Fedora Update System 2015-05-09 02:17:16 UTC
fillets-ng-1.0.1-7.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/fillets-ng-1.0.1-7.fc22

Comment 6 Fedora Update System 2015-05-09 02:18:50 UTC
fillets-ng-1.0.1-7.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/fillets-ng-1.0.1-7.fc21

Comment 7 Fedora Update System 2015-05-09 02:19:48 UTC
fillets-ng-1.0.1-7.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/fillets-ng-1.0.1-7.fc20

Comment 8 lnie 2015-05-12 08:25:45 UTC
fillets-ng-1.0.1-7.fc22 works

Comment 9 Fedora Update System 2015-05-13 01:16:54 UTC
fillets-ng-data-1.0.1-2.fc22, fillets-ng-1.0.1-7.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2015-05-15 13:35:02 UTC
Package fillets-ng-1.0.1-7.fc20, fillets-ng-data-1.0.1-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fillets-ng-1.0.1-7.fc20 fillets-ng-data-1.0.1-2.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-7825/fillets-ng-1.0.1-7.fc20,fillets-ng-data-1.0.1-2.fc20
then log in and leave karma (feedback).

Comment 11 Fedora Update System 2015-05-26 03:14:31 UTC
fillets-ng-1.0.1-7.fc20, fillets-ng-data-1.0.1-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2015-05-26 03:16:51 UTC
fillets-ng-data-1.0.1-2.fc21, fillets-ng-1.0.1-7.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.