Cockpit "Oops" as soon as the page finished loading

[hypersplash]

Explain what happens

1. I accessed the web console through Firefox
2. The red "Oops" message immediately popped up right after the page was loaded
3. As I clicked on Oops the message is simply
   Cockpit had an unexpected internal error. You can try restarting Cockpit by pressing refresh in your browser. The javascript console contains details about this error (Ctrl-Shift-I in most browsers).

Version of Cockpit

350-1

Where is the problem in Cockpit?

Navigation & Shell

Server operating system

Debian

Server operating system version

Sid (rolling release / bleeding edge)

What browsers are you using?

Firefox

System log

JavaScript log:
Content-Security-Policy: The page’s settings blocked an inline style (style-src-elem) from being applied because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-dd4J3UnQShsOmqcYi4vN5BT3mGZB/0fOwBA72rsguKc=', requires 'unsafe-hashes' for style attributes) or a nonce. content.js:85:443
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-sBQspCyjc+p8EI4pUICBc9cLXH52A/ESHuoYxoMMh14=') or a nonce. content.js:71:183
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-1IkHQxvyH27HA78GuzvXQnT+e54J4v29T6saiGzG++w=') or a nonce. content.js:71:183
Content-Security-Policy: The page’s settings blocked an inline style (style-src-elem) from being applied because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-dd4J3UnQShsOmqcYi4vN5BT3mGZB/0fOwBA72rsguKc=', requires 'unsafe-hashes' for style attributes) or a nonce. content.js:85:443
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-V0Qomdl85G96/mdoMb5Vr88Rl9TjMkxw26jCD5SauOQ=') or a nonce. content.js:71:183
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-EYjFYxX2T/s5tPW71M3BudI+b+LSBMgw6Ce5gDF8KuU=') or a nonce. content.js:71:183
Content-Security-Policy: The page’s settings blocked an inline style (style-src-elem) from being applied because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-dd4J3UnQShsOmqcYi4vN5BT3mGZB/0fOwBA72rsguKc=', requires 'unsafe-hashes' for style attributes) or a nonce. content.js:85:443
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-Jq55A8GuwIfTCaRN/DgW5dbu6ITvewQPAIsbXtW06FI=') or a nonce. content.js:71:183
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-uLQYgDd2xDHG9YSbWESKsRzhVwJEmcpmBL9SBzrUnXs=') or a nonce. content.js:71:183
Content-Security-Policy: The page’s settings blocked an inline style (style-src-elem) from being applied because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-dd4J3UnQShsOmqcYi4vN5BT3mGZB/0fOwBA72rsguKc=', requires 'unsafe-hashes' for style attributes) or a nonce. content.js:85:443
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-LV1b2IJ3+7MTa1NXxpJ9OW6cW9d44O2GR79kR/c3Wuw=') or a nonce. content.js:71:183
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-0Yxf1iNriNVzV1pw7WYOnIJGFNbE6zZPFoZXyLO9BTw=') or a nonce. content.js:71:183
Content-Security-Policy: The page’s settings blocked an inline style (style-src-elem) from being applied because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-dd4J3UnQShsOmqcYi4vN5BT3mGZB/0fOwBA72rsguKc=', requires 'unsafe-hashes' for style attributes) or a nonce. content.js:85:443
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-DNE55Jj5W7/FfZRqVFK+t5x4x64aBFj22keJgy5fCSI=') or a nonce. content.js:71:183
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “default-src 'self'”. Consider using a hash ('sha256-yVEZTqChOdNOUYyx7Lt2B73ODO86GkaULQZ5+RFsIYY=') or a nonce. content.js:71:183
RangeError: date value is not finite in DateTimeFormat.format()
    e3 http://localhost:6942/cockpit/@localhost/updates/updates.js:62
    t http://localhost:6942/cockpit/@localhost/updates/updates.js:62
    render http://localhost:6942/cockpit/@localhost/updates/updates.js:62
    gu http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    u0 http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    wk http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    _k http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    DT http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    vd http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    Iu http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    gk http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    fg http://localhost:6942/cockpit/@localhost/updates/updates.js:1
    ag http://localhost:6942/cockpit/@localhost/updates/updates.js:1
updates.js:8:161
Uncaught RangeError: date value is not finite in DateTimeFormat.format()
    e3 http://localhost:6942/cockpit/@localhost/updates/updates.js:62
    t http://localhost:6942/cockpit/@localhost/updates/updates.js:62
    render http://localhost:6942/cockpit/@localhost/updates/updates.js:62
    gu http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    u0 http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    wk http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    _k http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    DT http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    vd http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    Iu http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    gk http://localhost:6942/cockpit/@localhost/updates/updates.js:8
    fg http://localhost:6942/cockpit/@localhost/updates/updates.js:1
    ag http://localhost:6942/cockpit/@localhost/updates/updates.js:1
updates.js:62:7954

[jelly]

Thanks for the bug report:

Uncaught RangeError: date value is not finite in DateTimeFormat.format()

This seems to point to either of these calls:

pkg/packagekit/history.jsx:import * as timeformat from "timeformat";
pkg/packagekit/history.jsx:                    { title: timeformat.dateTime(update.time), props: { className: "history-time" } },
pkg/packagekit/updates.jsx:import * as timeformat from "timeformat";
pkg/packagekit/updates.jsx:        ? timeformat.distanceToNow(new Date().valueOf() + transactionProps.RemainingTime * 1000)
pkg/packagekit/updates.jsx:        lastChecked = cockpit.format(_("Last checked: $0"), timeformat.distanceToNow(new Date().valueOf() - timeSinceRefresh * 1000));

This all seems to point to packagekit giving us unexpected data.

