tdesktop
tdesktop copied to clipboard
Bot WebView don't working
Steps to reproduce
- Try to open any bot webview
Expected behaviour
Working bot Web App
Actual behaviour
(null) in WebView and errors in logs
Operating system
Arch Linux, linux-lqx 5.17.5, KDE Plasma 5.24.5
Version of Telegram Desktop
3.7.3
Installation source
Static binary from official website
Logs
**
GLib-GIO:ERROR:../glib/gio/gsocketclient.c:1982:g_socket_client_enumerator_callback: assertion failed: (data->error_info->best_error)
Bail out! GLib-GIO:ERROR:../glib/gio/gsocketclient.c:1982:g_socket_client_enumerator_callback: assertion failed: (data->error_info->best_error)
**
GLib-GIO:ERROR:../glib/gio/gsocketclient.c:1982:g_socket_client_enumerator_callback: assertion failed: (data->error_info->best_error)
Bail out! GLib-GIO:ERROR:../glib/gio/gsocketclient.c:1982:g_socket_client_enumerator_callback: assertion failed: (data->error_info->best_error)
enable beta restart telegram and post crash id on next restart
Linux polosatyi 5.15.35-xanmod1-1 #1 SMP Fri, 22 Apr 2022 10:06:56 +0000 x86_64 GNU/Linux
Report Tag: 3a3d6409-f95f-44a8-ddbb288b-f6a536b2
What I asked is to replace the useless kernel version string with useful info like asked by the issue template (operating system name, version and desktop environment), not "Linux".
And please notify when you fix the info as github doesn't notify when you edit messages. Thanks.
I changed "Operating System" in description
Googling for the error on your screenshot, I found this. Can you confirm you don't have an IPv6 proxy set anywhere?
I've checked my proxy settings in every place I know of, they're all off.
nmcli:
gsettings:
Environment Variables:
It seems you have got some bug in glib. All I can suggest is to ensure the URL you pass to the webview can't be treated as invalid by glib (i.e. try a completely another URL). If that doesn't help, try another distro with another glib version. If nothing helps, the only thing you can is to report the bug to glib apparently. Or switch to another OS.
Hey there!
This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.
Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!