On Fri, 2019-11-01 at 01:49 -0400, David H. Gutteridge wrote:
> On Tue, 2019-10-29 at 19:52 -0400, David H. Gutteridge wrote:
> > On Tue, 2019-10-29 at 10:38 +, Chavdar Ivanov wrote:
> > > I've tested xfce4 - a few days old build from -current pkgsrc -
> > > now
> > > on
> > > real hardware
I don't remove xfwm4.xml, just set use_compositing setting to no. Then
I am able to start xfce4 without a problem many times. EVen if I
delete that file - out of xfce4 - then startxfce4, it starts first
time; on exit use_compositing is set to true, subsequent startxfce4
starts, but without xfwm4
On Tue, 2019-10-29 at 19:52 -0400, David H. Gutteridge wrote:
> On Tue, 2019-10-29 at 10:38 +, Chavdar Ivanov wrote:
> > I've tested xfce4 - a few days old build from -current pkgsrc - now
> > on
> > real hardware with functional dri2. I get the same as with the
> > VirtualBox client - I have
On Tue, 2019-10-29 at 10:38 +, Chavdar Ivanov wrote:
> I've tested xfce4 - a few days old build from -current pkgsrc - now on
> real hardware with functional dri2. I get the same as with the
> VirtualBox client - I have to disable compositing to get xfwm4
> working. At the same time glmark2
I've tested xfce4 - a few days old build from -current pkgsrc - now on
real hardware with functional dri2. I get the same as with the
VirtualBox client - I have to disable compositing to get xfwm4
working. At the same time glmark2 returns the usual or close to
results.
The other thing is -
"David H. Gutteridge" wrote:
>On Wed, 2019-10-16 at 12:10 +0100, Chavdar Ivanov wrote:
> On Wed, 16 Oct 2019 at 11:03, David H. Gutteridge > wrote:
>
> > FWIW, aside from Firefox (where I also see this issue), I've found
> > since the recent Mesa upgrade, Xfce4's window manager consistently
>
On Sun, Oct 27, 2019 at 02:47:43PM -0400, David H. Gutteridge wrote:
> On Sun, 2019-10-27 at 02:24 +, m...@netbsd.org 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
On Sun, 2019-10-27 at 14:14 +, Chavdar Ivanov wrote:
> 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
On Sun, 2019-10-27 at 02:24 +, m...@netbsd.org 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
Chavdar Ivanov wrote:
>On Sun, 27 Oct 2019 at 16:25, Robert Swindells wrote:
>>
>> Chavdar Ivanov wrote:
>> >I do not have MesaLib installed on this v/b guest at all.
>>
>> Are you running modular or native xorg ?
>
>Native.
Ok, so either you have MesaLib from xsrc installed or you have
Native.
On Sun, 27 Oct 2019 at 16:25, Robert Swindells wrote:
>
>
> Chavdar Ivanov wrote:
> >I do not have MesaLib installed on this v/b guest at all.
>
> Are you running modular or native xorg ?
--
Chavdar Ivanov wrote:
>I do not have MesaLib installed on this v/b guest at all.
Are you running modular or native xorg ?
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
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
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.
On Sat, 26 Oct 2019 at 19:25, David H. Gutteridge wrote:
>
> On Sat, 2019-10-26 at 00:40 +, m...@netbsd.org wrote:
> > Can someone who has this issue explain
On Sat, 2019-10-26 at 00:40 +, m...@netbsd.org wrote:
> Can someone who has this issue explain it shortly?
>
> - Which GPU?
> - What part of updating (kernel, userland) did it?
> - Does a clean build of everything fix it?
>
> the i915 driver has broken userland compatibility. mrg/riastradh
Can someone who has this issue explain it shortly?
- Which GPU?
- What part of updating (kernel, userland) did it?
- Does a clean build of everything fix it?
the i915 driver has broken userland compatibility. mrg/riastradh fixed it,
but I won't be surprised if there's more we haven't spotted
On Wed, 2019-10-16 at 12:10 +0100, Chavdar Ivanov wrote:
> On Wed, 16 Oct 2019 at 11:03, David H. Gutteridge > wrote:
>
> > FWIW, aside from Firefox (where I also see this issue), I've found
> > since the recent Mesa upgrade, Xfce4's window manager consistently
> > crashes during startup.
18 matches
Mail list logo
