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 786070 - gtkmm30-3.22.1 breaks ABI without soversion bump
gtkmm30-3.22.1 breaks ABI without soversion bump
Status: RESOLVED OBSOLETE
Product: gtkmm
Classification: Bindings
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtkmm-forge
gtkmm-forge
Depends on:
Blocks:
 
 
Reported: 2017-08-09 20:17 UTC by Sandro Mani
Modified: 2018-05-22 12:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sandro Mani 2017-08-09 20:17:46 UTC 
As reported downstream [1], gtkmm30-3.22.1 breaks the ABI without a soversion bump, among affected symbols:

_ZN3Gio9ActionMap10add_actionERKN4Glib7ustringERKN4sigc4slotIFvvENS5_3nilES8_S8_S8_S8_S8_S8_EE

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1479921
Comment 1 Kjell Ahlstedt 2017-08-13 08:35:24 UTC 
Sorry, but I don't understand how to interpret the information in this bug and
the upstream bug. Gio::ActionMap belongs to glibmm, not gtkmm. Is the mentioned
symbol one that gtkmm references, but is missing in glibmm?
Comment 2 Kjell Ahlstedt 2017-08-13 08:36:51 UTC 
s/upstream/downstream/
Comment 3 Daniel Boles 2017-08-13 13:00:33 UTC 
Please confirm the affected glibmm version, as that function is from glibmm.

I suspect this may have been caused accidentally in 2.51.7 and resolved in 2.51.8 by
https://git.gnome.org/browse/glibmm/commit/?h=glibmm-2-52&id=f81107735d04569d6a9bd1bf473980f3ef1f1e01

Indeed, c++filt demangles your single quoted symbol to

Gio::ActionMap::add_action(Glib::ustring const&, sigc::slot<void (), sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil> const&)

as in the accidental change.

I certainly can't see any other recent commits that could cause this.


If so, apologies for the inconvenience, but a newer version is available fixing this, so best to get your distro to package it.

Besides, if that's the cause, it is weird to me that a distro would be packaging 2.52 already, as it's still in the unstable stage.
Comment 4 GNOME Infrastructure Team 2018-05-22 12:17:54 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtkmm/issues/21.