nextcloud / nextcloud/spreed

When no audio/video devices in the system are present, starting a call takes 2 minutes

Open
#17,494 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: WebRTC 🚡 needs info
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

[!TIP]

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. Run on computer with no mic/webcam
  2. start a conversation and click on start conference
  3. in the device selection screen you will see none for video and audio input,
  4. hitting the start conference button underneeth will freeze the ui for 2 minutes and after that "error accessing camera and mic"
  5. After those 2 minutes the conference starts and you can finally share your screen
Actual behaviour

Even more, in program settings, when using "check/verify devices" after the device menu is closed, the ui freezes for 2 minutes and after that "error accessing camera and mic"
This happens both in talk app but also in chrome and firefox on same actions.

Talk app

2.1.1
Talk app version: (see apps administration page: /index.php/settings/apps)
22.0.10
Custom Signaling server configured: yes/no and version (see Talk administration settings: /index.php/settings/admin/talk#signaling_server)
yes and shown as working in admin panel

Custom TURN server configured: yes/no (see Talk administration settings: /index.php/settings/admin/talk#turn_server)
yes and shown as working in admin panel

Custom STUN server configured: yes/no (see Talk administration settings: /index.php/settings/admin/talk#stun_server)
yes and shown as working in admin panel

Browser

test both : latest firefox and chrome

Microphone available: no

Camera available: no

Operating system: Windows

Browser name: Firefox/Chrome/Safari/...

Browser version: 124/125/...

Browser log
``` Insert your browser log here, this could for example include: a) The javascript console log b) The network log c) ... ```

Server configuration

Operating system: Ubuntu/RedHat/...
Ubuntu snap
Web server: Apache/Nginx

Database: MySQL/Maria/SQLite/PostgreSQL

PHP version: 8.1/8.2/8.3

Nextcloud Version: (see administration page)

List of activated apps:

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your server installation folder

Nextcloud configuration:

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
Server log (data/nextcloud.log)
Insert your server log here

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 call and “check/verify devices” flows on a Windows system without a microphone or camera, while collecting the browser console and network logs requested in the issue. Trace the Talk app’s device-selection and conference-start paths, including the configured signaling, TURN, and STUN services. Done means both flows avoid the two-minute UI freeze, report the missing devices promptly, and still allow screen sharing.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
audio-video-rtc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.