How to turn off the root menu entirely

[ArrayBolt3]

I'm attempting to use labwc with greetd and wlgreet to provide a login screen. The default compositor wlgreet uses is Sway, but I don't want to have both Sway and labwc installed on my system, so I've hacked together some simple config to get things to work with labwc instead. Unfortunately, it looks like the wlgreet application does not cover the entire compositor screen like a "desktop" such as pcmanfm-qt (in desktop mode) would do. As a result, I can access the labwc root menu from the login screen:

Obviously this isn't something I'd expect to be able to do at a login screen, so I'm wondering if there's any good way to make this go away without having to use a "real" desktop.

(Also, somewhat of a tangential question, but are there any unexpected ways of gaining code execution from a labwc session using purely default configuration (no config file)? It's documented that Super+Enter will pull up a terminal, but that doesn't seem to do anything on my VM, presumably because I haven't configured a terminal into labwc and don't have whatever terminal labwc considers the "default" installed. I'm going to be reading through the docs, but figured I may as well ask here too just in case.)

[tokyo4j]

You can overwrite the mousebind for Root mouse context with an empty action list.

Here's our default configuration:

<labwc_config>
  <mouse>
    <context name="Root">
      <mousebind button="Left" action="Press">
        <action name="ShowMenu" menu="root-menu" />
      </mousebind>
    </context>
  </mouse>
</labwc_config>

...and you can disable the root menu with this:

<labwc_config>
  <mouse>
    <context name="Root">
      <mousebind button="Left" action="Press" />
    </context>
  </mouse>
</labwc_config>

(Also, somewhat of a tangential question, but are there any unexpected ways of gaining code execution from a labwc session using purely default configuration (no config file)? It's documented that Super+Enter will pull up a terminal, but that doesn't seem to do anything on my VM, presumably because I haven't configured a terminal into labwc and don't have whatever terminal labwc considers the "default" installed. I'm going to be reading through the docs, but figured I may as well ask here too just in case.)

You use labwc -s [command] to launch labwc with a startup command. Our default terminal was alacritty prioir to labwc 0.9.0 and it's now replaced our wrapper command lab-sensible-terminal (whose name came from i3-sensible-terminal) that tries to execute a terminal from a list including alacritty, foot, xfce4-terminal, konsole etc.

[ArrayBolt3]

Thank you!

[johanmalm]

I'm curious now. If you run with pcmanfm-qt --desktop, could you interact with that desktop (like bringing up a context menu on an icon) whilst wlgreet is running.

From a design perspective, my initial reaction is that it would make sense for wlgreet layer-shell surfaces to fill the entire output (all outputs) to prevent pointer interactions with anything other than wlgreet.

[ArrayBolt3]

I'm curious now. If you run with pcmanfm-qt --desktop, could you interact with that desktop (like bringing up a context menu on an icon) whilst wlgreet is running.

I'll find out :) Sounds like a fun experiment.

[ArrayBolt3]

Well, I can't bring up a context menu, but I can drag a selection rectangle if I run pcmanfm-qt in desktop mode in the greeter session (which also shows what area of the screen the wlgreet display takes):