Applications-->Networking issues Not Found

[okcrum]

Explain what happens

1. Selecting Networking choice from main menu works fine.
2. Selecting Applications-->Networking yields a Not Found message.

Version of Cockpit

287.1-0+deb12u3

Where is the problem in Cockpit?

Navigation & Shell

Server operating system

Debian

Server operating system version

12 (bookworm)

What browsers are you using?

Firefox

System log

No errors logged by cockpit or apache2

[martinpitt]

I first thought of NetworkManager not being installed, but that's not it -- that was fixed in #15245 (version 238), and earlier versions had a different symptom. Can you please open the JS console (Ctrl-Shift-J) after logging in, then switch to the Networking page, and copy all the errors from there? That may already give a hint. Thanks!

[okcrum]

The following was logged by selecting (in order, from Overview):

Network
Applications-->Network (Not Found)
Network
Applications-->Network (Not Found)

Content-Security-Policy: Ignoring ‘block-all-mixed-content’ because mixed content display upgrading makes block-all-mixed-content obsolete. networkmanager

Partitioned cookie or storage access was provided to “view-source:https://192.168.1.5:9090/networkmanager” because it is loaded in the third-party context and dynamic state partitioning is enabled.

Content-Security-Policy: Ignoring ‘block-all-mixed-content’ because mixed content display upgrading makes block-all-mixed-content obsolete. apps

Partitioned cookie or storage access was provided to “view-source:https://192.168.1.5:9090/apps” because it is loaded in the third-party context and dynamic state partitioning is enabled.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://play.google.com/log?format=json&hasfast=true&authuser=0. (Reason: CORS request did not succeed). Status code: (null). 4
storage access was provided to “view-source:https://192.168.1.5:9090/apps” because it is loaded in the third-party context and dynamic state partitioning is enabled.

[martinpitt]

What does cockpit-bridge --packages show as the user that you used to log into cockpit? Do you have cockpit-networkmanager installed? Do you have anything in /usr/local/share/cockpit/ or ~/.local/share/cockpit?

[okcrum]

chuck@fruitcake:~ $ cockpit-bridge --packages
apps Applications /usr/share/cockpit/apps
base1 /usr/share/cockpit/base1
metrics /usr/share/cockpit/metrics
network Networking /usr/share/cockpit/networkmanager
pcp /usr/share/cockpit/pcp
performance /usr/share/cockpit/tuned
shell /usr/share/cockpit/shell
sosreport Diagnostic reports /usr/share/cockpit/sosreport
ssh /usr/share/cockpit/ssh
static /usr/share/cockpit/static
storage Storage /usr/share/cockpit/storaged
system Overview, Logs, Services, Terminal /usr/share/cockpit/systemd
updates Software updates /usr/share/cockpit/packagekit
users Accounts /usr/share/cockpit/users
wifimanager WiFi manager /usr/share/cockpit/wifimanager
checksum = a37d6011ae02b7fc27a1b7ee0f6cf775cca252bf2b74f45b22f8bc66dd5ff218
chuck@fruitcake:~ $ apt search cockpit-networkmanager
Sorting... Done
Full Text Search... Done
cockpit-networkmanager/stable,stable,now 287.1-0+deb12u3 all [installed,auto-removable]
Cockpit user interface for networking

chuck@fruitcake:~ $ l /usr/local/share/cockpit/
ls: cannot access '/usr/local/share/cockpit/': No such file or directory
chuck@fruitcake:~ $ l ~/.local/share/cockpit
ls: cannot access '/home/chuck/.local/share/cockpit': No such file or directory
chuck@fruitcake:~ $ l /usr/share/cockpit/
apps branding motd packagekit shell ssh storaged tuned wifimanager
base1 metrics networkmanager pcp sosreport static systemd users
chuck@fruitcake:~ $

[martinpitt]

Ah sorry, I misunderstood this -- so you are saying the "Networking" page itself works fine, you can manage your networks (at least the NetworkManager ones, not others from networkd or ifupdown or so)?

I booted a clean Debian 12 VM with cockpit-packagekit , cockpit version 287.1-0+deb12u3. Logged into Cockpit, refreshed the Apps page, but it stays at "No applications installed or available.". That is a bug (the AppStream metadata is supposed to be part of the Debian package archive), but apparently not what you observe.

What does the apps page show exactly? Please post a screenshot.

[okcrum]

Here you go. The main menu Network selection (on the left) points to https://192.168.1.5:9090/network
The Apps menu Network selection points to https://192.168.1.5:9090/networkmanager
This looks like the issue, since changing the second URI to the first and voila! Network Manager appears.

[martinpitt]

Thanks for confirming! This was fixed last year in commit b4d783a. Note that the official Debian backports have newer Cockpit versions which are much better supported. See https://cockpit-project.org/running.html#debian

[okcrum]

Any idea when this fix makes it into -stable?

[martinpitt]

As I said, you can install cockpit from -backports, it's fixed there. We won't do a stable release update in bookworm-updates, this bug isn't severe enough for that overhead/risk.

[okcrum]

I guess I was not clear enough. How long would you think that any release containing this fix (and, obviously other more major ones) takes to make it to -stable?

[martinpitt]

We do Debian (or Ubuntu) stable release updates only for security fixes. So in that sense, the answer to your question is "infinite/not at all".

Each new Cockpit release adds new features and fixes stuff, and sending them all to stable-updates is out of the question. That's what backports are for, and they timely get all the upstream releases. We generally recommend running the backports, they are better supported and 100% tested and supported in our CI.

[okcrum]

I'll wait for the release that fixes the TLS issues, then. Thanks.

[martinpitt]

@okcrum Check OSes which have at least Cockpit 313 then. I.e. Debian 12 + backports, or Debian testing, or Ubuntu ≥ 24.04 LTS (or Fedora or RHEL/CentOS 9/10 of course).