[06:36] <keestu> hi
[06:36] <didrocks> good morning
[06:37] <keestu> My ubuntu desktop i have connected to big monitor, and then moved back to  tiny htmi monitor. But unfrotunately,  the screen icors are very very big that i could  not even use it
[06:43] <didrocks> keestu: have you try to file a bug on launchpad? if the big icons are the one from the Shell, open in GNOME Shell package, if the icons are the nautilus one, open against nautilus, if it's the one in the monitor (and you are running disco), open it against gnome-shell-extension-desktop-icons, if not disco, nautilus
[06:56] <keestu> okey
[07:11] <jibel> Good morning
[07:26] <didrocks> salut jibel
[07:27] <jibel> Salut didrocks, ça va?
[07:31] <didrocks> jibel: ça va
[07:48] <jibel> \o/ finally found the cause of bug 1818285, now it is weird that the binary package contains undocumented changes
[09:03] <willcooke> morning
[09:03] <seb128> hey willcooke
[09:03] <seb128> how are you? had a good w.e?
[09:03] <seb128> oh and good morning desktop, seems like I forgot the channel :)
[09:06] <didrocks> hey willcooke, seb128
[09:06] <seb128> lut didrocks
[09:08] <seb128> jibel, looking at the ubiquity diff it doens't look like there are undocumented changes, as you pointed on the bug the binaries changing is probably a side effect of the toolchain available at the time of the upload
[09:10] <seb128> jbicha, kenvandine, epiphany-browser-master snap failed build on
[09:11] <seb128> |Dependency gtk+-3.0 found: NO found '3.22.30' but need: '>=3.24.0'
[09:12] <seb128> jbicha, you are replacing the autosync script by syncing the whole archive by hand? ;)
[09:14] <seb128> didrocks, thx for testing/merging that g-s theme change :-)
[09:17] <didrocks> yw!
[09:19] <Laney> PHEW
[09:24] <cpaelzer__> tjaalton: thanks for looking at 1815889
[09:24] <cpaelzer> wow underscore proliferation, that is better
[09:25] <cpaelzer> tjaalton: once you have made your decision on how to continue on it I'm especially interested in a "direct" answer to comment #25
[09:25] <willcooke> morning Laney
[09:25] <cpaelzer> morning Laney and willcooke
[09:25] <willcooke> hi cpaelzer
[09:25] <Laney> moin cpaelzer willcooke
[09:26] <tjaalton> cpaelzer: you didn't mention how urgent this is?
[09:26] <didrocks> hey Laney
[09:26] <Laney> hey didrocks
[09:26] <Laney> how's it going?
[09:26] <didrocks> good, yourself? Start to be grey though :/
[09:26] <cpaelzer> tjaalton: I thought the text in comment #25 made that rather clear - sorry - lets make it clear here then
[09:26] <seb128> hey Laney, was that a phew from someone who has been cycling against the crazy wind? ;)
[09:27] <cpaelzer> tjaalton: a bunch of new features which we really wanted users to try and test to get it mature until 20.04 is depending on gl backends
[09:27] <cpaelzer> tjaalton: and with the bug as-is it is absolutely non-usable in 19.04 onwards
[09:27] <cpaelzer> tjaalton: therefore I asked if we could revert the change in disco
[09:27] <cpaelzer> (the mesa change I referred)
[09:28] <tjaalton> cpaelzer: in disco for sure
[09:28] <tjaalton> or upstream will fix it otherwise
[09:28] <Laney> hey seb128, no not quite (we had that mostly last night, seems it moved across the north sea this morning), was from me recovering my broken server
[09:28] <cpaelzer> yeah, my assumption just was that upstream might take longer than we have for disco
[09:28] <cpaelzer> tjaalton: so my thought was revert this in Mesa for disco and in 19.10 follow whatever the usptreams concluded with
[09:28] <Laney> didrocks: sunny here!
[09:28] <tjaalton> if it's not fixed in 19.0 when it's released, I'll revert
[09:29] <cpaelzer> tjaalton: thanks, if you'd state on the bug that it will be fixed in Disco either way that would be nice
[09:30] <cpaelzer> I can (ugly) work around things until then
[09:30] <cpaelzer> tjaalton: might I ask what the planned release date for 19.0 is?
[09:30] <seb128> what's the bug number you guys are talking about?
[09:30] <seb128> can you make sure it's targetted to disco so we don't loose track of it?
[09:30] <cpaelzer> seb128: bug 1815889
[09:31] <seb128> cpaelzer, thx
[09:31] <cpaelzer> seb128: will you add the trackers the way the desktop Team uses them?
[09:32] <cpaelzer> Or is it just good old "target to series" ?
[09:32] <seb128> cpaelzer, just that
[09:32] <cpaelzer> I happened to realize that Teams have different approaches to that (e.g. milestones)
[09:32] <cpaelzer> ok , then I can do that
[09:32] <seb128> well, process is to tag rls-nn-incoming then we review/assign
[09:32] <seb128> but if that's one understood and that tjaalton is stracking you can directly target
[09:33] <seb128> then it ends up on http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html
[09:33] <seb128> which is the mapping by team of bugs targetted disco
[09:33] <seb128> cpaelzer, thx
[09:34] <cpaelzer> seb128: tjaalton: the mesa bug task now has a Disco target and a 19.04 milestone and is assigned to tjaalton - I hope that will cover every teams tracking of it :-)
[09:34] <tjaalton> thanks
[09:34] <tjaalton> I'll revert it from the test package
[09:34] <seb128> cpaelzer, yeah, we don't use the milestone but that can't hurt, thx!
[09:34] <tjaalton> so it's not lost
[09:39] <tjaalton> cpaelzer: I'll push a new version to x-staging soon
[09:39] <tjaalton> like, now
[09:39] <tjaalton> you'll have it built in 30min
[09:55] <cpaelzer> thanks tjaalton
[11:10] <jbicha> seb128: yes, epiphany 3.31 requires gtk 3.24 so we'll probably use the gnome-3-28-1804-sdk snap when it's ready
[11:11] <jbicha> I wasn't planning on doing the gupnp/gssdp transitions for disco
[11:14] <seb128> any reason not to if those are ready?
[11:14] <jbicha> I don't have the time to work on it now and those were low priority
[11:15] <seb128> on what? it looks like you did do those updates in Debian and we are in sync? you mean just the FFe paperwork?
[11:15] <jbicha> I'm fine with someone else doing it. You'll need to handle Debian bug 923576 and update rygel too
[11:15] <jbicha> it's a transition and I didn't test all the rdepends
[11:16] <seb128> k
[15:41] <Laney> clobrano: hey, are we going to have to update yaru when updating desktop-icons?
[15:41] <Laney> I'm just testing 19.01.1 and there's no visible selection any more
[15:42] <clobrano> Laney: hi o/
[15:42] <clobrano> that's weird indeed, it should work without any change on theme
[15:43] <Laney> hmm
[15:44] <Laney> wait one second, I have some weird local version number
[15:44] <Trevinho> we've fans https://gitlab.gnome.org/GNOME/gnome-shell/issues/1014
[15:44] <gitbot> GNOME issue 1014 in gnome-shell "Consider supporting AppIndicators by default (instead of a non-default extension)" [1. Feature, Opened]
[15:45] <clobrano> :D
[15:46] <clobrano> Laney: were you talking about rubberband selection or selected icon (or both)?
[15:46] <Laney> both
[15:46] <Trevinho> clobrano: there are few changes that should be done actually
[15:46] <clobrano> Trevinho: which ones?
[15:46] <Trevinho> I've not been going through all the diff yet
[15:46] <seb128> hey trevinho, how are you?
[15:47] <Trevinho> but upstream has changed some things, like as per the removal of the dock theming
[15:47] <clobrano> rubberband takes the color from .rubberband gtk class, icon selection from .view class
[15:47] <Trevinho> hey seb128 good, I had some writer inspirantion before so I blogged about the fractional thing xD
[15:47] <seb128> :)
[15:47] <seb128> good job!
[15:48] <Trevinho> clobrano: as per other things, I didn't spot regressions, but we should probably update the yaru upstream code and go through diffs, I would do it but I've other coding stuff to finish first, so I didn't had much time for it
[15:48] <Trevinho> ah clobrano one thing has been changed is the way the windowbuttons are drawn...
[15:49] <clobrano> Trevinho: we spotted some, like the arrows in calendar view
[15:49] <Trevinho> which are now made using css + icon...
[15:49] <Trevinho> clobrano: yep that's one
[15:49] <Trevinho> clobrano: that's weird though since while hacking on scaling I noticed the yaru one was drawn behind it
[15:49] <Trevinho> might be another icon thing + css or smth
[15:49] <clobrano> Trevinho: right, we wanted some icons to get delivered, so we can make a stable branch for 18.04 and go on
[15:50] <clobrano> but, we might speed up if needed, could you remember me the UI freeze date?
[15:51] <Trevinho> clobrano: https://wiki.ubuntu.com/DiscoDingo/ReleaseSchedule
[15:51] <Trevinho> so... ten days
[15:51] <Trevinho> but considering the landing, let's say a week
[15:52] <Laney> clobrano: forget me, I had a local copy in that VM
[15:52] <clobrano> Laney: uhu, better so :D
[15:52] <clobrano> Trevinho: got it, I'll talk to the icon team :)
[15:53] <Laney> yeh, doing that three way merge thing would be good
[15:53] <seb128> jbicha, Laney, trevinho, what's the status of the new gnome-shell? who is owning to get it migrated out of proposed, was that Jeremy who was looking at the other extensions?
[15:53] <cpaelzer> tjaalton: hi I'm trying to verify the qemu crash against the x-staging PPA
[15:54] <cpaelzer> tjaalton: so far no luck, but I realized that only some packages got upgraded
[15:54] <Laney> it's blocked on glibc
[15:54] <cpaelzer> tjaalton: can you pinpoint which of the mesa binary packages has the __pthread_setaffinity_new that breaks it
[15:54] <cpaelzer> so that I can check if that is one of those still on -rc5 level?
[15:54] <seb128> Laney, as it will clear off once glibc migrates?
[15:55] <seb128> or do we have work to do on our side still?
[15:55] <seb128> because you guys mentioned deleting extensions but no-one ever gave me a list
[15:55] <cpaelzer> tjaalton: for example libglapi-mesa doesn't want to install and if I try to foce it it would remove most x* packages
[15:56] <Laney> I think I said last week in the meeting that it will be more clear what to do once glibc clears out
[15:56] <cpaelzer> tjaalton: is there another ppa along ppa:canonical-x/x-staging that I need
[15:56] <andyrock> hey we forgot to update the tags and target this bug for rls https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1817020
[15:56] <seb128> Laney, k, sorry if I forgot that details, it just makes me a bit nervous that we are sitting on our hands and then we will realize that we still have work to do we could have started and delay ourselve by another week
[15:57] <seb128> andyrock, feel free to suggest target
[15:58] <seb128> andyrock, can you maybe take bug #1817546 from Marco? he's busy with other things and that one is probably a blocked to land the new shell
[15:58] <andyrock> seb128: sure thing
[15:58] <seb128> thx
[15:59] <andyrock> I'm about to propose a fix for the dnd bug
[15:59] <seb128> Carlos told me on friday that he changed things around libcanberra handking this cycle
[15:59] <seb128> so might be a bug he created
[15:59] <seb128> ah, great
[15:59] <andyrock> not sure upstream is going to like it, but it's the same workaround used in other places
[16:00] <andyrock> x11 touch in gnome-shell is a little bit broken :)
[16:00] <Laney> seb128: k, well I don't really have that worry (demoting things is not a week long task), but if it makes you happy I'll make you a little list
[16:01] <seb128> Laney, yeah, I'm not so worry about the demoting, more about the fact that we found other autopkgtest or such issues in the way, but I guess that's the part where we need glibc to clear to have a better idea
[16:02] <seb128> andyrock, :/
[16:02] <Laney> ok, well nagging on glibc would be what I would do first
[16:03] <seb128> Laney, ok, thx :)
[16:04] <seb128> clobrano, are you going to do that 3 way merge for the new gnome-shell/theme/yaru?
[16:04] <Trevinho> andyrock: might be an issue on the patch we ship though, more than actual shell (the locks up issue)
[16:06] <andyrock> Trevinho: I'm running vanilla gs
[16:06] <Trevinho> andyrock: and issue is there too (the one seb just pointed you eh)
[16:07] <andyrock> Trevinho: which bug are you talking about? the dnd or  the "volume" one? :)
[16:07] <andyrock> nm I guess you refer to #1817546
[16:08] <Laney> dunno why about 10 issues just got raised at once, is indeed confusing
[16:12] <Trevinho> andyrock: volume
[16:14] <cpaelzer> tjaalton: I pinged on the bug so take your time
[16:14] <cpaelzer> I'll only be able to pick it up tomorrow morning anyway
[16:14] <seb128> Laney, sorry, it was probably my fault, I'm getting a bit nervous about the different things that still needs to line up, but it's going to be ok :)
[16:15] <clobrano> seb128: yep, first I'll sync our upstream folder
[16:16] <seb128> clobrano, thx, let us know if you need help with something
[16:16] <clobrano> seb128: thanks!
[16:27] <andyrock> jbicha: the fix for autopkgtest's failures in tracker has been merged upstream
[16:28] <seb128> andyrock, well done!
[16:28] <andyrock> upstream is on fire lately
[16:31] <k_alam> seb128, Laney: Hi, is there any known dbus test failure issues with glib > = 2.59.3 ? libunity tests fail on proposed....it builds fine with 2.59.2...compiling with lp:~ricotz/libunity/syntax-fixes
[16:31] <k_alam> https://launchpadlibrarian.net/413376821/buildlog_ubuntu-disco-amd64.libunity_7.1.4+18.04.20180209.1-0ubuntu3+201903020606~ubuntu19.04.1_BUILDING.txt.gz
[16:33] <seb128> not known from me
[16:34] <Laney> afraid not
[16:34] <Laney> that message sounds like it provides a good place to start poking around though
[16:38] <k_alam> dee-CRITICAL **: 06:10:10.027: Unable to set up DBusServer....this is generating from https://bazaar.launchpad.net/~ricotz/libunity/syntax-fixes/view/head:/test/vala/test-diff.vala#L356
[16:39] <k_alam> and mainloop is running with timeout...
[16:49] <tjaalton> cpaelzer: that's weird, I'll check it out
[16:53] <tjaalton> cpaelzer: seems to work here just fine
[17:03] <cpaelzer> tjaalton: so it just installas all of them in disco for you?
[17:03] <tjaalton> cpaelzer: yes
[17:04] <cpaelzer> let me check why it would remove the X* packages
[17:04] <cpaelzer> maybe that shed some light
[17:05] <tjaalton> well I didn't have X installed
[17:05] <tjaalton> you have nvidia?
[17:06] <tjaalton> X installs fine
[17:06] <cpaelzer> tjaalton: libglx-mesa0 : Depends: libglapi-mesa (= 19.0.0~rc5-1ubuntu0.1) but 19.0.0~rc6-1ubuntu0.1 is to be installed
[17:06] <cpaelzer> tjaalton: it is a nuc with i915 graphics
[17:06] <tjaalton> dist-upgrade?
[17:07] <cpaelzer> tried, no help
[17:07] <cpaelzer> I might need to version force more of it
[17:07] <tjaalton> you shouldn't need to force anything
[17:08] <tjaalton> so if you just apt install libglx-mesa0 libglapi-mesa?
[17:08] <cpaelzer> aah
[17:08] <cpaelzer> I think it is glibc
[17:08] <cpaelzer> let me flip on propsoed as well
[17:08] <tjaalton> seems to work fine on my laptop too
[17:08]  * cpaelzer begs all your pardon for typo-storm here (it gets late)
[17:08] <tjaalton> you have some experimental stuff installed?
[17:09] <cpaelzer> libglx-mesa0 : Depends: libc6 (>= 2.29) but 2.28-0ubuntu1 is to be installed
[17:09] <cpaelzer> when I try to force rc6 I get this
[17:09] <cpaelzer> so glibc is at least involved
[17:09] <cpaelzer> just a sec to try that
[17:09] <cpaelzer> tjaalton: no experimental things - I set up the nuc to test this issue
[17:09] <tjaalton> are you on disco then?
[17:09] <cpaelzer> so the nuc has ubuntu-desktop + uvtool + gnome-boxes + gdb
[17:09] <cpaelzer> yes disco
[17:10] <tjaalton> ah yes, proposed is enabled for that ppa
[17:10] <cpaelzer> tjaalton: with proposed enabled I get way more installed
[17:11] <cpaelzer> tjaalton: do I need to restart X to get the new libs active?
[17:11] <tjaalton> no
[17:11] <cpaelzer> ok, then wait a minute and we will know
[17:13] <cpaelzer> tjaalton:  does that look good then ?
[17:13] <cpaelzer> http://paste.ubuntu.com/p/6BDXvFp8kY/
[17:13] <cpaelzer> working like a charm now
[17:13] <cpaelzer> \o/
[17:13] <cpaelzer> thanks tjaalton
[17:13] <cpaelzer> I'll update the bug
[17:13] <tjaalton> yes, that's better
[17:15] <cpaelzer> done
[17:15] <cpaelzer> tjaalton: if you need anything from me to make that revert happen in Disco let me know
[17:16] <cpaelzer> at the current state this is by far the most simple fix for the overall issue
[17:16] <tjaalton> no that's fine
[17:16] <tjaalton> we'll get it eventually, within the next few weeks
[17:24] <clobrano> seb128: is it correct to sync with gnome-shell tagged 3.30.2, right?
[17:28] <seb128> clobrano, sync in which sense?
[17:28] <seb128> clobrano, we currently have 3.31.90 in proposed
[18:02] <clobrano> seb128: okay, I was confused because looking at gnome-shell master the changes Trevinho was talking about seems to be in master, but not in the tagged versions
[18:03] <clobrano> I meant the changes in calendar arrows, for example
[18:13] <Trevinho> clobrano: ah, could be that something has not been relased yet, but will be soon
[18:26] <willcooke> night asll
[18:26] <willcooke> all
[18:37] <clobrano> Trevinho: I see, so is it safe sto start merging from master?
[18:37] <Trevinho> clobrano: yeah, then we can release to ubuntu it together with the shell itself
[18:38] <Trevinho> but upstream yaru should stay in sinc with latest stable branch upstream anyways
[18:38] <Trevinho> sync*
[18:39] <clobrano> Perfect 👌
[18:40] <Trevinho> thanks
[18:40] <Trevinho> let me know if you want a review or anything else
[18:40] <Trevinho> clobrano: ^
[18:44] <clobrano> Trevinho: yeah, I surely do :)
[18:59] <andyrock> seb128: Trevinho found the problem with the volume thing
[19:00] <Trevinho> and is...=
[19:00] <Trevinho> ?
[19:00] <andyrock> it's caused by g_cancellable_disconnect deadlocking
[19:01] <andyrock> finish_cb in meta-sound-player.c is calling g_cancellable_disconnect and finish_cb can be the result of cancelled_cb->ca_context_cancel
[19:01]  * andyrock is thinking about the best way to fix this
[19:02] <andyrock> maybe just an idle
[19:10] <andyrock> I'll propose a fix upstream
[19:10] <andyrock> hopefully we get it in before the release
[19:33] <seb128> andyrock, let's see what upstream says, well done figuring it out
[19:43] <andyrock> Trevinho: https://gitlab.gnome.org/GNOME/mutter/merge_requests/474
[19:43] <gitbot> GNOME issue (Merge request) 474 in mutter "sound-player: Call ca_context_cancel in an idle to avoid deadlocks." [Opened]
[19:43] <andyrock> EOD for me