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...)
- Queries
- All Stories
- Search
- Advanced Search
Feed Advanced Search
Advanced Search
Advanced Search
Jun 1 2017
Jun 1 2017
clutz added a comment to D6011: let's continue in debug code instead of returning from XRandRConfig::applyKScreenConfig.
clutz updated the summary of D6011: let's continue in debug code instead of returning from XRandRConfig::applyKScreenConfig.
clutz updated the summary of D6011: let's continue in debug code instead of returning from XRandRConfig::applyKScreenConfig.
clutz updated the summary of D6011: let's continue in debug code instead of returning from XRandRConfig::applyKScreenConfig.
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:
May 29 2017
May 29 2017