nextcloud / nextcloud/talk-desktop
App cannot be closed when there is a call
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 525
- Forks
- 85
- Avg merge
- 8h 5m
- Merged PRs (30d)
- 35
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Start a call
- Try to close an app or reload
Expected behaviour
It is possible, maybe with a warning
Actual behaviour
It is not possible, having a call blocks a page from being closed even from the system tray.
A use case - a failed call. When the server is unavailable, it is not possible to leave the call.
Diagnosis and logs
Diagnosis report
Insert a diagnosis report here.
Diagnosis report
| Nextcloud Talk Desktop | |
|---|---|
| Version | v1.0.0 |
| Built-in Talk version | v20.1.0 |
| Operating system | Windows_NT 10.0.26120 (Windows 11 Pro) |
| Executable Path | C:\Users\shgk\AppData\Local\NextcloudTalk\app-1.0.0\Nextcloud Talk.exe |
| Connected to | - |
| Nextcloud server version | 30.0.4 |
| Nextcloud Talk version | 20.1.0 |
notifications app enabled |
✅ yes |
notify_push app enabled |
✅ yes |
Application config
{
"theme": "default",
"systemTitleBar": false,
"monochromeTrayIcon": false,
"zoomFactor": 1,
"playSoundChat": "respect-dnd",
"playSoundCall": "respect-dnd",
"enableCallbox": "respect-dnd",
"playSound": "never"
}
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
No source file, test, or entry point is named. Reproduce the blocked-close behavior on Windows with an active call, then trace the desktop close and call lifecycle until the failure path is located. Done means the app can be closed or reloaded, with an appropriate warning if that is the chosen behavior, including when the server is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript
- Domain
- audio-video-rtc, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100