Ubuntu 22.04: Signal Desktop Beta crashes on launch after update due to Citrix Workspace

[shashwatsridhar]

• I have searched open and closed issues for duplicates

• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

---

Bug Description

Signal Desktop (beta) crashes on launch on my Ubuntu 22.04.2 machine. Launching from the app launcher shows no error window, and Signal just does not appear. Launching from the terminal yields an error message.

Steps to Reproduce

1. Launch Signal from the app launcher

or

1. Launch Signal from the ubuntu terminal

Actual Result:

Launching graphically does nothing. Occasionally, ubuntu says the application crashed, and offers to send a bug report to developers (which I have already done).

Launching from the terminal yields the following error message:

libc++abi: __cxa_guard_acquire detected recursive initialization: do you have a function-local static variable whose initialization depends on that function?
libc++abi: __cxa_guard_acquire detected recursive initialization: do you have a function-local static variable whose initialization depends on that function?
libc++abi: __cxa_guard_acquire detected recursive initialization: do you have a function-local static variable whose initialization depends on that function?
Aborted (core dumped)

Expected Result:

Signal should launch normally.

Screenshots

Platform Info

Signal Version:

This problem started occurring after Signal Desktop Beta updated to version 6.23.0-beta.1. Downgrading to 6.22.0-beta.3 resolves this issue. However, the latest version 6.24.0-beta.1 still has this issue.

Operating System:

Ubuntu 22.04.2 LTS,kernel: 5.19.0-45-generic

Linked Device Version:

6.24.4

Link to Debug Log

Not sure how to get a debug log if Signal just doesn't open. Would be happy to provide one if someone can tell me how.

[trevor-signal]

Do you by any chance have the Citrix Workspace app installed? Signal v6.23 included an upgrade to Chromium, and some users are seeing a similar error due to the Citrix app, see: https://askubuntu.com/questions/1470525/unable-to-open-chromium-based-browsers-libcabi-cxa-guard-acquire-detected for some more info and a potential solution.

[shashwatsridhar]

That was actually it!
I had the citrix workspace app installed with app protection enabled, I reinstalled it without the app protection, and voila! Signal works again :)

Thanks for the quick tip!

[elajkat]

Hi, I hit the same issue, and I use citrix as well to connect to protected company resources, so playing with app protection is not something I can do. Is there perhaps some solution for this to make signal-desktop and citrix live with the same chromium?

[scottnonnenberg-signal]

@elajkat Does actual Chromium/Chrome work on your machine? Perhaps Citrix needs some sort of exception like it has for those apps?

[elajkat]

@scottnonnenberg-signal, thanks for responding, I use Chromium (Version 115.0.5790.102 (Official Build) snap (64-bit) ) on Ubuntu Jammy (Ubuntu 22.04.2 LTS )

[scottnonnenberg-signal]

@elajkat Perhaps it would be good to reach out to Citrix support? This really sounds like a bug they need to fix on their end.

[elajkat]

Hi, thanks for your time. I played a little with these things, installed icaclient 23.7.0.17 without app protection and signal-destop 6.27.1 (all on Ubuntu 22.04.3) and it seems a working combination (at least I can reach the remote envs with citrix, and signal is started). I check the thing with my IT, what's their opinion.