#1 2024-05-15 14:50:48

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,640

flameshot and labwc

flameshot has an error when starting the program from the waybar (into which it integrates correctly).

   

in the "Environment" section:

...
MOZ_ENABLE_WAYLAND=1
VIEB_ENABLE_WAYLAND=1
QT_QPA_PLATFORMTHEME=qt6ct
FLAMESHOT_ENABLE_WAYLAND=1
...
XDG_CURRENT_DESKTOP=wlroots
...

Does anyone know what to do? 

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,032

Website

Re: flameshot and labwc

See if something here is useful...

https://github.com/flameshot-org/flames … support.md

And, of course...

https://packages.debian.org/sid/xdg-desktop-portal-wlr

I use grim, which didn't need a config. I don't need slurp so I just did a bind to the Print key. This is in hyprland...

bind = , Print, exec, sleep 5 && grim scrot.png

I'll check out flameshot though! I'll post back and report how it went.

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,640

Re: flameshot and labwc

See if something here is useful...

https://github.com/flameshot-org/flames … support.md

And, of course...

https://packages.debian.org/sid/xdg-desktop-portal-wlr

I use grim, which didn't need a config. I don't need slurp so I just did a bind to the Print key. This is in hyprland...

bind = , Print, exec, sleep 5 && grim scrot.png

I'll check out flameshot though! I'll post back and report how it went.

Thanks for your contribution. I still have to read the link...

I wanted flameshot because I can use it to make certain areas of the image unrecognizable etc. In addition, it has few dependencies unlike shutter-on-wayland and is qt5.

Brilliant idea with the key binding! Thanks for that! 

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,032

Website

Re: flameshot and labwc

So running this in a terminal works (or change full to launcher or to your argument/option of choice)...

XDG_CURRENT_DESKTOP=sway flameshot full

Copying org.flameshot/Flameshot.desktop from /usr/share/applications to ~/.local/share/applications and editing the 'Exec=' line to...

Exec=env XDG_CURRENT_DESKTOP=sway flameshot full

... also works to launch it from a main menu like jgmenu.

Hope that helps.

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,640

Re: flameshot and labwc

^Thank you for your efforts!

I can tell you that it is not working.
I'm sure there are still 'settings' I haven't tried / found yet.

labwc is not sway. 

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,032

Website

Re: flameshot and labwc

I know, but setting desktop=sway made it run for me in Hyprland/wlroots.

Post your terminal output.

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,640

Re: flameshot and labwc

I know, but setting desktop=sway made it run for me in Hyprland/wlroots.

Post your terminal output.

?
I don't understand. Please be more specific... 

---------------

What I keep bumping into with this topic and what I don't understand:
https://labwc.github.io/

Labwc only understands wayland-protocols & wlr-protocols, and it cannot be controlled with dbus, sway/i3-IPC or other technology. The reason for this is that we believe that custom IPCs and protocols create a fragmentation that hinders general Wayland adoption.

Then dbus, and its settings ala sway on labwc don't work at all. Or do you see it differently?

Last edited by unklar (2024-05-22 06:59:54)

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,032

Website

Re: flameshot and labwc

In a terminal, run...

XDG_CURRENT_DESKTOP=sway flameshot full

... and post the output. Create an issue on labwc's git to get some better insight than what I have.

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,640

Re: flameshot and labwc

In a terminal, run...

XDG_CURRENT_DESKTOP=sway flameshot full

... and post the output. Create an issue on labwc's git to get some better insight than what I have.

it gives me the save dialog.

Nevertheless, 0 is output when I send the echo command afterwards... 

flameshot full | echo $?
0
flameshot: error: Unable to detect desktop environment (GNOME? KDE? Sway? ...)
flameshot: error: Hint: try setting the XDG_CURRENT_DESKTOP environment variable.
flameshot: error: Unable to capture screen
flameshot: info: Screenshot aborted.

  or

flameshot gui | echo $?
0
flameshot: error: Unable to detect desktop environment (GNOME? KDE? Sway? ...)
flameshot: error: Hint: try setting the XDG_CURRENT_DESKTOP environment variable.
flameshot: error: Unable to capture screen
flameshot: error: Unable to capture screen
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
flameshot: info: Screenshot aborted.

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,032

Website

Re: flameshot and labwc

I'm using gdm3 as my display manager, maybe that's the difference?

So, for you, I built labwc from source...

You can see dbus-daemon is running.

I built flameshot from source, ran 'flameshot full'...

❯ flameshot full
flameshot: warning: If the USE_WAYLAND_GRIM option is not activated, the dbus protocol will be used. It should be noted that using the dbus protocol under wayland is not recommended. It is recommended to recompile with the USE_WAYLAND_GRIM flag to activate the grim-based general wayland screenshot adapter
^C

GUI didn't open.

Made no changes, ran 'XDG_CURRENT_DESKTOP=sway flameshot full'...

Both scrots taken with grim. Now I have to uninstall this fugly Qt GUI. Here's the flameshot scrot, which by default was saved to ~/Pictures/Screenshots...

Nice that labwc made a default autostart file that both set swaybg and started waybar. Very cool. ~/.config/labwc/autostart...

swaybg -i ~/Pictures/wall.png >/dev/null 2>&1 &
waybar >/dev/null 2>&1 &

I'm going to keep this labwc session and see what I can do with it. I'm definitely going to bin flameshot, though.

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,032

Website

Re: flameshot and labwc

Ugh, no uninstall script, manual uninstall. Seriously, screw flameshot.

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,640

Re: flameshot and labwc

I'm using gdm3 as my display manager, maybe that's the difference?

I don't use one. I start from tty1 as suggested by @malm by entering 'labwc'.

I built flameshot from source, ran 'flameshot full'...

Thank you sir! What an honor that you did that.

This terminal message is highly interesting. I must make a note of the flag.

Nice that labwc made a default autostart file that both set swaybg and started waybar. Very cool. ~/.config/labwc/autostart...

These five configuration files make labwc very clear. I have not edited/used 'themerc' yet. And, I always have the feeling that labwc 'feels good'.

I'm going to keep this labwc session and see what I can do with it. I'm definitely going to bin flameshot, though.

Keep labwc. @johnraff will thank you for having a team member who has practically dealt with labwc already.