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

Linux/Debian - save image dialog appears behind app for save attempts after the first #6184

Open
1 task done
IntrepidWhelk opened this issue Nov 23, 2022 · 1 comment
Open
1 task done

Comments

@IntrepidWhelk
Copy link

  • [X ] 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

Second image save prompt is in background instead of foreground / modal

Linux/Debian - when attempting to save images from note to self, the first save behaves as expected, but on attempting to save a subsequent image, the prompt appears in the background (not modal) leading to the app appearing frozen.

Steps to Reproduce

  1. Send more than one image to self via mobile app
  2. Save first image to desktop using desktop app
  3. Click through to second image, try to save this image. The app will appear frozen whereas in fact, the save prompt has appeared, but its behind the main app window.

Actual Result:

The prompt will appear, but not in front of the desktop app, which will freeze awaiting the closing of the save prompt, appearing frozen.

Expected Result:

The second and following save prompts should appear in front of the desktop app. Also the subsequent prompts should remember the last location saved to.

Screenshots

image

Platform Info

Signal Version:

5.63.1

Operating System:

Linux debian-ghost 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) x86_64 GNU/Linux

Linked Device Version:

5.59.1.0

Link to Debug Log

https://debuglogs.org/desktop/5.63.1/0e565a277abc9541dff213e1fb4a6c808447358d08cff1e37bfc51391b506990.gz

@jamiebuilds-signal
Copy link
Member

This is going to be a problem with the framework we use, Electron, instead of the Signal app itself. It's unlikely that we're able to do anything about it besides file an issue with Electron.

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

No branches or pull requests

3 participants