mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-10 01:10:09 +03:00
Delete Button Missing in Windows Desktop Client #86
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Chief7551 on GitHub.
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: ADMIN_TOKEN
Config:
Vaultwarden Build Version
1.34.1
Deployment method
Official Container Image
Custom deployment method
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: ADMIN_TOKEN
Config:
Reverse Proxy
nginx v2.10.3
Host/Server Operating System
Linux
Operating System Version
Windows 11
Clients
Desktop
Client Version
2025.6.1
Steps To Reproduce
Delete Button Missing in Windows Desktop Client
There is no delete button in view or edit mode (Just move in edit)
Expected Result
Delete Button Missing in Windows Desktop Client
There is no delete button in view or edit mode (Just move in edit)
Actual Result
Delete Button Missing in Windows Desktop Client
There is no delete button in view or edit mode (Just move in edit)
Logs
Screenshots or Videos
No response
Additional Context
@Chief7551 commented on GitHub:
Of course I have searched, why should I bother to compile all the information here. But what I have found concerns the browser extension (which I don't use). That's why I created the bug for the client.
But nice that this is simply deleted without any reference to a possible solution...
I just wanted to help fix bugs
@BlackDex commented on GitHub:
You definitely did not search! Why did you checked the boxes?
@UserX404 commented on GitHub:
https://github.com/dani-garcia/vaultwarden/issues/6007
@BlackDex commented on GitHub:
Well, there are enough discussions and issues which mention it is for all clients since v2025.6.
You can either use
:testingtagged images or wait for a new release.