bunsen-configs-wayland-plugin available for testing

johnraff · Yesterday 04:24:14

hhh wrote:

johnraff wrote:
But there doesn't seem to be a way on Wayland to do a screenshot of the "active window". I use that a lot, but it seems to be very difficult to do on Wayland.
grimshot, a helper for grim and slurp...
https://packages.debian.org/unstable/grimshot
EXAMPLES
An example usage pattern is to add these bindings to your sway config:
# Screenshots:
# Super+P: Current window
# Super+Shift+p: Select area
# Super+Alt+p Current output
# Super+Ctrl+p Select a window
bindsym Mod4+p exec grimshot save active
bindsym Mod4+Shift+p exec grimshot save area
bindsym Mod4+Mod1+p exec grimshot save output
bindsym Mod4+Ctrl+p exec grimshot save window
https://manpages.debian.org/testing/gri … .1.en.html
It has a dependency on sway, but I think that's fine if it works with labwc and the other wlroots compositors. The sway package is pretty light (977 kB), that's a bit bigger than labwc, I think. Make it an optional package if it's an issue of size? I haven't tested this yet, but it looks promising.

I just installed grimshot and while it takes wholescreen and "select area" screenshots OK, the "active" and "window" targets don't seem to work. I guess you need to be running sway not labwc.
Maybe as XFCE said, it can't currently be done with wlroots?

I had a look at the code - it's a shell script - and it calls swaymsg to get the active window, so I guess that means sway has to be running.

Last edited by johnraff (Yesterday 04:29:51)

hhh · Yesterday 04:31:09

^ Bummer. I found this and it's response, it's a quick read...

https://github.com/labwc/labwc/discussions/3299

We can ask for some info from @malm. I now summon @malm. Appear!

unklar · Yesterday 08:20:11

^I've got it now

pgrep -a labwc

the same result

1279 /usr/bin/labwc --config-dir /home/unklar/.config/bunsen/labwc --startup /usr/lib/bunsen/configs/bunsen-autostart

I removed the directory ~/.config/labwc with the 4 files (autostart, environment, menu.xml and rc.xml).

In my opinion there is a mixture. still in ~/.config/bunsen/autotart-wayland and ~/.config/bunsen/environment-wayland
to
~/.config/bunsen/labwc/autostart and ~/.config/bunsen/labwc/environment

I assume I should remove these too because they are identical to the files from the removed ~/.config/labwc directory?

PS:if it is useful

❯ bl-xdg-autostart --list
[ ] Labwc Generate Menu
	  File: /home/unklar/.config/autostart/lab-gen-menu.desktop
	  Executes: lab-gen-menu
	* Excluded by: Hidden

[ ] Zwischenablage
	  File: /home/unklar/.config/autostart/xfce4-clipman-plugin-autostart.desktop
	  Executes: xfce4-clipman
	* Excluded by: OnlyShowIn (XFCE, X-Cinnamon)

[ ] Shutter
	  File: /home/unklar/.config/autostart/shutter.desktop
	  Executes: shutter
	* Excluded by: Hidden

[ ] xbindkeys
	  File: /home/unklar/.config/autostart/xbindkeys.desktop
	  Executes: xbindkeys_autostart
	* Excluded by: Hidden

[ ] picom
	  File: /home/unklar/.config/autostart/picom.desktop
	  Executes: picom
	* Excluded by: Hidden

[ ] Sicherheitsdienst
	  File: /etc/xdg/autostart/gnome-keyring-secrets.desktop
	  Executes: /usr/bin/gnome-keyring-daemon --start --components=secrets
	* Excluded by: OnlyShowIn (GNOME, Unity, MATE)

[*] Xfce Bildschirmschoner
	  File: /etc/xdg/autostart/bunsen-exit-xfce4-screensaver.desktop
	  Executes: xfce4-screensaver

[*] Netzwerk-Manager-Applet
	  File: /etc/xdg/autostart/nm-applet.desktop
	  Executes: nm-applet

[ ] SSH-Schlüsselagent
	  File: /etc/xdg/autostart/gnome-keyring-ssh.desktop
	  Executes: /usr/bin/gnome-keyring-daemon --start --components=ssh
	* Excluded by: OnlyShowIn (GNOME, Unity, MATE)

[*] User folders update
	  File: /etc/xdg/autostart/xdg-user-dirs.desktop
	  Executes: xdg-user-dirs-update

[*] bl-xss-lock
	  File: /etc/xdg/autostart/bl-xss-lock.desktop
	  Executes: bl-xss-lock

[ ] Xfce Bildschirmschoner
	  File: /etc/xdg/autostart/xfce4-screensaver.desktop
	  Executes: xfce4-screensaver
	* Excluded by: OnlyShowIn (XFCE)

[*] AT-SPI D-Bus Bus
	  File: /etc/xdg/autostart/at-spi-dbus-bus.desktop
	  Executes: /usr/libexec/at-spi-bus-launcher --launch-immediately

[ ] Zertifikat-/Schlüsselverwahrung
	  File: /etc/xdg/autostart/gnome-keyring-pkcs11.desktop
	  Executes: /usr/bin/gnome-keyring-daemon --start --components=pkcs11
	* Excluded by: OnlyShowIn (GNOME, Unity, MATE)

[*] PolicyKit-Legitimationsagent
	  File: /etc/xdg/autostart/polkit-mate-authentication-agent-1.desktop
	  Executes: /usr/libexec/polkit-mate-authentication-agent-1

