Activity log for bug #1846699

Date Who What changed Old value New value Message
2019-10-04 09:21:53 Alejandro Claro bug added bug
2019-10-04 09:23:30 Alejandro Claro description In GTK+ 3.20 the theming mechanics was heavily changed. https://developer.gnome.org/gtk3/stable/ch32s10.html One of the major changes was the use of element names much more than style classes. For this the function gtk_widget_class_set_css_name() was added to t he API and used to assign the element names. However, this was not added in GTKmm, making impossible to assign element names in custom widget, and no automatically assignment was developed in GTKmm's Widget class in order to be able to identify widget classes in the theming system (CSS). The problem was discussed and tracked up to Glibmm in GNOME bug tracking system: https://gitlab.gnome.org/GNOME/gtkmm/issues/17 https://gitlab.gnome.org/GNOME/glibmm/issues/33 The issues are due to the lack of the mechanism to call gtk_widget_class_set_css_name() function in the instance init function. This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this version and it's affecting some of our products. We have applied a patch to the current version (2.56) of Glibmm2.4 in Ubuntu 18.04 successfully, but I would like to ask considered upgrading the version of Glibmm in the official repository or apply the patch. In GTK+ 3.20 the theming mechanics was heavily changed. https://developer.gnome.org/gtk3/stable/ch32s10.html One of the major changes was the use of element names much more than style classes. For this the function gtk_widget_class_set_css_name() was added to t he API and used to assign the element names. However, this was not added in GTKmm, making impossible to assign element names in custom widget, and no automatically assignment was developed in GTKmm's Widget class in order to be able to identify widget classes in the theming system (CSS). The problem was discussed and tracked up to Glibmm in GNOME bug tracking system: https://gitlab.gnome.org/GNOME/gtkmm/issues/17 https://gitlab.gnome.org/GNOME/glibmm/issues/33 The issues are due to the lack of the mechanism to call gtk_widget_class_set_css_name() function in the instance init function. This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this version and it's affecting some of our products. We have applied a patch to the current version (2.56) of Glibmm2.4 in Ubuntu 18.04 successfully, but I would like to ask you to consider upgrading the version of Glibmm in the official repository or apply the patch.
2020-07-06 10:23:12 Alejandro Claro attachment added Patch for version 2.56 that incorporates a fix related to the theme management in version 2.60 https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+attachment/5390142/+files/0001-Object-construction-Add-custom-class-init-and-instan.patch
2020-07-06 12:26:05 Ubuntu Foundations Team Bug Bot tags patch
2020-07-06 12:26:12 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Review Team
2020-11-30 10:30:42 Sebastien Bacher bug added subscriber Ubuntu Sponsors Team
2020-11-30 10:31:10 Sebastien Bacher glibmm2.4 (Ubuntu): importance Undecided Low
2020-11-30 10:31:16 Sebastien Bacher glibmm2.4 (Ubuntu): status New Fix Committed
2020-11-30 20:24:58 Mathew Hodson tags patch bionic patch
2020-11-30 20:26:39 Mathew Hodson bug watch added https://gitlab.gnome.org/GNOME/glibmm/-/issues/33
2020-11-30 20:26:39 Mathew Hodson bug task added glibmm
2020-11-30 20:31:15 Mathew Hodson nominated for series Ubuntu Bionic
2020-11-30 20:31:15 Mathew Hodson bug task added glibmm2.4 (Ubuntu Bionic)
2020-11-30 20:31:23 Mathew Hodson glibmm2.4 (Ubuntu Bionic): importance Undecided Low
2020-11-30 20:31:26 Mathew Hodson glibmm2.4 (Ubuntu): status Fix Committed Fix Released
2020-12-01 14:35:06 Sebastien Bacher bug task deleted glibmm2.4 (Ubuntu Bionic)
2022-05-20 15:59:40 Bug Watch Updater glibmm: status Unknown Fix Released