flameshot-org / flameshot

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

Flameshot is unable to capture screen on Arch Linux, KDE, Wayland #3052

Open FuckingToasters opened 1 year ago

FuckingToasters commented 1 year ago

Flameshot Version

Flameshot v12.1.0 ()

Installation Type

User repository (AUR), Flatpak from Flathub, Flatpak from Github, AppImage, Using the ready-made package from Github Releases, Compiled from source

Operating System type and version

Arch Linux x86_64

Description

Falmeshot never worked good for me, it always made the screenshot selection small at the top left hand corner.

Now, after some time starting my laptop again and doing a full pacman and yay update (pacman -Syyu & yay -Syyu) i noticed, that it don't work at all.

Flameshot always give me "unable to capture screenshot" notification which is not really detailed so i ran it from terminal and got the actual errors:

When running without sudo:

flameshot: error: Unable to capture screen
flameshot: error: Unable to capture screen
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

With sudo:

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
flameshot: error: Unable to connect via DBus

Steps to reproduce

  1. run flameshot normally on Arch Linux, Wayland & KDE
  2. receive error notification "unable to capture screenshot"
  3. run flameshot from terminal to see a more detailed output
  4. see the errors i posted above

Screenshots or screen recordings

No response

System Information

  1. Arch Linux x86_64 | Kernal Version: 6.1.1-arch1-1

  2. Can't make a screenshot -> Resulution: 1920x1280

  3. KDE Plasma 5.26.5 , Wayland

  4. Neofetch Output (Unnecessary details cencored using /):

    OS: Arch Linux x86_64 
    Host: /
    Kernel: 6.1.1-arch1-1 
    Uptime: /
    Packages: 821 (pacman), 7 (flatpak) 
    Shell: bash 5.1.16 
    Resolution: 1920x1280 
    DE: Plasma 5.26.5 
    WM: kwin 
    Theme: [Plasma], Breeze [GTK2/3] 
    Icons: [Plasma], breeze-dark [GTK2/3] 
    Terminal: konsole 
    CPU: Intel m5-6Y57 (4) @ 2.800GHz 
    GPU: Intel HD Graphics 515 
    Memory: 4306MiB / 7829MiB 
FuckingToasters commented 1 year ago

Update, when i run sudo flameshot gui it open sucessfully but only black is shown in the window

jilinoleg commented 1 year ago

Same behavior is present in Wayland session of Fedora 37 KDE spin after update to KDE 5.26.5, except before flameshot was working correctly

Censored neofetch output:

OS: Fedora Linux 37 (KDE Plasma) x86_64 
Host: /
Kernel: 6.0.15-300.fc37.x86_64 
Uptime: 3 days, 18 hours, 59 mins 
Packages: 4010 (rpm), 36 (flatpak) 
Shell: bash 5.2.15 
Resolution: 1920x1080 
DE: Plasma 5.26.5 
WM: kwin 
WM Theme: Materia 
Theme: [Plasma], Materia-light [GTK2/3] 
Icons: [Plasma], Papirus [GTK2/3] 
Terminal: konsole 
Terminal Font: Hack Nerd Font 10 
CPU: Intel /
GPU: Intel /
GPU: NVIDIA /
Memory: 5742MiB / 15794MiB

flameshot --version output

Flameshot v12.1.0 (-)
Compiled with Qt 5.15.5
mmahmoudian commented 1 year ago

@FuckingToasters

it always made the screenshot selection small at the top left hand corner.

You most probably have fractional scaling. That is another issue.

Update, when i run sudo flameshot gui it open sucessfully

You should NEVER run Flameshot as sudo.

Neofetch Output (Unnecessary details cencored using /)

neofetch is not useful for us. as we have explained in the bug report form, use inxi --graphics --system --width=80

Flameshot is unable to capture screen on Arch Linux, KDE, Wayland #3052

Please tell me how this is different from #2974 and #2880 ?

dongfengweixiao commented 1 year ago

+1

The discussion in this link may be helpful.

zsolt-p commented 1 year ago

+1

binarykitchen commented 2 months ago

Ugh, I just arrived here from a fresh Arch Linux install and that's an old, unresolved issue?

onyxcode commented 1 month ago

worked fine until a couple days ago, no idea what changed.