On Tuesday 31 May 2016 14:29:06 Sebastian Kügler wrote:
> Discussed with mgraesslin on IRC, preliminary conclusion below...
>
> On dinsdag 31 mei 2016 14:05:06 CEST Sebastian Kügler wrote:
> > https://bugs.kde.org/show_bug.cgi?id=358011 dual screen not setup after
> > reboot
> >
> > This bugrepor
On Wednesday 01 June 2016 00:05:10 Mark Gaiser wrote:
> Perhaps blockSignals can help you out [1]?
>
> object->blockSignals(true);
> // ...
> Write your changes
> // ...
> object->blockSignals(false);
>
> Object should be the object that currently receives the notification that
> the config file
On Tue, May 31, 2016 at 2:29 PM, Sebastian Kügler wrote:
> Discussed with mgraesslin on IRC, preliminary conclusion below...
>
> On dinsdag 31 mei 2016 14:05:06 CEST Sebastian Kügler wrote:
> > https://bugs.kde.org/show_bug.cgi?id=358011 dual screen not setup after
> > reboot
> >
> > This bugrepo
Discussed with mgraesslin on IRC, preliminary conclusion below...
On dinsdag 31 mei 2016 14:05:06 CEST Sebastian Kügler wrote:
> https://bugs.kde.org/show_bug.cgi?id=358011 dual screen not setup after
> reboot
>
> This bugreport seems to be a common problem, and it's a good example for
> what's
Hey,
I've been looking into the bug 358011, that is:
https://bugs.kde.org/show_bug.cgi?id=358011 dual screen not setup after reboot
This bugreport seems to be a common problem, and it's a good example for
what's wrong with the screen configuration on startup.
TL;DR: We have a race condition wh
