> Segmentation fault (core dumped)

This is a woefully inadequate bug report. Please review the guidelines [1] to ensure your bug reports are effective.

At the bare minimum, you'll need to provide a backtrace with debug symbols [2]. It's usually as simple as:

$ coredumpctl gdb (then answer y when it asks "Enable debuginfod for this session?")
(gdb) set logging enabled
(gdb) bt (or bt full)

Then post gdb.txt

[1] https://wiki.archlinux.org/title/Bug_reporting_guidelines
[2] https://wiki.archlinux.org/title/Debugging/Getting_traces

Hi, I've encountered the same issue, I've tried what you said, with "answer y when it asks "Enable debuginfod for this session", but it happens that it takes more than 32GB of ram... I've tried with answering no, and I got this https://0x0.st/HQt2.txt

for some reason this is impossible to debug, as obtaining the trace the way @toolybird suggested makes everything crash in a reasonably recent machine (it used up all my RAM and swap and ultimately crashed the terminal altogether). telegram-desktop -debug only points to one

attaching a few debug logs.

https://0x0.st/HQYw.txt
https://0x0.st/HQY3.txt
https://0x0.st/HQYY.txt

telegram-desktop-bin works, FYI. i also tried downgrading telegram-desktop a few versions but it still crashes.

Not sure why debuginfod is exhausting all memory (I've also seen this in the past myself). But luckily there are other ways to get a backtrace with debug symbols as documented in link [2] above e.g. manually install some relevant *-debug pkgs.

Anyway, we *still* have no info about when this crash happens. Do you think we are mind readers?

Can you reproduce easily? What steps to reproduce? What other relevant circumstances? What DE in use? Wayland? Are you using a proxy? Does it still crash if you don't use a proxy? etc, etc, etc. Please provide as much relevant info as possible otherwise you are *not* helping.

GNOME Wayland, I don't using any proxy.

> GNOME Wayland, I don't using any proxy.

Still too brief. Are we playing 20 questions? Hint: "Steps to reproduce:"

To reproduce just run:
$ telegram-desktop

> To reproduce just run

Cannot repro, i.e. works for me. Anyone affected by this bug will need to supply better quality information. Otherwise we cannot help, it's that simple. I'll remind folks again about the Arch bug guidelines [1] (when the Wiki comes back online :)

[1] https://wiki.archlinux.org/title/Bug_reporting_guidelines

being rude to people doesn't help anyone. debug symbols fetched whichever way (via telegram-desktop-debug or debuginfod) exhaust all the ram and gdb crashes.

anyway, more info:

1. crashes on startup before even displaying the list of users
2. gnome wayland/x11, doesn't really matter (network config doesn't seem to matter either)
3. i can't reproduce it on my pc with a nvidia gpu. my laptop has an intel gpu and before crashing i see this message a few times. not sure if it's related:

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

is there any dependency one could try to downgrade to see if anything changes?

Looks similar to https://bbs.archlinux.org/viewtopic.php?id=286789 with points to a libproxy bug

Step to reproduce : run telegram-desktop
Desktop env : Gnome Desktop with gnome-shell 44.2
Windowing system : X11
Kernel : Linux 6.1.35-1-lts
Graphic card : NVIDIA GeForce RTX™ 2060, using nvidia-lts 1:535.54.03-3 drivers.
Processor : AMD Ryzen™ 7 5700G with Radeon™ Graphics × 16

@arojas: bingo. downgrading libproxy to 0.4.18 works.

also, interesting, switching from "use system proxy settings" to "disable proxy" on telegram-desktop, while using libproxy 0.4.18, and then upgrading libproxy, telegram stops crashing.

as a side note, the system proxy settings are set to manual with no proxy enabled, so clearly there's something wrong there.

What if you use libproxy built with with the patch from the thread arojas linked? I have provided such a package linked below

https://drive.google.com/file/d/1LBP-KfXG_xGLiJcQFdgJO6F5jyvINu4A/view?usp=sharing libproxy-0.5.2-1.1-x86_64.pkg.tar.zst

Confirmed: With GNOME's proxy settings enabled and set to auto (which should result in no proxy here), Running `proxy udp:` crashes.

it works! telegram still freezes and won't connect if i click on "use system proxy settings" but at least it doesn't crash.

thinking that the freeze is probably a bug that should be reported upstream to telegram, thoughts?