Closed alba4k closed 6 months ago
The problem is there on both the version from the repos and the static binary.
On the static binary, you can enable debug mode with the debugmode
cheat code. After enabling it and restarting the application, the built-in deadlock detector will be activated and will abort the application letting you to go through the crash ID routine explained when creating issue.
I did what you suggested, but nothing happens during the freeze. I suppose that might be because the application isn't 100% stuck (I can still right click the tray, although none of the options do anything. Quit closes the app, but only after a long time)
Apparently, when telegram closed from the tray that time, it just crashed. And it crashed quite badly I must say, as the next time I reopened it it asked me to log in again, and my settings were gone. No big deal, but at least that issue is fixed now. Should I close this as not planned or something?
I can still right click the tray
This menu is managed by the panel. It only does request to the application after clicking on an action.
And it crashed quite badly I must say, as the next time I reopened it it asked me to log in again, and my settings were gone.
That's quite bad, maybe there's a QSaveFile missing somewhere...
Should I close this as not planned or something?
Yeah, there's no practical reason to keep it open if it's unreproducible
I was trying to figure out why I was unable to remove the window border (use system border thing). It happened again.
The transition to system border is quite bugged in Qt on Wayland, it will get fully applied only after closing & reopening the window
@ilya-fedin The problem is this border.
I'm not sure how to get rid of it, it was never turned on in the first place
Disable all titlebar buttons for gtk: gsettings set org.gnome.desktop.wm.preferences button-layout ''
You need to have xdg-desktop-portal + xdg-desktop-portal-gtk installed as tdesktop is not a gtk application but reads the gtk setting via portal.
Not sure that did much?
It worked fine before my settings got wiped tho, so unsure why that would be different now. Also I'm not seeing a profile picture in notifications anymore (dunst)
Sorry for bothering you for this ahah, it's just really annoying
You checked the xdg-desktop-portal-gtk, what about xdg-desktop-portal though?
It's running. Didn't check as it was running before too
busctl --user call org.freedesktop.portal.Desktop /org/freedesktop/portal/desktop org.freedesktop.portal.Settings Read ss org.gnome.desktop.wm.preferences button-layout
should return exactly what tdesktop gets
Call failed: Interfaccia «org.freedesktop.portal.Settings» inesistente sull'oggetto nel percorso /org/freedesktop/portal/desktop
(Call failed: interface <...> does not exist on the object in the path /org/...)
looks like it doesn't really work... do you have portals.conf config?
nvm fixed dw, xdg-desktop-portal-hyprland wasn't starting properly. Wrote a script that restarts it after login, everything works now, thanks.
Btw, how come it was working before, even without gkt portal installed?
Using the option you circled on the screenshot likely
No, that just adds more stuff to that window border (telegram icon, name, etc)
i'll repeat myself:
The transition to system border is quite bugged in Qt on Wayland, it will get fully applied only after closing & reopening the window
in other words: check the checkbox, close the window, open Telegram again
Would be easier if telegram wasn't just freezing when tryint to start it now...
Well I guess the lesson to learn is to never run the static binary again lol (I opened it again once now to test, guess what, it reset everything again for the 3rd time)
But yeah, it was the QT frame, thanks. Misinterpreted what you said the first time.
Also, it still freeezes immediately after logging in, then crashes after a while
Ok clered everything for what I hope will be the last time, removed xdp-gtk, set everything up again.
Thanks again for the help, have a great rest of your day, I guess you deserve it ahah
Still unsure about why the static build kept fucking things up tho. Maybe the debug stuff? no idea
Steps to reproduce
Expected behaviour
The chat opens normally
Actual behaviour
The program becomes unresponsive and must be killed and reopened
Operating system
Arch Linux, up to date
Version of Telegram Desktop
4.15.0
Installation source
Static binary from official website
Crash ID
-
Logs