Unable to interact with Signal app after file picker dialog

[beefcakefu]

• 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

Each time the file picker dialog is activated and dismissed, I lose control of the app.

Steps to Reproduce

1. Click the '+' icon of any chat.
2. Select an attachment. Or don't. Doesn't really matter.
3. Click 'Open' or 'Cancel'.

Actual Result:

It is as if another invisible dialog still has focus, and I am unable to:

• Type in the text area.
• Send the attachment (if I've selected one).
• Use any of the other chat icons: emoji, sticker, microphone or pick another attachment.
• Start a new conversation.
• Use the search.
• Or select another contact.

The only command Signal app will respond to is Alt+F4 to exit. If an attachment was selected in the file picker before, it is retained in the chat and app allows sending of selected attachement after restarting.

Expected Result:

Depending on whether an attachment was selected, allow me to interact with the app to perform other tasks, or allow me to send the attachment.

Screenshots

Platform Info

Signal Version: 5.58.0 - production

Operating System: Ubuntu 22.04, 64-bit, Linux kernel 5.15.0-47-generic

Linked Device Version:

Link to Debug Log

Unable to interact with app after bug occurs, including the debug log generated immediately after reopening: https://debuglogs.org/desktop/5.58.0/7ddf8b52a5d79b93489c00e43554bc3348b4a9bd0605b3be796a993c63e0249f.gz

[beefcakefu]

The same occurs for the file picker dialog in "Create / upload sticker pack". Unable to click the "Next" button after selecting image or do anything else other than Alt+F4 or X to dismiss the "Sticker pack creator" dialog. Signal app remains responsive after dismissing "Sticker pack creator" dialog.

[scottnonnenberg-signal]

I wasn't able to reproduce this on a Ubuntu 22.04 VM, stock window manager - I can still click around the app after attaching an image as a draft attachment via the + button and the file picker dialog.

Can you tell us more about your window manager and graphics hardware? Does it change if you use the --disable-gpu command-line argument to start Signal Desktop?

[beefcakefu]

Here's the output of wmctrl:

$ wmctrl -m
Name: GNOME Shell
Class: N/A
PID: N/A
Window manager's "showing the desktop" mode: OFF

Bug persists when starting with /opt/Signal/signal-desktop --no-sandbox --disable-gpu %U.

[beefcakefu]

I've also just tried switching between X11 and Wayland, and can confirm the issue persists across both.

Ubuntu 22.04 is installed on bare metal, AMD Ryzen 7 4700U with Radeon graphics, detailed specs here.

[scottnonnenberg-signal]

Can one of you who can repro this start the app with --enable-dev-tools on the command-line and have the dev tools open when this happens? Are the dev tools accessible? What if you try to inspect elements in the normal Signal UI when things aren't working?

[beefcakefu]

Can one of you who can repro this start the app with --enable-dev-tools on the command-line and have the dev tools open when this happens? Are the dev tools accessible? What if you try to inspect elements in the normal Signal UI when things aren't working?

Just tried. When it happens, dev tools become unresponsive too.

[beefcakefu]

I can interact with dev tools if I undock it first! What should I look for when I go through the elements?

[scottnonnenberg-signal]

There's a cursor icon in the top-right; I just want to see what kinds of elements are present in the UI. Is it something in the elements that is preventing (consuming) clicks, or something at the Electron layer.

[beefcakefu]

Is that the one whose tooltip says "Select an element in the page to inspect it - Ctrl + Shift + C" (it is top left for me in the dev tools window)?

When the main window becomes unresponsive, using the cursor doesn't highlight the elements on the page when I mouse over it like it does when it is responsive. Also, the menu bar (File, Edit, View, Window, Help) are all not responding to click events, so I think Electron layer?

[scottnonnenberg-signal]

@beefcakefu Thanks for your investigations. The next step is for us to create an Electron Fiddle minimum repro for the Electron folks. You could go file a bug now, but they require a 'minimum repro,' the smallest app that causes the issue to happen.

[beefcakefu]

So I should wait for the Fiddle, and then file a report with Electron?