flameshot gets freezed when I press save button

[Chaliuz]

Flameshot Version

I installed flameshot from Official Arch/Manjaro repository.

Flameshot v12.1.0 (-)
Compiled with Qt 5.15.10

Installation Type

User repository (AUR)

Operating System type and version

manjaro i3

Description

A while ago I updated my manjaro and from there flameshot get freezed when I press the button "save", it takes a lot of time opening the popup window and sometimes it doesn't open at all.

Steps to reproduce

1. run flameshot
2. select an area
3. press the save button

Screenshots or screen recordings

System Information

System:

  Host: chalius-pc Kernel: 6.9.3-3-MANJARO arch: x86_64 bits: 64
  Desktop: i3 v: 4.23 Distro: Manjaro Linux
Graphics:
  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
    driver: amdgpu v: kernel
  Device-2: Generalplus 808 Camera driver: snd-usb-audio,uvcvideo type: USB
  Display: x11 server: X.org v: 1.21.1.13 driver: X: loaded: amdgpu
    unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu resolution:
    1: 1920x1080~60Hz 2: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: radeonsi,swrast platforms: x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.9-manjaro1.1
    renderer: AMD Radeon RX 5600 XT (radeonsi navi10 LLVM 17.0.6 DRM 3.57
    6.9.3-3-MANJARO)

UPDATE:

• It seems to be a Qt problem, other programs that use the same Qt window to save files have the same problem.

[mmahmoudian]

Few points:

1. Would you please provide the full version of Flameshot here (edit your post). In this current format this bug report is invalid
2. how are you triggering Flameshot?

[Acpear]

Hey there! I've been wondering if you might be able to help me out with something. It's a bit strange, but I was wondering if you could try pressing the Ctrl + s (save) key to see if Flameshot will save the selected area? That way, we can get a better idea of where the problem might be coming from. Is it something with the buttons, or could it be something internal? Thanks so much in advance!

It sounds like you want flameshot to run normally (press "save," do "save") and fast ("it takes a lot of time opening"). The first one is a functional problem that might be solved after some debugging time and validated immediately. However, the second one is less clear and targetable, depending on many factors from system, Wayland, software, etc.

[Chaliuz]

Sorry for the delay.

• I edited the message and put the result of: "flameshot --version" command, this is correct?

• I tried to trigger flameshot in many ways and the same thing happens in all of them:

  • With i3 window manager command.
  • Clicking the tray icon.
  • Calling flameshot in a terminal (using: flameshot gui)

• When I use ctrl+s the problem is the same.

• I noticed that while the save window is loading the processor is 100%, and it lasts until the window is closed:
  

[mmahmoudian]

@Chaliuz

I edited the message and put the result of: "flameshot --version" command, this is correct?

If you install Flameshot through AUR, then the flameshot --version should give you the commit hash in the parenthesis:

If you install from official Arch/Manjaro repository, then the parenthesis will be empty

Please update the original post accordingly

Calling flameshot in a terminal (using: flameshot gui)

The Gif you provided in the original post and the one in your last post does not fit flameshot gui because you are activating pin as well. Would you please confirm that running only /usr/bin/flameshot gui without any other argument would give you the same CPU usage, same freezing, and also same pinned screenshot.

[Chaliuz]

Hello, thanks for answering.

• I updated the original post with the flameshot version.
• Yes, running the command /usr/bin/flameshot gui gives me the same result.
• Actually the pinned screenshot is the saving window, after a little more than 1 minute of loading the interface appears, but it's very slow.
• Here is other video with the previous command:

[Chaliuz]

hello,

I recently notice that other program that uses the same window in order to save a file gets the exact same problem,
I think the problem is the library that draws those windows, I don't know how to change it :(.