FS#62175 - [telegram-desktop] Voice messages not playing

Attached to Project: Community Packages
Opened by Alessio (spidernet) - Thursday, 28 March 2019, 16:09 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 03 September 2019, 23:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Jiachen Yang (farseerfc)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
Telegram is unable to play voice messages. Executing it from the terminal gives me this error:
```
[ogg @ 0x7efe30000900] 737 bytes of comment header remain
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
[ogg @ 0x7efe30000900] Packet processing failed: Invalid data found when processing input.
```
which might indicate that ffmpeg can't read the file.

The bug has already been reported upstream by another user, but since the binary from https://desktop.telegram.org/ works, I'm reporting it here too.

Additional info:
* community/telegram-desktop from 1.6.0-1 to 1.6.3-1 (latest)
* extra/ffmpeg 1:4.1.2-1 (latest)
* log file is attached, relevant error is at line 242.
* using the binary from https://desktop.telegram.org/ works as expected.
* link to upstream bug report: https://github.com/telegramdesktop/tdesktop/issues/5843

Steps to reproduce:
* Open telegram-desktop
* play voice message
   log_08_45.txt (42.9 KiB)
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 03 September 2019, 23:46 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed by upstream in the iOS update. Old voice messages will be forever lost, however.
Comment by Lev Lybin (lybin) - Monday, 15 April 2019, 14:47 GMT
1.6.7 works again..
Comment by Alessio (spidernet) - Monday, 15 April 2019, 15:02 GMT
It still doesn't work for me.

EDIT: I've also found that this only happens with audio messages that has been sent from an iPhone.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 15 April 2019, 15:56 GMT
Getting mixed signals here. Can you guys post the media info for a voice message that works without one that doesn't? That might allow us to track it down to a specific ffmpeg commit perhaps.
Comment by Alessio (spidernet) - Monday, 15 April 2019, 16:45 GMT
Sure, I'll attach the output of `mediainfo` and `ffplay` for a working audio and for a non working one. Keep in mind that downloading it as an .ogg and playing it works (even the one that doesn't work inside telegram).

Working mediainfo (https://pastebin.com/zMMabCuB), output of ffplay (https://pastebin.com/MQUv6WTB)

Non working mediainfo (https://pastebin.com/9c0xC09t), output of ffplay (https://pastebin.com/a6LS2m1i)
Comment by Lev Lybin (lybin) - Tuesday, 16 April 2019, 06:46 GMT
Sorry, still works not fully correct. I can hear only first seconds... first time this behavior..
Comment by Javier Fernández (WyRe) - Wednesday, 05 June 2019, 17:22 GMT
I'm exactly having this issue, I'm going to try AUR package.
Comment by 0 none (0none) - Monday, 05 August 2019, 15:07 GMT
For me this happens only with voice messages sent from iPhones.
Every other voice message plays normally.
Also this doesn't happen with the official binaries for me.
Comment by Riccardo Torre (lalincedeldeserto) - Saturday, 31 August 2019, 14:23 GMT
Yes, I can confirm that this happens when I try to play voice messages sent from iPhones, as 0none said.

This happens in version 1.8.2
Comment by Lev Lybin (lybin) - Saturday, 31 August 2019, 14:27 GMT
As far as I know bug was in telegram IOS, new ffmpeg version(also in archlinux) can't decode misformed audio. All old audio will be defected forever.

Loading...