clutz (Christoph Lutz)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Sunday

  • Clear sailing ahead.

User Details

User Since
May 29 2017, 2:24 PM (359 w, 4 d)
Availability
Available

Recent Activity

Jun 1 2017

clutz added a comment to D6011: let's continue in debug code instead of returning from XRandRConfig::applyKScreenConfig.

Hi David, there's no bug report for that in the KDE issue tracker (but in our custom one). I adjusted the patch description above. Is that ok for the kind of documentation that you want to have? (I would prefer to send you a new git-patch that contains a complete description, but phabricator seems to drop any patch descriptions...)

Jun 1 2017, 8:36 AM · Plasma
clutz updated the summary of D6011: let's continue in debug code instead of returning from XRandRConfig::applyKScreenConfig.
Jun 1 2017, 8:30 AM · Plasma
clutz updated the summary of D6011: let's continue in debug code instead of returning from XRandRConfig::applyKScreenConfig.
Jun 1 2017, 8:30 AM · Plasma
clutz updated the summary of D6011: let's continue in debug code instead of returning from XRandRConfig::applyKScreenConfig.
Jun 1 2017, 8:29 AM · Plasma
clutz added a comment to D6011: let's continue in debug code instead of returning from XRandRConfig::applyKScreenConfig.

Thanks David for reviewing that. Oh, I already tried to find the underlying bug that causes the inconsistency. The debugging led me from libkscreen to xrandr to libxrandr (XRRGetOutputInfo) to the kernel. Here I noticed the following things:

Jun 1 2017, 6:59 AM · Plasma

May 29 2017

clutz created D6011: let's continue in debug code instead of returning from XRandRConfig::applyKScreenConfig.
May 29 2017, 2:33 PM · Plasma