Hmm… interesting and strange thing with “File” menu. I will try to reproduce that myself later. Of course I will share my working config (with regard to the menu’s in Firefox). It is no secret and not a big thing (part of the Picom learning curve). I’ve found it on an Arch forum, but it took me quite a while to find it initially. Don’t have the time now, but I will come back with that.
Update About your observations.
Ad 1 This file /usr/share/picom-conf/picom.conf.example is the template used by picom-conf to generate ~/.config/picom.conf (if it did not exist, simply by just pushing ‘Apply’). This file overrules possible other files in the chain of search directories (as desbribed in the picom man page).
Ad 2 The autostart facility offers a nice convient way of autostarting an application (sic) by placing an applications .desktop file in the /etc/xdg/autostart directory. LXQt does not verify or try to restart those applications. That is what Modules are doing. It is totally other thing.
Ad 3 Correct. What you should worry about is that the current template file used by picom-conf (in Plucky) differs substantially from the sample configuration file provided by the picom project itself. The latter is using another mechanism, and contains rules. This is according to the picom project itself the preferred way to configure picom. You can read all about this at the picom project website .
Ad 4 I had the same problem. Well, at first I just noticed that before dragging a window. After dragging, the window did not remove itself correctly (at the original location the screen remained as a phantom). I think the two things are related somehow. After a while it all works fine. Strange. Never seen it before in a VM.
Removing menu borders in Firefox (on picom)
The fix for removing the strange border around menus in Firefox is as follows (based on the old config format as currently produced in Plucky by picom-conf):
Best replace (in the template file /usr/share/picom-conf/picom.conf.example) the following fragment:
shadow-exclude = [
“name = ‘Notification’”,
“class_g = ‘Conky’”,
“class_g ?= ‘Notify-osd’”,
“class_g = ‘Cairo-clock’”,
“_GTK_FRAME_EXTENTS@:c”
];
with
shadow-exclude = [
“name = ‘Notification’”,
“class_g = ‘Conky’”,
“class_g ?= ‘Notify-osd’”,
“class_g = ‘Cairo-clock’”,
“class_g = ‘firefox_firefox’”,
“_GTK_FRAME_EXTENTS@:c”
];
This should do the trick (after first removing an already generated ~/.config/picom.conf file). The :c could be removed from the last element, because it is not needed anymore (in neither case in the file b.t.w.).
For the interested reader: the added attribute class_g refers to a very low level item from the X Window System (the second part of so called WM_CLASS(STRING) attribute), which on Lubuntu’s snap instance happens to be this value. Thanks to xprop I discovered this.
Should the Lubuntu picom maintainers eventually decide to abolish the old configuration file format (as produced by picom-conf), another solution is needed eventually. That is documented well on the internet.
IMNSHO Power users will not need or use picom-conf.
Ad nauseum perhaps
I hope you are aware of the existence of locate (from the plocate package) . If its search index is up to date (# updatedb), it works easier and quicker than find.
Thunderbird
Thunderbird has the same issue with picom. In this case, with the snap install, the following needs to be added as well:
“class_g = ‘thunderbird_esr’”,
directly after the other addition.
Who’s next?
BTW minimal installation
Picom and picom-conf are not by default provided in this profile.
Extra at Ad 2
For me, adding the magic line X-LXQt-Module=true to file /etc/xdg/autostart/picom.desktop was sufficient to chang picom from autostart to a proper module. No need to reboot, only logging out and in did the trick.
