search

flameshot-org / flameshot

Powerful yet simple to use screenshot software :desktop_computer: :camera_flash:
https://flameshot.org
GNU General Public License v3.0
25.04k stars 1.6k forks source link

flameshot monitor unexpected behavior #2522

Open apprehensions opened 2 years ago

apprehensions commented 2 years ago

Flameshot Version

Flameshot v11.0.0 (-) Compiled with Qt 5.15.2

Installation Type

Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)

Operating System type and version

Void 5.16.18_1 x86_64 GenuineIntel uptodate FFFFFF

Description

flameshot screen default behavior gives me an image very offset from where my cursor's display residence is. also duplicates a small portion of the display with it. [1] flameshot screen --number 0: [2], offset flameshot screen --number 1: [3], normal i have a multi-monitor setup. display numbers are always 0, 1 or 2. flameshot screen --number 2: zsh: segmentation fault flameshot screen --number 2 flameshot segmentation faults on a screen that 'doesn't exist' (eg. 9)

Steps to reproduce

  1. have a multi monitor setup
  2. flameshot screen, flameshot screen --number 1, flameshot screen --number 2,

Screenshots or screen recordings

i have a multi monitor setup: image [1] image [2] image [3] image

System Information

  1. Void Linux Void 5.16.18_1 x86_64 GenuineIntel uptodate FFFFFF
  2. 
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier     "Monitor0"
VendorName     "Unknown"
ModelName      "AOC 24G2W1G4"
HorizSync       160.0 - 160.0
VertRefresh     48.0 - 144.0
Option         "DPMS"
EndSection

...

Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 Option "Stereo" "0" Option "nvidiaXineramaInfoOrder" "DFP-2" Option "metamodes" "DP-0: 1920x1080_144 +768+143, HDMI-1: nvidia-auto-select +0+0 {rotation=right}" Option "SLI" "Off" Option "MultiGPU" "Off" Option "BaseMosaic" "off" SubSection "Display" Depth 24 EndSubSection EndSection


3. dwm-6.3 X11
borgmanJeremy commented 2 years ago

Are you using factional scaling?

apprehensions commented 2 years ago

Are you using factional scaling?

No. i don't think so,

borgmanJeremy commented 2 years ago

I just merged a patch that resolves the seg fault.

apprehensions commented 2 years ago

flameshot screen --number 0 image flameshot screen --number 1 image flameshot screen --number 2

flameshot: info: Requested screen exceeds screen count
flameshot: info: Screenshot aborted.

however, the only real values i can use for the monitor is 0,1 but it comes out very weird and i cannot use my other monitor.

mmahmoudian commented 2 years ago

@wael444 would you please provide full info of your monitor setup. In your original post you only provided info for the "Monitor0"

apprehensions commented 2 years ago

@wael444 would you please provide full info of your monitor setup. In your original post you only provided info for the "Monitor0"

i don't know how else i can provide more monitor setup.

here is xrandr 

Screen 0: minimum 8 x 8, current 2688 x 1366, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 1920x1080+768+143 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080     60.00 + 144.00*  119.98   119.88    99.93    59.94    50.00  
   1680x1050     59.88  
   1440x900      59.90  
   1280x1024     75.02    60.02  
   1280x720      60.00    59.94    50.00  
   1024x768     119.99    99.97    75.03    70.07    60.00  
   800x600      119.97    99.66    75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480      119.52    99.77    75.00    72.81    59.94    59.93  
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected 768x1366+0+0 right (normal left inverted right x axis y axis) 410mm x 230mm
   1366x768      59.79*+
   1920x1080     59.94  
   1280x1024     75.02    60.02  
   1280x720      60.00    59.94  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   720x480       59.94    59.94  
   640x480       75.00    72.81    59.94
mmahmoudian commented 2 years ago

Yeah this is fine, but it only shows two connected monitors. In your original post you said you have 3.

You can use inxi --edid to get detailed monitor info

apprehensions commented 2 years ago

In your original post you said you have 3.

i don't remember explicitly saying 3 but in one of the screenshots it shows 1 primary monitor with a vertical monitor.

Error 22: Unsupported option: --edid
Check -h for correct parameters.

