signalapp
App/GUI launches but mouse click seems to do nothing...
Using a supported version?
- [x] I have searched searched open and closed issues for duplicates.
- [x] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.
Overall summary
Title mostly sums it up. Clicking in the GUI does nothing. It's responsive to keyboard keys, like Tab, Enter, etc.
Steps to reproduce
- Run signal-desktop.
- Try to click with the mouse.
Expected result
I expect clicking the GUI with the mouse to do something.
Actual result
Clicking the GUI with the mouse does nothing.
Screenshots
No response
Signal version
7.43.0
Operating system
Debian GNU/Linux 12 (Linux penguin 6.6.56-05934-gf790fe104dba x86_64 (Chromium OS 19.0_pre530567))
Version of Signal on your phone
No response
Link to debug log
I can get to View->Debug Log with the keyboard, but I'm not seeing a URL to copy... (It doesn't look like it's doing anything when I hit Enter on Debug Log...although when I Alt+Tab, it kind of looks like I can see an additional window in the preview image?)
Hmm. I noticed there was a ChromeOS update, so I did that, and after restarting, Signal seemed to be working... Closed Signal and then re-opened it after a few minutes and it's back to not responding to mouse clicks... So possibly something that doesn't load right away after an OS restart is interfering?
The plot thickens... It looks like this is only an issue when using an external monitor...
Thank you for the report. Unfortunately, it doesn't sound like something we are in control of. This is low level behavior provided by Electron. Do you think you could file a bug with them, instead?
I've also been having this issue since last week. I'm not using an external monitor (just a laptop screen), but am using Linux (KDE Neon 6.3.2, Wayland, Signal Flatpack). Signal is unresponsive to mouse clicks at launch, but fixes if I resize the window. Touch presses and keyboard do work fine at launch.
Edit: currently using Signal 7.44.0, but it seems quite likely I also had it on 7.43.0 given the timeline.
Thank you for the report. Unfortunately, it doesn't sound like something we are in control of. This is low level behaviour provided by Electron. Do you think you could file a bug with them, instead?
Looking at the commit history, it seems like the Electron version was bumped from 33.3.1 to 34.0.1 shortly before the first 7.43 alpha, so I'd guess the Electron 34 update broke this. I'll see if I can find an existing issue for it or not not open one.
Couldn't find one, so have opened it here https://github.com/electron/electron/issues/45886
If anyone with more experience with Electron and the Signal desktop app codebase is able to help with the bug report (eg for providing a test case), that would be appreciated.
This issue has recently gone away for me. I'm not sure exactly what version this happened in, but I'm currently using 7.54.0.
We just upgraded our version of Electron in 7.54 so maybe that fixed it. I'll close now but let us know if the issue comes back