[CaptInsano]

Came here to report same issue:

Happening on 2 my my machines (only have 2 running Cockpit)

Same on either Chromium or Firefox browsers (latest updates).

Console gives me the following:

overview.js:144 Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
(anonymous) @ overview.js:144
overview.js:213 failed to fetch lastlog2: V
updates.js:8 RangeError: Invalid time value
    at e3 (updates.js:62:7954)
    at updates.js:62:9708
    at Array.map (<anonymous>)
    at es.render (updates.js:62:9384)
    at gu (updates.js:8:6201)
    at u0 (updates.js:8:5998)
    at wk (updates.js:8:45257)
    at _k (updates.js:8:40034)
    at DT (updates.js:8:39962)
    at vd (updates.js:8:39815)
mu @ updates.js:8
updates.js:8 Uncaught RangeError: Invalid time value
    at e3 (updates.js:62:7954)
    at updates.js:62:9708
    at Array.map (<anonymous>)
    at es.render (updates.js:62:9384)
    at gu (updates.js:8:6201)
    at u0 (updates.js:8:5998)
    at wk (updates.js:8:45257)
    at _k (updates.js:8:40034)
    at DT (updates.js:8:39962)
    at vd (updates.js:8:39815)
cockpit.js:6 cockpit.format_{bytes,bits}[_per_sec](..., GiB, [object Object]) is deprecated.
r @ cockpit.js:6

All time setting seem OK on my machine, TZ etc all correct.

[jelly]

Is this also on Debian Sid?

[hypersplash]

And no, I don't think my system time is offset or anything, it's always up to date with Cloudflare's NTP server. If that information helps

[jelly]

And no, I don't think my system time is offset or anything, it's always up to date with Cloudflare's NTP server. If that information helps

No no, its unrelated to your local time, we receive some data from PackageKit which includes timestamps which we represent as textual date format to the user. There seems to be an issue here. What would be good to know is what the PackageKit version is which you have installed.

[hypersplash]

It's 1.3.2-1, this is the dpkg output if you need it

Desired=Unknown/Install/Remove/Purge/Hold`
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=====================================
ii packagekit 1.3.2-1 amd64 Provides a package management service

[jelly]

Tried to reproduce this issue and I can't so it has to be something specific on your setup:

root@debian-testing-127-0-0-2-2201:~# pkcon --version
1.3.2

Investigating a bit deeper:

-> updates.js:62:7954 where 7954 is format(e)

    var Dv = k(io(), 1)
      , JP = Dv.default.gettext
      , Jf = () => Dv.default.language.replace("_", "-")
      , JF = e => new Intl.DateTimeFormat(Jf(),e);
    var e3 = e => JF({
        dateStyle: "medium",
        timeStyle: "short"
    }).format(e);
    var Bh = [{
        name: "second",
        max: 60
    }, {
        name: "minute",
        max: 3600
    }, {
        name: "hour",
        max: 86400
    }, {
        name: "day",
        max: 86400 * 7
    }, {
        name: "week",
        max: 86400 * 30
    }, {
        name: "month",
        max: 86400 * 365
    }, {
        name: "year",
        max: 1 / 0
    }];

Called from:

            let o = this.mergeHistory();
            if (o.length === 0)
                return null;
            let t = o.map( (r, n) => {
                let a = Pn.default.createElement("div", {
                    className: "list-view-pf-additional-info-item"
                }, Pn.default.createElement(F6, null), Nv.default.format(Nv.default.ngettext("$0 package", "$0 packages", r.num_packages), r.num_packages))
                  , l = Pn.default.createElement(Rv, {
                    packages: r.packages
                });
                return {
                    props: {
                        key: r.time
                    },
                    columns: [{
                        title: e3(r.time),
                        props: {
                            className: "history-time"
                        }
                    }, {
                        title: a,
                        props: {
                            className: "history-pkgcount"
                        }
                    }],
                    initiallyExpanded: n == 0,
                    hasPadding: !0,
                    expandedContent: l

So this is some specific update you have which crashed, code in question is pkg/packagekit/history.jsx

[CaptInsano]

My setup:

2 machines with same hardware & software both presenting as above

        _,met$$$$$gg.          user@machine
     ,g$$$$$$$$$$$$$$$P.       --------------
   ,g$$P""       """Y$$.".     OS: Debian GNU/Linux forky/sid (forky) x86_64
  ,$$P'              `$$$.     Host: Guado (1.0)
',$$P       ,ggs.     `$$b:    Kernel: Linux 6.16.12+deb14+1-amd64
`d$$'     ,$P"'   .    $$$     Uptime: 1 day, 22 hours, 21 mins
 $$P      d$'     ,    $$P     Packages: 652 (dpkg)
 $$:      $$.   -    ,d$$'     Shell: bash 5.3.3
 $$;      Y$b._   _,d$P'       Terminal: /dev/pts/0
 Y$$.    `.`"Y$$$$P"'          CPU: Intel(R) Celeron(R) 3215U (2) @ 1.70 GHz
 `$$b      "-.__               GPU: Intel HD Graphics @ 0.85 GHz [Integrated]
  `Y$$b                        Memory: 892.54 MiB / 3.70 GiB (24%)
   `Y$$.                       Swap: 0 B / 977.00 MiB (0%)
     `$$b.                     Disk (/): 4.69 GiB / 13.15 GiB (36%) - ext4
       `Y$$b.                  Local IP (enp1s0): 192.168.20.200/24
         `"Y$b._               Locale: en_IE.UTF-8
             `""""


user@machine:~$ pkcon --version
1.3.2

[jelly]

PackageKit gives us the "wrong" data, we'll filter the invalid entries and log invalid timespec's in #22575