[Bug]: v24 - Switching loglevel produces white page and browser console JS errors

[solracsf]

⚠️ 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 (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

On NC 24.0.2, trying to switch loglevel by un-checking a checkbox produces a white page and browser console errors.

Steps to reproduce

1. Go to /settings/admin/logging
2. Click on ... and try to remove some error level by un-checking a checkbox
3. White page and browser console errors

Expected behavior

No errors.

List of activated Apps

Enabled:
  - accessibility: 1.10.0
  - activity: 2.16.0
  - cloud_federation_api: 1.7.0
  - comments: 1.14.0
  - contactsinteraction: 1.5.0
  - dav: 1.22.0
  - federatedfilesharing: 1.14.0
  - federation: 1.14.0
  - files: 1.19.0
  - files_pdfviewer: 2.5.0
  - files_rightclick: 1.3.0
  - files_sharing: 1.16.2
  - files_trashbin: 1.14.0
  - files_versions: 1.17.0
  - files_videoplayer: 1.13.0
  - logreader: 2.9.0
  - lookup_server_connector: 1.12.0
  - nextcloud_announcements: 1.13.0
  - notifications: 2.12.0
  - notify_push: 0.4.0
  - oauth2: 1.12.0
  - onlyoffice: 7.5.2
  - password_policy: 1.14.0
  - photos: 1.6.0
  - provisioning_api: 1.14.0
  - serverinfo: 1.14.0
  - settings: 1.6.0
  - sharebymail: 1.14.0
  - survey_client: 1.12.0
  - systemtags: 1.14.0
  - theming: 1.15.0
  - twofactor_backupcodes: 1.13.0
  - updatenotification: 1.14.0
  - viewer: 1.8.0
  - workflowengine: 2.6.0

Nextcloud Signing status

No errors have been found.

Nextcloud Logs

Nothing related

[merwan]

I have the same issue since a few weeks, adding a text version of the two error messages to make it easier to find this issue using GitHub issues search.
First error:

Error: Minified React error #188; visit https://reactjs.org/docs/error-decoder.html?invariant=188 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    findDOMNode React
    transition CSSTransitionGroupChild.js:129
    componentWillEnter CSSTransitionGroupChild.js:97
    performEnter TransitionGroup.js:83
    componentDidUpdate TransitionGroup.js:192
    componentDidUpdate TransitionGroup.js:191
    React 2
    unstable_runWithPriority scheduler.production.min.js:18
    React 4
    unstable_runWithPriority scheduler.production.min.js:18
    React 6
    g App.js:160
    emit events.js:153
    e LogProvider.js:466
    c runtime.js:63
    _invoke runtime.js:294
    w runtime.js:119
    Babel 6
    value LogProvider.js:484
    e App.js:212
    c runtime.js:63
    _invoke runtime.js:294
    w runtime.js:119
    Babel 14
    value App.js:229
    React 2
    unstable_runWithPriority scheduler.production.min.js:18
    React 9
    _t index.js:17
    _t index.js:28
    <anonymous> index.js:23
    <anonymous> index.js:23
    <anonymous> index.js:23
react-dom.production.min.js:216:199

Second error:

Uncaught (in promise) Error: Minified React error #188; visit https://reactjs.org/docs/error-decoder.html?invariant=188 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    findDOMNode React
    transition CSSTransitionGroupChild.js:129
    componentWillEnter CSSTransitionGroupChild.js:97
    performEnter TransitionGroup.js:83
    componentDidUpdate TransitionGroup.js:192
    componentDidUpdate TransitionGroup.js:191
    React 2
    unstable_runWithPriority scheduler.production.min.js:18
    React 4
    unstable_runWithPriority scheduler.production.min.js:18
    React 6
    g App.js:160
    emit events.js:153
    e LogProvider.js:466
    c runtime.js:63
    _invoke runtime.js:294
    w runtime.js:119
    Babel 2
react-dom.production.min.js:289:283

[Thyroxine]

Hi, I've found a workaround if somebody needs quick fix of the page.
In my case the same behavior was permanent regardless of checkboxes.

1. Set 'loglevel' => 2 in config/config.php (was 0 before)
   (If you have docker version, login as root and find the corresponding volume directory in /var/lib/docker/volumes)
2. Clear browser cache and visit the page again.

[MartinX3]

Still an issue with 25.0.2 on a fresh rootless podman installation.
Somehow it seems to be triggered by the LDAP user and group backend app.
The same app creates an internal server error on login and some pages for me, even with the tested ldap configuration finding users.
But after changing the ldap configuration again to a different one which also has a successful test result but also let me login fixes this protocol view error.

It's funny that the protocol view doesn't work if it protocols important errors.

[solracsf]

See nextcloud/logreader#815