Error on script registered on GMCP event

Bug #1660082 reported by cyril duez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mudlet
Invalid
Undecided
Unassigned

Bug Description

Hello,

I have created a simple script (called GMCP) which is registered upon gmcp.char

It only contains : display(gmcp)

Now when i received the GMCP event i have this message in the debug window : "LUA: ERROR running script GMCP (GMCP) ERROR: attempt to call a nil value"

I have tested this on the latest release (3.0.iota) and i have built the latest commit (e5b832b) but i get the same result.

Revision history for this message
Vadim Peretokin (vperetokin) wrote : Re: [Mudlet-makers] [Bug 1660082] [NEW] Error on script registered on GMCP event

Could you attach a screenshot of your script?

On Sat, 28 Jan 2017 11:35 pm cyril duez, <email address hidden> wrote:

> Public bug reported:
>
> Hello,
>
> I have created a simple script (called GMCP) which is registered upon
> gmcp.char
>
> It only contains : display(gmcp)
>
> Now when i received the GMCP event i have this message in the debug
> window : "LUA: ERROR running script GMCP (GMCP) ERROR: attempt to call a
> nil value"
>
> I have tested this on the latest release (3.0.iota) and i have built the
> latest commit (e5b832b) but i get the same result.
>
> ** Affects: mudlet
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Mudlet
> Makers, which is subscribed to Mudlet.
> https://bugs.launchpad.net/bugs/1660082
>
> Title:
> Error on script registered on GMCP event
>
> Status in Mudlet:
> New
>
> Bug description:
> Hello,
>
> I have created a simple script (called GMCP) which is registered upon
> gmcp.char
>
> It only contains : display(gmcp)
>
> Now when i received the GMCP event i have this message in the debug
> window : "LUA: ERROR running script GMCP (GMCP) ERROR: attempt to call
> a nil value"
>
> I have tested this on the latest release (3.0.iota) and i have built
> the latest commit (e5b832b) but i get the same result.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1660082/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mudlet-makers
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mudlet-makers
> More help : https://help.launchpad.net/ListHelp
>

Revision history for this message
cyril duez (siril) wrote :

Of course, here it is.

Revision history for this message
Vadim Peretokin (vperetokin) wrote : Re: [Mudlet-makers] [Bug 1660082] Re: Error on script registered on GMCP event

Do you have any loading errors at the start of Mudlet?

On Tue, 31 Jan 2017 2:50 am cyril duez, <email address hidden> wrote:

> Of course, here it is.
>
> ** Attachment added: "script_gmcp.jpg"
>
> https://bugs.launchpad.net/mudlet/+bug/1660082/+attachment/4811145/+files/script_gmcp.jpg
>
> --
> You received this bug notification because you are a member of Mudlet
> Makers, which is subscribed to Mudlet.
> https://bugs.launchpad.net/bugs/1660082
>
> Title:
> Error on script registered on GMCP event
>
> Status in Mudlet:
> New
>
> Bug description:
> Hello,
>
> I have created a simple script (called GMCP) which is registered upon
> gmcp.char
>
> It only contains : display(gmcp)
>
> Now when i received the GMCP event i have this message in the debug
> window : "LUA: ERROR running script GMCP (GMCP) ERROR: attempt to call
> a nil value"
>
> I have tested this on the latest release (3.0.iota) and i have built
> the latest commit (e5b832b) but i get the same result.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1660082/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mudlet-makers
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mudlet-makers
> More help : https://help.launchpad.net/ListHelp
>

Revision history for this message
cyril duez (siril) wrote :

This is the message i get in the terminal on startup :

cTelnet::encodingChanged() called!
error: ./en_US.aff: cannot open
error: ./en_US.dic: cannot open
error: ./en_US.aff: cannot open

FYI, when i save the script or when i click on it on the left sidebar, the script is executed and i see the content of the gmcp object in the main window without problem. The issue occurs only when mudlet receive the gmcp message and then try to execute the script.

Revision history for this message
Stephen Lyons (slysven) wrote :

The CTelnet::encodingChanged() message is normal.
The others look like you are missing the hunspell spell-checker system - not quite sure how it is done on all platforms but on Linux you will want at least the hunspell-en-us (we default to en-US) DICTIONARY file as well as libhunspell the RUNTIME LIBRARIES (and libhunspell-dev the DEVELOPMENT header files if you are building Mudlet from source). It seems you do not have the first and/or the second of these to hand. On windows the situation is less clear to me but I suspect you need the dictionary and associated affixes files en_US.dic & en_US.aif respectively to be in the same directory as the executable.

Revision history for this message
cyril duez (siril) wrote :

I have installed the hunspell-en to clear the message.

Revision history for this message
Vadim Peretokin (vperetokin) wrote :

Sorry, we got distracted by the missing dictionary. Are you still having the issue?

Revision history for this message
cyril duez (siril) wrote :

I just tried 28fda4d and yes, i have still the issue.

Revision history for this message
Vadim Peretokin (vperetokin) wrote :

No immediate answer for this is coming up. gmcp table should always be
present and Mudlet does not delete it.

Could you try the next two steps:
* see if it happens on a new profile
* record a video showing the issue, also include that running the script
directly works fine

Apologies for the issue and appreciate your patience in troubleshooting
this.

On Mon, 6 Mar 2017 4:15 am cyril duez, <email address hidden> wrote:

> I just tried 28fda4d and yes, i have still the issue.
>
> --
> You received this bug notification because you are a member of Mudlet
> Makers, which is subscribed to Mudlet.
> https://bugs.launchpad.net/bugs/1660082
>
> Title:
> Error on script registered on GMCP event
>
> Status in Mudlet:
> New
>
> Bug description:
> Hello,
>
> I have created a simple script (called GMCP) which is registered upon
> gmcp.char
>
> It only contains : display(gmcp)
>
> Now when i received the GMCP event i have this message in the debug
> window : "LUA: ERROR running script GMCP (GMCP) ERROR: attempt to call
> a nil value"
>
> I have tested this on the latest release (3.0.iota) and i have built
> the latest commit (e5b832b) but i get the same result.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1660082/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mudlet-makers
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mudlet-makers
> More help : https://help.launchpad.net/ListHelp
>

Revision history for this message
Vadim Peretokin (vperetokin) wrote :

Any luck with this?

Revision history for this message
cyril duez (siril) wrote : Re: [Bug 1660082] Re: Error on script registered on GMCP event

I did reproduced the issue with a new profile.

I might have the video ready in a couple of weeks or so as i need more time.

On March 18, 2017 3:34:16 AM EDT, Vadim Peretokin <email address hidden> wrote:
>Any luck with this?

Revision history for this message
agda (agda) wrote :

It is not as simple that you need to have a function with the same name as as the script name, "GMCP"?

function GMCP()
  display(gmcp)
end

Revision history for this message
cyril duez (siril) wrote :

Actually it is simple than that, thank you!

Revision history for this message
Vadim Peretokin (vperetokin) wrote :

Can't believe I missed this either, hah.

Changed in mudlet:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.