Closed why-not-try-calmer closed 2 years ago
Logs
Go to settings, enter showlogs
blindly, it should open the directory with actual logs
Logs
Go to settings, enter
showlogs
blindly, it should open the directory with actual logs
Hello Ilya, thank you for your quick reply. I am not sure I understand. While running Telegram (flatpak), I need to go under Settings and just type "showlogs" there? I've done that but that doesn't do anything.
Are you sure you did it in settings (sometimes people confuse settings with the sidebar)? Are you sure you had english layout active when doing that?
Absolutely. But isn't there a standard path on Linux? In which case I can simply look there.
I don't believe it's the same in case of flatpak. And I don't remember where the flatpak version stores it :(
I re-checked, you should actually type viewlogs
Thank you very much for double-checking, it worked, I've updated my initial comment with the logs.
[2022.03.12 23:34:39] Audio Info: recreating audio device and reattaching the tracks [2022.03.12 23:34:45] Audio Info: Closing audio playback device.
Looks like it was playing something for 6 seconds. Maybe you just muted Telegram stream in pulseaudio settings?
That's a good guess but I don't think this is the case.
Are you stopping it manually? If you let it play longer, maybe some error will be written to the log?
I was stopping it manually, and then waiting for the file's full duration -- no change. Also I've tried switching off and back on the "play media with OpenGL", without success. There is however something interested on line 66, that reads: Streaming Error: Error in avformat_open_input (code: -1, text: Operation not allowed.)
log.txt
Maybe you're hitting #7063?
Possibly, I'll look into that, thanks for referencing that issue.
Okay the good news is that I am running into the very same issue using the official binary provided by telegram.org (Linux generic, x86_64). So the flatpak version is not the culprit. The bad news is that I have no idea how to solve this... The two obvious suspect are Wayland + Pipewire, both of which I am using. I'll report if a different combination avoids the issue.
Same issue, i get this messages through terminal
[ogg @ 0x7fc24a435000] 727 bytes of comment header remain
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Same issue, i get this messages through terminal ...
Are you using Wayland and / or Pipewire?
I am using pipewire.
El lun., 14 mar. 2022 10:54 a. m., Adrien @.***> escribió:
Same issue, i get this messages through terminal ...
Are you using Wayland and / or Pipewire?
— Reply to this email directly, view it on GitHub https://github.com/telegramdesktop/tdesktop/issues/24178#issuecomment-1066582937, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCL2RDQWBC4GYDCXCX5JCTU74EE3ANCNFSM5QRW7ZZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
I am using pipewire. El lun., 14 mar. 2022 10:54 a. m., Adrien @.> escribió: … Same issue, i get this messages through terminal ... Are you using Wayland and / or Pipewire? — Reply to this email directly, view it on GitHub <#24178 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCL2RDQWBC4GYDCXCX5JCTU74EE3ANCNFSM5QRW7ZZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.Message ID: @.>
Ah this is interesting. Might be the start of a pattern here :)
I'm using pipewire too, it was working until version 3.5.2, now I'm using version 3.6 (official statically build) and it still hits me.
There are some errors as soon as it opens:
ALSOFT_LOGLEVEL=3 .local/bin/Telegram/Telegram -debug
error: : cannot open
error: : cannot open
error: : cannot open
[ogg @ 0x7f7d58236000] 727 bytes of comment header remain
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
log.txt has:
[2022.03.14 11:13:23] Audio Info: recreating audio device and reattaching the tracks
[2022.03.14 11:13:53] Audio Error: Could not create default playback device, enumerating..
[2022.03.14 11:13:53] Audio Playback Devices: Family 17h (Models 10h-1fh) HD Audio Controller Analog Stereo
[2022.03.14 11:13:53] Audio Playback Default Device: Family 17h (Models 10h-1fh) HD Audio Controller Analog Stereo
Telegram shows up as using a sound device in either pavucontrol
or gnome sound settings
only if I go into "Call Settings" to manually set the output 🤷🏼♂️
As soon as I left this modal, it vanishes from the sound settings.
I'll repeat this, no sound at all when playing local vocal messages.
I use Telegram Desktop since 2016, never ran into such an error, never...
[2022.03.14 11:13:53] Audio Error: Could not create default playback device, enumerating..
Try to run the executable with ALSOFT_LOGLEVEL=3
[2022.03.14 11:13:53] Audio Error: Could not create default playback device, enumerating..
Try to run the executable with
ALSOFT_LOGLEVEL=3
I am getting this:
[ogg @ 0x7fe16c836000] 727 bytes of comment header remain
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
[ALSOFT] (EE) Failed to set real-time priority for thread: Opération non permise (1)
[ALSOFT] (II) Key pulse/allow-moves not found
[ALSOFT] (II) Connecting to "(default)"
[ALSOFT] (II) Key channels not found
[ALSOFT] (II) Key sample-type not found
[ALSOFT] (II) Key frequency not found
[ALSOFT] (II) Key period_size not found
[ALSOFT] (II) Key periods not found
[ALSOFT] (II) Key sources not found
[ALSOFT] (II) Key slots not found
[ALSOFT] (II) Key sends not found
[ALSOFT] (II) Key ambi-format not found
[ALSOFT] (II) Created device 0x7fe16c8d4840, "Audio interne Stéréo analogique"
[ALSOFT] (II) Key hrtf not found
[ALSOFT] (II) Pre-reset: Stereo, Float32, 44100hz, 882 / 2646 buffer
[ALSOFT] (II) Active port: analog-output-speaker (Haut-parleurs)
[ALSOFT] (II) Key pulse/allow-moves not found
[ALSOFT] (II) Key pulse/adjust-latency not found
[ALSOFT] (II) Key pulse/fix-rate not found
[ALSOFT] (II) minreq=7056, tlength=21168, prebuf=0
[ALSOFT] (II) Post-reset: Stereo, Float32, 48000hz, 882 / 2646 buffer
[ALSOFT] (II) Key stereo-mode not found
[ALSOFT] (II) Key cf_level not found
[ALSOFT] (II) Key stereo-encoding not found
[ALSOFT] (II) Stereo rendering
[ALSOFT] (II) Channel config, Main: 3, Real: 2
[ALSOFT] (II) Allocating 5 channels, 20480 bytes
[ALSOFT] (II) Enabling single-band first-order ambisonic decoder
[ALSOFT] (II) Max sources: 256 (255 + 1), effect slots: 64, sends: 2
[ALSOFT] (II) Key dither not found
[ALSOFT] (II) Key dither-depth not found
[ALSOFT] (II) Dithering disabled
[ALSOFT] (II) Key output-limiter not found
[ALSOFT] (II) Output limiter disabled
[ALSOFT] (II) Fixed device latency: 0ns
[ALSOFT] (II) Increasing allocated voices to 256
[ALSOFT] (II) Key volume-adjust not found
[ALSOFT] (II) Created context 0x7fe16c862300
I get this message using ALSOFT_LOGLEVEL=3
[ogg @ 0x7f13aae89000] 727 bytes of comment header remain Invalid return value 0 for stream protocol Invalid return value 0 for stream protocol Invalid return value 0 for stream protocol Invalid return value 0 for stream protocol [ALSOFT] (EE) Failed to set real-time priority for thread: Operación no permitida (1) [ALSOFT] (II) Key pulse/allow-moves not found [ALSOFT] (II) Connecting to "(default)" qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment [ALSOFT] (WW) Failed to open playback device: Playback Stream did not get ready (Tiempo de espera) [ALSOFT] (WW) Error generated on device (nil), code 0xa004 [ALSOFT] (II) Freeing device 0x7f13aaf5d040 [ALSOFT] (II) Got device "Audio Adapter (Unitek Y-247A) Estéreo analógico", "alsa_output.usb-C-Media_Electronics_Inc._USB_Audio_Device-00.analog-stereo" [ALSOFT] (II) Got device "Family 17h (Models 10h-1fh) HD Audio Controller Speaker + Headphones", "alsa_output.pci-0000_04_00.6.HiFi__hw_Generic_1__sink" [ALSOFT] (II) Got device "Meteor condenser microphone Estéreo analógico", "alsa_output.usb-Samson_Technologies_Samson_Meteor_Mic-00.analog-stereo" [ALSOFT] (II) Got device "Renoir Radeon High Definition Audio Controller HDMI / DisplayPort 2 Output", "alsa_output.pci-0000_04_00.1.HiFi__hw_Generic_7__sink" [ALSOFT] (II) Got device "Renoir Radeon High Definition Audio Controller HDMI / DisplayPort 1 Output", "alsa_output.pci-0000_04_00.1.HiFi__hw_Generic_3__sink
El lun, 14 mar 2022 a las 15:06, ilya-fedin @.***>) escribió:
[2022.03.14 11:13:53] Audio Error: Could not create default playback device, enumerating..
Try to run the executable with ALSOFT_LOGLEVEL=3
— Reply to this email directly, view it on GitHub https://github.com/telegramdesktop/tdesktop/issues/24178#issuecomment-1066915038, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCL2RBE3N6WSULYVQTTRYLU75IWFANCNFSM5QRW7ZZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
@why-not-try-calmer your output seems ok @0trenixjetix your audio server returns timeout error for some reason while openal tries to open playback device
[2022.03.14 11:13:53] Audio Error: Could not create default playback device, enumerating..
Try to run the executable with
ALSOFT_LOGLEVEL=3
That's exactly what I did https://github.com/telegramdesktop/tdesktop/issues/24178#issuecomment-1066855910
But somehow no debugging info is shown in any logs...
When -debug is used, tdesktop sets debug variables on its own and redirects the output from those libraries to files (primary because there's no terminal output on Windows)
I've noticed that.
That's why it has:
ls $HOME/.local/share/TelegramDesktop/DebugLogs
last_openal_log.txt log_12_45.txt log_15_30.txt log_17_45.txt mtp_12_00.txt mtp_14_45.txt mtp_17_00.txt tcp_11_15.txt tcp_14_00.txt tcp_16_15.txt tcp_18_30.txt
log_10_45.txt log_13_30.txt log_15_45.txt log_18_00.txt mtp_12_15.txt mtp_15_00.txt mtp_17_15.txt tcp_11_30.txt tcp_14_15.txt tcp_16_30.txt
log_11_00.txt log_13_45.txt log_16_00.txt log_18_15.txt mtp_12_30.txt mtp_15_15.txt mtp_17_30.txt tcp_11_45.txt tcp_14_30.txt tcp_16_45.txt
log_11_15.txt log_14_00.txt log_16_15.txt log_18_30.txt mtp_12_45.txt mtp_15_30.txt mtp_17_45.txt tcp_12_00.txt tcp_14_45.txt tcp_17_00.txt
log_11_30.txt log_14_15.txt log_16_30.txt mtp_10_45.txt mtp_13_30.txt mtp_15_45.txt mtp_18_00.txt tcp_12_15.txt tcp_15_00.txt tcp_17_15.txt
l
But last_openal_log.txt
doesn't have anything in it 😔
OpenAL writes to the log only after terminating the application for some reason
Oh, got it
Thanks!
cat DebugLogs/last_openal_log.txt
[ALSOFT] (II) Initializing library v1.21.1-01bbfd3 fix_pulse_default
[ALSOFT] (II) Supported backends: pulse, alsa, oss, null, wave
[ALSOFT] (II) Loading config /etc/openal/alsoft.conf...
[ALSOFT] (II) Loading config /etc/xdg/alsoft.conf...
[ALSOFT] (II) Loading config /home/beholder/.alsoftrc...
[ALSOFT] (II) Loading config /home/beholder/.config/alsoft.conf...
[ALSOFT] (II) Got binary: /home/beholder/.local/bin/Telegram, Telegram
[ALSOFT] (II) Loading config /home/beholder/.local/bin/Telegram/alsoft.conf...
[ALSOFT] (II) Key disable-cpu-exts not found
[ALSOFT] (II) Vendor ID: "AuthenticAMD"
[ALSOFT] (II) Name: "AMD Ryzen 7 5700U with Radeon Graphics"
[ALSOFT] (II) Extensions: +SSE +SSE2 +SSE3 +SSE4.1
[ALSOFT] (II) Key rt-prio not found
[ALSOFT] (II) Key resampler not found
[ALSOFT] (II) Key trap-al-error not found
[ALSOFT] (II) Key trap-alc-error not found
[ALSOFT] (II) Key reverb/boost not found
[ALSOFT] (II) Key drivers not found
[ALSOFT] (II) Key pulse/spawn-server not found
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
[ALSOFT] (II) Initialized backend "pulse"
[ALSOFT] (II) Added "pulse" for playback
[ALSOFT] (II) Added "pulse" for capture
[ALSOFT] (II) Key excludefx not found
[ALSOFT] (II) Key default-reverb not found
[ALSOFT] (II) Got device "JBL Endurance DIVE", "bluez_output.00_1E_7C_9F_F1_8D.a2dp-sink"
[ALSOFT] (II) Got device "Family 17h (Models 10h-1fh) HD Audio Controller Analog Stereo", "alsa_output.pci-0000_05_00.6.analog-stereo"
[ALSOFT] (II) Got device "Renoir Radeon High Definition Audio Controller Digital Stereo (HDMI 2)", "alsa_output.pci-0000_05_00.1.hdmi-stereo-extra1"
[ALSOFT] (II) Got device "Family 17h (Models 10h-1fh) HD Audio Controller Analog Stereo", "alsa_input.pci-0000_05_00.6.analog-stereo"
[ALSOFT] (II) Got device "Monitor of Family 17h (Models 10h-1fh) HD Audio Controller Analog Stereo", "alsa_output.pci-0000_05_00.6.analog-stereo.monitor"
[ALSOFT] (II) Got device "Monitor of Renoir Radeon High Definition Audio Controller Digital Stereo (HDMI 2)", "alsa_output.pci-0000_05_00.1.hdmi-stereo-extra1.monitor"
[ALSOFT] (II) Got device "Monitor of JBL Endurance DIVE", "bluez_output.00_1E_7C_9F_F1_8D.a2dp-sink.monitor"
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
[ALSOFT] (II) Key pulse/allow-moves not found
[ALSOFT] (II) Connecting to "(default)"
[ALSOFT] (WW) Failed to open playback device: Playback Stream did not get ready (Timeout)
[ALSOFT] (WW) Error generated on device (nil), code 0xa004
[ALSOFT] (II) Freeing device 0x7fa3c41bb880
[ALSOFT] (II) Got device "JBL Endurance DIVE", "bluez_output.00_1E_7C_9F_F1_8D.a2dp-sink"
[ALSOFT] (II) Got device "Family 17h (Models 10h-1fh) HD Audio Controller Analog Stereo", "alsa_output.pci-0000_05_00.6.analog-stereo"
[ALSOFT] (II) Got device "Renoir Radeon High Definition Audio Controller Digital Stereo (HDMI 2)", "alsa_output.pci-0000_05_00.1.hdmi-stereo-extra1"
Your log is just like @0trenixjetix
That's the same thing that @0trenixjetix had, the only difference is that his log is in Spanish 🙂
@ilya-fedin, we said the same thing at the same time 🙂.
Anyway, is there some solution for this?
FYI: I'm using pipewire in everything else without issues: mpd, firefox, chromium...
I don't think so, apparently pipewire broke compatibility with a part of PA APIs used by openal, but not by other applications
Well, apparently openal was some initial support to an old version of pipewire
: https://github.com/kcat/openal-soft/blob/master/CMakeLists.txt#L903
It's not in any release
It isn't... maybe we should wait for 1.22, probably
I don't think openal would release pipewire support as there's a blocker on pipewire side: there's no way to detect whether pipewire is used for audio or only for video
So reporting that compatibility bug to pipewire would be a way faster solution
Other OpenAL apps are being hit by the same issue: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2189
So reporting that compatibility bug to pipewire would be a way faster solution
so, 3rd party bug?
Seems so...
yeah
But @why-not-try-calmer doesn't seem to have such errors, so maybe his case is different
Seems like pipewire guys are cooking a solution: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2189#note_1284610
Interesting. Thanks for looking into the issue!
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2189#note_1297061
A fix is being made for Debian, Gentoo and NixOS
I opened a MR for fixing it on Exherbo Linux. No need to fix anything on Telegram nor OpenAL for now.
I opened a MR for fixing it on Exherbo Linux. No need to fix anything on Telegram nor OpenAL for now.
Wait, this issue affects user of the flatpak'ed version too, so also the runtime used by this version needs the fix -- not just Linux distributions per se.
Daemons aren't a part of flatpak runtime
Daemons aren't a part of flatpak runtime
Ah ok I didn't read it through, never mind.
Steps to reproduce
Click on the Play button associated with a vocal message.
Expected behaviour
Telegram Desktop should play the selected vocal message.
Actual behaviour
Telegram Desktop does not play the selected vocal message.
Operating system
Linux x86_64
Version of Telegram Desktop
Flatpak commit 81b1eb20b50cae7980e80dd3b1e0d2b0497917ef275217c27e0e043c51517c6a
Installation source
Flatpak
Logs