Still an issue in Matheria 7.2.2.4 (server version 32.0.5).

This also manifests a bit differently when using the lock screen player: resuming playback after the call actually skips back to to the start of a previously played track instead of resuming the current one (from where you were when the call came in). The player even shows the current track title, despite playing a different one.

Steps to reproduce this variant:

1. have a directory with two audio files, 1.m4a and 2.m4a
2. start to play 2.m4u
3. lock the screen
4. call the phone (just have it ring, then hang up)
5. resume playback from the lock screen

Expected behaviour

Playback of 2.m4a resumes from where it was when the call came in

Actual behaviour

The player beings to play 1.m4a from the start (but claims to play 2.m4a)

As a workaround, adding --no-warnings seems to suppress this output.

I just tested uploading from the Nextcloud app, and it is similarly affected: no conflict dialog is shown and the existing file gets overwritten.

Steps to reproduce

1. Have a PDF file with the name ”ä.pdf” (sic) in your Nextcloud.
2. Have a different PDF file with the same name on your IOS device (Files app).
3. Choose to share the file from your IOS device to Nextcloud.
4. Select the folder where ”ä.pdf” already exists.
5. Upload.

Expected behaviour

Get a dialog to choose how to deal with the filename conflict.

Actual behaviour

No dialog. The the existing file is silently overwritten by the newly shared file.

Logs

Nothing in server logs, but here’s the app log (at the default level).

Reasoning or why should it be changed/implemented?

The issue leads to data loss. I discovered this when I realized that saving bills from my banking app by sharing them to my Nextcloud had been doing this for who knows how long. (My electricity bills have the service provider name, ”Oulun Energia Sähköverkko Oy” in their filename.)

Environment data

iOS version: 17.0.3

Nextcloud iOS app version: ”Nextcloud Liquid for iOS 4.9.1.0”

Server operating system:

Web server: Apache 2.4.41

Database: MySQL/MariaDB 10.3.38

PHP version: 8.2

Nextcloud version: 27.1.3.2

Miscellaneous

• This is not reproducible on Android (with my server), which is why I’m pretty sure the fault lies with the IOS app.
• Also not reproducible on IOS with filenames with ASCII-only names (FWICT); this general case was apparently fixed when first reported as Upload via Share Menu Silently Overwrites Existing Files #1737.

25.0.3 (as indicated by output from `occ –version` above).

The exit code issue is still there:

# sudo -u www-data /usr/bin/php /var/www/nextcloud/occ --version
Nextcloud 25.0.3
# sudo -u www-data /usr/bin/php /var/www/nextcloud/occ files:scan -- nonexistantuser
Unknown user 1 nonexistantuser
+---------+-------+--------------+
| Folders | Files | Elapsed time |
+---------+-------+--------------+
| 0       | 0     | 00:00:00     |
+---------+-------+--------------+
# echo $?
0

Still present in Nextcloud 3.21.2. My device is a Samsung A9 running Android 10.

Hi @claucambra, I tested the appimage and the issue still reproduces.

Bug description

Using a path with umlauts as logDir causes an incorrectly encoded directory to be created and used as log directory, instead of the specified directory.

Steps to reproduce

1. Quit the client.
2. Edit nextcloud.cfg. Set logDir=/home/jani/Tänne (applying appropriately to your home directory)
3. Start the client.
4. ls /home/jani/Tänne

Expected behavior

A listing of new log files residing in /home/jani/Tänne.

Which files are affected by this bug

This question is unclear. The log files are the ones affected.

Operating system

Linux

Which version of the operating system you are running.

Ubuntu 20.04

Package

Distro package manager

Nextcloud Server version

24.0.4

Nextcloud Desktop Client version

3.5.4-20220806.084713.fea986309-1.0~focal1

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

Updated from a minor version (ex. 3.4.2 to 3.4.4)

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

No response

Additional info

This bizarre and otherwise exhaustingly long issue form is lacking a ”What happens instead of my expected outcome” question, so I’m entering it here instead: there are no logs in the specified target directory (it doesn’t even exist if you’ve not created it beforehand). Instead, like in the ye olden days, there is now a directory called Tänne containing the logs. In nextcloud.cfg the path has been re-encoded as logDir=/home/jani/T\xc3\xa4nne/ which is apparently how it should be, since a similarly re-encoded value for a ...localPath with umlauts in the [accounts] section has been working just fine for as long as I can remember using it.

Sorry for necromancing, but because Google seems to like this thread, I just thought I’d add a mention that a check_data_directory_permissions option for config.php has since been implemented (and backported down to NC12), and it allows the admin to turn off the automatic permissions reset (by assigning it false).

This is discouraged however, and ACLs or other means of managing access are still the better option where available.