Bug 230796 - net-im/linux-telegram-desktop: The program crashes when you try to send a file
Summary: net-im/linux-telegram-desktop: The program crashes when you try to send a file
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Rene Ladan
Depends on:
Reported: 2018-08-21 10:32 UTC by Roman
Modified: 2020-05-13 10:26 UTC (History)
3 users (show)

See Also:
henry.hu.sh: maintainer-feedback+

Additional info (320.45 KB, application/zip)
2018-08-21 10:32 UTC, Roman
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roman 2018-08-21 10:32:50 UTC
Created attachment 196412 [details]
Additional info

Hello! When I click on the clip icon to unzip the file, the program crashes. Judging by the dump phone, the Telegram crashes on the next call:

  48202 Telegram CALL linux_sched_setscheduler (0x18ddc, 0,0x43400d6c)
  48202 Telegram RET linux_sched_setscheduler -1 errno -1 Operation not permited

After the crash, the QFileInfoGather.crep file is created, but it is very large and the gdb does not treat it as a dump file.

Additional information is attached as an archive.

P.S. I know that I have an updated version up to 1.3.10, but with the version from the port the same story.
Comment 1 Henry Hu 2018-08-23 04:13:56 UTC
Would you please try the native version? It's just updated to 1.3.12.
Comment 2 Roman 2018-08-23 07:43:49 UTC
Thank you, I missed that the native version was updated.
Native versions work fine (at least not crashes and not noticeably obvious bugs), but in fact at the moment it's alpha version 1.3.12. However, unfortunately, the native version is released extremely rarely, when the Linux version is released quite often. And before it worked fine under linuxator without modifications, just download from the site and run (via sh script).
Comment 3 Henry Hu 2018-08-24 04:46:06 UTC
(In reply to Roman from comment #2)
I didn't notice that it's an alpha version when I updated it. Next time I'll only update to stable version. Now I have a better method to update the native version. Hopefully I'll update it more often.

On the other hand, problems in Linux version is hard to fix, and usually it's caused by problems/lack of features in the linuxulator. Thus, it would be easier to just update the native version more frequently.
Comment 4 Roman 2018-08-24 06:33:05 UTC
In any case, thank you for your response and help.
Comment 5 Walter Schwarzenfeld freebsd_triage 2019-08-28 08:45:03 UTC
Any news here?
Comment 6 Henry Hu 2019-08-28 22:01:34 UTC
As I mentioned in comment #3, the suggested workaround is to use the native version.
I've checked several linux versions, but all the ones newer than the current one cannot start. I can check the latest version, but in general it's not recommended to use the linux version.
Comment 7 Rene Ladan freebsd_committer 2020-05-12 19:30:31 UTC
Any news? Should we just remove this expired port and let people use the native version instead?
Comment 8 Henry Hu 2020-05-12 23:52:38 UTC
Yes, there's no point in keeping the linux version.
Comment 9 Rene Ladan freebsd_committer 2020-05-13 10:26:31 UTC
OK, I'll remove this Linux version.