MS Teams - screen sharing terminates Wavebox

[waldauf]

I upgraded to Wavebox from version 10.0.172 to 10.0.179. Now I cannot share the screen in MS Teams. If I click on the screen share button in MS Teams whole Wavebox is terminated.

In version 10.0.172 screen sharing works.

• Wavebox Version: 10.0.179
• Operating System & Version: Arch Linux
• Account type (if applicable): MS (Outlook, Calendar, Teams, Yammer), 2x Gmail, ...

[Thomas101]

Thanks for reporting. Do you have the latest Chrome installed on your machine? Would you be able to test with this?

Would you also be able to run Wavebox from the terminal using the wavebox-launcher script from the install directory, and start a screen share to see what the stack trace is?

[waldauf]

I thought that the previous version of Wavebox are resistant to failures but last week I found out that version 10.0.172 has the same problem.

The output from manual run wavebox-launcher:

❯ ./wavebox-launcher
[26459:26459:0615/091225.310560:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[26263:26263:0615/091225.548705:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.", source: chrome-extension://melkgfabmbpgmkaphjkjljaadioagbij/_generated_background_page.html (0)
[26462:26478:0615/091238.445768:ERROR:object_proxy.cc(632)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[26462:26478:0615/091238.445788:ERROR:kwallet_dbus.cc(100)] Error contacting kwalletd5 (isEnabled)
[26462:26478:0615/091238.446081:ERROR:object_proxy.cc(632)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files
[26462:26478:0615/091238.446090:ERROR:kwallet_dbus.cc(72)] Error contacting klauncher to start kwalletd5
[26462:26478:0615/091238.523490:ERROR:object_proxy.cc(632)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[26462:26478:0615/091238.523511:ERROR:kwallet_dbus.cc(414)] Error contacting kwalletd5 (close)
[26653:22:0615/091307.945089:ERROR:audio_rtp_receiver.cc(89)] AudioRtpReceiver::OnSetVolume: No audio channel exists.
[26653:23:0615/091308.583634:ERROR:webrtc_video_engine.cc(3252)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[26653:23:0615/091308.583821:ERROR:webrtc_video_engine.cc(3252)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[26653:23:0615/091308.583988:ERROR:webrtc_video_engine.cc(3252)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[26653:23:0615/091308.584145:ERROR:webrtc_video_engine.cc(3252)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[26653:23:0615/091308.584298:ERROR:webrtc_video_engine.cc(3252)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[26653:23:0615/091308.584424:ERROR:webrtc_video_engine.cc(3252)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[26653:23:0615/091308.584558:ERROR:webrtc_video_engine.cc(3252)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[1]    26263 segmentation fault (core dumped)  ./wavebox-launcher

I don't have installed Chrome just Chromium. I'm not sure if is it important for you to use Chrome? I can test it on Chromium.

[Thomas101]

Chromium would be brilliant. Might also be worth giving your machine a restart to see if the problem persists after that

[waldauf]

My laptop is restarted almost every second/third day. In Wavebox is ratio around 50:50 when it works or fails.

I tried Chromium (many times) and where after a click on the sharing window was Chromium terminated also. I also tried Vivaldi with the same result.

[Thomas101]

This looks very much like an upstream Chromium issue as a variety of Chromium-based browsers exhibit the same. Which desktop environment are you using? I'll see if there's anything reported on the Chromium bug tracker

[waldauf]

I'm running KDE desktop environment.