GTK oxygen packages are too old

[Ruslan]

Current official versions of oxygen-gtk and oxygen-gtk3 are 1.2.3 and 1.0.3 respectively. They have quite some bugs fixed since previous releases.
But (K)Ubuntu still ships versions 1.2.2 and 1.0.2. Because of this many users report old fixed bugs just to learn that they have to build latest versions from source.
Please update gtk3-engines-oxygen and gtk2-engines-oxygen packages.

[Marco (makro)]

I can confirm a lot of GTK apps crash or don't work.
PgAdmin3 crashes every time a dialog is open (try to modify a column and click OK or Cancel, or to change font size in options dialog forces application to close)
Filezilla connect dialog has the same behavior
Easytag seems to be blind at every file or tag editing (it doesn't ask to save changes)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[negora (negora)]

I also confirm all these bugs. Many GTK applications remain useless because of them. Opening a simple dialog window on pgAdmin III already triggers a crash. It would be good to have it fixed. Thank you for your efforts :) .

[Ruslan (b7-10110111)]

What does Fix Released status mean? Does it mean that new packages are made available in the repo? If yes, then I don't confirm it: current Ubuntu release (Ubuntu Precise) has oxygen-gtk3 1.0.2 (http://packages.ubuntu.com/en/precise/gtk3-engines-oxygen) and oxygen-gtk2 1.2.2 (http://packages.ubuntu.com/precise-updates/gtk2-engines-oxygen).
This means that current LTS release has highly buggy oxygen-gtk packages, and this also results in high invalid bug report rate at bugs.kde.org.
Could you please make current versions (1.0.4 and 1.2.4) available at least in Precise?

[Felix Geyer (debfx)]

Fix release here means it's fixed in the development release.

The difference .2 and .4 is quite large so I doubt it would be a good idea to just upgrade the upstream version as that can cause regressions which is not acceptable for stable release updates.

What we need instead is bug reports about individual bugs and the upstream commit that fixes the issue (can be determined with git bisect).

[Ruslan (b7-10110111)]

The fixes are not just a single commit: there has been plenty of them, and the differences (by which I believe you mean change in dependencies) are also due to bug fixes. If they weren't just to fix bugs, we'd only push them to major releases.
Currently we have to ask the bug reporters to first remove gtk3-engines-oxygen and gtk2-engines-oxygen and install latest versions from source. And after this they have to resolve the bugs as invalid. I think it's no good, especially for LTS release.

As for regressions, it seems there's so many normal bugs in old packages, that the regressions in new ones can be neglected.

[Harald Sitter (apachelogger)]

"As for regressions, it seems there's so many normal bugs in old packages, that the regressions in new ones can be neglected."

Right, which are those particular bugs that were fixed?

[Ruslan (b7-10110111)]

Here're some of them:
http://tinyurl.com/d7mhf22 , plus some later reported bugs which were resolved as INVALID or similar because upgrading fixed them.

[James Maddison (jamesmadd)]

Is "Fixed Released" really accurate here? This present serious usability bugs with the (unchanged) Kubuntu 12.04 packages.

[Serhiy (xintx-ua)]

Felix, but that bug is against the Ubuntu version, this is not the upstream, so it should be "Fix Committed" at least. It's still not released.
And please add a link to build from source.

[Ruslan (b7-10110111)]

@Сергій
> And please add a link to build from source.
For the links to releases and repository see this page: http://kde-look.org/content/show.php/Oxygen+Gtk?content=136216 .
How to build is described in INSTALL file.

[Serhiy (xintx-ua)]

Yes, I've tried it and it's even worse than current version. Maybe there is something more that should be done besides the INSTALL contents?

[Ruslan (b7-10110111)]

@Сергій
Come to #oxygen at freenode, ping l0ll0lll, and I'll try to help you.

[Serhiy (xintx-ua)]

With help from Ruslan it worked for me. Here is the bash code:
http://pastebin.com/raw.php?i=KmGcdLFc

[Joar Jegleim (joar-jegleim)]

I confirm following directions from http://pastebin.com/raw.php?i=KmGcdLFc worked for me . (thnx Ruslan and comment #14 by xintx-ua )

[Ruslan (b7-10110111)]

@Felix
A year has passed, an Ubuntu still ships quite out of date packages. Could you elaborate on which commits between v1.2.2 and 1.2.5 you consider too large to ship? I'd then make a special release for Ubuntu Precise without those commits (and maybe also follow-up release to include some important fixes from 1.3 branch), so that we would still have more or less stable packages here, without too much risks.
Also would be good to do the same for commits between vgtk3-1.0.2 and vgtk3-1.0.5.
There've been 55 commits in gtk2 and 178 commits in gtk3, It looks too much effort to report corresponding bugs twice, just for bureaucratic reasons, especially because some of them haven't been reported to bugs.kde.org since they were found by devs and promptly fixed.