Ubuntu
gtk+3.0 package

  1. Bug #1621215
  2. Comment #8

Comment 8 for bug 1621215

Revision history for this message
Jeremy Bícha (jbicha) wrote :

I'm reassigning this from (nautilus and glib2.0) to (gtk+3.0 and glib2.0) because upgrading gtk+3.0 to 3.21.5 also fixes this and downgrading back to yakkety's gtk+3.0 brings the bug back.

Therefore, I believe this bug can be fixed in either GTK or glib.