nextcloud / nextcloud/desktop

[Bug]: Name conflict dialoge is not debounced, sends same requests repeatedly

Open
#8,108 0 comments 0 reactions 0 assignees View on GitHub
1. to develop bug confirmed feature: :cloud: GUI Prio: high
Dominant language
C++
Stars
3.9k
Forks
1k
Avg merge
1d 21h
Merged PRs (30d)
127

Description

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

- [x] This is a **bug**, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)

### Bug description

The *OK* button of the name conflict dialogue has no loading/disabled state. You can click it as often as you like. I twill lead to a number of requests and more errors.

### Steps to reproduce

1. Admin enable windows compatible filenames
2. Have a file with a `:`
3. Try to rename a file
4. Change name
5. Click *OK*
6. wait
7. Click *OK* because nothing happens
8. wait
9. Click *OK* because nothing happens

-> I get an error that the path already exists

### Expected behavior

Disabled button

### Which files are affected by this bug

na

### Operating system

Linux

### Which version of the operating system you are running.

6

### Package

Distro package manager

### Nextcloud Server version

31.0.0

### Nextcloud Desktop Client version

1.2.3.4.5

### 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

```shell

```

### Additional info

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.