pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: xfwm4 crashes on NetBSD 9.99.17 (was "Re: firefox dumping core after NetBSD upgrade")

I do not have MesaLib installed on this v/b guest at all.

I bisected xfwm4.xml to try to find out which setting was causing the
problem. I didn't bother to read it first, as the result was obvious:
~ diff -u .config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml.HIDE
--- .config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml.HIDE 2019-10-25
22:13:04.791908990 +0100
+++ .config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml  2019-10-27
14:09:13.334172740 +0000
@@ -71,7 +71,7 @@
     <property name="toggle_workspaces" type="bool" value="false"/>
     <property name="unredirect_overlays" type="bool" value="true"/>
     <property name="urgent_blink" type="bool" value="false"/>
-    <property name="use_compositing" type="bool" value="true"/>
+    <property name="use_compositing" type="bool" value="false"/>
     <property name="workspace_count" type="int" value="4"/>
     <property name="wrap_cycle" type="bool" value="true"/>
     <property name="wrap_layout" type="bool" value="true"/>

So the problem is that on first invocation xfce4 sets use_composing to
true, even if composing is not available or not functional.

On Sun, 27 Oct 2019 at 02:24, <> wrote:
> On Sun, Oct 27, 2019 at 01:30:48AM +0100, Chavdar Ivanov wrote:
> > In my case its also swrast_dri, VirtualBox host. I haven't recently
> > tried xfce4 on a real hardware with intel, I might di that later.
> I could finally reproduce a crash.
> And it went away when I pkg_delete'd MesaLib. I wonder if our issue is
> mixing two libGL implementations. That's a minefield.


Home | Main Index | Thread Index | Old Index