in the 394 bug report. :)
The revert seems to be interesting for prepared updates for
the R13. But I hesitate whether I can risk to include it?
Yeah, the patch was committed 2011-10-26 and 3.5.13 was released 2011-11-1.
You folks have a better grasp of those things than me. :)
I suppose somebody could back port the patch to a 3.5.13 test system and test for several
days. My guess is the errors/warnings reported in the bug report will reappear because
whatever was the true cause of those messages was not really fixed with that patch. I
think this one of those moments when one problem masked another. Therefore reverting that
one patch in 3.5.13 without the other unknown fixes is likely to resurrect those
messages.
I'm guessing something else changed along side of or after that one patch that
actually resolved the messages.
Possibly browsing through the Commit Patches web page might reveal possible candidates.
Anything related to dcop is possible, but if the cause was due to some tq/TQ cleanup then
we are unlikely to ever know.
If I was an admin or distro maintainer, unless I could find the other fix that likely
resolved the problem, I'd leave 3.5.13 as is and revert the patch only in GIT builds.
I can only offer that reverting the patch in GIT solved "my" problem of running
kate concurrently as normal and root users. Nobody else has yet confirmed the same problem
exists for them.
Darrell
