Black Screen on Ubuntu 22.04

[andyczerwonka]

Brief summary of issue

When I try and take a screen shot, my entire screen goes black.

Steps to reproduce the issue

1. Install Shutter via sudo apt install shutter on Ubuntu 22.04
2. Selection Tool

Error output

Screen goes black

Extra information, such as Shutter version, display server in use (Xorg or Wayland), operating system and ideas for how to solve:

Running x11, nvidia 525

[ygol]

same problem here with popOS 22.04

[andyczerwonka]

It works fine on a single screen for me, but when I plug in my external monitor, it breaks.

[DarthGandalf]

Does it break only on that monitor, or on both?

[andyczerwonka]

Breaks on both in that case.

[ygol]

when disabling "fractional scaling" it works for me

[passabilities]

when disabling "fractional scaling" it works for me

Unfortunately, I can confirm this was the cause.

[gandalfmeister]

Can confirm the problem, and the source of the problem (fractional scaling) on Linux Mint 22 cinnamon with dual monitors. Works correctly if you disable fractional scaling. It also works if you start Shutter with fractional scaling switched off, and then switch it back on when Shutter is running.. screenshots then work Weird!

System: Kernel: 6.8.0-45-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 clocksource: hpet Desktop: Cinnamon v: 6.2.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.2.0 vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22 Wilma base: Ubuntu 24.04 noble Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50-E1 v: 0410 serial: Mobo: ASUSTeK model: PN50-E1 serial: uuid: UEFI: ASUSTeK v: 0410 date: 03/01/2023 CPU: Info: 8-core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP smt: arch: Zen 2 rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 8 MiB Speed (MHz): avg: 1397 min/max: 1400/2000 boost: disabled cores: 1: 1397 2: 1397 3: 1397 4: 1397 5: 1397 6: 1397 7: 1397 8: 1397 bogomips: 31942 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Renoir [Radeon RX Vega 6 ] vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 16 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1 empty: DP-2,DP-3 bus-ID: 05:00.0 chip-ID: 1002:1636 class-ID: 0300 temp: 73.0 C Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 10240x2880 s-dpi: 120 s-size: 2167x610mm (85.31x24.02") s-diag: 2251mm (88.63") Monitor-1: DP-1 mapped: DisplayPort-0 pos: right model: BenQ PD3200Q serial: res: 5120x2880 hz: 60 dpi: 184 size: 708x399mm (27.87x15.71") diag: 813mm (32") modes: max: 2560x1440 min: 720x400 Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: primary,left model: Samsung U32R59x serial: res: 5120x2880 hz: 60 dpi: 187 size: 697x392mm (27.44x15.43") diag: 800mm (31.5") modes: max: 3840x2160 min: 720x400 API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi inactive: gbm,wayland API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.2.0-devel glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (renoir LLVM 16.0.3 DRM 3.57 6.8.0-45-generic) device-ID: 1002:1636 Info: Memory: total: 32 GiB note: est. available: 30.77 GiB used: 11.22 GiB (36.5%) Processes: 371 Power: uptime: 8h 52m states: freeze,mem suspend: deep wakeups: 0 hibernate: disabled Init: systemd v: 255 target: graphical (5) default: graphical Compilers: gcc: 13.2.0 alt: 11/12 Client: Cinnamon v: 6.2.9 inxi: 3.3.34

[Photon89]

@gandalfmeister

screenshots then work

Are they correctly scaled, that is, the correct part of the screen is captured?

[gandalfmeister]

@gandalfmeister

screenshots then work

Are they correctly scaled, that is, the correct part of the screen is captured?

I'm afraid i didn't check the scaling.. but yes the correct part of the screen was captured.

[Photon89]

That's good news! Unfortunately, I can't take care of it any time soon, but it sounds like not that hard to fix, looks like there is just some check on startup misbehaving.