Overlay icons show "sync" instead of the warning (yellow) or error (red) icon for sync errors.
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 55/100
Línea de trabajo
Start by tracing how the desktop client maps ignored, excluded, and blacklisted file statuses to Windows overlay icons. Reproduce the invalid-name warning and quota-error cases described in the issue, then locate the relevant overlay status handling and tests. Done when those cases show the expected yellow warning or red error icon instead of sync arrows.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
[DC-425]
Pre-submission Checks
- I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
- I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.
Describe the bug
Files that the client reports as ignored, excluded or failed show the sync overlay icon in the local sync folder instead of the yellow warning triangle or the red error icon.
Yellow warning triangle: files with names that are not valid on Windows are listed in the client's errors list as ignored or excluded, but their overlay icon is sync instead of yellow warning triangle.
Red error icon: a 600 MB file is added to an account with a 1 GB quota that is already almost used up. The upload fails with error in client as blacklisted but the overlay icon is sync arrows instead of red error icon.
Expected behavior
Files that are not synced because of a problem, such as an invalid name, should show the yellow warning triangle.
Files and folders that are not synced because of a fatal problem should show the red error icon.
Steps to reproduce the issue
Yellow warning triangle
- Connect the ownCloud desktop client to the server and let the local sync folder sync fully.
- Open the local sync folder and add a problematic file, for example a file with a trailing dot, a file with a trailing space, or a file with a reserved name.
- The client lists the files as ignored or excluded in error section, but they show the sync icon instead of the yellow warning triangle in local sync folder.
Red error icon
- Connect the desktop client to its server.(preferably login to account with small quota set)
- Open the local sync folder and create a fatal problem, for example by adding files that are larger than the available quota.
- The client shows the quota error for the file with status blacklisted, but it shows the sync icon instead of the red error icon.
Screenshots
The red boxes in local sync shows overlay icons, and the notes beside tells what should have been there.
- The files with invalid names show the sync icon instead of the yellow warning triangle. The client shows them with the "i" icon in the Errors section with status file ignored or excluded.
fill2.binshows the sync icon instead of the red error icon. The client shows it with the "x" icon in the Errors section with status blacklisted.
Logs
No response
Client version number
ownCloud 7.2.0.19922-rc.3 584b08
Libraries Qt 6.8.3, OpenSSL 3.4.5 7 Apr 2026
Using virtual files plugin: wincfapi
OS: windows-10.0.26200 (build arch: x86_64, CPU arch: x86_64)
QPA: windows
Desktop environment (Linux only)
No response
Client package version and origin (Linux only)
No response
Installation path (Windows only)
C:\Program Files\ownCloud
Server information
Server: ownCloud Infinite Scale (oCIS)
Server version: 8.2.0
Web UI: ownCloud Web UI 12.5.0
Server execution: Running in Docker (docker compose) on Ubuntu 24.04.5 LTS, using the image owncloud/ocis:8.2.0
Additional context
The test case describes uploading files and folders with path longer than 255 characters causes error when syncing. But that does not cause an error, even when long paths are disabled in Windows. The file syncs and shows the green tick.
- Lenguaje dominante
- C++
- Estrellas
- 1.5k
- Forks
- 695
- Merge medio
- 8 d 7 h
- PR fusionados (30 d)
- 6
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de owncloud/client
-
Add Ubuntu 26.04 LTS packagesAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
-
Account removal silently keeps the local sync folder, so re-adding creates ownCloud (2), (3), …Posiblemente ocupada @Eiji-Kondo la tomó hace 8 días. Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 58/100
Los mantenedores suelen responder en 1 día
Todos los issues de owncloud/client
Issues similares
-
needs-format
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Niko1221/Strata#6251 · 1 comentario ·
Los mantenedores suelen responder en 5 días
-
[Bug]: NP 管理器文件编辑器里删除键无效Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
metasequoiaime/msime#11666 ·
Los mantenedores suelen responder en 1 día
-
DAE2 crashes on call.without.effects with a non ref.func expressionPosiblemente ocupada @stevenfontanella la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
WebAssembly/binaryen#9404 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 65/100
CodeZombie/goodluckOS#178 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
CVO-Org/immersive-cigs-rewrite#313 ·
Los mantenedores suelen responder en 1 día