Re: Compatibility problems with latest GTK+ applications

2014-05-07 Thread Martin Graesslin
On Wednesday 07 May 2014 19:42:21 Albert Astals Cid wrote: > El Dimecres, 7 de maig de 2014, a les 10:11:37, Martin Gräßlin va escriure: > > Hi all, > > > > I need some advice. The new GTK+ release > > For those that don't follow much the GTK+ world, which release number is > that? 3.12.1 - mino

Re: Compatibility problems with latest GTK+ applications

2014-05-07 Thread Albert Astals Cid
El Dimecres, 7 de maig de 2014, a les 10:11:37, Martin Gräßlin va escriure: > Hi all, > > I need some advice. The new GTK+ release For those that don't follow much the GTK+ world, which release number is that? Cheers, Albert signature.asc Description: This is a digitally signed message part.

Re: KDE Frameworks Release Cycle

2014-05-07 Thread Sebastian Kügler
On Monday, May 05, 2014 11:11:53 Martin Klapetek wrote: > However this highly depends on the distro policies - if some of the big > distros say "we will not update KF5 every month because our policies", then > the 6 months buffer is just moved elsewhere, at the distro level because > they will upda

Re: Review Request 117044: Avoid unnecessary automounting in KDiskFreeSpaceInfo::freeSpaceInfo

2014-05-07 Thread Sebastian Kügler
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117044/#review57500 --- Note that this change won't make it automatically into Plasma

Re: Compatibility problems with latest GTK+ applications

2014-05-07 Thread Thomas Lübking
On Mittwoch, 7. Mai 2014 12:08:19 CEST, Aleix Pol wrote: Personally, I don't think we want to even try to convince them against. They're introducing interaction within the decoration space so they are committed to the idea. That's actually not the point. The correct way would have been to say

Re: Compatibility problems with latest GTK+ applications

2014-05-07 Thread Aleix Pol
On Wed, May 7, 2014 at 10:11 AM, Martin Gräßlin wrote: > Hi all, > > I need some advice. The new GTK+ release introduced and enforces > client-side- > decorations (CSD) and that is causing severe compatibility problems with > Plasma Workspaces (especially the stable release which we cannot adjust

Re: Re: Compatibility problems with latest GTK+ applications

2014-05-07 Thread Martin Gräßlin
On Wednesday 07 May 2014 11:24:03 Marco Martin wrote: > On Wednesday 07 May 2014 10:11:37 Martin Gräßlin wrote: > > * A hung window can no longer be closed or moved. Technical explanation: > > there is a ping protocol to detect hung applications. KWin only sends ping > > requests when the window is

Re: Compatibility problems with latest GTK+ applications

2014-05-07 Thread Marco Martin
On Wednesday 07 May 2014 10:11:37 Martin Gräßlin wrote: > * A hung window can no longer be closed or moved. Technical explanation: > there is a ping protocol to detect hung applications. KWin only sends ping > requests when the window is being closed from the window manager (e.g. > decoration clos

Re: Compatibility problems with latest GTK+ applications

2014-05-07 Thread Marco Martin
On Wednesday 07 May 2014 10:11:37 Martin Gräßlin wrote: > * A hung window can no longer be closed or moved. Technical explanation: > there is a ping protocol to detect hung applications. KWin only sends ping > requests when the window is being closed from the window manager (e.g. > decoration clos

Compatibility problems with latest GTK+ applications

2014-05-07 Thread Martin Gräßlin
Hi all, I need some advice. The new GTK+ release introduced and enforces client-side- decorations (CSD) and that is causing severe compatibility problems with Plasma Workspaces (especially the stable release which we cannot adjust any more). I'll give a list of issues below. I'm not sure what w

Re: KDE Frameworks: There will be a beta 3

2014-05-07 Thread Andrei Amuraritei
On Monday, May 05, 2014 08:57:37 PM Kevin Ottens wrote: > Hello all, > > After the release of beta 2, we realized that it couldn't be the last beta > for several reasons: > * a long standing release blocker in libsolid still wasn't addressed in > time for beta 2, it'll hopefully be solved in the