From: dm17 <dm17@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] telegram-desktop-4.14.2 segfault on start
Date: Wed, 03 Jan 2024 22:38:13 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48056@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
New issue by dm17 on void-packages repository
https://github.com/void-linux/void-packages/issues/48056
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.9_1 x86_64-musl GenuineIntel uptodate rFFFFF
### Package(s) Affected
telegram-desktop
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
running telegram-desktop runs the application as it has without fail for as long as I can remember
### Actual behaviour
running telegram-desktop immediately segfaults
### Steps to reproduce
I've installed telegram-desktop-dbg as well, and I see the following with gdb:
1) run `gdb telegram-desktop`
2) type `run` -> `Starting program: /usr/bin/telegram-desktop`
3) see debug output:
```Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7fbb98c in scan_trans (alt=<synthetic pointer>, local=1, t=-9223372014364800) at src/time/__tz.c:280
warning: 280 src/time/__tz.c: No such file or directory```
next reply other threads:[~2024-01-03 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 21:38 dm17 [this message]
2024-01-03 21:52 ` classabbyamp
2024-01-03 21:53 ` Johnnynator
2024-01-03 21:53 ` classabbyamp
2024-01-03 21:59 ` dm17
2024-01-03 22:55 ` Johnnynator
2024-01-07 12:10 ` Johnnynator
2024-01-07 12:10 ` [ISSUE] [CLOSED] " Johnnynator
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48056@inbox.vuxu.org \
--to=dm17@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).