-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Can't record video message #28749
Comments
same issue. btw, are you using wayland? may be it is related to the problem? |
when you stop recording you can see that it captures the last frame, so actually it was recording always |
Getting the same issue using Hyprland. (You can see that OP does not use Wayland as i3 is an Xorg-only WM.) I wonder if some codecs Telegram expects are missing. |
issue still persists, using Ubuntu |
Issue still persists, using ArchLinux/Hyprland |
reproducible on archlinux/qtile/wayland |
Same, reproduced on Linux Mint 22.1 Xia with x11 as the display server. The problem still persists on version 5.10.5. |
Same. Manjaro+KDE(Wayland) |
The Issue still persists on Ubuntu |
Same, arch/hyprland |
Same: |
reproducible on archlinux+wayland+sway |
same: |
Steps to reproduce
telegram-desktop
Expected behaviour
Telegram will record the video message
Actual behaviour
Telegram captured the first frame (it can be seen behind blur). stopped recording and after 2 seconds exits the recording screen with the error message "Could not start audio recording. Please check your microphone". But audio messages are recorded correctly.
After about 0,5s from start recording "drag to lock" freezes too, and you can only stop the recording.
I tried to launch "telegram-desktop -debug" through term and saw multiple "QWidget::repaint: Recursive repaint detected" after recording screen exited with error.
By the way in settings both webcamera and microphone works properly.
Operating system
Arch linux. WM: i3 (4.24)
Version of Telegram Desktop
5.9
Installation source
Static binary from official website
Crash ID
No response
Logs
The text was updated successfully, but these errors were encountered: