FS#60198 - [telegram-desktop] GNOME session crashes when dealing with image attachments

Attached to Project: Community Packages
Opened by Luca Franceschini (LucaFranceschini) - Wednesday, 26 September 2018, 09:35 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 01 January 2019, 19:03 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Telegram makes my GNOME session crash when dealing with (image) attachments. First it happened randomly, then I was able to "reproduce" it by messing with images: opening them, forwarding them, attaching them, until the screen went black, my session terminated and the GDM login screen was presented. My session was lost.

Unfortunately I am still not able to exactly pinpoint a (sequence of) event consistently triggering it. Log in attach.

I don't know whether it is a telegram bug or a GNOME one, but so far it only happened with telegram, and only when performing described actions.


Additional info:
* telegram-desktop 1.3.14-1
* gnome-shell 3.30.0+37+g969eecb88-1
* relevant portion of journalctl output attached


Steps to reproduce: use telegram features related to image attachments.
   telegram log.txt (12.4 KiB)
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 01 January 2019, 19:03 GMT
Reason for closing:  No response
Additional comments about closing:  Reopen if you manage to figure out which flags to change in which package. I don't think this is a problem of telegram-desktop with the information provided.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 01 October 2018, 17:12 GMT
Well, gnome should definitely NOT crash even if applications are misbehaved. Report this upstream and post the bug here.
Comment by Luca Franceschini (LucaFranceschini) - Wednesday, 03 October 2018, 14:16 GMT
Here: https://gitlab.gnome.org/GNOME/mutter/issues/329
I also added a way to consistently reproduce the issue (at least on my system).
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 03 October 2018, 16:15 GMT
I'll track this here for some time but honestly, I can't do much at all about this. Stuff crashing usually is not related to how we package things.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 10 December 2018, 22:55 GMT
Does this still occur?
Comment by Luca Franceschini (LucaFranceschini) - Tuesday, 11 December 2018, 08:36 GMT
Yep, the same procedure I describe in the bug report upstream still causes the crash. Didn't get much attention upstream, I'll rebuild mutter with debug symbols, post a new core dump there and see if it helps.
Comment by Luca Franceschini (LucaFranceschini) - Thursday, 13 December 2018, 08:45 GMT
Fun fact: can't reproduce after recompiling mutter through ABS with the debug option...
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 13 December 2018, 10:04 GMT
That could mean that the crashes are compiler option related in mutter. You could try various -O flags and see whether it still crashes.

Loading...