You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I've had a ZimaBoard sitting on my shelf for probably ~2 years. I finally decided to mess around with it. It's runninv CasaOS v0.3.6 and of course the first thing I wanted to do was updated it to the latest (apparently v.0.4.15). Hitting "Upgrade Now" however had the web interface just sitting there for .. close to an hour. I'm on a decent connection and I have many Debian packages cached on my network.
Anyway, eventually I logged in through SSH, rebooted it, and then manually ran a sudo apt update, only to be prompted several times because upstream has changed testing from bookworm to trixie.
I imagine the web interface locked up because when this happens, apt requires the user's explicit acceptance to move forward.
Expected behavior
If needed, pass that on to the user through the web interface so that apt can do its job.
Screenshots
System Time
Run timedatectl and share the output
Local time: Fri 2025-01-24 22:42:07 EST
Universal time: Sat 2025-01-25 03:42:07 UTC
RTC time: Sat 2025-01-25 03:42:07
Time zone: America/New_York (EST, -0500)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
The text was updated successfully, but these errors were encountered:
Describe the bug
I've had a ZimaBoard sitting on my shelf for probably ~2 years. I finally decided to mess around with it. It's runninv CasaOS v0.3.6 and of course the first thing I wanted to do was updated it to the latest (apparently v.0.4.15). Hitting "Upgrade Now" however had the web interface just sitting there for .. close to an hour. I'm on a decent connection and I have many Debian packages cached on my network.
Anyway, eventually I logged in through SSH, rebooted it, and then manually ran a
sudo apt update
, only to be prompted several times because upstream has changedtesting
frombookworm
totrixie
.I imagine the web interface locked up because when this happens,
apt
requires the user's explicit acceptance to move forward.Expected behavior
If needed, pass that on to the user through the web interface so that
apt
can do its job.Screenshots
System Time
The text was updated successfully, but these errors were encountered: