The Accounts tab is working just fine on my Raspberry Pi on latest Tumbleweed, so I cannot replicate the issue. And I wasn't able to find anything from the logs that might cause the issue.

Are there any errors or warnings on the browser console when you open the Accounts tab?

Did you login as root on a new installation? By default, cockpit is not suppose to allow you to login directly as root.

As Miika said, it would be good to see any messages from the browser console which would have errors from the backend as to why user accounts are not visible.

(In reply to Adam Majer from comment #2)
> Did you login as root on a new installation? By default, cockpit is not
> suppose to allow you to login directly as root.
> 
> As Miika said, it would be good to see any messages from the browser console
> which would have errors from the backend as to why user accounts are not
> visible.

I tried both, root login is possible. As user I can enter root password for administrative access. I have this issue for both.
What I can see on tab page is a never ending cycle (refreshing).

And Tumbleweed on x86_64 works with Accounts tab and root login is okay as well.

(In reply to Zaoliang Luo from comment #3)
> (In reply to Adam Majer from comment #2)
> > Did you login as root on a new installation? By default, cockpit is not
> > suppose to allow you to login directly as root.
> > 
> > As Miika said, it would be good to see any messages from the browser console
> > which would have errors from the backend as to why user accounts are not
> > visible.
> 
> I tried both, root login is possible. As user I can enter root password for
> administrative access. I have this issue for both.
> What I can see on tab page is a never ending cycle (refreshing).
> 
> And Tumbleweed on x86_64 works with Accounts tab and root login is okay as
> well.

Can you provide information about the browser console? That is where errors are reported.

Also, can you answer the question "was this a new installation"?

(In reply to Adam Majer from comment #4)
> (In reply to Zaoliang Luo from comment #3)
> > (In reply to Adam Majer from comment #2)
> > > Did you login as root on a new installation? By default, cockpit is not
> > > suppose to allow you to login directly as root.
> > > 
> > > As Miika said, it would be good to see any messages from the browser console
> > > which would have errors from the backend as to why user accounts are not
> > > visible.
> > 
> > I tried both, root login is possible. As user I can enter root password for
> > administrative access. I have this issue for both.
> > What I can see on tab page is a never ending cycle (refreshing).
> > 
> > And Tumbleweed on x86_64 works with Accounts tab and root login is okay as
> > well.
> 
> Can you provide information about the browser console? That is where errors
> are reported.
> 
> Also, can you answer the question "was this a new installation"?

yes, this is a fresh installation as well. I compared both, updated and fresh installation. both has same issue on my rpi4.

browser console works normal.

(In reply to Zaoliang Luo from comment #6)
> browser console works normal.

Of course it works normal.. the question is are there any warnings, errors, notices that give a hint why the accounts page is not loading?

Created attachment 871693 [details]
screen record

please check the screen record for details.

(In reply to Adam Majer from comment #7)
> (In reply to Zaoliang Luo from comment #6)
> > browser console works normal.
> 
> Of course it works normal.. the question is are there any warnings, errors,
> notices that give a hint why the accounts page is not loading?

no, no errors, no warnings

(In reply to Zaoliang Luo from comment #9)
> please check the screen record for details.

https://firefox-source-docs.mozilla.org/devtools-user/browser_console/index.html

I'm talking about this Web Console. It's part of the web browser. If you could,

1. open the webconsole
2. laod cockpit page (don't open new tab, etc... since webconsole is for the tab you opened it in)
3. go to Accounts
4. notice if some errors/warnings appeared on the webconsole window.

(In reply to Adam Majer from comment #2)
> Did you login as root on a new installation? By default, cockpit is not
> suppose to allow you to login directly as root.

To clarify this mystery, it is allowed after we changed cockpit-ws back from container into a regularly installed package. With the container it went through ssh with no root login, but now the the login happens locally where root is allowed, as it used to be.

(In reply to Robert Simai from comment #12)
> (In reply to Adam Majer from comment #2)
> > Did you login as root on a new installation? By default, cockpit is not
> > suppose to allow you to login directly as root.
> 
> To clarify this mystery, it is allowed after we changed cockpit-ws back from
> container into a regularly installed package. With the container it went
> through ssh with no root login, but now the the login happens locally where
> root is allowed, as it used to be.

cockpit has its own list of not allowed logins. Sadly, it's created on install only in a scriptlet.


%post
....
%if 0%{?disallow_root}
    printf "root\n" >> /etc/cockpit/disallowed-users
%endif
    chmod 644 /etc/cockpit/disallowed-users

(In reply to Adam Majer from comment #13)

> cockpit has its own list of not allowed logins. Sadly, it's created on
> install only in a scriptlet.
> 
> 
> %post
> ....
> %if 0%{?disallow_root}
>     printf "root\n" >> /etc/cockpit/disallowed-users
> %endif
>     chmod 644 /etc/cockpit/disallowed-users

I see (and that all probably deserves an own bug/discussion) but was it ever deliberately disallowed, maybe only in Tumbleweed? SLE Micro clearly allowed it and behavior accidentally changed in Dolomite (for a while) because of the cockpit-ws container. Anyhow, would be great to use the same standard in Tumbleweed and ALP to not confuse users.

(In reply to Adam Majer from comment #11)
> (In reply to Zaoliang Luo from comment #9)
> > please check the screen record for details.
> 
> https://firefox-source-docs.mozilla.org/devtools-user/browser_console/index.
> html
> 
> I'm talking about this Web Console. It's part of the web browser. If you
> could,
> 
> 1. open the webconsole
> 2. laod cockpit page (don't open new tab, etc... since webconsole is for the
> tab you opened it in)
> 3. go to Accounts
> 4. notice if some errors/warnings appeared on the webconsole window.

okay, I see.

here is what I found in web console:

--

terminal.js:12  Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://compute:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

_updateDimensions @ terminal.js:12
terminal.js:12  Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://compute:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-6albFgZ6yaYoS5i33kNNTRg+wTKn1H3i75bXizv1Jzs='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

_updateDimensions @ terminal.js:12
terminal.js:12  Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://compute:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

_injectCss @ terminal.js:12
terminal.js:12  Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://compute:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-xmGr5sL2sH/dXZBBUjFw3/75KjFpgvnHYkS2v4QD8Gk='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

_injectCss @ terminal.js:12
terminal.js:12  Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://compute:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

_updateDimensions @ terminal.js:12
terminal.js:12  Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://compute:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-tTIHoZ3tXZQskZ5POZmkH6xXiCcZgU9rgv4YBvH0qyA='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

_updateDimensions @ terminal.js:12
6storaged.js:15  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ storaged.js:15
3networkmanager.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ networkmanager.js:11
services.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ services.js:11
storaged.js:15  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ storaged.js:15
3networkmanager.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ networkmanager.js:11
3storaged.js:15  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ storaged.js:15
3networkmanager.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ networkmanager.js:11
services.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ services.js:11
3storaged.js:15  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ storaged.js:15
6networkmanager.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ networkmanager.js:11
services.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ services.js:11
6storaged.js:15  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ storaged.js:15
3networkmanager.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ networkmanager.js:11
services.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ services.js:11
3storaged.js:15  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ storaged.js:15
22networkmanager.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ networkmanager.js:11
services.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ services.js:11
3storaged.js:15  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ storaged.js:15
6networkmanager.js:11  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.
(anonymous) @ networkmanager.js:11

(In reply to Adam Majer from comment #2)
> Did you login as root on a new installation? By default, cockpit is not
> suppose to allow you to login directly as root.

I downloaded a new raspberry pi image and did nothing but install cockpit on it and was able to login as a root.

Also I'm now able to replicate the issue: After creating a fresh install on a VM and installing cockpit on it, the Accounts tab is not working. But it's working on my older install. I ran `zypper ref; zypper dup` to make sure that both systems are up-to-date.

Still not sure what's causing it though. I can see a lot of javascript errors but they are too generic ("o.split is not a function") and the backtrace points to minified js files which makes it harder to debug.

The error that's repeated:

Uncaught (in promise) TypeError: o.split is not a function
    JA https://192.168.122.186:9090/cockpit/$449e2e561375c2b8aeafef6a1023401b92e51eaee02af5ae2e90fbedb5dec36b/users/users.js:72