"Syncing" and "Up to date" status icons are simultaneously displayed in Linux

Abierto
#12,680 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, linux
Área
desktop

Línea de trabajo

Start by checking how the desktop client supplies sync status icons to Nautilus and how those statuses are updated during file operations. The report gives four scenarios to reproduce, including renaming a folder after moving files and reconnecting after offline changes; compare the displayed icons with the client's current sync state. Done means each item shows only the icon appropriate to its current state across the reported scenarios.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

[DC-424]

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

The ownCloud desktop client's sync-status icons in Nautilus sometimes display two status icons simultaneously for the same file or folder: the syncing icon and the up-to-date (synced) icon.

This makes the synchronisation status unclear, as the same item appears to be both actively synchronising and already synchronised.

The issue has been observed on both Fedora and Ubuntu. I have not been able to reproduce it on Windows.

The behaviour has been observed in several scenarios:

Scenario 1 - When moving a file and immediately renaming its destination folder, both icons sometimes appear.
Scenario 2 - When another member of a shared space renames a shared file, both status icons sometimes appear for the affected item.
Scenario 3 - When trying manage sub-folder sync
Scenario 4 - Reconnecting to the Internet after making changes while offline

The issue is occurring at irregular intervals rather than continuously and has been observed across these different operations.

Expected behavior

Each file or folder should display the appropriate sync-status icon for its current synchronisation state.
The syncing and up-to-date icons should not appear simultaneously for the same item.

Steps to reproduce the issue
Scenario 1: Renaming a folder immediately after moving files into it
  1. Ensure that the ownCloud desktop client is running and the local synchronised folder is fully synced.
  2. Open the local synchronised folder.
  3. Create a new folder.
  4. Move a few existing files into the newly created folder.
  5. Immediately rename the folder after moving the files.
  6. Observe the sync-status icons displayed in the contents of the renamed folder in the file manager.
  7. Check whether both the "Syncing" and "Up to date" icons appear simultaneously.
Scenario 2: A Space member renames a shared file
  1. Log in to the ownCloud web interface as an administrator.
  2. Create a new Space.
  3. Add another user as a Space member (Example: Katherine) and grant them Can Edit permissions.
  4. Add the Space to the respective users' ownCloud desktop clients.
  5. Ensure that the Space is available and synchronised on the desktop clients.
  6. Log in to the desktop client as the Space member Katherine
  7. Navigate to the shared Space and rename an existing file.
  8. Observe the sync-status icon displayed on the renamed file in the file manager.
  9. Check whether both the "Syncing" and "Up to date" icons appear simultaneously.
Scenario 3: When trying manage sub-folder sync
  1. Open Manage Subfolder Sync.
  2. Under Deselect remote folders..., deselect all remote folders and save the changes.
  3. Open Manage Subfolder Sync again.
  4. Under Deselect remote folders..., select any previously deselected folder and save the changes.
  5. Open the re-enabled folder in the file manager.
  6. Observe the sync status icons displayed for the files inside the folder while synchronization is in progress.
Scenario 4: Reconnecting to the Internet after making changes while offline
  1. Add an ownCloud account to the ownCloud desktop client on Fedora.
  2. Ensure that the account is connected and the local synchronised folder is available.
  3. Disconnect the Fedora machine from the Internet to simulate an offline state.
  4. While the Fedora client is offline, log in to the ownCloud web interface from another machine.
  5. Upload a folder named "newFedoraTest" containing a few files to the server.
  6. On the Fedora machine, navigate to the local synchronised folder.
  7. Create another folder with the same name "newFedoraTest"
  8. Add different files to this locally created folder.
  9. Reconnect the Fedora machine to the Internet.
  10. Wait for the ownCloud desktop client to reconnect and begin synchronisation.
  11. During synchronisation, observe the status icons displayed on the content of the affected folder in the local file manager.
Screenshots
Actual Behaviour

Both the syncing and up-to-date status icons are displayed simultaneously on the same file or folder in Nautilus.
This occurs in different situations involving folder synchronisation, file operations, shared-folder changes, and offline synchronisation.

On Ubuntu

Scenario 1: When we try to rename a folder after immediately moving some files in them

https://github.com/user-attachments/assets/5d4c4915-e905-43b5-8a2e-4303a1f83550

Scenario 2: When a space member tries to rename a shared file

https://github.com/user-attachments/assets/ad5bc960-b985-4de3-814c-8ca71665a2c7

Scenario 3: When trying manage sub-folder sync

https://github.com/user-attachments/assets/09fd8886-f57e-4f6d-8135-4f653fc8ff21

On Fedora

Scenario 4: While reconnecting after Connection to Internet

https://github.com/user-attachments/assets/ce12dcc2-5ffc-4336-8232-02b3a66c89a6

Image
Logs

No response

Client version number

ownCloud desktop client: 7.2.0.19922-rc.3

Desktop environment (Linux only)

Fedora Linux 44 (Workstation Edition) with GNOME Nautilus 50.0 and Ubuntu 24.04.5 LTS with GNOME Nautilus 46.4

Client package version and origin (Linux only)

Installed Linux app image from https://download.owncloud.com/desktop/ownCloud/testing/7.2.0.19922-rc.3/linux-appimage/

Installation path (Windows only)

C:\Program Files\ownCloud

Server information

Server: ownCloud Infinite Scale (oCIS)

Server version: 8.2.0+42f7fdcfee2

Web UI: ownCloud Web UI 12.5.0

Server execution: Built from binary and running using ocis/bin/ocis server.

Additional context

Platform Comparison:

  • Fedora: Issue observed.
  • Ubuntu: Issue observed.
  • Windows: Issue not observed during testing.
Lenguaje dominante
C++
Estrellas
1.5k
Forks
695
Merge medio
8 d 7 h
PR fusionados (30 d)
6

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de owncloud/client

Todos los issues de owncloud/client

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.