flameshot-org
Logout and black screen trying to save/copy screen to clipboard
Flameshot Version
Flameshot v12.1.0 () Compiled with Qt 5.15.10 linux: 6.8.0-55-generic org.kde.Platform: 5.15-23.08
Installation Type
Flatpak from Flathub
Operating System type and version
Linux Mint 22.1
Description
When i take a screenshot with Flameshot adn try to copy it to my clipboard, or either save it as a file on my computer, the screen goes black and i'm sent back to the user session login screen of Mint. When i type in my password and enter back my session, the screen is black, nothing seemingly responds, and all i can do is force-shutdown my computer and restart it.
I've found an existing issue that seems to relate to mine in terms of what happens : #3125
Steps to reproduce
- Start Flameshot using the "Print Screen" button shortcut:
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=/app/bin/flameshot org.flameshot.Flameshot gui - Select an area of the screen i want to screenshot
- Either save it as file or copy to clipboard
- Bug occurs: you're sent back to the session logging screen
- Try to enter your previous session
- Black screen that shows the mouse moving, but nothing else
Screenshots or screen recordings
No response
System Information
Part of the info removed for concision:
System:
Kernel: 6.8.0-55-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.41 wm: xfwm4 v: 4.18.0 with: xfce4-panel vt: 7
dm: LightDM v: 1.30.0 Distro: Linux Mint 22.1 Xia base: Ubuntu 24.04 noble
Machine:
Type: Laptop System: LENOVO product: 20AMS7X300 v: ThinkPad X240 serial: <superuser required>
Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20AMS7X300 v: SDK0E50510 WIN serial: <superuser required>
part-nu: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240 uuid: <superuser required>
UEFI-[Legacy]: LENOVO v: GIET76WW (2.26 ) date: 08/27/2014
CPU:
Info: dual core model: Intel Core i3-4030U bits: 64 type: MT MCP smt: enabled arch: Haswell
rev: 1 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 1896 min/max: 800/1900 cores: 1: 1896 2: 1896 3: 1896 4: 1896 bogomips: 15165
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics vendor: Lenovo ThinkPad X240 driver: i915
v: kernel arch: Gen-7.5 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:0a16 class-ID: 0300
Device-2: Lite-On Integrated Camera driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
lanes: 1 bus-ID: 2-8:4 chip-ID: 04ca:7035 class-ID: 0e02
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 compositor: xfwm4 v: 4.18.0
driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0
screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: BOE Display 0x05e0 res: 1366x768 hz: 60 dpi: 125
size: 277x156mm (10.91x6.14") diag: 318mm (12.5") modes: 1366x768
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus device: 1 drv: swrast
gbm: drv: crocus surfaceless: drv: crocus x11: drv: crocus inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.8-1ubuntu1~24.04.1 glx-v: 1.4
direct-render: yes renderer: Mesa Intel HD Graphics 4400 (HSW GT2) device-ID: 8086:0a16
API: Vulkan v: 1.3.275 layers: 7 surfaces: xcb,xlib device: 0 type: integrated-gpu driver: N/A
device-ID: 8086:0a16 device: 1 type: cpu driver: N/A device-ID: 10005:0000
Info:
Memory: total: 8 GiB note: est. available: 7.45 GiB used: 2.54 GiB (34.1%)
Processes: 268 Power: uptime: 5h 24m states: freeze,mem,disk suspend: deep wakeups: 2
hibernate: platform Init: systemd v: 255 target: graphical (5) default: graphical
Compilers: gcc: 13.3.0 alt: 11/12 Client: Unknown python3.12 client inxi: 3.3.34
Are you using fractional scaling?
No, i don't.
In this picture here, "Échelle" is Scaling.
And here at the bottom, it says Windows scaling and it's set to No Scaling
I do have this activated though in my Appearances settings, which might correspond ? It is Personalized DPI parameter, it's activated and it's been set to 96.
I did some quick testing following the above message since i had some time.
Changing the DPI setting i had concerns about did not change anything. Instead, the problem seems to come from the command i used for my shortcut /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=/app/bin/flameshot org.flameshot.Flameshot gui : everytime this is used, saving the file fails. On the other hand, I tried opening Flameshot as any other app clicking my way there from the Whisker menu, and it succeeded in saving the file, so it's may not be inherent to Flameshot.
I've had issues with previous Flatpak apps failing to save files, and i don't remember the gist of it, i think i replaced a daemon with another or something, and everything worked well from then on. Maybe my workaround somehow messes with Flameshot's way of saving files ? Or maybe it's the command line i use which is somehow faulty, or brings on a faulty version of Flameshot ?
When you open the app through the Whisker menu is it still using the flatpak version?
When you open the app through the Whisker menu is it still using the flatpak version?
Yes. Here is the command run when i run it from there: /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=/app/bin/flameshot org.flameshot.Flameshot
Maybe it's just the gui argument then ?
Definitely the gui argument there: i tried changing my shortcut by removing it, and while pressing the shortcut didn't take me directly to the area selection screen (as expected), prompting Flameshot to do so from the bottom right icon did not trigger any crash or bug.
I cannot replicate this in a VM. I'm wondering if its like the closed issues you referenced where it was a hardware specific problem.
https://github.com/user-attachments/assets/19b24d90-4f2d-4313-b80b-9ffbdd8b46b3
I compared both our setups as provided by various commands, and the only "similarities" that could, maybe, slightly matter were these:
On my side Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 compositor: xfwm4 v: 4.18.0
On their side Display: x11 server: X.Org v: 1.21.1.3 driver: X:
But i don't even know if it's worth mentioning 🤷
It seemed to be a driver issue in their occurrence. Could you help me a bit and direct to the type of driver that might interact with Flameshot, so i can test them up and report back ? I'm not sure where to start from. Or give me hints as to what i could do to help find the root cause of this issue.
I'm really not sure since I can't replicate it.
when you get kicked to the black screen you could maybe drop to a tty and look at dmesg or journalctl.
What do you mean by "drop to a tty" ? When i experience te black screen, the mouse is visible and i can move it, but i can't type anything or do any meaningful action (as far as i can tell). So i can't look at these two commands you recommand.
Would it be possible for me to investigate what's happening in my previous session from a second session ? I suspect whatever happens triggers some kind of loop that the computer can't get out of, and forcibly forces the user out to the session logging screen (for whatever reason).
Usually ctrl + alt + F2
(Or f3 or f4) will switch to a new tty with no graphics.
I think in managed to get something valuable.
I've had issues with previous Flatpak apps failing to save files, and i don't remember the gist of it, i think i replaced a daemon with another or something, and everything worked well from then on. Maybe my workaround somehow messes with Flameshot's way of saving files ?
As i previously suspected, this seems to come from dbus-broker, which i dropped in as a replacement for dbus-daemon as it wasn't working well with flatpaks trying to access/save files.
Below is a selection from journalctl -r, you'll have to browse it from the bottom up as it's in reverse order.
mai 15 10:55:53 Baluchon systemd-logind[837]: Session c1 logged out. Waiting for processes to exit.
mai 15 10:55:53 Baluchon systemd[1113]: xdg-document-portal.service: Failed with result 'exit-code'.
mai 15 10:55:53 Baluchon systemd[1113]: xdg-document-portal.service: Main process exited, code=exited, status=20/n/a
mai 15 10:55:53 Baluchon lightdm[1105]: pam_unix(lightdm-autologin:session): session closed for user crapahute
mai 15 10:55:53 Baluchon systemd[1113]: dbus-broker.service: Failed with result 'exit-code'.
mai 15 10:55:53 Baluchon systemd[1113]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
mai 15 10:55:53 Baluchon systemd[1]: run-user-1000-doc.mount: Deactivated successfully.
mai 15 10:55:53 Baluchon systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully.
mai 15 10:55:53 Baluchon dbus-broker-launch[1139]: Exiting due to fatal error: -131
mai 15 10:55:53 Baluchon dbus-broker-launch[1139]: main @ ../src/launch/main.c +178
mai 15 10:55:53 Baluchon dbus-broker[1359]: Dispatched 479 messages @ 18(±24)μs / message.
mai 15 10:55:53 Baluchon dbus-broker-launch[1139]: run @ ../src/launch/main.c +152
mai 15 10:55:53 Baluchon dbus-broker-launch[1139]: ERROR launcher_run @ ../src/launch/launcher.c +1462: Return code 1
mai 15 10:55:53 Baluchon dbus-broker-launch[1139]: Caught SIGCHLD of broker.
mai 15 10:55:53 Baluchon gvfsd[1304]: A connection to the bus can't be made
mai 15 10:55:53 Baluchon systemd[1113]: xdg-permission-store.service: Failed with result 'exit-code'.
mai 15 10:55:53 Baluchon systemd[1113]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE
mai 15 10:55:52 Baluchon unknown[1361]: Name org.xfce.Xfconf lost on the message dbus, exiting.
mai 15 10:55:52 Baluchon systemd[1113]: flatpak-session-helper.service: Failed with result 'exit-code'.
mai 15 10:55:52 Baluchon systemd[1113]: flatpak-session-helper.service: Main process exited, code=exited, status=1/FAILURE
mai 15 10:55:53 Baluchon xfce4-notifyd[1528]: Un autre démon de notification est en cours d’exécution, arrêt.
mai 15 10:55:53 Baluchon xfce4-notifyd[1528]: Un autre démon de notification est en cours d’exécution, arrêt.
mai 15 10:55:52 Baluchon polkitd[826]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.57, object path /org/gnome/PolicyKit1/AuthenticationAg>
mai 15 10:55:52 Baluchon systemd[1]: [email protected]: Deactivated successfully.
mai 15 10:55:52 Baluchon gvfsd[1674]: A connection to the bus can't be made
mai 15 10:55:52 Baluchon systemd-coredump[1931]: [🡕] Process 1151 (dbus-broker) of user 1000 dumped core.
Module dbus-broker from deb dbus-broker-35-2.amd64
Stack trace of thread 1151:
#0 0x00007107dbf8b75d __strlen_avx2 (libc.so.6 + 0x18b75d)
#1 0x00005787bf8cecf8 n/a (dbus-broker + 0x1ecf8)
#2 0x00005787bf8cff11 n/a (dbus-broker + 0x1ff11)
#3 0x00005787bf8d2c7c n/a (dbus-broker + 0x22c7c)
#4 0x00005787bf8d5dfa n/a (dbus-broker + 0x25dfa)
#5 0x00005787bf8bf462 n/a (dbus-broker + 0xf462)
#6 0x00005787bf8c1c16 n/a (dbus-broker + 0x11c16)
#7 0x00005787bf8c6a5a n/a (dbus-broker + 0x16a5a)
#8 0x00005787bf8cbab0 n/a (dbus-broker + 0x1bab0)
#9 0x00005787bf8b69f9 n/a (dbus-broker + 0x69f9)
#10 0x00005787bf8b5a5f n/a (dbus-broker + 0x5a5f)
#11 0x00007107dbe2a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)
#12 0x00007107dbe2a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)
#13 0x00005787bf8b5d95 n/a (dbus-broker + 0x5d95)
ELF object binary architecture: AMD x86-64
mai 15 10:55:52 Baluchon systemd[1]: Started [email protected] - Process Core Dump (PID 1930/UID 0).
mai 15 10:55:52 Baluchon systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump.
mai 15 10:55:52 Baluchon kernel: Code: 00 00 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 <c>
mai 15 10:55:52 Baluchon kernel: dbus-broker[1151]: segfault at 0 ip 00007107dbf8b75d sp 00007ffcf83c6428 error 4 in libc.so.6[7107dbe28000+188000] likely on CPU 3 (co>
mai 15 10:55:52 Baluchon kernel: show_signal_msg: 118 callbacks suppressed
mai 15 10:55:52 Baluchon systemd-resolved[655]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.5.167.
mai 15 10:55:52 Baluchon kernel: warning: `flameshot' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
mai 15 10:55:52 Baluchon flameshot[1923]: Failed to load module "xapp-gtk3-module"
mai 15 10:55:52 Baluchon systemd[1113]: Started app-flatpak-org.flameshot.Flameshot-1912.scope.
mai 15 10:55:52 Baluchon systemd[1113]: Started dbus-:[email protected].
mai 15 10:55:52 Baluchon systemd[1113]: Created slice app-dbus\x2d:1.6\x2dorg.flameshot.Flameshot.slice - Slice /app/dbus-:1.6-org.flameshot.Flameshot.
mai 15 10:55:49 Baluchon wpa_supplicant[852]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-20 noise=9999 txrate=72200
mai 15 10:55:45 Baluchon systemd[1]: blueman-mechanism.service: Deactivated successfully.
mai 15 10:55:45 Baluchon systemd[1]: systemd-hostnamed.service: Deactivated successfully.
mai 15 10:55:45 Baluchon systemd-timesyncd[666]: Initial clock synchronization to Thu 2025-05-15 10:55:45.019970 CEST.
lines 2730-2767
mai 15 10:55:53 Baluchon xfce4-notifyd[1528]: Un autre démon de notification est en cours d’exécution, arrêt.
mai 15 10:55:52 Baluchon polkitd[826]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.57, object path /org/gnome/PolicyKit1/AuthenticationAg>
mai 15 10:55:52 Baluchon systemd[1]: [email protected]: Deactivated successfully.
mai 15 10:55:52 Baluchon gvfsd[1674]: A connection to the bus can't be made
mai 15 10:55:52 Baluchon systemd-coredump[1931]: [🡕] Process 1151 (dbus-broker) of user 1000 dumped core.
Module dbus-broker from deb dbus-broker-35-2.amd64
Stack trace of thread 1151:
#0 0x00007107dbf8b75d __strlen_avx2 (libc.so.6 + 0x18b75d)
#1 0x00005787bf8cecf8 n/a (dbus-broker + 0x1ecf8)
#2 0x00005787bf8cff11 n/a (dbus-broker + 0x1ff11)
#3 0x00005787bf8d2c7c n/a (dbus-broker + 0x22c7c)
#4 0x00005787bf8d5dfa n/a (dbus-broker + 0x25dfa)
#5 0x00005787bf8bf462 n/a (dbus-broker + 0xf462)
#6 0x00005787bf8c1c16 n/a (dbus-broker + 0x11c16)
#7 0x00005787bf8c6a5a n/a (dbus-broker + 0x16a5a)
#8 0x00005787bf8cbab0 n/a (dbus-broker + 0x1bab0)
#9 0x00005787bf8b69f9 n/a (dbus-broker + 0x69f9)
#10 0x00005787bf8b5a5f n/a (dbus-broker + 0x5a5f)
#11 0x00007107dbe2a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)
#12 0x00007107dbe2a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)
#13 0x00005787bf8b5d95 n/a (dbus-broker + 0x5d95)
ELF object binary architecture: AMD x86-64
mai 15 10:55:52 Baluchon systemd[1]: Started [email protected] - Process Core Dump (PID 1930/UID 0).
mai 15 10:55:52 Baluchon systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump.
mai 15 10:55:52 Baluchon kernel: Code: 00 00 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 <c>
mai 15 10:55:52 Baluchon kernel: dbus-broker[1151]: segfault at 0 ip 00007107dbf8b75d sp 00007ffcf83c6428 error 4 in libc.so.6[7107dbe28000+188000] likely on CPU 3 (co>
mai 15 10:55:52 Baluchon kernel: show_signal_msg: 118 callbacks suppressed
mai 15 10:55:52 Baluchon systemd-resolved[655]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.5.167.
mai 15 10:55:52 Baluchon kernel: warning: `flameshot' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
mai 15 10:55:52 Baluchon flameshot[1923]: Failed to load module "xapp-gtk3-module"
mai 15 10:55:52 Baluchon systemd[1113]: Started app-flatpak-org.flameshot.Flameshot-1912.scope.
mai 15 10:55:52 Baluchon systemd[1113]: Started dbus-:[email protected].
mai 15 10:55:52 Baluchon systemd[1113]: Created slice app-dbus\x2d:1.6\x2dorg.flameshot.Flameshot.slice - Slice /app/dbus-:1.6-org.flameshot.Flameshot.
``