Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 814176 - net-im/telegram-desktop-bin-3.1.0 window size is not saved
Summary: net-im/telegram-desktop-bin-3.1.0 window size is not saved
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-21 13:20 UTC by bagas
Modified: 2021-09-22 20:24 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bagas 2021-09-21 13:20:49 UTC
Hello.
After rebooting the system, the telegram window is opened on the half-screen of the monitor.
I have to manually reduce the size of the telegram window each time.
There were no such errors in the version of telegrams 2.9+.
The packages are up-to-date in the system.

How to remember the position and size of the telegram application window?

My system.
Linux 5.10.61-gentoo x86_64
xfce4 4.16.0

Install.
[ebuild   R   ~] net-im/telegram-desktop-bin-3.1.0::gentoo  0 KiB

Reproducible: Always
Comment 1 bagas 2021-09-21 13:42:33 UTC
By the method of scientific poking, I found what the mistake.
In telegram settings -> advanced settings -> System integration: Window system frame.

I am using telegram without system window frame.
If you specify to use the system window frame and reboot, the position and size of the window is preserved.
Even if after removing the parameter in the telegrams the system frame of the window, after the restart, the position and size of the window are saved.
Here's a bug.
Comment 2 Jonas Stein gentoo-dev 2021-09-22 20:24:04 UTC
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3].
I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4].
Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product.

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/