[ ] Energieverwaltung
	  File: /etc/xdg/autostart/xfce4-power-manager.desktop
	  Executes: xfce4-power-manager
	* Excluded by: OnlyShowIn (XFCE)

[*] Blueman Applet
	  File: /etc/xdg/autostart/blueman.desktop
	  Executes: blueman-applet

[ ] Xfce Benachrichtigungsdienst
	  File: /etc/xdg/autostart/xfce4-notifyd.desktop
	  Executes: sh -c "systemctl --user start xfce4-notifyd.service 2>/dev/null || exec /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd"
	* Excluded by: OnlyShowIn (XFCE)

Last edited by unklar (Yesterday 08:56:50)

unklar · Yesterday 08:28:53

johnraff wrote:

unklar wrote:
Calling gmrun in the terminal results in the image below.
https://i.postimg.cc/1VwGp9SC/20260807- … s-grim.png
That looks OK. Can you run commands there?

Yes, I can do that.

So Alt+F3 brings up something that looks like dmenu, but different colours? That will be tofi.
But clicking one of the items does nothing??

And can you click on the items in that list to launch them?

I can click on it, none of the applications start.

johnraff · Today 00:35:51

unklar wrote:

johnraff wrote:
unklar wrote:
Calling gmrun in the terminal results in the image below.
https://i.postimg.cc/1VwGp9SC/20260807- … s-grim.png
That looks OK. Can you run commands there?
Yes, I can do that.

OK so gmrun works.

So Alt+F3 brings up something that looks like dmenu, but different colours? That will be tofi.
But clicking one of the items does nothing??
And can you click on the items in that list to launch them?
I can click on it, none of the applications start.

Hmm... that needs looking into.

johnraff · Today 00:49:33

unklar wrote:

^I've got it now
pgrep -a labwc
the same result
1279 /usr/bin/labwc --config-dir /home/unklar/.config/bunsen/labwc --startup /usr/lib/bunsen/configs/bunsen-autostart
I removed the directory ~/.config/labwc with the 4 files (autostart, environment, menu.xml and rc.xml).

It should not be necessary to remove ~/.config/labwc. Launched with the above command, labwc should ignore that directory, but if you go back to a non-BL session just calling "labwc" then those files will be used, so you can have both sessions configured.

In my opinion there is a mixture. still in ~/.config/bunsen/autotart-wayland and ~/.config/bunsen/environment-wayland
to
~/.config/bunsen/labwc/autostart and ~/.config/bunsen/labwc/environment

Yes there seems to be a possible issue whith labwc reading ~/.config/bunsen/labwc/autostart even if it's given a separate --startup script to run. But that file does not exist unless you put it there! bunsen-configs-wayland-plugin puts neither autostart nor environment in ~/.config/bunsen/labwc/ Just delete those files if you have them. The "vanilla" labwc session does not use them, it uses files in ~/.config/labwc. I think I'll put empty files there for autostart and environment with comments explaining the situation and what files BL users should edit.

I assume I should remove these too because they are identical to the files from the removed ~/.config/labwc directory?

Well, yes. But I'm puzzled how those files got into ~/.config/bunsen/labwc/ anyway.

PS:if it is useful

❯ bl-xdg-autostart --list
[ ] Labwc Generate Menu
	  File: /home/unklar/.config/autostart/lab-gen-menu.desktop
	  Executes: lab-gen-menu
	* Excluded by: Hidden
...etc...

That looks OK I think.

Last edited by johnraff (Today 01:27:54)

johnraff · Today 06:01:29

johnraff wrote:

...there seems to be a possible issue with labwc reading ~/.config/bunsen/labwc/autostart even if it's given a separate --startup script to run. But that file does not exist unless you put it there! bunsen-configs-wayland-plugin puts neither autostart nor environment in ~/.config/bunsen/labwc/ Just delete those files if you have them. The "vanilla" labwc session does not use them, it uses files in ~/.config/labwc. I think I'll put empty files there for autostart and environment with comments explaining the situation and what files BL users should edit.

Now I think about it, it shouldn't be seen as a bug that labwc checks the config-dir it's been given for autostart and environment files along with rc.xml and menu.xml, even if our startup script specifies ~/.config/bunsen/autostart-wayland and ~/.config/bunsen/environment-wayland.

I've put this in ~/.config/bunsen/labwc/autostart:

# DO NOT USE THIS FILE

# The Bunsenlabs Wayland autostart file is
# ~/.config/bunsen/autostart-wayland
#
# While labwc will also refer to this file,
# putting commands here will cause unnecessary confusion.
#
# To edit your startup session, please edit:
# ~/.config/bunsen/autostart-wayland

and a similar message in ~/.config/bunsen/labwc/environment

#21 Yesterday 04:24:14

Re: bunsen-configs-wayland-plugin available for testing

#22 Yesterday 04:31:09

Re: bunsen-configs-wayland-plugin available for testing

#23 Yesterday 08:20:11

Re: bunsen-configs-wayland-plugin available for testing

#24 Yesterday 08:28:53

Re: bunsen-configs-wayland-plugin available for testing

#25 Today 00:35:51

Re: bunsen-configs-wayland-plugin available for testing

#26 Today 00:49:33

Re: bunsen-configs-wayland-plugin available for testing

#27 Today 06:01:29

Re: bunsen-configs-wayland-plugin available for testing

Board footer