=== Class7_ is now known as Class7 [09:32] Trevinho: the Yaru team is asking if we can drop debian/patches/scrollbar-background-theming.patch in gnome-terminal [09:32] Trevinho: it creates some artefacts with the default and Yaru team [09:32] https://community.ubuntu.com/t/call-for-participation-an-ubuntu-default-theme-lead-by-the-community/1545/1741 [09:32] do you mind answering/looking at it? [10:01] Laney: MERGE https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/355192 [10:02] didrocks: I was wondering that... Then i noticed it would break ambiance though [10:10] Trevinho: any workaround in the theme we can push to Yaru? [10:10] (please answer on the community hub thread) [11:48] is there a meeting on IRC today? :-) [11:51] Nafallo, you already asked that after the previous meeting, still no :) === pavlushka_ is now known as pavlushka [12:10] I guess my laptop really likes my printer because even after removing it, it adds it back. [12:11] Ah it's a feature of CUPS [12:15] seb128: you weren't sure ;-) [12:25] kenvandine, willcooke, jamesh, looking at the calendar it doesn't seem like we have slots schedules for the snap topic from our agenda, is that something we should sort out now so we are sure to get the people who need (I guess the snapd team is busy and it's not easy to get them)? e.g "Multiple apps (snaps) with same name", "limited bandwidth", "Talk to snap team about updates notifications and turn off auto-updates from UI", [12:25] debug symbols [12:26] seb128: there is a session for debug symbols on Friday [12:26] jamesh, ah, good, I see it now [12:26] what about the other topics? ;) [12:27] which of the others are most important? [12:28] I don't know what the "multiple apps" is, but willcooke put it on the agenda so... [12:28] maybe it is multiple snaps with the same human readable name? [12:28] we should talk to them about the low bandwith one, that was discussed on IRC recently [12:28] or similar names [12:29] the feature is there, but they needed to get confidence on the feature working so we need to figure out what testing is needed/how to unblock [12:29] or maybe we should just schedule a "desktop/snapd catchup" session and cover the different topics in one slot [12:29] there might be other things worth discussing === pavlushka is now known as Guest35516 === pavlushka_ is now known as pavlushka [13:02] robert_ancell, http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html [13:02] you can change bb to cc [13:02] and incoming to tracking [13:02] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html [13:03] robert_ancell, http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html is the main list atm [13:41] seb128: new glib 2.58.0-4 didn't fix indicator-messages https://launchpad.net/ubuntu/+source/indicator-messages/13.10.1+17.04.20170120-0ubuntu3/+build/15461977 [13:42] see https://gitlab.gnome.org/GNOME/glib/issues/1513 which has some details about the change in 2.58 [13:42] GNOME issue 1513 in glib "GIcon regression?" [Gicon, Closed] [14:10] jbicha, thx [14:10] Trevinho, ^ [14:16] jbicha, did you ask muktupavels about it? [14:17] no [14:37] seb128, jbicha: well it is more or less same bug / caused by same change... [14:38] There are not much options... Either change is reverted in glib or tests must be updated. In indicator-messages case symbolic icon names should be added. [14:40] https://developer.gnome.org/gio/stable/GThemedIcon.html [14:40] g_themed_icon_new_with_default_fallbacks documentation is no longer true... [15:00] muktupavels, wasn't the recent commit supposed to revert the behaviour change? [15:01] the new commit didn't fully revert the behavior change [15:01] seb128: no, it fixed only one thing to match documentation. [15:03] Trevinho, can you unreject https://code.launchpad.net/~seb128/indicator-messages/symbolic-icons-tests/+merge/355144 ? :) [15:03] muktupavels, uncompatible behaviour change in stable APIs are not nice :/ [15:04] seb128: why are you telling that to me? I know and I agree with you. :) [15:06] muktupavels, sorry, I read the who-is-telling-what on that gitlab issue report wrong :)