edit: it seems the void package for inxi doesnt support --edid..? here is inxi --edid from git sources:

Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2060 Rev. A] vendor: ASUSTeK
    driver: nvidia v: 510.60.02 pcie: gen: 3 speed: 8 GT/s lanes: 1 link-max:
    lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1f08 class-ID: 0300
  Display: server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia gpu: nvidia
    display-ID: :1 screens: 1
  Screen-1: 0 s-res: 2688x1366 s-dpi: 92 s-size: 742x381mm (29.21x15.00")
    s-diag: 834mm (32.84")
  Monitor-1: DP-0 pos: primary,bottom-r res: 1920x1080 dpi: 93
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
  Monitor-2: HDMI-1 pos: primary,top-left res: 768x1366 hz: 60 dpi: 85
    size: 230x410mm (9.06x16.14") diag: 470mm (18.51") modes: N/A
  OpenGL: renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2
    v: 4.6.0 NVIDIA 510.60.02 direct render: Yes
dmolin commented 2 years ago

same issue here:

When running "flameshot screen ..." the image I get out is a cropped image of my main display (4K res.) + black space (or garbage background content) around it: it's like the screenshot was taken with an region of +1000px on the x-axis and around 4-500px its y-axis.

Basically, I get a result that I would expect if running flameshot with "--region 3840x2160+1000+450"

The only way for me to have "screen" working is to hardcode the screen number (I'm running with 2 screens); What I don't get though is how flameshot figures out which screen is "0" and which is "1". my "xrandr --listmonitors" gives me my primary display as nr "0", but flameshot recognizes it as "1". If I call flameshot with "-n 0" I get the same mish-mash of an image (so my other screen is never captured actually).

My hunch is this is something that might be related to the way the 2 monitors are laid out maybe:

This is my layout for the 2 screens, in case it might be of help:

Monitors: 2 0: +*DP-4 3840/941x2160/529+1440+517 DP-4 1: +DP-0 1440/597x2560/336+0+0 DP-0

image

wizardlink commented 2 years ago

I feel like this is related so I'll add my coin to this post, I have a multi-monitor set-up but a more widely used one (two landscape monitors right beside each other) and I have an issue when using flameshot screen alone, while flameshot screen --number 0 and flameshot screen --number 1 work as intended.

For reference, when using flameshot screen on my secondary monitor I get a proper screenshot, while in the primary, a black screen (probably wrong coordinates).

In case it helps, here's my inxi output:

Graphics:
  Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: Sapphire
    driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: DP-2,DP-3 empty: DP-1,HDMI-A-1 bus-ID: 08:00.0 chip-ID: 1002:73ff
    class-ID: 0300
  Device-2: Logitech C922 Pro Stream Webcam type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1-10:3 chip-ID: 046d:085c
    class-ID: 0102 serial: 8772B96F
  Display: x11 server: X.Org v: 1.20.14 compositor: kwin_x11 driver: X:
    loaded: amdgpu gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
    s-diag: 1055mm (41.54")
  Monitor-1: DP-2 mapped: DisplayPort-1 pos: primary,right
    model: Lenovo Y25f serial: U4AC2593 built: 2019 res: 1920x1080 dpi: 90
    gamma: 1.2 chroma: red: x: 0.639 y: 0.337 green: x: 0.314 y: 0.627 blue:
    x: 0.153 y: 0.055 white: x: 0.314 y: 0.329 size: 544x303mm (21.42x11.93")
    diag: 623mm (24.5") ratio: 16:9 modes: 1920x1080, 1680x1050, 1280x1024,
    1440x900, 1280x800, 1280x720, 1440x576, 1024x768, 1440x480, 832x624,
    800x600, 720x576, 720x480, 640x480, 720x400
  Monitor-2: DP-3 mapped: DisplayPort-2 pos: primary,left
    model: Philips PHL 242V8 serial: 97003 built: 2021 res: 1920x1080 dpi: 93
    gamma: 1.2 chroma: red: x: 0.647 y: 0.333 green: x: 0.306 y: 0.627 blue:
    x: 0.149 y: 0.055 white: x: 0.314 y: 0.329 size: 527x296mm (20.75x11.65")
    diag: 604mm (23.8") ratio: 16:9 modes: 1920x1080, 1680x1050, 1280x1024,
    1440x900, 1280x960, 1280x800, 1280x720, 1024x768, 832x624, 800x600,
    720x576, 720x480, 640x480, 720x400
  OpenGL: renderer: AMD Radeon RX 6600 XT (dimgrey_cavefish LLVM 14.0.0 DRM
    3.44 5.17.8-300.fc36.x86_64)
    v: 4.6 Mesa 22.0.3 direct render: Yes
mmahmoudian commented 2 years ago

@wizardlink which window manager, OS, and Flameshot version are you using?

wizardlink commented 2 years ago

@wizardlink which window manager, OS, and Flameshot version are you using?

I'm using KWin as my WM, my OS is Fedora 36 and I have this issue since Fedora 34 (wasn't a big deal so I never reported) and my Flameshot version is 11.0.0.

qerphrail commented 1 year ago

The same problems are happening here. I currently have two monitors. There is a confusion that Flameshot makes when applying flameshot screen --number 0 and flameshot screen --number 1. It depends on which screen the cursor is on (Flameshot reverses the screenshots and some appear with a black band at the bottom, as if the resolution is being misinterpreted). The flameshot screen also has flaws: it depends on which screen the cursor is positioned on. Screen number 0 is captured with incorrect resolution while screen 1 is not captured (the output is a captured image almost entirely black, with a small piece of the right part). flameshot full and flameshot gui seem to work fine. Soon I will install the third monitor.

Has anyone found a solution to these problems?

Operating System: Linux Mint 21.2 Kernel: Linux 5.15.0-76-generic (the Kernel in progress is earlier because only through this one does my Bluetooth work) Flameshot version: v12.1.0