flameshot icon indicating copy to clipboard operation
flameshot copied to clipboard

macOS windows disappear when Flameshot initiates screenshot

Open jg3 opened this issue 1 year ago • 3 comments

Flameshot Version

Flameshot v12.1.0 (96c2c82e) Compiled with Qt 5.15.5 darwin: 23.2.0 osx: 14.2

(I installed by downloading a .dmg file from flameshot.org; I uninstalled and reinstalled using the latest .dmg in the course of initial troubleshooting)

Installation Type

Using the ready-made package from Github Releases

Operating System type and version

macOS 14.2.1 (23C71)

Description

When attempting to take a screenshot all the windows on the desktop disappear when I invoke Flameshot to take a screenshot. I have been using Flameshot happily for years, I believe this began around my first upgrade to Sonoma.

I also get a message that Flameshot needs permission in system settings for screen recording at every reboot (but that permission is already granted and persists in System Settings, so I'm not sure why that's happening or if it is related)

Steps to reproduce

  1. With flameshot running
  2. Take a screenshot (using either the menu option or the keyboard shortcut)
  3. Watch all the windows disappear (oh no! why did that happen?)
  4. Take a screenshot anyway (or don't, whatever)
  5. Only the desktop/background items which were visible are captured in the screenshot (not surprising)
  6. After taking screenshot (or escaping out), destop windows return as before.

Screenshots or screen recordings

(gif demo of the issue) flameshot-issue-demo-20240105

System Information

MacBook Pro 16-inch 2019 (Intel) Built-in display (3072 × 1920) I often use an external display at up to (3840 × 2160), but that does not seem to have any impact on this issue.

jg3 avatar Jan 05 '24 18:01 jg3

I have the same problem Happens both with the built-in display and with an external display MacBook Pro 14-inch 2021 (M1) osx: 14.2

pinuts-StephanGiesen avatar Jan 19 '24 15:01 pinuts-StephanGiesen

I have the same issue after upgrading to Sonoma. I think it's a weird privacy issue.. image

trusiik avatar Jan 25 '24 08:01 trusiik

The problem has resolved itself for me. After the OS update to version OSX 14.3, I had the same error message like @trusiik. I stopped flameshot and removed it completely from the autostart. After a restart, flameshot is now working properly again.

pinuts-StephanGiesen avatar Jan 29 '24 07:01 pinuts-StephanGiesen