-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wallet WebApp bot not working on GNOME 45.2 #27251
Comments
Yeah, it looks like webkitgtk has lost compatibility with QtWaylandCompositor in one of recent webkitgtk updates so apparently it won't work on Wayland anymore (in case of GNOME on X11 as well). |
This is not a solution to the problem, but only a statement. But that's good too |
Yeah, there's sadly no solution. Maybe web bots should be disabled on Linux... |
Ideally the cross-platform API abstraction should get API to signal that the webview has crashed so the window could display a text for that instead of just being empty. Once the API is made, it should be connected to the platform code here, with an intermediate here or there. After that the API users (1, 2) just have to listen to the signal and display the text. By signal I mean not a Qt signal (they're discouraged in tdesktop codebase) but a rpl::producer or a function to set a handler like already existing ones in the class. Sadly I haven't got anywhere in discusstions with @john-preston about the API, apparently he is too busy... |
I tried to craft something based on the pre-existing widget destruction signal, it won't work with X11 but will with Wayland where most crashes seem to happen |
Steps to reproduce
Install Wayland, Gnome shell
pacman -S telegram-desktop
1.Start Telegram-Desktop. Open wallet
2.Waiting...Waiting...Waiting!?!
Expected behaviour
View menu of Wallet like at on my phone?
Actual behaviour
Infinity loading
WebAppError.mp4
Operating system
Arch Linux | Wayland | Shell Gnome 45.2
Version of Telegram Desktop
4.12.2
Installation source
Other (unofficial) source
Crash ID
No response
Logs
The text was updated successfully, but these errors were encountered: