On Monday, May 30, 2016 11:36:54 AM CEST Kurt Hindenburg wrote:
> There are a number of lines that division by zero could happen in
> frameworks/kwindowsystem/src/platforms/xcb/kwindowsystem.cpp if
> displayGeometry returns a 0 QRect. I think that is what is happening with
> bug 349512.
urgh. Th
On Sunday 07 June 2015 08:34:22 Scarlett Clark wrote:
> After closer inspection it seems the NoX11 had deploy false and that is why
> OSX had nothing to sync. I am rather shocked this has only been an issue
> now. Short term solution is I created an "All" for osx that still disables
> X11. Long te
On Sunday, June 07, 2015 10:17:21 AM David Faure wrote:
> On Sunday 07 June 2015 00:13:11 David Faure wrote:
> > On Saturday 06 June 2015 22:01:50 no-re...@kde.org wrote:
> > > Check console output at
> > >
> > > https://build.kde.org/job/kxmlgui%20master%20kf5-qt5/PLATFORM=OSX,compil
> > > er
>
On Monday, March 3, 2014 10:34:40 Martin Gräßlin wrote:
> It's an incorrect usage caused by XLib not being thread safe. We just
> couldn't use KWindowInfo in the runner thread. With the switch to xcb
> that's no longer the case and it would be better to have just a QList
> and fetch the data in the
On Monday 03 March 2014 09:56:11 Aaron J. Seigo wrote:
> On Monday, March 3, 2014 08:35:16 you wrote:
> > The reason to remove the default ctor was that if one used it, KWindowInfo
> > would crash on first usage as it was completely broken. It was documented
> > to be there for usages in container
On Monday, March 3, 2014 08:35:16 you wrote:
> The reason to remove the default ctor was that if one used it, KWindowInfo
> would crash on first usage as it was completely broken. It was documented to
> be there for usages in container classes but lxr doesn't show any usage and
kde-workspace/plasm
