[Bug 1846699] Re: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm

Sebastien Bacher 1846699 at bugs.launchpad.net
Mon Nov 30 19:46:57 UTC 2020


The way launchpad bug tracking is working is that the status reflect the
current serie, and as you said it's fixed in 20.10. If the fix is needed
in older serie it's possible to target an older serie which would add a
line to the bug table. We do need to determine if the bug is important
enough for a stable update though and a testcase to be able to verify a
fix candidate. Could you provide a simple testcase that anyone could
follow to confirm the issue and that a package update correct resolve
it?

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1846699

Title:
  Missing mechanism in Glibmm that prevents the support of some themes
  (CSS) in Gtkmm

Status in glibmm2.4 package in Ubuntu:
  Fix Committed

Bug 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 you to consider
  upgrading the version of Glibmm in the official repository or apply
  the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions



More information about the Ubuntu-sponsors mailing list