[PATCH] Re: KDE 4.6.0: go or no go?

Sebastian Trüg trueg at kde.org
Thu Jan 20 15:09:39 GMT 2011

On 01/20/2011 03:18 PM, Sebastian Trüg wrote:
> This patch does in no way solve the issue.

Let me give some detail here: I only did see the disabling of Strigi
which makes no sense.
I am fine with disabling the KRunner plugin for now. But AFAIK this only
is a problem in combination with Akonadi.
I did improve the KRunner situation though. Normally it should not
create ugly queries anymore. At least I did not see it again.

The patches Will posted do provide a real solution. However, they still
have the problem that existing data needs to be converted to a certain
degree. This took roughly half an hour for me.

I could strip the patch down, remove parts of it. But honestly I am not
comfortable with doing that now. I would rather do that for 4.6.1.


> On 01/20/2011 02:00 PM, Dirk Mueller wrote:
>> On Wednesday 19 January 2011, Dirk Mueller wrote:
>>> so the general consensus seems to be against slipping the schedule and
>>> inserting a RC3.
>>> This means that we need to solve bug 246678. Given that there seems to be
>>> no fix in sight (no comment in the last 14 days), can we mitigate it. is
>>> there a way to disable whatever causes the problem by default? what would
>>> be the patch for that?
>> Hi,
>> I think the attached patch should make the services be disabled by default, 
>> thereby avoiding kde bug 246678. I'm asking for a review and a comment whether 
>> we can go ahead with this workaround for KDE 4.6.0. 
>> As the general consensus was (previously) already against slipping the 
>> schedule, I need a solution NOW to be able to release 4.6.0 in time. 
>> Please review/comment. 
>> Thanks,
>> Dirk

More information about the kde-core-devel mailing list