Skip to content
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

Closed
kaiyga opened this issue Dec 22, 2023 · 6 comments · Fixed by desktop-app/patches#169
Closed

Wallet WebApp bot not working on GNOME 45.2 #27251

kaiyga opened this issue Dec 22, 2023 · 6 comments · Fixed by desktop-app/patches#169
Labels

Comments

@kaiyga
Copy link

kaiyga commented Dec 22, 2023

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

Screenshot from 2023-12-19 05-06-07

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

qt.svg: Error while inflating gzip file: SVG format check failed
unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor is running

(telegram-desktop:62942): GLib-GIO-WARNING **: 18:51:14.598: Your application does not implement g_application_activate() and has no handlers connected to the 'activate' signal.  It should do one of these.

(telegram-desktop:62942): Gtk-WARNING **: 18:51:14.767: Theme parser error: gtk.css:7791:21-28: Expected a valid color.

(telegram-desktop:62942): Gtk-WARNING **: 18:51:14.767: Theme parser error: gtk.css:7796:21-28: Expected a valid color.

(telegram-desktop:62942): Gtk-WARNING **: 18:51:14.767: Theme parser error: gtk.css:7814:21-28: Expected a valid color.

(telegram-desktop:62942): Gtk-WARNING **: 18:51:14.767: Theme parser error: gtk.css:7820:21-28: Expected a valid color.

(telegram-desktop:62942): Gtk-WARNING **: 18:51:14.801: Theme parser error: gtk.css:7791:21-28: Expected a valid color.

(telegram-desktop:62942): Gtk-WARNING **: 18:51:14.801: Theme parser error: gtk.css:7796:21-28: Expected a valid color.

(telegram-desktop:62942): Gtk-WARNING **: 18:51:14.801: Theme parser error: gtk.css:7814:21-28: Expected a valid color.

(telegram-desktop:62942): Gtk-WARNING **: 18:51:14.801: Theme parser error: gtk.css:7820:21-28: Expected a valid color.
error in client communication (pid 62942)
Gdk-Message: 18:51:14.927: Error 71 (Protocol error) dispatching to Wayland display.
@kaiyga kaiyga added the bug label Dec 22, 2023
@ilya-fedin
Copy link
Contributor

ilya-fedin commented Dec 22, 2023

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).

@kaiyga
Copy link
Author

kaiyga commented Dec 22, 2023

This is not a solution to the problem, but only a statement. But that's good too
Thanks

@ilya-fedin
Copy link
Contributor

Yeah, there's sadly no solution. Maybe web bots should be disabled on Linux...

@ilya-fedin
Copy link
Contributor

@Aokromes i guess it's not really a 3rd party, tdesktop has to acknowledge this by disabling or removing the non-working implementation. Maybe also add this to #25126 so someone would help to report this to Qt or webkitgtk...

@ilya-fedin
Copy link
Contributor

ilya-fedin commented Dec 22, 2023

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...

@ilya-fedin
Copy link
Contributor

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants