One post-4.5.0 patch to fix the freeze of kded on first use of the network:/ kio-slave

2010-08-09 Thread Friedrich W. H. Kossebau
Dear packagers,

please consider backporting the following commit to your 4.5.0 packages:
http://websvn.kde.org/?revision=1160391&view=revision

It fixes a total freeze of kded if the network:/ kio-slave is first invoked. 
The kio-slave calls its kded module networkwatcher via D-Bus, kded loads the 
module on demand (as configured since 4.5), but the module itself also does a 
D-Bus call in its initialisation which seems blocked by a mutex hold by kded 
due to the D-Bus call which triggered the load of the module initially -> 
deadlock.

Sorry about the late notification. I am short of time and with messed up 
computers currently, so my short testing missed to see this in time, and it 
seems nobody else who tested the network:/ kio-slave was ambitious enough to 
report this. Will also blog about this problem.

Thanks
Friedrich
-- 
KDE Okteta - a simple hex editor - http://utils.kde.org/projects/okteta
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: BIC in libkonq

2010-08-09 Thread Modestas Vainius
Hello,

On pirmadienis 09 Rugpjūtis 2010 17:07:17 Jonathan Riddell wrote:
> On Mon, Aug 09, 2010 at 02:57:20PM +0100, Richard Moore wrote:
> > On Mon, Aug 9, 2010 at 10:47 AM, David Faure  wrote:
> > > I'm perfectly fine with increasing the SOVERSION now. 5a or 6? I wasn't
> > > aware that one could use letters in the SOVERSION :)
> > 
> > 6 Please, or we'll start joining the openssl version number insanity!
> 
> I don't see any point in doing that now.  The BIC change was in
> January and we've had 4.4 and 4.5 releases since then.

4.5 has not been released yet.

-- 
Modestas Vainius 


signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: BIC in libkonq

2010-08-09 Thread Jonathan Riddell
On Mon, Aug 09, 2010 at 02:57:20PM +0100, Richard Moore wrote:
> On Mon, Aug 9, 2010 at 10:47 AM, David Faure  wrote:
> > I'm perfectly fine with increasing the SOVERSION now. 5a or 6? I wasn't 
> > aware
> > that one could use letters in the SOVERSION :)
> 
> 6 Please, or we'll start joining the openssl version number insanity!

I don't see any point in doing that now.  The BIC change was in
January and we've had 4.4 and 4.5 releases since then.

Jonathan
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: BIC in libkonq

2010-08-09 Thread Richard Moore
On Mon, Aug 9, 2010 at 10:47 AM, David Faure  wrote:
> I'm perfectly fine with increasing the SOVERSION now. 5a or 6? I wasn't aware
> that one could use letters in the SOVERSION :)

6 Please, or we'll start joining the openssl version number insanity!

Rich.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: BIC in libkonq

2010-08-09 Thread David Faure
On Tuesday 03 August 2010, Dirk Mueller wrote:
> On Monday 02 August 2010, Modestas Vainius wrote:
> > > Good point. we should
> 
> bump it to version 6?
> 
> > Yes, one of the main SONAME purposes is to manage
> 
> BIC changes.
> 
> > Unfortunately, libraries outside kde(pim)libs break BC all
> 
> the time but
> 
> > rarely ever bump SOVERSIONs (for example, kdebase-workspace
> 
> libraries).
> 
> > Hopefully, such a bump in libkonq would set a good example for
> 
> the future.
> 
> Well, most libraries outside the kde*libs space are only used
> within their module, thats why BC is lesser of a concern here.
> 
> libkonq is
> an edge case, it is used in quite some other modules, on the other side,
> due to the anything that depends on *workspace* must require the exact
> version anyway, making an exception for libkonq doesn't make that much
> sense to me.

I apologize for the BIC in libkonq. The reason why I didn't increase the 
soversion is simple: I didn't think about it.

Note, however, that KNewMenu is no longer used in any of the kde svn code.
>From Modestas' `apt-cache rdepends libkonq5` list, I see only kmess which 
could be affected by this. OK, and of course an update of libkonq without 
updating older kdebase stuff like konqueror... 

I'm perfectly fine with increasing the SOVERSION now. 5a or 6? I wasn't aware 
that one could use letters in the SOVERSION :)

-- 
David Faure, fa...@kde.org, http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org).
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team