User-Agent: Opera/9.21 (X11; Linux i686; U; de) Build Identifier: If I disable loading the Composite extension, the "Compositor" tab still is accessible and even usable within the window manager tweaks. But of course, the compositor won’t work this way. Thus, the tab should be hidden in this case. Reproducible: Always Steps to Reproduce: 1. Disable loading the Composite extension 2. Open window manager tweaks Actual Results: The "Compositor" tab is visible. Expected Results: It should not.
This is already the case, the compositor tab is not shown if the display doesn't support the composite extension.
What does that give? xdpyinfo | grep Composite Did you restart gdm after changing the option in xorg.conf? Do you have this in your xorg.conf: Section "Extensions" Option "Composite" "Disable" EndSection
> What does that give? > > xdpyinfo | grep Composite No output. > Did you restart gdm after changing the option in xorg.conf? Yes. > Do you have this in your xorg.conf: > > Section "Extensions" > Option "Composite" "Disable" > EndSection Yes, but I commented the Option out, thus it should not be enabled. Killing and starting xfwm4 from a terminal proves this: > ** (xfwm4:17164): WARNING **: The display does not support the XComposite extension. > > ** (xfwm4:17164): WARNING **: Compositing manager disabled. The tab is still accessible.
> > ** (xfwm4:17164): WARNING **: Compositing manager disabled. > > The tab is still accessible. > Well, it works here, and has always. Can you check if you don't have an older version of the wmtweaks plugin around?
(In reply to comment #4) > > > ** (xfwm4:17164): WARNING **: Compositing manager disabled. > > > > The tab is still accessible. > > > > Well, it works here, and has always. Can you check if you don't have an older > version of the wmtweaks plugin around? Uhm, not sure what you mean by that. Do you mean that I should check if the wmtweaks_plugin.so is outdated? It isn’t.
Oh I know what you do wrong... I bet you force the compositor with --compositor=on in the session. And of course, if forced, it's considered active (that's the logic of forcing an option, isn't it?) Now, since composite extension is not supposed to vanish during the lifetime of an X session (it's an X thingy, so it stays on or off as long as X is not restarted), restarting xfwm4 makes obviously no difference... Unless you also restart xfce-mcs-manager. So Can you check if you do you force the --compositor option in your session? If you are using xfce4-session, check in .cache/sessions/xfce4-session-`hostname -f`\:0
(In reply to comment #6) > Oh I know what you do wrong... I bet you force the compositor with > --compositor=on in the session. Exactly. And the line looks a bit weird: > $ ps aux | grep [x]fwm4 > ashura 4715 0.0 1.0 24620 10648 ? S 19:41 0:03 xfwm4 --compositor=on--daemon --sm-client-id 117f000001000115304131500000182230001 --display :0.0 The missing space between the --compositor and --daemon line definitely looks wrong. > And of course, if forced, it's considered active (that's the logic of forcing > an option, isn't it?) Yep, makes sense now. > If you are using xfce4-session, check in > .cache/sessions/xfce4-session-`hostname -f`\:0 There it is. Is it alright to edit this file manually?
(In reply to comment #7) > There it is. Is it alright to edit this file manually? From a terminal, killall xfwm4; sleep 3; xfwm4& Then logout saving your session and you'll be safe.
(In reply to comment #8) > (In reply to comment #7) > > > There it is. Is it alright to edit this file manually? > > From a terminal, > > killall xfwm4; sleep 3; xfwm4& > > Then logout saving your session and you'll be safe. Heh, that’s why I asked. I don’t want to logout ATM but do this while everything is running. I went ahead now, edited this file, killed both xfwm4 and xfce-mcs-manager and restarted both. Works. The "Compositor" tab is gone now. Thanks for your time.