nextcloud / nextcloud/talk-desktop

After standby the app cant establish a call / WINDOWS 11

Open
#1,397 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs info needs triage
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

  1. Have Talk running, stop using it and close it to its minimized in the Taskbar
  2. Go in Standby and let 1 day pass
  3. Next day open Talk and try to resume a call.
Expected behaviour

Establish the call

Actual behaviour

After opening Talk i see my last used chat. I click start call. The call rings, the other party answers, the calls drops and reconnects. Reconnection repeats, no call can be established.

CTRL Shift L didn't provide any logs. Shortcut seems to not function.

Only after a closing the app completely (clearing from ram) and opening it it would work as expected.
I think there might be a session issue after a longer break. If the app would simply force refresh if sessions timed out it might be solved. The server side works fine.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Windows 11 sequence: leave Talk minimized through standby for a day, then try to resume a call without fully closing the app. Trace the call and session handling after resume; done means the call establishes normally without restarting Talk, with useful diagnostics despite the reported shortcut problem.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.