Flameshot on Wayland not handling multiple screens #2364
Comments
|
@Steffo99 can you also post here your monitor arrangement and if you have different resolutions and scalings on the monitors. |
|
My monitor arrangement is:
That said... OBS seems to be failing to launch, so there might be something else currently not working on my setup... I should be able to do more research on the problem either tomorrow or on Sunday: I'll keep you updated with my findings! |
mmahmoudian
added
the
Waiting For Info
System information 2I just noticed I forgot to mention that I'm using Wayland with the Nvidia proprietary driver and the newly introduced GBM API. Screen capture failureI couldn't get a single screen capture program to work, so I'm starting to suspect that something is wrong with my setup. OBS, KSnap and Grim logssteffo@nitro:~$ obs
Attempted path: share/obs/obs-studio/locale/en-US.ini
Attempted path: /usr/share/obs/obs-studio/locale/en-US.ini
Attempted path: share/obs/obs-studio/themes/Dark.qss
Attempted path: /usr/share/obs/obs-studio/themes/Dark.qss
info: Platform: Wayland
info: CPU Name: AMD Ryzen 5 1600X Six-Core Processor
info: CPU Speed: 3102.166MHz
info: Physical Cores: 6, Logical Cores: 12
info: Physical Memory: 15992MB Total, 8343MB Free
info: Kernel Version: Linux 5.16.5-zen1-1-zen
info: Distribution: "Arch Linux" Unknown
info: Session Type: wayland
info: Portable mode: false
Attempted path: share/obs/obs-studio/themes/Dark/no_sources.svg
Attempted path: /usr/share/obs/obs-studio/themes/Dark/no_sources.svg
QMetaObject::connectSlotsByName: No matching signal for on_tbar_position_valueChanged(int)
QMetaObject::connectSlotsByName: No matching signal for on_actionShowTransitionProperties_triggered()
QMetaObject::connectSlotsByName: No matching signal for on_actionHideTransitionProperties_triggered()
info: OBS 27.1.3-tytan652-14 (linux)
info: ---------------------------------
info: ---------------------------------
info: audio settings reset:
samples per sec: 48000
speakers: 2
info: ---------------------------------
info: Initializing OpenGL...
info: Using EGL/Wayland
info: Initialized EGL 1.5
error: eglChooseConfig failed
error: device_create (GL) failed
error: Failed to initialize video. Your GPU may not be supported, or your graphics drivers may need to be updated.
Cannot find EGLConfig, returning null config
error: obs_display_init: Failed to create swap chain
info: Freeing OBS context data
info: == Profiler Results =============================
info: run_program_init: 2076.4 ms
info: ┣OBSApp::AppInit: 6.239 ms
info: ┃ ┗OBSApp::InitLocale: 0.861 ms
info: ┗OBSApp::OBSInit: 77.217 ms
info: ┣obs_startup: 12.337 ms
info: ┗OBSBasic::OBSInit: 6.23 ms
info: ┣OBSBasic::InitBasicConfig: 0.102 ms
info: ┣OBSBasic::ResetAudio: 0.227 ms
info: ┗OBSBasic::ResetVideo: 5.864 ms
info: obs_hotkey_thread(25 ms): min=0 ms, median=0 ms, max=0.001 ms, 99th percentile=0.001 ms, 100% below 25 ms
info: audio_thread(Audio): min=0.008 ms, median=0.019 ms, max=0.032 ms, 99th percentile=0.032 ms
info: =================================================
info: == Profiler Time Between Calls ==================
info: obs_hotkey_thread(25 ms): min=25.032 ms, median=25.082 ms, max=25.491 ms, 100% within ±2% of 25 ms (0% lower, 0% higher)
info: =================================================
info: Number of memory leaks: 184steffo@nitro:~[130]$ ksnip
Warning: Unable to find any translation files for ksnip.
Warning: Unable to find any translation files for kImageAnnotator.
Warning: Wayland does not support QWindow::requestActivate()
Warning: Wayland does not support QWindow::requestActivate()
Warning: This plugin does not support setting window opacity
Critical: Unable to show image: No image provided but one was expected.
Warning: Wayland does not support QWindow::requestActivate()
Warning: Wayland does not support QWindow::requestActivate()steffo@nitro:~$ grim
compositor doesn't support wlr-screencopy-unstable-v1The |
Segfault?
steffo@nitro:~$ flameshot screen
fish: Job 1, 'flameshot screen' terminated by signal SIGSEGV (Address boundary error) |
Example screenshotThis is what screenshots of the middle screen taken with
|
Screenshot of the bug
|
|
If you need additional info I'd be glad to provide them :) |
|
I have similar setup and don't have this issues. Similarities:
Differences:
I can't mess up with this computer to try to reproduce this issue. So let's wait and see if other devs have a solution/hypothesis in mind. P.s: thanks for providing all these information 👍🏼 |
|
I have the same issue, I'm running Wayland with DWL on Gentoo with Nvidia proprietary drivers. I have my laptop 1920x1080 and an external monitor 3840x2160. I do not have Xwayland enabled in DWL but I do have Xwayland installed |
|
This is not related to NVIDIA, I have the same issue using sway with an AMD GPU. Interesting to note is, it captures my left screen, but displays the editor on my right screen, even tho I tried to capture my middle screen. |
mmahmoudian
added
Wayland
|
Hi Have the same issue in the same setup. Manjaro, Plasma version 5.24.2, and using wayland with proprietary nvidia drivers. Appears in both scenarios when resolution on all screens is equal and when center monitor have higher resolution, but differently. In first case flameshot appears on the right screen showing the left screen, in second - appears on the center screen and shows left screen with a bit bit of the center screen. In the terminal "flameshot gui" has this info: flameshot screen:
|
mmahmoudian
added
Bug
|
Yeah, I'm having the same issue on Sway as well, screenshots the left screen and shows the GUI on the right screen. |
|
Am I late to the party? At least now it starts on Plasma 5.24.1 (Wayland, no scaling, intel iGPU) and flameshot 11, but... Spectacle: Flameshot: (shifted to the right by one FullHD screen) |
|
I'm running KDE plasma 5.24.2 with multiple monitors and I'm also experiencing this issue. What seems to be occurring is that flameshot starts with the total screen real-estate of both monitors combined, but tries to present that real estate on the primary monitor. This obviously can't fit, so things appear to shift around as it presents just the top left view of the total combined real estate. I've noticed that on Gnome, you're prompted to select a monitor first (via xdg-desktop-portal), which limits flameshot's initial starting to a single monitor. This means that you can't create screenshots across monitors, but it doesn't have the issue where window contents are shifted around as it tries to squeeze the entire real estate view into a single monitor. Perhaps do something similar with KDE plasma running on wayland and present the xdg-desktop-portal dialog? |
|
I also have the same issue. My Setup:Betriebssystem: Manjaro Linux Flameshot v11.0.0 (-) |
|
Hey, I'd like to report I have the same issue as well. Running flameshot v11.0.0 on sway 1.7 and wlroots 0.15.1. Seems it grabs my left-most monitor as the only display when using For reference, I have two monitors that are arranged like the attached photo shows. Both are 1080p with the same amount of scaling.
|
This also fixes the issues i've been having in KDE Plasma with multiple monitors, thanks for the tip! |
|
Although the above fix works (apparently only when launching FS via the terminal), I was able to verify, that version 0.10.2 doesn't have this problem |
|
Yeah. Im not by a computer to check for the commit currently, but I believe from past conversation and issues that xwayland was used by default in 0.10.2. If I have time later I'll try to bisect where the breaking commit is.
|
|
Setting |
|
For me, it simply opens on the right-most monitor, full screen. Luckily that's easily fixed in the sway config: |
Thanks for this, that fixed my multi monitor issue. Now I just need to fix my clipboard and it'll be working perfectly. |
|
We just merged a change to use the XDG portal on KDE wayland. That might have resolved this. |
|
The change doesn't seem to have helped, still need the QT_QPA_PLATFORM=xcb, which still breaks the shortcuts |
Thanks man, that helped putting me on the right track on sway. I wanted to only have the screenshot editor to be fullscreen, not the savings dialog or the config menu. added: to my sway config, works as expected now. |
|
Workaround for hyprland: |
|
Edit: Sorry, I was wrong about this. This patch does NOT resolve the issue.
--- flameshot-12.1.0.bak/src/core/flameshot.cpp 2022-07-03 15:42:21.000000000 +0200
+++ flameshot-12.1.0/src/core/flameshot.cpp 2023-12-13 13:31:06.850534282 +0100
@@ -124,6 +124,10 @@
m_captureWindow->raise();
#else
m_captureWindow->showFullScreen();
+ if (DesktopInfo().waylandDetected()) {
+ m_captureWindow->activateWindow();
+ m_captureWindow->raise();
+ }
// m_captureWindow->show(); // For CaptureWidget Debugging under Linux
#endif
return m_captureWindow; |
|
What worked for me using KDE and Wayland:
|
|
I am running into this issue as well, and the workaround suggested above does indeed work. If the window matching is set up too loose, the rules will also apply to the settings dialog, for instance, so I set:
As you can see from the screenshot below, these settings work around the issue perfectly, so thanks everyone for your tips!
|
|
Just wanted to chime in also, @Lightfire228's and @Christian-Klempau combined suggestions fixed the issue for me. Thanks very much! |
|
I have 2 unequal monitors and these settings in kde plasma have made it work for me without needing to move around my monitors to meet some weird 0,0 standard |
|
Not sure whether the change is about KDE 6, but there's no the "Ignore requested geometry | Force | Yes" option here anymore. This option might have been replaced with "Obey geometry restrictions | False | No", but in my case this option's not needed for Flameshot to recover. In case that one may want to just directly import the window rule configuration (it doesn't have "Obey geometry restrictions" configured), save it as [Flameshot workaround (#2364)]
Description=Flameshot workaround (#2364)
above=true
aboverule=2
fullscreenrule=2
position=0,0
positionrule=2
title=flameshot
titlematch=1
types=1
wmclass=flameshot flameshot
wmclasscomplete=true
wmclassmatch=1 |
This seems to be the case for me as well. Forcing position, fullscreen, and keep above others are still necessary for the aforementioned reasons. Otherwise, the workaround works perfectly in kde 6.0 kwin rules screenshot
There still is a noticeable lag before the gui comes up, but oh well |
This settings perfectly worked for me, after Plasma 6 (and Wayland) upgrade on Arch. |
|
I'm having multi monitor issues on X11 |
For me the workaround is working on KDE 6. Only thing now is that scaling is a bit wonky, but for the screenshot creation this is fine for me. Of course I want to see this fixed, but time is a thing :) |
|
Hi, Working for me with this screen disposition.
|
|
Anyone has any idea of the codepath impacted that is causing this bug ? What do we need to change ? I'm willing to work on a PR and I've got a VM setup just for fixing flameshot issues, as they've been here for too long. |
|
@AkechiShiro The problem isn't flameshot, really. It's that in Wayland windows can't request/demand to be opened at specific coordinates: it's up to the wayland compositor to place the window. On KDE this means kwin decides where the flameshot gui appears. You can use kwin rules like those shown in the issue here to make kwin place the window differently, but there's nothing you can do from within flameshot. I'm not familiar enough with kwin to know if they have some sort of "quirks" ruleset where the devs specify rules for particular applications ahead of time, but if they do that's probably the only place where you can realistically make this change. For other window managers / desktop environments that's again in the power of their compositor and would have to be changed at each place individually. This will NEVER happen with Gnome, so there will never be a full solution to this issue under wayland, unless the by now several year old issue about respecting window placement requests is merged, which I doubt will happen. |
|
Was this problem reported upstream to Wayland in details ? @insunaa That Flameshot has lots of bugs due to this decision ? And that it is breaking the user experience for everyone moving to Wayland and using Flameshot for screenshots ? |
Actually, there has to be some sort auf "quirk", since it works with Plasma's "Spectacle". Or does that tool use a completely different approach? |
@Cybso Just to add to the conversation, some DEs have their own private API that have access to certain parts of compositor and window manager that other apps which use the public API don't. The infamous example is Gnome which their own private API gives all sorts of access to their own apps including the Gnome screenshot, but other screenshot tools are given the same level of access. That's why Gnome screenshot tool works smoothly and all other screenshot apps are suffering. I don't remember the KDE Plasma situation, but they might also use some sort of private API as well. That should be checked, so take it with a grain of salt. Also I myself have now moved to Wayland Plasma and I can reproduce the problem in multi-monitor setup. I tried to see if window rules in Plasma can be configured to improve the situation, but nothing good came out of that. |
|
@mmahmoudian then a way forward with this issue might be to ask if those API can be used by screenshots open source software and not just by their own private app What do you think if I open up two issues one from GNOME and one for KDE regarding this issue and link them here ? |
|
I've got this exact same issue when using Wayland, but trying every variation of the kwin rule above does not workaround the problem for me.
It makes no difference if I have the left monitor at 0x0 or not... crashes in the same manner. Flameshot works great with X11, and Spectacle works fine with Wayland. |
|
@3vi1 you tried it with the "Initial Placement: Force: Random" selector? That's what did the trick for me. Tho granted I'm on kde 6.1.2 |
Yes. I tried that, and even tried to start the app multiple times just in case the "Random" location was somehow bad - but it didn't appear to make any difference. Thank you for the suggestion though. |
|
I am running into this exact issue. Whe prefixing the |
Issues
Notes
ConfigurationOS: NixOS 24.11.19700101.dirty (Vicuna) x86_64 Kernel: Linux 6.6.50 Screen configuration: $ kscreen-doctor -o
Output: 1 DP-1
enabled
connected
priority 2
DisplayPort
Modes: 0:2560x1440@60! 1:2560x1440@165 2:2560x1440@144* 3:2560x1440@120 4:1920x1080@165 5:1920x1080@120 6:1920x1080@60 7:1920x1080@60 8:1920x1080@50 9:1680x1050@60 10:1280x1024@75 11:1280x1024@60 12:1440x900@60 13:1280x960@60 14:1152x864@75 15:1280x720@120 16:1280x720@100 17:1280x720@60 18:1280x720@60 19:1280x720@50 20:1440x576@50 21:1024x768@75 22:1024x768@70 23:1024x768@60 24:1440x480@60 25:800x600@75 26:800x600@72 27:800x600@60 28:800x600@56 29:720x576@50 30:720x480@60 31:640x480@75 32:640x480@73 33:640x480@60
Geometry: 0,0 1440x2560
Scale: 1
Rotation: 8
Overscan: 0
Vrr: Automatic
RgbRange: unknown
HDR: disabled
Wide Color Gamut: disabled
ICC profile: none
Color profile source: EDID
Output: 2 DP-2
enabled
connected
priority 1
DisplayPort
Modes: 0:3840x2160@60! 1:3840x2160@144* 2:3840x2160@120 3:3840x2160@120 4:3840x2160@100 5:3840x2160@60 6:3840x2160@50 7:3840x2160@30 8:3840x2160@25 9:3840x2160@24 10:2560x1440@144 11:2560x1440@120 12:2560x1440@60 13:1920x1200@60 14:1920x1080@144 15:1920x1080@120 16:1920x1080@120 17:1920x1080@100 18:1920x1080@60 19:1920x1080@60 20:1920x1080@50 21:1920x1080@30 22:1920x1080@25 23:1600x1200@60 24:1680x1050@60 25:1600x900@60 26:1280x1024@75 27:1280x1024@60 28:1280x800@60 29:1152x864@75 30:1280x720@60 31:1024x768@75 32:1024x768@60 33:800x600@75 34:800x600@60 35:720x576@50 36:720x480@60 37:640x480@75 38:640x480@60 39:640x480@60
Geometry: 1440,416 3072x1728
Scale: 1.25
Rotation: 1
Overscan: 0
Vrr: Automatic
RgbRange: unknown
HDR: disabled
Wide Color Gamut: disabled
ICC profile: none
Color profile source: sRGBExample ImageThe following is shown in my primary screen: |
Please checkout the links in this part of our documentation: https://flameshot.org/docs/guide/wayland-help/#i-am-asked-to-share-my-screen-every-time |
and others
Initial report
Flameshot Version
Installation Type
Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)
Operating System type and version
Linux 5.16.5-arch1-1 #1 SMP PREEMPT Tue, 01 Feb 2022 21:42:50 +0000 x86_64 GNU/LinuxDescription
Summary
While using multiple screens on Plasma Wayland, Flameshot seems unable to detect all of them properly, and instead takes a screenshot of the left-most screen through KWin, and prompts the user to edit it via the editor.
Additionally, Flameshot seems unable to copy the selected screenshot to the clipboard, but no error is shown and I'm unsure it's related to this bug.
Logs
Steps to reproduce
With a Wayland session with multiple monitors, using Plasma Desktop:
flameshot guiScreenshots or screen recordings
Will provide a screen recording as soon as OBS Studio finishes compiling 🥲
System Information
unamePlasma
Plasma Desktop installed from the
plasma-desktop5.23.5-1 Arch Linux package.The text was updated successfully, but these errors were encountered: