libubus-lua: dependencies broken on 25.12.5
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
The report identifies libubus-lua and shows unresolved Lua symbols when loading /usr/lib/lua/ubus.so on OpenWrt 25.12.6. Start by inspecting the ubus package and its Lua binding build and dependency metadata, then reproduce the require("ubus") failure with the reported Lua 5.1 packages. Done means the binding loads successfully from both a Lua script and collectd-mod-lua on the reported target.
Written by the indexing model from the issue text.
Description
Package Name
libubus-lua
Maintainer
@nbd168
OpenWrt Version
25.12.6
OpenWrt Target/Subtarget
ipq40xx/generic
Steps to Reproduce
New image has been built using main release tagged imagebuilder containing collectd-mod-lua, which in turn pulls in libubus-lua and liblua:
# apk list -I|grep lua
collectd-mod-lua-5.12.0-r56 arm_cortex-a7_neon-vfpv4 {feeds/packages/feeds/packages/utils/collectd} (MIT GPL-2.0-or-later) [installed]
liblua5.1.5-5.1.5-r11 arm_cortex-a7_neon-vfpv4 {feeds/base/utils/lua} (MIT) [installed]
libubus-lua-2026.06.28~24864e78-r2 arm_cortex-a7_neon-vfpv4 {feeds/base/system/ubus} (LGPL-2.1) [installed]
lua-5.1.5-r11 arm_cortex-a7_neon-vfpv4 {feeds/base/utils/lua} (MIT) [installed]
# apk list -I|grep ubus
libubus-lua-2026.06.28~24864e78-r2 arm_cortex-a7_neon-vfpv4 {feeds/base/system/ubus} (LGPL-2.1) [installed]
libubus20251202-2026.06.28~24864e78-r2 arm_cortex-a7_neon-vfpv4 {feeds/base/system/ubus} (LGPL-2.1) [installed]
ubus-2026.06.28~24864e78-r2 arm_cortex-a7_neon-vfpv4 {feeds/base/system/ubus} (LGPL-2.1) [installed]
ubusd-2026.06.28~24864e78-r2 arm_cortex-a7_neon-vfpv4 {feeds/base/system/ubus} (LGPL-2.1) [installed]
ucode-mod-ubus-2026.01.16~85922056-r2 arm_cortex-a7_neon-vfpv4 {feeds/base/utils/ucode} (ISC) [installed]
uhttpd-mod-ubus-2026.08.24~373145f7-r1 arm_cortex-a7_neon-vfpv4 {feeds/base/network/services/uhttpd} (ISC) [installed]
libubus-lua is missing symbols:
# ldd /usr/lib/lua/ubus.so
ldd (0xb6ede000)
libubus.so.20251202 => /lib/libubus.so.20251202 (0xb6ed1000)
libubox.so.20260213 => /lib/libubox.so.20260213 (0xb6ec3000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb6eb6000)
libc.so => ldd (0xb6ede000)
Error relocating /usr/lib/lua/ubus.so: lua_touserdata: symbol not found
Error relocating /usr/lib/lua/ubus.so: lua_pushlightuserdata: symbol not found
Error relocating /usr/lib/lua/ubus.so: lua_isnumber: symbol not found
Error relocating /usr/lib/lua/ubus.so: luaL_ref: symbol not found
Error relocating /usr/lib/lua/ubus.so: lua_objlen: symbol not found
Error relocating /usr/lib/lua/ubus.so: lua_getfield: symbol not found
etc
Actual Behaviour
Loading ubus from inside a lua script running under collectd-mod-lua fails. Loading it from the command line also fails:
# lua
Lua 5.1.5 Copyright (C) 1994-2012 Lua.org, PUC-Rio (double int32)
> local ok, ubus = pcall(require, "ubus")
>
> if not ok then
>> print ("fail")
>> end
fail
>
Confirmation Checklist
- The package is maintained in this repository.
- I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
- I am reporting an issue for OpenWrt, not an unsupported fork.
- Dominant language
- Makefile
- Stars
- 4.7k
- Forks
- 4k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 251
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openwrt/packages
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
openwrt/packages#31307 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
openwrt/packages#31306 · 1 comment ·
Maintainers usually reply within 1 day
All issues in openwrt/packages
Similar issues
-
bug(core): JsonOutputKeyToolsParser ignores returnId: truePossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/langchainjs#12239 ·
Maintainers usually reply within 1 day
-
Board view: the Monitoring column is always empty because compact issue rows drop displayStatusOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
paperclipai/paperclip#21837 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug(python): read_transaction raises TypeError on a Rewrite with rewritten indicesPossibly taken @Borg93 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
lance-format/lance#11117 ·
Maintainers usually reply within 2 days
-
[Bug]: time_expr "between november and january" returns an inverted range and matches nothingPossibly taken @KshitijKasodkar claimed this today. Openbug claim-pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
doobidoo/mcp-memory-service#2030 · 1 comment ·
Maintainers usually reply within 1 day