Hi Thomas, I have the following sample (new.lua): #! /usr/bin/env lua local lgi = require 'lgi' local Gtk = lgi.Gtk local w = Gtk.Window {} Gtk.main() When I run it, I get: $ lua new.lua lua: /usr/share/lua/5.3/lgi/override/GObject-Object.lua:100: bad argument #4 to 'object_new' (table expected, got nil) stack traceback: [C]: in upvalue 'object_new' /usr/share/lua/5.3/lgi/override/GObject-Object.lua:100: in field '_construct' /usr/share/lua/5.3/lgi/override/GObject-Object.lua:216: in function </usr/share/lua/5.3/lgi/override/GObject-Object.lua:215> (...tail calls...) new.lua:4: in main chunk [C]: in ? It seems that the issue is known and it has been fixed upstream (https://github.com/pavouk/lgi/issues/167). Would it be possible to update lua-lgi to version 0.9.2, so that it works again? Many thanks for your help, Pablo
lua-lgi-0.9.2-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8746844ddf
lua-lgi-0.9.2-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-aa1677f74e
lua-lgi-0.9.2-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-8746844ddf
lua-lgi-0.9.2-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-aa1677f74e
lua-lgi-0.9.2-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
lua-lgi-0.9.2-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.