After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 689027 - Adwaita 3.6.2 GTK theme with GTK 3.6.0 makes everything segfault
Adwaita 3.6.2 GTK theme with GTK 3.6.0 makes everything segfault
Status: RESOLVED FIXED
Product: gnome-themes-standard
Classification: Core
Component: general
3.6.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-themes-standard-maint
gnome-themes-standard-maint
Depends on:
Blocks:
 
 
Reported: 2012-11-25 14:19 UTC by Jeremy Bicha
Modified: 2012-11-27 08:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeremy Bicha 2012-11-25 14:19:30 UTC
I unfortunately stumbled across this bug with the GNOME3 PPA for Ubuntu 12.10. Ubuntu 12.10 ships GTK 3.6.0 since that was the last stable GTK until release week.

Trying to use Adwaita from gnome-themes-standard 3.6.2 as the GTK theme when GTK is only 3.6.0 causes segfaults in at least everything using GTK, making it impossible to get a desktop after logging in.

To fix this, bump GTK_VERSION_REQUIRED to 3.6.2 in configure.ac (3.6.1 may also be sufficient but I didn't test that).

And please, please save your refactoring for the unstable phase of development cycles, not stable releases.
Comment 1 Cosimo Cecchi 2012-11-25 16:40:26 UTC
(In reply to comment #0)
> I unfortunately stumbled across this bug with the GNOME3 PPA for Ubuntu 12.10.
> Ubuntu 12.10 ships GTK 3.6.0 since that was the last stable GTK until release
> week.
> 
> Trying to use Adwaita from gnome-themes-standard 3.6.2 as the GTK theme when
> GTK is only 3.6.0 causes segfaults in at least everything using GTK, making it
> impossible to get a desktop after logging in.
> 
> To fix this, bump GTK_VERSION_REQUIRED to 3.6.2 in configure.ac (3.6.1 may also
> be sufficient but I didn't test that).

Do you have a backtrace? I suspect this is due to commit [1] being required for [2]. Feel free to commit the version bump.

> And please, please save your refactoring for the unstable phase of development
> cycles, not stable releases.

Uh? What refactoring are you thinking of and what does it have to do with this bug?

[1] http://git.gnome.org/browse/gtk+/commit/?h=gtk-3-6&id=e09cf6978e762d3a3c6d5b4fcf0a2124a99bc8f7
[2] http://git.gnome.org/browse/gnome-themes-standard/commit/?h=gnome-3-6&id=737530bc7d8fa11c7d1e83fbcd0fc0e5256127c0
Comment 2 Jeremy Bicha 2012-11-25 17:11:48 UTC
(In reply to comment #1)
> Uh? What refactoring are you thinking of and what does it have to do with this
> bug?

I was referring to "* CSS: - huge refactoring to avoid computing wrong values" from GTK+ 3.6.1's NEWS. I assumed that gnome-themes-standard was depending on something that had changed since 3.6.0.