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

Screensharing does not work on Wayland - Ubuntu 21.10 (Possible regression) #150

Closed
baarkerlounger opened this issue Nov 4, 2021 · 7 comments

Comments

@baarkerlounger
Copy link

Using the Flathub Flatpak build of Slack (4.20.0) and Ubuntu 21.10 (Gnome 40.4, Wayland) screensharing on Slack no longer works. I believe (but haven't confirmed) this was working on Ubuntu 21.04 so this may be a regression?

Pipewire version is 0.3.32.

@WhyNotHugo
Copy link
Collaborator

WhyNotHugo commented Nov 4, 2021 via email

@cacack
Copy link

cacack commented Jan 19, 2022

I'm having the same overall issue (screen sharing not working) in a fresh install of Fedora 35 (Gnome 41, pipewire v0.3.43) using the flatpak build of Slack v4.23.0. Still orienting myself with Wayland (former XFCE user), but when in a huddle and go to share my screen, the flatpak build does pull up the screen sharing "permissions" dialog but the buttons don't do anything and the screen is never actually shared.

I'm happy to help troubleshoot and provide info as best I can, but will likely fall back to XFCE (and Xorg) soon as I need this ability for my livelyhood.

@lestephane
Copy link

Seeing how this issue seems to be ignored, I wanted to add more info, in order to clarify the requirements and command-line flags required for this to work, because the full picture is still unclear to me. Hopefully this will help others.

Basically, I'm unable to get screensharing to work on Waynlad on Ubuntu 22.04 either. The app crashes.

I used Flatseal to reset permissions to the defaults, to make sure I start from a sane base, then I tried to add ALL flags that I know of (old and new style) to use Wayland and screen-sharing, and I also added to the command-line --allow=devel to get a better crash information.

I run in my terminal:

$ /usr/bin/flatpak run --socket=wayland --allow=devel \
  --branch=stable --arch=x86_64 --command=slack com.slack.Slack -- \
    --enable-webrtc-pipewire-capturer --ozone-platform-hint=auto \
    --enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapture

And get the following output while Slack is starting up (I'm adding it here because I don't know what may be relevant to the problem at hand yet)

[2:0502/114945.928742:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Initializing local storage instance
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
Gtk-Message: 11:49:46.631: Failed to load module "canberra-gtk-module"
Gtk-Message: 11:49:46.632: Failed to load module "canberra-gtk-module"
[2:0502/114946.656388:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0502/114946.656659:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Gkr-Message: 11:49:46.689: secret service operation failed: org.freedesktop.DBus.Error.ServiceUnknown
LaunchProcess: failed to execvp:
xdg-settings
[2:0502/114946.797959:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0502/114946.798251:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0502/114946.798452:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0502/114948.016217:ERROR:bus.cc(562)] Failed to get the ownership of org.kde.StatusNotifierItem-2-1: org.freedesktop.DBus.Error.ServiceUnknown
[2:0502/114948.027626:ERROR:browser_main_loop.cc(273)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[2:0502/114948.028624:ERROR:browser_main_loop.cc(273)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[2:0502/114950.380106:ERROR:browser_main_loop.cc(273)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[50:0502/114950.396425:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[2:0502/114950.462241:ERROR:browser_main_loop.cc(273)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[2:0502/114950.463088:ERROR:browser_main_loop.cc(273)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[50:0502/114956.325911:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[50:0502/114956.329330:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!

Then I run the audio, video, and screen sharing test in Slack, and get the additional following output in the terminal

[OpenH264] this = 0x0x1ad408874fc0, Warning:Actual input framerate 0.000000 is different from framerate in setting 15.000000, suggest to use other rate control modes
[0502/115048.718442:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0502/115048.718556:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0502/115048.722433:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0502/115048.722518:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0502/115048.773371:ERROR:directory_reader_posix.cc(42)] opendir /home/lestephane/.var/app/com.slack.Slack/config/Slack/Crashpad/attachments/d443d031-8f84-453c-aeee-bf27aae31833: No such file or directory (2)

Is it a problem with Ubuntu? Or the Flatpak? Or the Slack project? What am I missing?

@bhack
Copy link

bhack commented Sep 8, 2023

Slack 4.34.115 changelog

Linux users on Wayland noticed that screensharing in huddles would crash the app as soon as sharing ended. No good deed goes unpunished, they say. We're working to change that to "No bad bug goes unfixed." Please resume sharing with impunity.

@evan-a-a
Copy link
Collaborator

Closing, upstream issue.

@evan-a-a evan-a-a closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2023
@devurandom
Copy link

Slack 4.34.115 changelog

Linux users on Wayland noticed that screensharing in huddles would crash the app as soon as sharing ended. No good deed goes unpunished, they say. We're working to change that to "No bad bug goes unfixed." Please resume sharing with impunity.

@bhack Does that mean the issue is fixed when using version e903031, 4a99861, be9f314 or 3a012f6 of this Flatpak? Did you test / can you confirm?

@bhack
Copy link

bhack commented Dec 12, 2023

@devurandom No a final upstream solution isn't in any release. Check #101 (comment)

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

No branches or pull requests

7 participants