I'm using prosody0.10 on ArchLinux. Every time somebody enters a muc, I get
this traceback:
general: Attempt to read a non-existent global 'affiliation'
stack traceback:
/usr/lib/prosody/modules/muc/mod_muc.lua:42: in function 'set_affiliation'
/usr/lib/prosody/modules/muc/muc.lib.lua:355: in function '?'
/usr/lib/prosody/util/events.lua:73: in function </usr/lib/prosody/util/events.lua:69>
(tail call): ?
(tail call): ?
/usr/lib/prosody/modules/muc/muc.lib.lua:381: in function </usr/lib/prosody/modules/muc/muc.lib.lua:370>
(tail call): ?
/usr/lib/prosody/util/events.lua:73: in function </usr/lib/prosody/util/events.lua:69>
(tail call): ?
/usr/lib/prosody/core/stanza_router.lua:187: in function 'core_post_stanza'
/usr/lib/prosody/core/stanza_router.lua:135: in function 'core_process_stanza'
/usr/lib/prosody/modules/mod_c2s.lua:239: in function 'func'
/usr/lib/prosody/util/async.lua:88: in function </usr/lib/prosody/util/async.lua:86>
Also (I'm not sure whether this is related or not) when try to modify a muc and
make it members only, I get this one:
c2s140f130: Traceback[c2s]: /usr/lib/prosody/modules/muc/muc.lib.lua:726:
attempt to index local 'item' (a nil value)
stack traceback:
/usr/lib/prosody/modules/muc/muc.lib.lua:726: in function </usr/lib/prosody/modules/muc/muc.lib.lua:724>
(tail call): ?
/usr/lib/prosody/util/events.lua:73: in function </usr/lib/prosody/util/events.lua:69>
(tail call): ?
(tail call): ?
(tail call): ?
/usr/lib/prosody/util/events.lua:73: in function </usr/lib/prosody/util/events.lua:69>
(tail call): ?
/usr/lib/prosody/core/stanza_router.lua:187: in function 'core_post_stanza'
/usr/lib/prosody/core/stanza_router.lua:135: in function 'core_process_stanza'
/usr/lib/prosody/modules/mod_c2s.lua:239: in function 'func'
/usr/lib/prosody/util/async.lua:88: in function </usr/lib/prosody/util/async.lua:86>
Original issue reported on code.google.com by sankerm...@gmail.com on 24 Jul 2015 at 3:16
Original issue reported on code.google.com by
sankerm...@gmail.com
on 24 Jul 2015 at 3:16