Bug: Call duration timer starts with negative values before counting up normally
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
When joining a Nextcloud Talk call, the call duration timer initially starts with negative values (for example -1:-1:-33) before it begins counting upwards normally.
The issue is reproducible and occurs for all participants in the call, not just a single client.
The negative values disappear after a short time, and the timer continues counting up correctly. The call itself is not affected (audio, video and screen sharing work normally).
Steps to reproduce
- Start a new Nextcloud Talk call.
- Join the call with one or more participants.
- Observe the call duration displayed in the top bar.
Expected behavior
The call duration should start at 00:00:00 (or 00:00) and count upwards immediately.
Actual behavior
The timer starts with negative values such as:
-1:-1:-33
After a few seconds it automatically switches to a normal increasing timer.
Environment
- Nextcloud Hub 26 (34.0.1)
- Talk 24.0.2
- High Performance Backend (HPB) configured and working
- Docker deployment
- Reverse proxy: Nginx Proxy Manager
- Cloudflare Tunnel
- Ubuntu Server 24.04 LTS
Additional information
- The issue is visible for every participant in the call.
- The timer eventually corrects itself without any user interaction.
- Audio, video, screen sharing and messaging work correctly.
- Server time is synchronized correctly.
- No related errors are visible in the browser console or server logs.
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
Reproduce the issue by joining a Nextcloud Talk call and observing the duration in the top bar. Trace the frontend call-duration timer and its initial time value; done means every participant sees 00:00:00 or 00:00 immediately, with no negative values, while the timer continues counting normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100