[Bug]: Nextcloud files showing like badly named сломана

[XeonG]

⚠️ Before submitting, please verify the following: ⚠️

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

Bug description

I get this kind of error spam in the Nextcloud file sync... as a giant red log, that you can't copy in text form and doesn't appear to be logged somewhere

On windows the file exists as De Lorra-K A T A N Aキッド.mp3 on Linux nextcloud server in the webui it is shown as De Lorra-K A T A N Aキッド.mp3

Not sure when this got messed up like this, however is a lot of files like this now and I'd like to get them matching with what they look like on Windows desktop and remove all the error spam about it, what can I do about this?

Steps to reproduce

Upload file errors

Expected behavior

Matching file names on client desktop and server cloud

Which files are affected by this bug

Many files

Operating system

Windows

Which version of the operating system you are running.

Win11

Package

Official Linux AppImage

Nextcloud Server version

Nextcloud 31.0.13

Nextcloud Desktop Client version

3.16

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

Updated from a minor version (ex. 3.16.1 to 3.16.2)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

Additional info

No response

[johndoe7000]

Try this...
First make a full backup of your nextcloud server (and files) for safety.

SSH into your nextcloud server and open this file inside your nextcloud webroot folder with nano or any other editor you like.
lib/private/legacy/OC_Util.php
Search for "normalize" and you wll find this...

    /**
     * Normalize a unicode string
     *
     * @param string $value a not normalized string
     * @return bool|string
     */
    public static function normalizeUnicode($value) {
            if (Normalizer::isNormalized($value)) {
                    return $value;
            }

Change this code so it looks like this...

    /**
     * Normalize a unicode string
     *
     * @param string $value a not normalized string
     * @return bool|string
     */
    public static function normalizeUnicode($value) {
            return mb_convert_encoding($value,"UTF-8");
            if (Normalizer::isNormalized($value)) {
                    return $value;
            }

The new line return mb_convert_encoding($value,"UTF-8"); makes the magic at least for me and many others.
Save the changes and restart your nextcloud client and look if this change fixes your problem.
If not, remove the line or restore this file from backup.

[XeonG]

I shall give it a go, though if it does work then what, I gotta do this after every update?

just seems a little broken if this is result?

nvm doesn't seem to make any difference at all, after restarting the client it still just had all the same errors with these sort of file names :S

[XeonG]

was there some cli tool I needed to run on the server after changing that line?