Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start recording, getting a number of errors #43

Open
pomtom44 opened this issue Mar 2, 2022 · 6 comments
Open

Unable to start recording, getting a number of errors #43

pomtom44 opened this issue Mar 2, 2022 · 6 comments

Comments

@pomtom44
Copy link

pomtom44 commented Mar 2, 2022

General Description

Followed the install instructions, and have the nextcloud instance talking to the talked instance
(hosted on same server)
however when running /recording start
getting a few errors about pulse audio and x11

Operating System

ubuntu 20.04.03 LTS Server
Running on a hyperV VM (not sure if relevent or not?)

Logs

log output here
https://pastebin.com/FZVzA6FJ

Talked Version

not sure of version?
installed today following the install instructions on home page

@mwalbeck
Copy link
Collaborator

mwalbeck commented Mar 3, 2022

Hi, can you try setting the log level in the config.toml file to "info" and then try running it again? And in the /opt/talked folder there should be a geckodriver.log file, if you could post the contents of that as well, then that would be great!

@pomtom44
Copy link
Author

pomtom44 commented Mar 3, 2022

Heres the output of the log file with Info enabled
https://pastebin.com/BFHq5T2J

and heres the gecko log
https://pastebin.com/F7T3qndz

@mwalbeck
Copy link
Collaborator

mwalbeck commented Mar 5, 2022

Hey, a quick question, how is your talk setup? Barebones, with a TURN server or with the Talk HPB backend?

@pomtom44
Copy link
Author

pomtom44 commented Mar 5, 2022

I dont think im running either?
Im just running whatever is part of the default nextcloud install

@mwalbeck
Copy link
Collaborator

mwalbeck commented Mar 8, 2022

I think the biggest blocker for you is the same as in this issue currently #42 so my last reply also applies here #42 (comment)

The error messages from Pulseaudio are currently expected, so they are the reason why it isn't working.

@mwalbeck
Copy link
Collaborator

The issue you experienced may have been caused by something completely different from what I thought. I have created a new release, v0.3.2, that hopefully resolves your issue as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants