Modify

Opened 4 years ago

Last modified 2 years ago

#17309 reopened defect

Luci Meta Package Misconfigured with Theme

Reported by: johnllyon@… Owned by: developers
Priority: normal Milestone:
Component: packages Version: Barrier Breaker 14.07
Keywords: Cc:

Description

I installed Barrier Breaker RC-2, but noticed that the Luci web-interface

After upgrading to Barrier Breaker, I performed the following commands to update my packages:

opkg update
opkg install luci luci-app-qos luci-proto-ipv6 ...

Luci installed successfully. I then started the uhttp daemon to enable access to Luci. However, when attempting to access the Luci Web Interface, I get the following error in my browser window:

/usr/lib/lua/luci/dispatcher.lua:284: No valid theme found
stack traceback:
	[C]: in function 'assert'
	/usr/lib/lua/luci/dispatcher.lua:284: in function 'dispatch'
	/usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194>

My first thought was that the meta-package was misconfigured and failed to install a theme for Luci. However, when I try to install a them manually, I get the following console output:

root@OpenWrt:~# opkg install luci-theme-bootstrap
Package luci-theme-bootstrap (svn-r10459-1) installed in root is up to date.

So it looks like the Luci meta-package is misconfigured. I'm using a WNDR3700, so I'm using the ar71xx/generic set of packages and builds.

Attachments (0)

Change History (5)

comment:1 Changed 4 years ago by jow

  • Resolution set to worksforme
  • Status changed from new to closed

Your /etc/config/luci probably still refers to the OpenWrt theme.

comment:2 Changed 4 years ago by johnllyon@…

  • Resolution worksforme deleted
  • Status changed from closed to reopened

Reopening because /etc/config/luci that was installed with the meta-package does not refer to any themes. Below is the content of the /etc/config/luci file:

config core main
        option lang auto
        option mediaurlbase /luci-static/openwrt.org
        option resourcebase /luci-static/resources

config extern flash_keep
        option uci              "/etc/config/"
        option dropbear "/etc/dropbear/"
        option openvpn  "/etc/openvpn/"
        option passwd   "/etc/passwd"
        option opkg             "/etc/opkg.conf"
        option firewall "/etc/firewall.user"
        option uploads  "/lib/uci/upload/"

config internal languages

config internal sauth
        option sessionpath "/tmp/luci-sessions"
        option sessiontime 3600

config internal ccache
        option enable 1

config internal themes

comment:3 Changed 4 years ago by hnyman

The theme is not included in the main default config file. Instead, it is added via a uci-defaults script, which makes it vulnerable in some scenarios:

  • firmware upgrade scenarios that include restoring settings from backup after reboot.
  • You manually install luci, start uhttpd, but do NOT reboot the router, so nothings runs the uci-defaults script. Installed default config includes no theme, yet, so Luci hangsto that assertation. Reboot will help as the uci-defaults should then run once and theme will get inserted into the config. (Sounds like this happened to op.)

Uci-defaults script is located at the theme: http://luci.subsignal.org/trac/browser/luci/trunk/themes/bootstrap/root/etc/uci-defaults/luci-theme-bootstrap

I wrote a Luci ticket about this ~10 months ago after having been locked out of my Luci GUI due to this issue. http://luci.subsignal.org/trac/ticket/618

Regarding forthcoming BB release, I think it would be better to have the current default theme included in the default config. That would ease upgrading from older versions.

comment:4 Changed 3 years ago by anonymous

thank you guys

comment:5 Changed 2 years ago by dorogi.zoltan@…

I had the same problem, after an upgrade.

The solution in ssh:

opkg update
opkg install luci-theme-bootstrap --force-reinstall

The web interface came back! :-)

Good luck!

D.Z.

Add Comment

Modify Ticket

Action
as reopened .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.