Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Office unlock problem when server is unreachable #7415

Open
5 of 8 tasks
Mika-6-9 opened this issue Oct 25, 2024 · 0 comments
Open
5 of 8 tasks

[Bug]: Office unlock problem when server is unreachable #7415

Mika-6-9 opened this issue Oct 25, 2024 · 0 comments

Comments

@Mika-6-9
Copy link

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

Bug description

Problem 1 :
When you close an office file, the file locking process begins.
If the server is not able to be reached (restart of server processes, internet access problem, ...) a message appears indicating that the file could not be unlocked (Problem 2 : no focus on the message window, we can miss the information).
When the server is reachable again, the file(s) are not unlocked.

Steps to reproduce

  1. Close Office file
  2. Have a connection problem (internet, server, ...) just before (or during)

Expected behavior

Problem 1 : When the server becomes reachable again, the file(s) are unlocked (memorization of actions?)

Problem 2 : Bring the warning window to the front (focus)

Which files are affected by this bug

Office files

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Official Linux AppImage

Nextcloud Server version

29.0.8

Nextcloud Desktop Client version

3.12.8 & latest

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

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant