[Bug]: user status change not sticking, reverts to previous status on page load

[gerbrent]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Given a user status change, the new user status seems not to be permanent - the user status reverts to the previous status when other apps or interface changes are requested/clicked on.

Steps to reproduce

1. have a user status set - e.g. "Away"
2. set a new status - e.g. "Online"
3. click on an element in Hub that loads much of the page, a non-cached Talk conversation or a new app
   (confirmed with clicking on a Talk conversation that was never loaded/cached in this session, or moving to a different app e.g. Calendar from Talk)
4. once the page loads, user status is reverted to the previous status - e.g. "Away"

Expected behavior

expecting the user status to stick despite interface loading, app switching, or multitasking with Hub open in multiple browser windows

Installation method

None

Nextcloud Server version

28.0.0 beta 2

Operating system

Other

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

Updated from a MINOR version (ex. 22.1 to 22.2)

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

Nextcloud Server version 28.0.0 beta 2
Firefox & Chromium
openSUSE Tumbleweed

[ordinaly]

Same running on Docker, forever in a meeting 🫣

[joshtrichards]

I'm unable to reproduce this behavior. Can one of you please provide more details about your setup/environment? The issue template is nearly completely blank so not a lot to go on here. :-)

Shot in the dark: Any chance you're using NPM as a reverse proxy with Cache Assets accidentally enabled or have a not up-to-date Nginx web config?

[gerbrent]

I haven't seen this behaviour in a few months now, which feels promising.

[nextcloud-command]

This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.