-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Problems running over waypipe #277
Comments
I'm afraid you'll have to dig yourself, I doubt a lot of people will run into this. It looks related to WebkitGTK and sandbox. I suggest trying to reproduce with GNOME Web (flatpak) |
Thanks, that is a good idea. I'll try that and report back if I find something out. |
You were right, the problem is the same with gnome-web:
|
I think your best chance is to report the issue to waypipe. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please include (to the best of your knowledge) the following information:
Debugging Information
WebKitGTK 2.40.1
GJS 1.76.0
Adw 1.3.2
GTK 4.10.3
GLib 2.76.2
libsoup 3.4.1
GStreamer 1.20.6
Flatpak version
flatpak --version
Flatpak 1.10.8
Operating System
PureOS Byzantium (Debian Bullseye)
Desktop Environment
Notebook: Gnome 3.38.5 wayland, gnome-shell 3.38.6
→waypipe -n ssh -R /tmp/socket-way:/tmp/socket-l5 Librem5
→Librem5: Gnome 3.38.5 wayland, Phosh 0.27.0
waypipe 0.8.6 (commit 033d0e7eb613f1ddfe104d07079a81b8d4e02dac)
I connected (actually to debug some other issue 🤦) from my notebook through ssh to my Librem5 phone using waypipe to get the tangram window from the phone on my notebook.
Problem
Starting Tangram everything seems to be normal and I get the following messages on the command line:
Tangrams window shows up on my notebook (forwarded over waypipe/ssh from the phone I logged into via ssh):
Clicking the
Go
button gives me the following message on the console:And the gui output looks like this:
Each time I enter a new address and click on
Add
the error message(process:2): Gtk-WARNING **: 14:48:35.776: Failed to open display
is repeated and I end up with the same window content.The text was updated successfully, but these errors were encountered: