Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 916899 - net-im/telegram-desktop-4.11.3: force closing when opened via desktop icon and then reduced to sidebar icon
Summary: net-im/telegram-desktop-4.11.3: force closing when opened via desktop icon an...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Esteve Varela Colominas
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-05 16:30 UTC by Marco Scardovi (scardracs)
Modified: 2023-11-11 21:29 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge-info,6.82 KB, text/plain)
2023-11-07 16:57 UTC, Marco Scardovi (scardracs)
Details
Log files (logs.tar.gz,226.55 KB, application/gzip)
2023-11-07 16:59 UTC, Marco Scardovi (scardracs)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Scardovi (scardracs) 2023-11-05 16:30:18 UTC
Hi,
I've built telegram-desktop using the qt6 and qt6-imageformats USEFLAGS and when I launch it from its icon on plasma I've facing force close and the following warn [1]. It happens when I reduce telegram at icon and happens with the latest ~ version as well as previous one. I've tried running it from terminal but I did not face any particular problem. If you have any solution it would be awesome.


[1] Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Comment 1 Marco Scardovi (scardracs) 2023-11-05 16:32:46 UTC
Passages made:

1. Open telegram desktop
2. Close it with X button (it will reduced to sidebar)
3. After some time (seems a fixed amount of time) the error appears.
4. Done. The application closes itself.
Comment 2 Esteve Varela Colominas 2023-11-05 17:58:57 UTC
Have you tried rebooting the computer?
Comment 3 Marco Scardovi (scardracs) 2023-11-05 18:21:35 UTC
(In reply to Esteve Varela Colominas from comment #2)
> Have you tried rebooting the computer?

I’ve tried multiple times without any success. I’m not sure how to do a log because when I try from terminal everything work as expected.
Comment 4 Esteve Varela Colominas 2023-11-05 18:26:58 UTC
Try using the debugmode and viewlogs cheat codes[1] to gather a log.

[1]: https://github.com/telegramdesktop/tdesktop/wiki/Cheat-Codes
Comment 5 Esteve Varela Colominas 2023-11-05 18:27:51 UTC
Also can someone edit the title of this bug to include the version (4.11.3) in the name?
Comment 6 Marco Scardovi (scardracs) 2023-11-05 18:49:26 UTC
(In reply to Esteve Varela Colominas from comment #5)
> Also can someone edit the title of this bug to include the version (4.11.3)
> in the name?

I haven’t added it because I had it on 4.11.1 too. Fixed
Comment 7 Esteve Varela Colominas 2023-11-05 19:42:25 UTC
Did you happen to try 4.10.3? That's the version I intend to stabilize
Comment 8 Marco Scardovi (scardracs) 2023-11-05 19:46:55 UTC
(In reply to Esteve Varela Colominas from comment #7)
> Did you happen to try 4.10.3? That's the version I intend to stabilize

I haven’t tried it because I’ve started with version 4.11.x
Comment 9 Esteve Varela Colominas 2023-11-05 20:24:40 UTC
Upload your `emerge --info '=net-im/telegram-desktop-4.11.3'` and whatever logs you gather as per comment #4 . depending on what these show I might ask to report this upstream.
Comment 10 Marco Scardovi (scardracs) 2023-11-05 20:45:58 UTC
I've deleted .local/share/TelegramDesktop (by mistake) and now everything work as expected. I'm closing it
Comment 11 Marco Scardovi (scardracs) 2023-11-07 16:57:10 UTC
Nevermind Esteve. I open it again because it happened again. This time I post all the logs I've collected
Comment 12 Marco Scardovi (scardracs) 2023-11-07 16:57:53 UTC
Created attachment 874266 [details]
emerge --info
Comment 13 Marco Scardovi (scardracs) 2023-11-07 16:59:04 UTC
Created attachment 874267 [details]
Log files
Comment 14 Marco Scardovi (scardracs) 2023-11-07 17:02:45 UTC
I've noticed in dbus-monitor lots of these errors:

error time=1699376461.658175 sender=:1.12 -> destination=:1.9 error_name=org.freedesktop.portal.Error.NotFound reply_serial=431
Comment 15 Esteve Varela Colominas 2023-11-07 17:43:41 UTC
Nothing sussy in that emerge info, looks like a pretty clean install. Time to go upstream with the issue.
Comment 16 Esteve Varela Colominas 2023-11-07 17:45:57 UTC
Wait, before we do, can you try to reproduce it using the official binary, or net-im/telegram-desktop-bin?
Comment 17 Marco Scardovi (scardracs) 2023-11-07 17:50:41 UTC
(In reply to Esteve Varela Colominas from comment #16)
> Wait, before we do, can you try to reproduce it using the official binary,
> or net-im/telegram-desktop-bin?

Yep, a bi less than with telegram-desktop but yes
Comment 18 Marco Scardovi (scardracs) 2023-11-07 17:54:28 UTC
(In reply to Esteve Varela Colominas from comment #16)
> Wait, before we do, can you try to reproduce it using the official binary,
> or net-im/telegram-desktop-bin?

Before your report let me try with 4.11.5 and see if it works. I've seen the changelog and states that some fixes are made.
Comment 19 Marco Scardovi (scardracs) 2023-11-07 21:32:45 UTC
I will wait some more days but before closing but seems it's finally fixed with 4.11.5
Comment 20 Marco Scardovi (scardracs) 2023-11-11 20:24:34 UTC
Closing as it does not afftect me anymore. Thanks Esteve for your help
Comment 21 Esteve Varela Colominas 2023-11-11 21:29:39 UTC
No problem! Thanks for checking!