nextcloud / nextcloud/files_lock
[Bug]: Editing a note from the web make it locked forever
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 10
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 48
Description
⚠️ This issue respects the following points: ⚠️
- This is not a troubleshooting question, general support matter, or webserver/proxy problem, but likely a bug (if unsure, ask the Community Help Forum).
- This issue is not already reported on Github OR solved at the Community Help Forum (I've searched!).
- I'm using a maintained major version of Nextcloud Server and tested against the latest patch level. (Supported major versions and current patch levels).
- I agree to follow Nextcloud's Code of Conduct.
- I've tried my best to provide clear reproduction steps that someone unfamiliar with this bug could use to reproduce it.
Bug description
Nextcloud 34.0.4 on opensuse leap 16.0
I have nextcloud app note in the phone and I can edit any note in the phone that I have already edited in the web browser (i have the NC dashboard as home page).
I have see that the problem is that this files are locked and the lock remains.
I have check that any note opened in the web (firefox 155.0.1) set a lock and then when i close the tab of firefox the lock remains, so the note can be edited from the phone with the nextcloud app, and can be viewed with the nexcloud notes app, but can't be saved from this last one.
Is reproducible always.
sudo -u wwwrun php /srv/www/htdocs/nextcloud/occ files:lock --status 10368
File nextcloud/server#10368 is locked by text
- Locked at: 2026-08-20T10:17:44+00:00
I have just upgraded the server but the bug was there before and still is there
Steps to reproduce
- Create a note from the web edit it, save it
- Close the browser
- Check the file lock
Expected behavior
The lock should be deleted after I finished editing the file in the browser and then the file should be capable of edit in the nextcloud notes app and saved.
Nextcloud Server version
34
Operating system
Other
PHP engine version
None
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 32.0.1 to 32.0.2)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
{
"system": {
"instanceid": "***REMOVED SENSITIVE VALUE***",
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": [
"samara.com.es"
],
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"dbtype": "mysql",
"version": "34.0.4.1",
"overwrite.cli.url": "https:\/\/mydomain.com\/nextcloud",
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbport": "",
"dbtableprefix": "oc_",
"mysql.utf8mb4": true,
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"installed": true,
"app_install_overwrite": [
"gpxedit",
"deck",
"maps",
"forms"
],
"maintenance": false,
"theme": "",
"loglevel": 2,
"memcache.locking": "\\OC\\Memcache\\Redis",
"memcache.local": "\\OC\\Memcache\\APCu",
"redis": {
"host": "***REMOVED SENSITIVE VALUE***",
"port": 6379,
"timeout": 0
},
"mail_from_address": "***REMOVED SENSITIVE VALUE***",
"mail_smtpmode": "smtp",
"mail_sendmailmode": "smtp",
"mail_domain": "***REMOVED SENSITIVE VALUE***",
"mail_smtphost": "***REMOVED SENSITIVE VALUE***",
"mail_smtpport": "465",
"default_phone_region": "ES",
"mail_smtpsecure": "ssl",
"mail_smtpauthtype": "LOGIN",
"mail_smtpauth": 1,
"mail_smtpname": "***REMOVED SENSITIVE VALUE***",
"mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
"trashbin_retention_obligation": "auto, 365",
"logtimezone": "Europe\/Paris",
"maintenance_window_start": 1,
"trusted_proxies": "***REMOVED SENSITIVE VALUE***",
"overwritehost": "samara.com.es",
"overwriteprotocol": "https",
"overwritewebroot": "\/nextcloud"
}
}
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the web note edit and browser-close steps, then check the lock with occ files:lock --status 10368. Done means the lock is removed after closing the browser and the same note can be edited and saved from the Nextcloud notes app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, javascript, mariadb, redis
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100