[01:28] <RAOF> robert_ancell: I'm happy to look at any SRUs you want to drive through.
[01:29] <RAOF> As long as you also make sure they're tested, so they don't sit on our pending dashboard for the better part of a year :)
[01:39] <robert_ancell> RAOF, \o/
[01:40] <robert_ancell> RAOF, the first one is snapd-glib - bug 1699005
[01:40] <robert_ancell> This one should be fairly uncontroversial, since it's mostly about matching functionality with snapd and it wasn't used in any depth until artful.
[01:46] <RAOF> “Doesn't support new APIs” is not normally SRU material :)
[01:46] <RAOF> But, obviously, snapd-glib is different.
[01:46] <robert_ancell> RAOF, yeah, is there a more paperwork required to make that more palatable?
[01:47] <robert_ancell> I need to write a Wiki page for an SRU exception, but plan to do that for the next SRU
[01:47] <RAOF> robert_ancell: You probably want to do somethinrg based on https://wiki.ubuntu.com/SnapdUpdates
[02:08] <robert_ancell> RAOF, so, I need to write that page for this SRU or we can continue without it?
[02:08] <RAOF> We can probably continue without it this time.
[02:08] <RAOF> Please get one in future, though :)
[02:08] <RAOF> Actually, what are the rdepends on snapd-glib in 16.04? and 17.04?
[02:10] <robert_ancell> RAOF, nothing
[02:10] <robert_ancell> Actually, no, gnome-software is using it but only one method call (to access snapd-login-service)
[02:25] <RAOF> My, my, that's a lot of code.
[02:26] <RAOF> robert_ancell: So, what's the test plan for snapd-glib?
[02:26] <robert_ancell> RAOF, check that gnome-software still works
[02:26] <robert_ancell> And run the tests inside the source tree
[02:26] <RAOF> We might need to have something a little more detailed :)
[02:28] <RAOF> The thing you'd need to test in gnome-software is that (a) it starts up, (b) you can try and install a snap without being logged in to your SSO account and it'll prompt you to log in, and (c) once you're logged in you can install a snap?
[02:28] <RAOF> Oh, and I guess that being logged in to the SSO account persists.
[02:28] <RAOF> ?
[02:28] <robert_ancell> Just that it prompts you when you don't have credentials and can install with them
[02:28] <robert_ancell> The credentials are managed by g-s, so that shouldn't need testing
[02:34] <RAOF> OK. Stick that up on the bug, and I'll wave in into -proposed.
[02:38] <robert_ancell> RAOF, as a comment or the test case?
[02:38] <RAOF> As the test case (please edit the bug description)
[02:40] <robert_ancell> RAOF, done
[02:41] <robert_ancell> RAOF, I didn't propose this to Yakkety since it's days from EOL. That wont be an issue will it?
[02:41] <RAOF> Nope.
[02:42] <robert_ancell> RAOF, OK, next one is updating gnome-software to 3.20.5 in xenial (bug 1703461)
[02:43] <robert_ancell> This one is a bit scary, but ultimately I think puts us in a better position than we are currently
[02:44] <robert_ancell> There's a couple of uploads, but 3.20.5-0ubuntu<IP_ADDRESS> should be the right one (reject the others)
[02:44] <RAOF> Well, at least you've pre-filed the paperwork for this one (the GNOME standing exception) ☺
[02:44] <RAOF> I shall check gnome-software after lunch.
[02:44] <robert_ancell> RAOF, cool, thanks
[06:12] <didrocks> good morning
[06:12] <jibel> morning didrocks
[06:19] <didrocks> duflu: on bug #1704050, how do you try to force the wayland session in gdm? I only have one entry "ubuntu", which should prefers X right now
[06:20] <didrocks> there is no "ubuntu on wayland" session like in lightdm
[06:20] <duflu> didrocks, There is Ubuntu on Wayland _and_ GNOME on Wayland :)
[06:20] <didrocks> duflu: hum, I don't see that one, despite having the session available
[06:20] <didrocks> (on disk)
[06:20] <duflu> Also, I'm working on Wayland :)
[06:21] <didrocks> duflu: I would like to have that session to reproduce :p
[06:21]  * duflu uploads ThinkStation to didrocks
[06:21]  * didrocks waits :)
[06:22] <didrocks> duflu: more seriously, do you think there can be some autodetection making my hw blacklisted in some way?
[06:22] <didrocks> like does wayland has a helper to test like we had in nux?
[06:22] <duflu> didrocks, I don't know... The only error I get is from X
[06:22] <duflu> Is there a gdm3 log?
[06:22] <didrocks> duflu: unrelated to that error
[06:23] <didrocks> duflu: just in general, as you are working on wayland, you may know about that detection mechanism
[06:23] <didrocks> duflu: yes, in the journal
[06:23]  * didrocks doesn't see anything related
[06:23] <duflu> didrocks, No like many people I'm just fighting to make things work with Wayland. I don't really *get it* :)
[06:24] <didrocks> duflu: it's an interesting side-effect of some code I changed (appending a session before prepending)
[06:24] <didrocks> but grrrr that I can't get a wayland option
[06:25] <duflu> didrocks, my artful install is old. Started with Unity7, then added Ubuntu Gnome, then lots of updates...
[06:25] <didrocks> same here
[06:25] <didrocks> I wonder if the list is built twice in gdm
[06:25] <didrocks> and so, there is an index mismatch
[06:26] <didrocks> which might explain your bug
[06:26] <duflu> In fact I have 8 shells to choose from :)
[06:26] <didrocks> :p
[06:27] <duflu> Oops, no errors logged because I'm using the workaround
[06:28] <didrocks> I bet something is assuming in the code to have wayland sessions before X one on their list
[06:29] <duflu> Oh I see. Yes maybe something is assuming the array order never changes
[06:31] <didrocks> mind running with debug enabled? https://help.gnome.org/admin/gdm/stable/troubleshooting.html.en
[06:31] <duflu> OK, will reproduce and check for logs in a sec
[06:31] <didrocks> as I can't reproduce as not having that session listed, I would like to keep the same logic of appending wayland sessions and fixing the other part of the code making a wrong assumption
[06:33] <duflu> didrocks,   Jul 13 14:31:15 haz gdm3[1046]: Cannot find a command for specified session: ubuntu-wayland
[06:34] <didrocks> hum, anything else more helpful in debug mode?
[06:35] <didrocks> I can try a patch in the dark and push to a ppa for you to test
[06:38] <duflu> didrocks, lots in debug: https://launchpadlibrarian.net/328568645/gdmfail-debug-log.txt
[06:38] <didrocks> Jul 13 14:35:32 haz gdm3[1050]: GdmSession: File 'ubuntu-wayland.desktop' not found: Valid key file could not be found in search dirs
[06:38] <didrocks> so, changing the session order hide it
[06:39] <didrocks> you have only one desktop file with that name on your disk, correct?
[06:39] <didrocks> under /usr/share/wayland-sessions/ubuntu-wayland.desktop
[06:39] <duflu> didrocks, $ ls -l /usr/share/wayland-sessions
[06:39] <duflu> total 12
[06:39] <duflu> -rw-r--r-- 1 root root 218 Jul 12 18:18 gnome-wayland.desktop
[06:39] <duflu> -rw-r--r-- 1 root root 221 Jul 12 18:18 ubuntu-wayland.desktop
[06:39] <duflu> -rw-r--r-- 1 root root 126 Feb  5 17:57 weston.desktop
[06:39] <didrocks> yep, all looks good
[06:40] <didrocks> so, libgdm reads in revert orders
[06:40] <didrocks> I wonder if that's this list which is unsync
[06:40] <duflu> If it's an array, maybe something is already assuming the order is fixed? So prepending is dangerous
[06:41] <didrocks> duflu: it's the contrary
[06:41] <didrocks> duflu: it was prepending
[06:41] <didrocks> we are appending
[06:42] <didrocks> https://launchpad.net/~didrocks/+archive/ubuntu/ppa/+build/13081407 is a stab in the dark, continuing to look meanwhlie
[06:45] <didrocks> hum
[06:45] <didrocks> with the older version
[06:45] <didrocks> when you log into the "ubuntu" session (X one)
[06:45] <didrocks> was it really starting X?
[06:45] <didrocks> or wayland?
[06:45] <duflu> didrocks, does appending break the 0 element on the end? https://developer.gnome.org/glib/stable/glib-Arrays.html#g-array-new
[06:46] <didrocks> duflu: I've used glist appending for years, no, it does the right thing and shift the 0 element on the end
[06:47] <didrocks> duflu: but yeah, do you mind trying this? ^
[06:47] <didrocks> so downgrade to working gdm
[06:47] <didrocks> try the ubuntu session
[06:47] <didrocks> check if it's running wayland
[06:47] <didrocks> (I bet it does)
[06:47] <didrocks> where you expect X
[06:47] <duflu> didrocks, failed to build?
[06:48] <didrocks> duflu: yeah, let's not worry about the small patch right now
[06:48] <didrocks> just downgrade to -5
[06:48]  * duflu reboots to check it's really X
[06:48] <didrocks> I'm pretty sure I understand the issue
[06:48] <jbicha> duflu: The gGNOME on Wayland session comes from the gnome-session binary package
[06:48] <duflu> Yes it's really Xorg
[06:49] <didrocks> ah, so scratch that
[06:49] <didrocks> or maybe… it has smart checks in that way
[06:49] <jbicha> I had the same problem with "Ubuntu on Wayland" not working today, but I had a kernel upgrade and more and hadn't tried isolating the cause yet
[06:50] <duflu> jbicha, bisected to gdm already
[06:50] <duflu> jbicha, https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1704050/comments/1
[06:50] <didrocks> jbicha: the issue is the append instead of prepend
[06:50] <didrocks>         search_dirs = get_system_session_dirs (self),
[06:50] <jbicha> thanks
[06:51] <didrocks> no debug to know what are search_dirs (it should be the list with Xorg, then wayland)
[06:51] <jbicha> speaking of gdm, did you see Security's response at LP: #1686393 :(
[06:51] <duflu> That said I shall reapply the workaround to reconfirm
[06:52] <didrocks> duflu: ah, you are not in -5?
[06:52] <duflu> Yep, 3.24.2-1ubuntu5 works fine
[06:52] <didrocks> and if you log into ubuntu
[06:52] <didrocks> you have the X session
[06:52] <duflu> didrocks, my above debugging was from 7 (where it's broken)
[06:52] <didrocks> with that gdm version? ^
[06:52] <didrocks> ahhhh
[06:52] <didrocks> please try with 5
[06:53] <duflu> didrocks, OK I have 5. Retry what part?
[06:53] <didrocks> log into the ubuntu session (the X one)
[06:53] <didrocks> check it's running X and not wayland
[06:53] <didrocks> jbicha: do you know what checks are done on gdm startup? I don't have any wayland session available on my machine
[06:54] <duflu> didrocks, Yes Ubuntu is 'Xorg'
[06:54] <duflu> in 5
[06:54] <didrocks> ok, so definitively not that theory
[06:54] <didrocks> thanks duflu
[06:54] <didrocks> ok, let's revert the order and set a default session for now
[06:54] <didrocks> sounds like the sanest
[06:54] <duflu> Weird. It looks like private information within that function. Order wouldn't matter
[06:55] <didrocks> yeah
[06:55] <didrocks> that's why I'm really puzzled
[06:55] <jbicha> didrocks: do you want to merge this in when you do the upload? https://code.launchpad.net/~willcooke/gdm/ubuntu/+merge/327165
[06:56] <didrocks> jbicha: maybe will should first fix the changelog conflicts
[06:56] <didrocks> that would be a good exercise for him :)
[06:57] <didrocks> duflu: the issue is from https://github.com/GNOME/gdm/blob/master/daemon/gdm-session.c#L401
[06:57] <didrocks> it can't find that ubuntu-wayland.desktop here
[06:57] <didrocks> which is the list we just build…
[06:57] <didrocks> with append instead of prepend
[06:58] <jbicha> stop changing the changelog then ;) but yeah, his changelog does need cleaning up :)
[06:58] <duflu> Also willcooke has a pending proposal that will conflict
[06:59] <duflu> Oh, you mean that one
[06:59] <didrocks> the 2 others parts of the code depending on #ENABLE_USER_DISPLAY_SERVER doesn't seem related to anything order related
[06:59] <didrocks> (so meaning: if people build with that disabled, maybe they face the same bug)
[06:59] <didrocks> duflu: do you have time for a quick local test + build?
[07:00] <didrocks> I would be interested in printing out search_dirs after the line I pointed ^ to know the list content
[07:00] <duflu> Sure, I've been distracted from my actual work for days already :)
[07:01] <didrocks> duflu: keep me posted once you get that value
[07:03] <duflu> Ah, I forgot I hadn't answered some upstream questions yet. Even more behind
[07:04] <duflu> In other news: Is there a reason why the Gnome Software icon is different between artful machines? Is that an upgrade issue ?
[07:04] <duflu> (so it's only changed in fresh installs)
[07:05] <didrocks> duflu: like fresh install has an ubuntu icon, but not on upgrade, it's the Gnome one?
[07:05] <duflu> Yeah
[07:05] <didrocks> duflu: XDG_DATA_DIRS is correct and I have an impacted machine
[07:05] <jbicha> duflu: for me, I get the Ubuntu Software branding in 'Ubuntu' but GNOME Software in 'Ubuntu on Wayland'
[07:05] <didrocks> so need to look at it, I filed a bug for this already
[07:05] <didrocks> jbicha: yeah, that's expected (and we should fix that)
[07:05] <duflu> OK, no problem.
[07:06] <duflu> In other other news: Whose idea was it to design buttons that don't look like buttons in Gnome?
[07:06] <didrocks> I wonder if G_N_ELEMENTS() isn't puzzled by NULL though
[07:07] <duflu> didrocks, It's a null terminated array so maybe that flag tells it to count the size manually
[07:07] <didrocks> yeah
[07:07] <duflu> Interesting
[07:07] <didrocks> mind priniting its result?
[07:08] <didrocks> (the G_N_ELEMENTS() count)
[07:08] <didrocks> I really wonder if that code branch never worked
[07:08] <jamesh> G_N_ELEMENTS() is compile time: it doesn't know what is stored in the array
[07:09] <duflu> Yeah that's for C arrays not GArray
[07:09] <duflu> #define G_N_ELEMENTS(arr)               (sizeof (arr) / sizeof ((arr)[0]))
[07:09] <oSoMoN> good morning desktoppers
[07:09] <didrocks> hey oSoMoN, jamesh
[07:09] <duflu> Hi oSoMoN
[07:09] <oSoMoN> salut didrocks, hey duflu, jamesh
[07:14] <duflu> didrocks, actually I can tell you just by reading it that use if G_N_ELEMENTS is wrong
[07:14] <duflu> It won't find the wayland entry because that's after a NULL
[07:15] <duflu> Problem solved
[07:15] <didrocks> duflu: wait, the count doesn't have NULL, so only the number of elements
[07:15] <didrocks> as it's based on sizeof(arr)/sizeof(elem)
[07:15] <duflu> didrocks, yeah NULL gets appended, before wayland
[07:16] <duflu> So only prepending works
[07:16] <didrocks> hum
[07:16] <didrocks> G_N_ELEMENTS (x_search_dirs) is 4
[07:16] <didrocks> no?
[07:16] <duflu> Should be 5 (I am not up to debugging yet)
[07:16] <didrocks> as NULL takes 0?
[07:16] <didrocks> (in term of size)
[07:16] <duflu> didrocks, No it's the number of pointers in the array, hence 5
[07:16] <didrocks> ohhhh
[07:17] <didrocks> yeah, it's pointers ofc
[07:17] <didrocks> so yeah, NULL is set in search_array
[07:17] <duflu> Good news - didrocks did the right thing and was fooled by bad code
[07:17] <didrocks> and then, wayland is appended
[07:17] <duflu> Maybe
[07:17] <didrocks> yeah, that code branch never worked
[07:18] <didrocks> tell me once you get that debug printed out :p
[07:18] <duflu> Actually the code is good, but it was nonobvious that append would not work
[07:18] <didrocks> well
[07:18] <didrocks> look at the original code
[07:18] <didrocks> https://github.com/GNOME/gdm/blob/master/daemon/gdm-session.c#L360
[07:18] <didrocks> if you define ENABLE_WAYLAND_SUPPORT and not define ENABLE_USER_DISPLAY_SERVER, you are in that case
[07:18] <didrocks> (which doesn't work)
[07:19] <duflu> didrocks, Oh yes, the bug already existed
[07:19] <duflu> So indeed "Good news - didrocks did the right thing and was fooled by bad code"
[07:19] <didrocks> :p
[07:20] <duflu> didrocks, I think someone can fix that without further testing...?
[07:20] <didrocks> yeah
[07:21] <didrocks> do you want to do it? I can do it, just don't want to steal your commit :)
[07:21] <duflu> didrocks, well I can test and verify it for sure... no problem
[07:21] <didrocks> and praise when reported upstream
[07:21] <didrocks> ;)
[07:37] <didrocks> duflu: tell me once you get your patch tested and I'll just sponsor it
[07:38] <duflu> didrocks, yeah I'll do it today. Probably Ubuntu before upstream tho
[07:38] <didrocks> duflu: sounds good
[07:38] <didrocks> duflu: just open a bug in bugzilla and reference it on the quilt patch
[07:39] <didrocks> (even if I think next time we touch that patch we'll just inverse the logic back to favor wayland sessions)
[08:02] <Laney> morning
[08:03] <flexiondotorg> Morning Laney didrocks duflu oSoMoN jamesh
[08:03] <didrocks> hey Laney, flexiondotorg
[08:03] <oSoMoN> good morning Laney, flexiondotorg
[08:04] <duflu> Morning flexiondotorg
[08:04] <duflu> Morning Laney
[08:06] <Laney> hey flexiondotorg hey didrocks hey oSoMoN hey duflu
[08:06] <Laney> how's it going?
[08:06] <oSoMoN> not too bad round here
[08:06] <didrocks> good, started with some interesting gdm bug :p
[08:07] <Laney> oh yeah
[08:07] <Laney> what's that?
[08:07] <didrocks> but everything is under control once someone has a session to test :)
[08:07] <didrocks> Laney: basically, the branch with "append" instead of "prepend" never worked
[08:07] <didrocks> the bottom of it is that the previous list we append to already has a NULL pointer
[08:07] <didrocks> so, the wayland session was never found
[08:08] <didrocks> (patch to get upstream, even if I don't think anyone is building with the 2 #ifdef condition)
[08:08] <Laney> ah right
[08:08] <willcooke> morning all
[08:11] <didrocks> hey willcooke
[08:11]  * didrocks needs to add a new expection in the seed for a -dbg package
[08:13] <didrocks> thunderbird pulls thunderbird-gnome-support-dbg in main, which brings thunderbird-gnome-support, which brings indicator-messages, which pulls libindicator-messaging-menu, which …
[08:17] <seb128> hey Laney willcooke
[08:17] <seb128> or and other desktopers, looks like I was too busy to chat on other channels and forgot to say hi here
[08:18] <flexiondotorg> Morning willcooke seb128
[08:19] <seb128> hey flexiondotorg
[08:21] <oSoMoN> salut seb128
[08:21] <oSoMoN> good morning willcooke
[08:21] <willcooke> How's it going oSoMoN?  I'm reading good comments about the new LO snap - great stuff!
[08:22] <oSoMoN> willcooke, doing good, thanks! trying to wrap up everything that’s on my list before I leave for holidays
[08:22] <ricotz> hey desktopers
[08:22] <oSoMoN> hey ricotz
[08:23] <ricotz> hey oSoMoN
[08:24] <willcooke> duflu, still around?  https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946
[08:24] <willcooke> Do I just update the changelog to say artful?  is it that simple?
[08:26] <duflu> willcooke, yes I think so
[08:27] <Laney> it's quite normal for the uploader to do that too
[08:27] <willcooke> ah, good to know.  Well, I'm happy to just edit the debdiff and reattach it, if that helps
[08:27] <willcooke> I'll attach one with the change anywy, wont take a sec
[08:34] <duflu> Laney: I was wondering that, thanks
[08:34] <duflu> Not like it's checksummed
[08:43] <duflu> didrocks: OK, done. Works too.
[08:44] <seb128> lut oSoMoN
[08:45] <Laney> hey seb128
[08:45] <Laney> you good?
[08:46] <didrocks> duflu: excellent, MP against the ubuntu branch?
[08:46] <duflu> didrocks, https://code.launchpad.net/~vanvugt/gdm/fix-1704050/+merge/327360
[08:47] <didrocks> duflu: does it work with the prepend case still?
[08:47] <didrocks> (when you submit it upstream)
[08:47] <didrocks> duflu: just: mind opening a bug upstream and reference it from your patch?
[08:48] <duflu> didrocks, already have an upstream bug with the patch
[08:48] <didrocks> duflu: just add it on top of debian/patches/Avoid-double-NULL-terminated-array-LP-1704050.patch
[08:48] <didrocks> that way, we can track
[08:49] <duflu> didrocks, I was reluctant to reformat as I could not remember the rules. Also upstream already have that patch. The upstream bug is linked in Launchpad now
[08:49] <didrocks> duflu: linking in LP is good enough, thanks!
[08:49] <didrocks> merging and sponsoring
[08:51] <didrocks> hum, no tag and you set it to artful
[08:51]  * didrocks adds a tag
[08:52] <duflu> didrocks, we were just talking about that. Do you prefer UNRELEASED if not tagged?
[08:52] <didrocks> duflu: I generally prefer UNRELEASED not tagged, but not a biggie
[08:53] <duflu> OK then willcooke got it more right
[08:53] <duflu> For reviewer=didrocks
[08:53] <didrocks> (so, basically, a separate commit to set it to artful + tag for release)
[08:54] <duflu> didrocks, cool will do in future
[08:54] <duflu> I don't think I usually/ever propose to ubuntu branches
[08:54] <didrocks> duflu: no worry! sponsored :)
[08:55] <duflu> So sorry in advance to willcooke. I am making new conflicts in gdm
[08:55] <didrocks> ;)
[08:56] <didrocks> highly demanded package
[08:56] <duflu> didrocks, I _assume_ and it seems to be true that append does go before the implicit NULL :)
[08:57] <didrocks> duflu:yeah, I hope that the prepend case does have an implicit NULL so that your fix is accepted :)
[08:58] <duflu> didrocks, I think prepend will always work regardless of the contents
[08:58] <didrocks> I meant, if there is no match and the list isn't ended by NULL…
[08:59] <duflu> didrocks, I think new = {NULL}
[09:02] <seb128> Laney, I'm good thanks, you?
[09:03] <Laney> good!
[09:03] <Laney> went to folk club last night, was funny
[09:05] <seb128> nice
[09:06] <duflu> didrocks, do you recomment UNRELEASED for debdiffs too?
[09:06] <duflu> recommend
[09:09] <didrocks> duflu: no, debdiff can be the final thing, ready to sponsor
[09:10] <duflu> Makes sense
[09:10] <duflu> both ways
[09:10] <didrocks> the only thing with UNRELEASED in a branch is that the author can ammend, commit separated a fix while still being in the "UNRELEASED" part
[09:10] <didrocks> amend*
[09:13] <flexiondotorg> Could one of the desktopers merge this please - https://code.launchpad.net/~ubuntu-mate-dev/indicator-session/mate-integration/+merge/325600
[09:13] <flexiondotorg> I've addressed all the feedback and been running a PPA build for several weeks.  If landing by hand you need to copy the commit message from the MP because it's not in bzr
[09:23] <didrocks> duflu: depends on the branch, some prefer to always merge, some not.
[09:23] <duflu> didrocks, fair enough. I'll keep it in mind
[09:23] <didrocks> we should just standardize on one way to do it IMHO
[09:24] <didrocks> so that you don't have wrong expectations, I see what you wanted…
[09:24] <didrocks> (also one tool, not some branches in git vs other in bzr)
[09:24] <didrocks> I guess a discussion at the start of a cycle, one all the transitions are over and polish done :)
[09:37] <seb128> L_aney is going to work on the git-for-packaging for Debian pkg-gnome during debconf
[09:37] <seb128> so we might want to look at building on top of that next cycle then
[09:37] <didrocks> nice!
[09:37] <seb128> a discussion to have for when we get our team week
[09:37] <didrocks> yep
[09:57]  * duflu -> vegetable peeling fun
[10:27] <willcooke> quick reboot
[10:29] <didrocks> popey: if you are too impatient to wait for gdm to published in the release pocket, it's in -proposed right now
[10:30] <Laney> a gdm3 upload a day
[10:30] <Laney> keeps the something something away
[10:30] <didrocks> ;)
[10:30] <didrocks> "bugs" for one someting
[10:30] <didrocks> but need another adjective
[10:31] <didrocks> am I the only one to get this with wayland + our theme on gnome-terminal: http://imgur.com/a/k48Se ?
[10:31] <didrocks> ah, that's the transparency feature
[10:31] <jibel> didrocks, it's a known bug
[10:32] <Laney> it's reported
[10:32] <didrocks> ah nice, do you know if our transparency patch is the same than in fedora?
[10:32]  * didrocks will look
[10:32] <jibel> bug 1650395
[10:33] <Laney> more or less
[10:33] <didrocks> interesting that the color is theme-dependent
[10:33]  * didrocks likes
[10:33] <Laney> but maybe rishi fixed it or something
[10:33] <didrocks> my borders are bigger :)
[10:33] <Laney> and we need to pull i again
[10:33] <didrocks> yeah, would worth a look
[10:33] <Laney> he's got a repo with it in
[10:34] <didrocks> hum, do you want to test it? (I'm not going to do it today, just as you seem to know more where things are…)
[10:34] <didrocks> I'm happy next week to have a look otherwise
[10:34] <Laney> https://github.com/debarshiray/gnome-terminal
[10:34]  * didrocks got a new tab
[10:34] <didrocks> thx
[10:34] <Laney> we took that and then added the theme colours stuff
[10:35] <Laney> will look eventually, but not right now
[10:35] <Laney> so whoever gets there first can :-)
[10:35] <didrocks> deal!
[10:35] <didrocks> :-)
[10:36] <Laney> actually I'll ask him quickly, that'll be easier
[11:09] <willcooke> has anyone tried artful on a wired ethternet connection?  I can't get it to accept a DHCP address.  Its being offered one, but seems to be ignoring it.  cyphermox perhaps?
[11:14] <popey> didrocks: will test!
[11:17] <willcooke> popey, be a love and test wired network as well would you?
[11:18] <Laney> I'm on wired right now
[11:18] <Laney> these bits are wires alllllllll the way baby
[11:19] <willcooke> mannn
[11:19] <willcooke> that means its something on my network.  Damn it.
[11:19]  * willcooke tries a live session
[11:31] <popey> willcooke: i am on wired
[11:32] <willcooke> and it just works?
[11:32] <willcooke> curses
[11:32] <popey> wfm
[11:33]  * willcooke breaks out tcpdump
[11:33] <popey> what does "nmcli d" say?
[11:33] <willcooke> I know it's requesting a dhcp address, I can see it on the server
[11:33] <willcooke> and in syslog
[11:34] <popey> i haven't setup wifi on this laptop yet
[11:34] <popey> only wired
[11:36] <popey> ok, connected to wifi, also works, and doesn't seem to have a problem switching between wired and wifi
[11:41] <andyrock> anyone aware of touchpad issues with xenial in the last few weeks?
[11:41] <andyrock> mostly with double finger scrolling and syntaptic device
[11:43] <popey> i haven't. been using a touchpad for the first time in a while these last couple of weeks and it's just as crazy as ever (ie. not a nipple) :D
[11:48] <seb128> andyrock, what sort of issues?
[12:01] <Trevinho> popey: it's impossible to stay away from nipples :-D
[12:01] <Trevinho> I can't too
[12:01]  * Laney titters
[12:01] <Trevinho> Laney: you should get a thinkpad or at least a thinkpad BT keyboard to love it more :-D
[12:04] <Trevinho> mpt: hey, remember that change for u-c-c, we defined the graphics levels as "High" and "Low", but I think we should also add the "auto-detect" mode... As by default we use that way, while we use the setting only when set
[12:04] <Trevinho> are you ok with that?
[12:55] <didrocks> FINALLY indicator-messages off main
[13:05] <seb128> didrocks, well done
[13:08] <jbicha> seb128: upstreams says "no, fix your tools" :) https://bugzilla.gnome.org/show_bug.cgi?id=784877
[13:17] <andyrock> seb128: seems like it does not work after login (the mouse)
[13:17] <andyrock> or a new created user session it works fine
[13:17] <popey> didrocks: nice work fixing gdm :)
[13:17] <andyrock> probably not a but (just a misconfiguration)
[13:17] <andyrock> but I'm wondering how I could fix it
[13:18] <didrocks> popey: well, it was co-analyze with duflu (I don't have the wayland session displayed at all here, had to force it) :)
[13:18] <didrocks> but thanks for confirming the fix worked!
[13:18] <seb128> jbicha, I'm not surprised ;-) thanks for trying though!
[13:18] <jbicha> didrocks: I'm going to go ahead and merge and upload will's GDM bluetooth workaround now if you don't object
[13:19] <seb128> andyrock, settings doesn't work?
[13:19] <jbicha> seb128: I might push it to Debian though since we're nearly in sync there
[13:19] <didrocks> jbicha: all is fine for me, I guess nobody plans to upload GDM in the next 20 minutes… :p
[13:19] <jbicha> lol
[13:20] <andyrock> seb128:  there is no setting for the mouse
[13:20] <andyrock> at least for the touchpad
[13:20] <seb128> andyrock, weird
[13:20] <seb128> did you try binput?
[13:21] <andyrock> xinput?
[13:21] <andyrock> yep but the weird thing it that it's an user session problem
[13:28] <jbicha> didrocks: I'm fine with uploading the debdiff from LP: #1130137 now
[13:30] <didrocks> jbicha: if you think upstream is going to fix it, yeah, feel free to sponsor it
[13:30] <didrocks> willcooke: ^
[13:31] <didrocks> if it's something we will carry in the long term, a more maintainable solution is needed
[13:45] <seb128> jbicha, unsure uploading the bluetooth workaround is right, that removes the motivation to push toward the real fix
[13:46] <seb128> we can do workarounds around beta time if needed as plan B
[14:01] <jbicha> seb128: the bug affects Ubuntu GNOME since 16.04 LTS; the workaround kills bluetooth audio on the login screen but bluetooth audio in the session seems a lot more important
[14:07] <seb128> jbicha, right, doesn't change my statement
[14:08] <seb128> I mean devel is to fix issues the proper way
[14:08] <seb128> workarounds are backup solutions when we can't get the proper fix
[14:08] <seb128> jbicha, btw I'm surprised that it's affecting most distros, some have wiki instructions to workaround and nobody opened an upstream gdm bug about that before (I did it yesterday)
[14:09] <seb128> jbicha, anyway I'm not strongly against it so if you want to upload the workaround feel free, I would just have done that at beta time (and SRU to help stable users)
[14:15] <jbicha> seb128: by the time you spoke up, I had already pushed gdm to bzr and tagged it but didn't quite dput yet, so I'm not sure how to fix it now
[14:16] <Laney> didrocks: http://people.canonical.com/~laney/weird-things/transparent.png
[14:16] <seb128> jbicha, just dput it's not the end of the world
[14:16] <willcooke> I can add a known issue to the release notes now
[14:16] <seb128> jbicha, and might make artful more enjoyable for those who are on it
[14:17] <jbicha> thanks, done
[14:17] <willcooke> popey, looks like we're going to "fix" the bt audio issue re: your blog post for testing ^
[14:17] <popey> I'll add wording to say "this may or may not be fixed by the time you come to test", or something?
[14:18] <willcooke> popey, sure
[14:18] <didrocks> Laney: nice! with a new version of the patch?
[14:18] <Laney> rishi pointed me to one from fedora
[14:18] <didrocks> excellent! :)
[14:22] <willcooke> is it possible that two things are fighting over apt/sources.list?  I've got loads of errors about things being configured multiple times all of a sudden
[14:22] <willcooke> I'm fixing it manually, but I dont know how it came to be like this
[14:24] <jbicha> Laney: btw, I'm interested in rishi's notifications patches for vte/terminal but I had trouble getting it to work months ago
[14:25] <jbicha> willcooke: that's LP: #1697120 and LP: #1579372 I believe you can workaround it by uninstalling apt-file
[14:25] <willcooke> jbicha, ahh
[14:25] <willcooke> jbicha, that's almost certainly what it was, thanks!
[14:29] <Laney> jbicha: vte.sh isn't run for us, because we run bash as a non-login shell. you'll need to change that option in your gnome-terminal profile preferences at least.
[15:19] <jbicha> did you see the response from Security on LP: #1686393 ?
[16:22] <jbicha> Laney: were you planning on SRUing the terminal transparency fix? or I could…
[16:22] <Laney> No
[16:22] <Laney> Fixing things on wayland in old releases isn't a good use of my work time - so feel free
[16:55] <pitti> Laney: oh dear @ http://autopkgtest.ubuntu.com/running -- glibc plus KDE fun
[16:55] <Laney> pitti: and lgw01 is down
[16:56] <pitti> Laney: how are the minions holding up so far?
[16:56] <pitti> ouch
[16:56] <Laney> been hassling to get it fixed
[16:56] <pitti> glad that we have the -huge queues
[17:05] <Laney> hopefully we'll get back up to full capacity soon
[17:06] <Laney> otherwise I'll think about killing some of the queue
[18:45] <willcooke> night all
[18:58] <immu> hmm
[20:23]  * oSoMoN falls off the face of the internet for two weeks
[20:23] <oSoMoN> see you!


[03:09] <shirish> does anybody else have problems installing git-core new version?
[03:14] <pwnguin> yes
[03:14] <pwnguin> i already filed a bug
[03:15] <Hobbsee> bug #?
[03:15] <pwnguin> 164167
[03:16] <Hobbsee> bug  164167
[03:16] <ubotu> Launchpad bug 164167 in git-core "git-core fails to install" [Undecided,New] https://launchpad.net/bugs/164167
[03:16] <Hobbsee> nice
[03:17] <pwnguin> i guess nobody wants ownership of git
[03:17] <pwnguin> or perhaps the recommended way to use git is to get git to get itself
[03:18] <shirish> pwnguin: confirmed it
[03:18] <Hobbsee> ah yes, debian knows about it
[03:18] <Hobbsee> those packages are all directly synced from debian
[03:22] <Hobbsee> looks like it only broke yesterday.  they should fix it
[03:23] <pwnguin> probably
[03:23] <pwnguin> but how do the kernel people get along?
[03:33] <pwnguin> what's the deal with jmicron IDE?
[03:33] <pwnguin> my roommate has utterly failed at ubuntu
[03:34] <RAOF> At one point the deal was that the chipset didn't actually have integrated IDE, and there was no support for the tacked-on IDE controller.  Is this still a problem with {Gutsy, Hardy} though?
[03:34] <pwnguin> we install it, and then reboot and grub errors
[03:34] <pwnguin> theres probably like eight errors hiding in here
[03:34] <pwnguin> he wants ubuntu on an ide drive and vista on sata
[03:35] <pwnguin> its def a problem for gutsy
[03:36] <pwnguin> the chipset has to have IDE, as thats the only reason its on the mobo
[03:36] <RAOF> Ooooh. Sounds tricky.
[03:36] <pwnguin> he made it work before
[03:36] <pwnguin> but now grub just gives error 25 on boot
[03:37]  * RAOF is clueless
[03:38] <pwnguin> the forums all have workarounds for cd drives on ide
[03:38] <pwnguin> which is good i guess, if you have an ide cdrom
[03:38] <pwnguin> its possible that grub doesn't suppor jmicron
[03:39] <pwnguin> as it only recieved linux support in like 2.6.17
[03:39] <RAOF> Surely grub doesn't *have* to support jmicron.  It's the bios that does?
[03:40] <pwnguin> got me
[03:40] <pwnguin> theres lots of "set the mode to ahci" or something
[03:40] <pwnguin> no such setting
[03:40]  * shirish remembers lot of hue & cry about Jmicron during Gutsy's time.
[03:41] <pwnguin> RAOF: note that jmicron IS the tacked on IDE
[03:41] <RAOF> Yeah.
[03:41] <pwnguin> i havent put the drive into my computer, but i think it actually installed ok
[03:41] <pwnguin> theres clearly partitions set up
[03:41] <RAOF> :)
[03:41] <pwnguin> i had a talk with ompaul about it
[03:42] <pwnguin> i should probably just reread it / hit him up
[03:45] <shirish> https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/81596 which talks about the JMicron chip
[03:45] <ubotu> Launchpad bug 81596 in linux-source-2.6.20 "Feisty Herd 4 does not boot on ASUS P5W DH Deluxe" [Medium,Incomplete]
[04:56] <cps1966> !kde4
[04:56] <ubotu> KDE 4 is the next major release of the K Desktop Environment. For more information see <http://en.wikipedia.org/wiki/KDE_4>. The Release Schedule is available at http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule. Beta 3 packages can be found at http://kubuntu.org/announcements/kde4-beta3.php
[09:49] <alon_> Amaranth: Remember my font problem? It isn't a font problem, it's a driver problem - when I switch to vesa in xorg.conf it goes away. So fontconfig is fine, it's something with the driver.
[09:49] <Amaranth> fun
[09:49] <alon_> :)
[09:58] <pwnguin> which driver are you normally using?
[10:13] <alon_> pwnguin: I usually use "intel". After hardy upgrade it gave me the described problems. Switching to vesa is ok (but then I don't have accel or dual screen). And now "intel" just hangs. Currently apt-geting the dbg driver to get a better call stack.
[10:29] <Hobbsee> alon_: current -intel wont be fixed for a while
[10:29] <Hobbsee> they're going to get the kernel for the new stuff in, and then the new intel driver, then look for regressoins
[10:38] <alon_> Hobbsee: stack showes it isn't stuck in intel, but in xserver - specifically probing for modes. It seems to not like my preferred mode some how (I have it set to 1440x900). This is the bottom most (unless you count libc):../../../../hw/xfree86/modes/xf86Crtc.c:1406. I have the sources - it is a loop going through the modes. It seems to be endless for some reason (bad next pointers?)
[10:39] <Hobbsee> no idea
[10:39] <alon_> Hobbsee: of course it doesn't get stuck when using vesa driver, so naturally it has something to do with the intel driver. I have no idea either - I'm going to use vesa for now.
[10:39] <Hobbsee> true
[10:39]  * Hobbsee just hasnt upgraded -intel
[10:40] <alon_> Hobbsee: you think I can downgrade it without having a problem with the newer X packages all around?
[10:42] <Hobbsee> this is the feisty version of -intel :)
[10:42] <Hobbsee> well, built for gutsy
[10:43] <alon_> Hobbsee: I have to confess I haven't actually downgraded a package, so I'll have to go read some docs. I'll do it later..
[11:28] <alon_> Hobbsee: removing PreferredMode solved the infinite loop problem.
[11:57] <alon_> Hobbsee: well, problem solved, sorta - NoAccel makes it ok again. So I guess fontconfig does something that is accelerated, while enlightenment e17 and xterm (and yudit) don't. Now I can patiently wait for someone to fix this.
[11:57] <alon_> maybe I should be reporting this to the intel guys?
[18:28] <silent> does anyone know how to mount ntfs-3g in fstab giving users permission to mount? 'users' isn't working
[18:38] <stdin> silent: users,noauto ?
[18:52] <silent> stdin, current entry
[18:52] <silent> UUID=791F09DC27F6580D /win ntfs-3g nls=utf8,users,noauto,exec,umask=000,uid=1000,gid=1000 0 0
[18:54] <silent> Error opening partition device: Permission denied
[18:54] <silent> Failed to mount '/dev/sda1': Permission denied
[18:54] <pwnguin> is it users or user?
[18:55] <pwnguin> oh
[18:55] <pwnguin> silent: what groups is your user in?
[18:56] <pwnguin> ntfs3g is a fuse FS, so you need access to the fuse device
[18:56] <silent> pwnguin, 1000
[18:56] <pwnguin> what?
[18:56] <pwnguin> group*s*
[18:56] <silent> user is silent in group silent
[18:56] <pwnguin> need moar groups
[18:57] <silent> k this will take a while
[18:57] <pwnguin> just bring up a terminal and run "groups"
[18:57] <silent> uid=1000(silent) gid=1000(silent) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),104(scanner),108(lpadmin),110(admin),115(netdev),117(powerdev),1000(silent)
[18:58] <pwnguin> add user silent to the group fuse
[18:58] <silent> how? I've never added users to groups before
[18:58] <pwnguin> just use the gui
[19:00] <pwnguin> hit users&groups then go to the properties of your user
[19:00] <silent> I'm in the gui, I can manage groups but I dont see any option to add groups
[19:00] <pwnguin> hmm
[19:00] <silent> k I'm on the account tab
[19:01] <pwnguin> user privledges
[19:01] <pwnguin> "allow use of fuse devices like LTSP thin..."
[19:01] <pwnguin> if it's not there we need to add it
[19:01] <silent> its there
[19:01] <silent> I'll try mounting now
[19:02] <silent> permission denied
[19:03] <pwnguin> truth be told ive not set up ntfs-3g
[19:04] <silent> this skin is messing with me, I cant tell which options are enabled and which arent
[19:04] <pwnguin> https://help.ubuntu.com/community/MountingWindowsPartitions/ThirdPartyNTFS3G
[19:04] <pwnguin> which skin?
[19:04] <silent> custom theme
[19:05] <pwnguin> hmm
[19:05] <silent> changed it
[19:06] <silent> now i have check marks in bullets
[19:06] <pwnguin> does /var/log/messages or /var/log/dmesg contain any information on what went wrong?
[19:07] <silent> doesnt look like it
[21:46] <bardyr> !info linux-image-generic
[21:46] <ubotu> linux-image-generic: Generic Linux kernel image. In component main, is optional. Version <IP_ADDRESS>.21 (gutsy), package size 24 kB, installed size 52 kB
[21:47] <bardyr> hey btw :)
[22:20] <theunixgeek>  Hello. I'm following the osdev Bare Bones tutorial for writing a simple kernel. http://www.osdev.org/wiki/Bare_bones I'm a complete noob at this, so please don't assume I know all the terminology you guys do. I'd like to be able to boot the kernel shown in the tutorial in either Bochs or QEMU. How would I go about this?
[22:46] <knix> thomax: What does this have to do with ubuntu?
[22:46] <knix> ignore that :)


[01:06] <Wild_Man> Hi krytarik you around?
[01:07] <krytarik> Yeah.
[01:08] <Wild_Man> I am reviewing the wiki and I do not know if we want this kind of article included, imo I do not think so, https://samuelhewitt.com/blog/2019-01-18-addressing-icon-themes
[01:08] <Wild_Man> Please have a look
[01:08] <krytarik> Ok, looking.
[01:09] <krytarik> Is the Lubuntu Council one in the Planet section yet btw?
[01:09] <Wild_Man> Yes
[01:09] <Wild_Man> So is this article
[01:13] <krytarik> Yeah, I'd agree passing on this on - i.e. not including it.
[01:14] <Wild_Man> Okay, That is what I thought
[01:14] <Wild_Man> When did we go to doing so much editing on the wiki instead of in gdoc?
[01:16] <krytarik> We didn't?  Except this week it seems the blog section wasn't quite ready yet while Bashing-om wanted to get started on the wiki page already - which was an appropriate decision to make.
[01:23] <Wild_Man> krytarik, this one is about live patching but mentions SuSe, so I am thinking again that we should drop it? https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.1-Livepatch-Atomic
[01:23] <krytarik> Ok, looking too.
[01:25] <guiverc> fyi: Wild_Man i never looked at it, the late summaries I wrote was between 0000-0200 this morning; that was new & i didn't want to look (nor did I add it)
[01:26] <Wild_Man> guiverc, that is okay you have done good, trying to keep up and clean up summaries of others
[01:27] <Wild_Man> Live patching is of interest just do not know if we should include this one
[01:27] <Wild_Man> guiverc, I am not thinking clearly I have a fever and chills at the moment
[01:28] <krytarik> Wild_Man: The last one is appropriate to include though - he only mentions SUSE as part of the developers working on this.
[01:29] <Wild_Man> Okay, just wanted to make sure, thanks!
[01:29] <guiverc> it's also I think a better quality summary; I can't find copy/pastes (non-original work); needs heading fixed..
[01:30] <guiverc> i take it back - the summary is for a different article?
[01:32] <Wild_Man> I have to go fix dinner for my wife bbl
[02:48] <Bashing-om> looking, and going back to laying down to rest.
[09:51] -SwissBot:#ubuntu-news- ::Softpedia:: Linux Virus Removes Security Software to Mine Monero @ https://news.softpedia.com/news/linux-virus-remove-security-software-to-mine-monero-524623.shtml (by Bogdan Popa, Microsoft News Editor)
[16:27] -SwissBot:#ubuntu-news- ::Planet:: Santiago Zarate: Open Build Service- Contributing on a project @ https://foursixnine.io/blog/2019/01/21/Open-Build-Service-Contributing-on-a-project.html
[18:35] <Bashing-om> Polishing in Gdoc for UWN562. Target time for publishing -> hope at 21:00 GMT.
[20:13] <Bashing-om> And UWN562 - done. up for critique and careful proof reading. Target time to publish 45 minutes.
[21:07] <Bashing-om> And M/L is away .. post to the forum done, got a small error to fix on the WIKI.
[21:25] <Bashing-om> Annddd .. the re-directs done. Pending is the social media.
[21:29] <Bashing-om> Off on break .. will check back here in a bit.
[22:13] <guiverc> push uwn #562 to fridge?
[22:27] -SwissBot:#ubuntu-news- ::Planet:: Kubuntu General News: KDE Plasma 5.14.90 (the beta for Plasma 5.15) is available for testing @ https://kubuntu.org/news/kde-plasma-5-14-90-the-beta-for-plasma-5-15-is-available-for-testing/
[22:42] <Wild_Man> Hello, just got back from the Doctor, does social media need done?
[22:45] <Wild_Man> Hello Bashing-om , ^^^
[22:48] <guiverc> Wild_Man, hasn't gone to fridge, i was after 2nd to publish
[22:49] <Wild_Man> guiverc, I 2nd
[22:49] <guiverc> (i haven't looked or thought about social media) - thanks Wild_Man :)
[22:49] <Wild_Man> guiverc, I will do social
[22:50] <guiverc> http://fridge.ubuntu.com/2019/01/21/ubuntu-weekly-newsletter-issue-562/
[22:52] <Wild_Man> Thanks!
[22:58] <Wild_Man> Done!
[23:00] <guiverc> :) & thanks Wild_Man
[23:01] <Wild_Man> guiverc, Your welcome! I am going to be away a few days while I recover from the flu.
[23:12] -SwissBot:#ubuntu-news- ::Planet:: The Fridge: Ubuntu Weekly Newsletter Issue 562 @ http://fridge.ubuntu.com/2019/01/21/ubuntu-weekly-newsletter-issue-562/
[23:21] <guiverc> you get well Wild_Man
[23:23] <Bashing-om> Wild_Man: Take care of that flu .. it is bad news !


[05:37] <pitti> Good morning
[06:00] <didrocks> good morning
[06:24] <pitti> bonjour didrocks
[06:24] <didrocks> Guten Morgen pitti
[07:25] <didrocks> fginther: hey, once you are around: FYI, the amd64 machine is down again after the daily update… Can you give me access to be able to reboot it until you switch to the better solution?
[07:33] <willcooke> morning
[07:33] <didrocks> hey willcooke
[07:37] <seb128> good morning desktopers
[07:37] <didrocks> salut seb128
[07:38] <seb128> lut didrocks ;-)
[07:54] <didrocks> seb128: on https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1353951, did you want to wait on someone to prepare a patch? Not sure why sponsored is subscribed as there is nothing ready to sponsor
[07:54] <didrocks> seb128: I can do the work if needed as my sponsoring shift, even if it's not really "sponsoring"
[07:56] <seb128> didrocks, sponsors is subscribed because it's a patch we need and that's the most obvious way we have to keep it visible
[07:56] <seb128> didrocks, I planned to do it myself this week if nobody does it before
[07:56] <seb128> didrocks, yes, I slightly abuse the sponsoring queue for those items, but I think that makes sense
[07:56] <didrocks> seb128: I'll do it then
[07:56] <seb128> thanks
[07:56] <didrocks> yw
[07:57] <seb128> it might be good to SRU to trusty as well
[07:58] <willcooke> tkamppeter, hey hey!  It's meeting time again.  Same deal as yesterday I think
[07:58] <didrocks> seb128: hum, wouldn't it be better to update trusty with .6 rathe?
[07:58] <didrocks> rather*
[07:59] <tkamppeter> willcooke, I have dialled in ad waiting for you to connect.
[07:59] <seb128> didrocks, hum?
[07:59] <willcooke> tkamppeter, dialing now
[07:59] <didrocks> seb128: https://git.gnome.org/browse/evolution-data-server/?h=evolution-data-server-3-12
[07:59] <seb128> didrocks, which one did you mean "utopic with .6" ?
[07:59] <didrocks> seb128: so e-d-s 3.12.6
[08:00] <seb128> didrocks, trusty is on 3.10 and there is no > .4
[08:00] <seb128> didrocks, utopic is on 3.12 which has a .6
[08:00] <didrocks> seb128: I'm talking about utopic, as we are on 3.12
[08:00] <seb128> didrocks, you wrote trusty ;-)
[08:00] <didrocks>  evolution-data-server | 3.12.4-0ubuntu1     | utopic           | source, amd64, arm64, armhf, i386, powerpc, ppc64el
[08:00] <seb128> didrocks, right, that makes sense
[08:00] <seb128> didrocks, I was wondering if you wanted to SRU 3.12 to trusty
[08:00] <didrocks> seb128: so, utopic doesn't have .6, right?
[08:00] <seb128> or if you typoed
[08:00] <seb128> no
[08:00] <seb128> .6 is recent
[08:01] <seb128> if you want to do the update please do ;-)
[08:01] <didrocks> yeah, will be similar
[08:01] <seb128> Laney handled e-d-s this cycle and I think that one went out since he's away
[08:01] <didrocks> .5 in august though!
[08:01] <didrocks> slacker ;)
[08:01] <seb128> hehe
[08:06] <didrocks> interesting, I didn't have germinate installed
[09:34] <marga> Trevinho, the feedback has been a bit silent for my taste, but at least nobody has said that they got the missing-password issue after installing your package
[09:35] <marga> They did say that compiz was eating CPU like crazy but this happened to people running both the modified and the unmodified version, so I expect it's a different issue.
[09:47] <seb128> dpm, hey
[09:48] <dpm> hey seb128
[09:48] <seb128> dpm, I enabled translations for a few packages that were missing it, like sync-monitor or indicator-transfer
[09:48] <seb128> dpm, do we need to let the translators know in some way, or flag those in the list so they show in the phone high ranking?
[09:49] <dpm> I will add them to the stats pages. However, last time I looked, they were missing i18n altogether, and I've not seen any status changes in the bugs (although I'm still catching up on e-mail)
[09:50] <seb128> dpm, the indicator is missing i18n? what does that mean?
[09:50] <seb128> dpm, that it wouldn't use the strings even if the .mo is there? I doubt it, it's an indicator and it's standard code similar to the other ones
[09:50] <seb128> dpm, sync-monitor I don't know about
[09:51] <seb128> dpm, still we should get it translated, so when we fix the code the strings are there
[09:51] <dpm> seb128, there weren't any strings marked for translation. But before I speculate more, let me have a look again
[09:51] <seb128> dpm, thanks
[09:51] <seb128> dpm, well, in those cases they are strings and I made the templates be imported
[09:52] <seb128> dpm, https://translations.launchpad.net/ubuntu/utopic/+source/sync-monitor
[09:52] <dpm> ok, cool
[09:52] <seb128> dpm, https://translations.launchpad.net/ubuntu/utopic/+source/indicator-transfer
[09:54] <dpm> seb128, ah, that's what confused me: http://bazaar.launchpad.net/~indicator-applet-developers/indicator-transfer/trunk.14.10/files/head:/po/ - no .pot file, however luckily the source package does generate one
[09:58] <seb128> dpm, thanks for calling my work "luckily" :p
[09:58] <seb128> dpm, it generate one because I did submit fixes for that to happen and then accepted the template in launchpad
[09:58]  * dpm hugs seb128
[09:58] <seb128> shrug
[09:58] <seb128> that's slightly insulting
[09:59] <seb128> dpm, if I did it the wrong way feel free to tell me what I should have done instead at least ;-)
[09:59]  * seb128 hugs dpm back
[10:01] <dpm> seb128, it's perfect. I just meant that the upstream devs should have enabled translations upstream. And by luckily I wasn't implying that the work got done by chance, I just meant that it's good that even upstream translations are not enabled, the source package ones are
[10:01] <seb128> dpm, well, I did it this way because the "translation in upstream trunk" doesn't work
[10:01] <seb128> dpm, we keep having outdated pot files
[10:01] <seb128> dpm, we need a way to get the pot updated automatically
[10:02] <seb128> the "translate in ubuntu" is more robust
[10:02] <seb128> dpm, I'm pondering undoing the "translate upstream" for ubuntu-system-settings btw
[10:02] <dpm> seb128, yeah, I was meant to have a conversation about automatically updating .pot files in the ci-train with Lukasz, but I didn't manage before going on holiday
[10:03] <seb128> dpm, we do update the pot in individual merge requests (at least for settings) because then all merge requests conflict on the pot
[10:03] <seb128> we don't*
[10:03] <dpm> seb128, please don't disable upstream exports, unless it's affecting development in any way. I'm still using these to update the stats at http://projects.davidplanella.org/stats/utopic
[10:03] <seb128> dpm, we often have several changes queued which update strings, and it becomes challenging to land stuff together if you include the pot refresh
[10:04] <seb128> dpm, ok, still we keep having outdated templates, which is annoying
[10:04] <dpm> I need to have these conversation about updating pots automatically
[10:04] <seb128> that doesn't happen on the ubuntu side
[10:04] <seb128> right
[10:05] <seb128> dpm, btw, speaking about translation, we started hitting bugs because launchpad's gettext is too old/doesn't handle "\u<nnnn>" unicode chars
[10:05] <seb128> larsu, btw, did you open a bug on launchpad itself about that? if not we should probably do it
[10:06] <dpm> seb128, yeah, it's a tradeoff right now. On the Ubuntu side it's difficult to point developers to the right packages/click apps to translate (and we can't have click apps in the source packages list), and we can't have reliable stats for OEMs, that's why I created the stats page
[10:07] <dpm> seb128, yeah, I think it's ancient. It does not handle {arg} translations for python either. I asked wgrant a while ago, and it seems the server is still on an old Ubuntu release
[10:07] <larsu> seb128: good point
[10:07] <larsu> dpm: is there already a bug open about that?
[10:07] <dpm> larsu, I don't remember having opened one
[10:08] <larsu> okay, I'll open one then
[10:09] <seb128> larsu, danke
[10:10] <larsu> dpm: with {arg} you mean the python3 str.format() style?
[10:10] <dpm> larsu, exactly
[10:10] <larsu> ok
[10:13] <larsu> seb128, dpm: bug #1367213
[10:13] <dpm> thanks larsu
[10:15] <seb128> larsu, danke
[11:10] <Trevinho> marga: ok, thanks.... Let's continue the test for few days.. That change is going to be SRU'ed anyway
[11:34] <didrocks> is launchpad on crack?
[11:34] <didrocks> File evolution-data-server_3.10.4-0ubuntu2.debian.tar.gz already exists in Primary Archive for Ubuntu, but uploaded version has different contents.
[11:34] <didrocks> nothing in trusty queue: https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=
[11:35] <didrocks> and not in trusty: https://launchpad.net/ubuntu/+source/evolution-data-server
[11:35]  * didrocks wonders if now, launchpad looks at other releases and try to match the content
[11:35] <didrocks> like this one on utopic: https://launchpad.net/ubuntu/+source/evolution-data-server/3.10.4-0ubuntu2
[11:54] <seb128> didrocks, it always did that
[11:54] <seb128> didrocks, you can't use again a version number that has a been used
[11:54] <seb128> didrocks, like it 3.10.4-0ubuntu2 existed in utopic you can't use it in trusty
[11:54] <seb128> that's why we do the 1.1 thing usually
[11:54] <didrocks> seb128: hum, weird, I was in my mind really sure that after forking between r and r+1, we did that in the past
[11:55] <didrocks> but probably bad memory, and long time I didn't do "regular packaging" apart from CI ones :)
[11:55] <didrocks> (anyways, already uploaded 1.3 btw)
[12:04] <didrocks> Sweetshark: hey! so GunnarHj provided some translation patches some weeks ago, do you mind having a look? https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1308771
[12:04] <didrocks> Sweetshark: sounds useful to SRU to trusty as well
[12:06] <Sweetshark> didrocks: hmmm, we just bumped Libreoffice on trusty to 4.2.6 though, but yes: I should keep that in mind when bumping to 4.2.7 on trusty.
[12:06] <didrocks> Sweetshark: please do (and update the status of the bug as well then)
[13:28] <willcooke> tkamppeter, do you have a link to the information about how printer makers can add their drivers to the database?  I did a quick search, but I couldnt find what I was looking for
[13:31] <willcooke> didrocks, once your next blog post is out, do you think it's worth us organising a community hangout to talk about the next steps (what our next targets are etc)?  Or perhaps that is better suited to a mailing conversation?
[13:34] <tkamppeter> willcooke: http://www.linuxfoundation.org/collaborate/workgroups/openprinting/writingandpackagingprinterdrivers
[13:35] <willcooke> great, thanks tkamppeter.  And thank you very much for your hard work in the conference calls.  Great job
[13:35] <willcooke> I think they went really well
[13:43] <didrocks> willcooke: I guess a hangout can work (funny you tell this, I wrote this 20 minutes ago in a comment on g+) ;)
[13:44] <willcooke> didrocks, how about that?!
[13:44] <willcooke> ;)
[13:44] <didrocks> heh
[13:44] <willcooke> It reminded be to do something about it
[13:44] <didrocks> yeah, that was my guess, you cheated! :)
[13:44] <willcooke> So if you're happy to do that, I will work with dpm or jcastro and get something in the diary
[13:45] <didrocks> willcooke: that would be perfect!
[13:45] <didrocks> willcooke: didn't get time with the infrastructure flakyness to prepare the blog post yet. Probably tomorrow
[13:45] <willcooke> didrocks,  aint no thing
[14:55] <didrocks> fginther: so i386 is again (3rd time of the day) off after the revert, it seems that it's the jenkins slave that doesn't boot up or there is a race
[14:56] <didrocks> fginther: I can ssh to it and it's indeed reverted without any jenkins process
[14:56] <didrocks> I remember that jibel had an upstart job to fail & retry, maybe we should check with him and put that into the vm image?
[14:56] <fginther> didrocks, oh, sorry about that. I saw your message, then got sucked into meetings
[14:56] <didrocks> fginther: no worry, I reverted and rebooted thanks to virsh myself, the other times :)
[14:56] <didrocks> but as it seems it's quite frequent and only related to not having the jenkins slave process, maybe we can workaround this
[14:57] <fginther> didrocks, yes, I was going to add a workaround to the revert job if this continued to be a problem, I can do that now
[14:58] <fginther> the upstart job is set to retry, perhaps it's respawning too fast. The logs get removed on the revert, so I haven't looked at them yet
[14:58] <didrocks> fginther: yeah, want me to just try a "start jenkins-slave"
[14:59] <fginther> didrocks, sure, I was just going to make that a part of the revert job
[14:59] <didrocks> fginther: so, the agent started, without any issue
[15:00] <didrocks> and it runs the update
[15:00] <didrocks> fginther: how do you want to make that as part of the revert job, as you are on another machine?
[15:00] <didrocks> just sshing to both of them and try a start?
[15:00] <fginther> ssh to it
[15:00] <didrocks> (after the 300s)
[15:00] <didrocks> ok
[15:00] <fginther> yep
[15:00] <didrocks> sounds good enough for now ;)
[15:00] <didrocks> fginther: you can run the revert job if you need btw
[15:01] <didrocks> (to tests 2-3 times)
[15:01] <fginther> didrocks, so you're not using it at the moment?
[15:01] <didrocks> fginther: for the next hour, no
[15:22] <didrocks> fginther: you should add a || true I guess
[15:22] <didrocks> + ssh ubuntu@ps-trusty-desktop-amd64-1 /usr/bin/sudo start jenkins-slave
[15:22] <didrocks> start: Job is already running: jenkins-slave
[15:23] <didrocks> fginther: doing and restarting
[15:23] <fginther> thanks
[15:24] <didrocks> yw!
[15:25] <desrt> 5 minutes!
[15:26] <didrocks> 17:24:59      desrt | 5 minutes!
[15:26] <didrocks> desrt: fail at 1s here! :)
[15:26] <desrt> check your clock!
[15:27]  * didrocks checks and trusts his clock
[15:28] <desrt> 2 minutes!
[15:29] <desrt> 1 minute!
[15:29] <didrocks> better!
[15:29]  * Sweetshark lurks moar
[15:30] <desrt> willcooke: GO!
[15:30] <willcooke> Roll call (taking in to account holidays and people I know aren't here):   attente_, desrt, didrocks, larsu, qengho, seb128, sweetshark, tkamppeter
[15:30] <didrocks> o/
[15:30] <Sweetshark> o/
[15:30] <larsu> \o
[15:31] <desrt> oh.  hi.
[15:31] <willcooke> Shall we go in alphabetical order, or does someone want to go first?
[15:31] <larsu> desrt: disappointing :(
[15:31] <desrt> larsu: i've heard that you shouldn't use \o or o/ so i wanted to avoid it
[15:32] <larsu> desrt: why not?
[15:32] <dgadomski> willcooke: I haven't been called, but I will gladly take a look what's going on ;)
[15:32] <desrt> apparently from the side it looks like a nazi salute
[15:32] <willcooke> cool!  hi dgadomski - good to have you here
[15:32] <larsu> willcooke: in the order you specified
[15:32] <didrocks> willcooke: let's go alphabetical I guess :)
[15:32] <willcooke> attente_, you're first
[15:33] <willcooke> don't think attente_ is around atm, so let's move on to desrt and come back around
[15:33]  * desrt phones attente_ :)
[15:33] <attente_> sorry, i'm here, i just didn't have my status ready
[15:33] <willcooke> tsch
[15:33] <willcooke> ;)
[15:33] <willcooke> attente_, you want us to come back to you>?
[15:34] <attente_> please :)
[15:34] <willcooke> ok, desrt go for it
[15:34] <desrt>  - fixed long-standing difficult-to-track-down bug in glib's mime handling code where the wrong default app was being picked
[15:34] <desrt>  - proselytised for the church of gperf
[15:34] <desrt>  - spent most of the week working on adding support for StopUnit and Abandon to the cgroup scopes in systemd-shim
[15:34] <desrt> fin
[15:35] <willcooke> Excellent, thanks desrt.  Moving on to didrocks
[15:35] <seb128_> desrt, do you have a bug reference for the wrong mime one?
[15:35] <seb128_> or an example
[15:35] <desrt> seb128_: no :(
[15:35] <seb128_> I wonder if that's something we should SRU
[15:35] <seb128_> k :/
[15:35] <desrt> no.
[15:36] <desrt> it's in my new mime code which i only did this cycle
[15:36] <seb128> k
[15:36] <desrt> so it won't impact other releases
[15:36] <seb128> thanks
[15:36] <desrt> however, there are older similar bugs...
[15:36] <desrt> but uh... OBSOLETE now, i guess, and no patches to pick :(
[15:36] <desrt> we changed the spec pretty throughly at the last freedesktop summit...
[15:36] <desrt> that's actually maybe something to talk about: we should stop using defaults.list: it is deprecated
[15:37] <desrt> should now be gnome-mimeapps.list (since only GNOME ever processed this file anyway)
[15:37] <desrt> but now we can also have unity-mimeapps.list, kde-mimeapps.list, etc, etc.
[15:38] <didrocks> seb128: desrt: done then?
[15:38] <desrt> sure.  let's chat in detail after the meeting.
[15:38] <didrocks> ok, so my status is 12 lines, to avoid any complain from seb128, I'm using a pastebin: http://paste.ubuntu.com/8300814/ :)
[15:38] <seb128> desrt, k, that's a discussion worth having next month when we are together
[15:38] <didrocks> EOF then :p
[15:38] <desrt> seb128: even better
[15:38] <seb128> desrt, ;-)
[15:38] <seb128> didrocks, lol
[15:38] <seb128> didrocks -q
[15:38] <seb128> :p
[15:38] <desrt> didrocks: WRAP YR TEXT!
[15:39] <didrocks> desrt: use plain mode!
[15:39] <didrocks> http://paste.ubuntu.com/8300814/plain/
[15:39] <seb128> need to auth to go in plain
[15:39] <seb128> that pastebin is ridiculous
[15:39] <didrocks> yeah, but wrapping shouldn't be a matter of the paster tbh :p
[15:39] <desrt> the most important thing is that we still get to complain about the way in which didrocks gives his status
[15:39] <didrocks> screen width is changing between setup
[15:39] <seb128> :-)
[15:39] <didrocks> desrt: I see that ;)
[15:39] <seb128> 80 chars wrapping!
[15:39] <didrocks> don't even dare!
[15:40] <didrocks> so adding:
[15:40] <didrocks> * Got a wrapping argument with the CI team :)
[15:40] <seb128> happyaron, didrocks, what's the status of the fcitx mir?
[15:40] <didrocks> seb128: no news from happyaron, still pending on him to do the needed changes + releases
[15:40] <seb128> k
[15:40] <didrocks> seb128: and I'm getting more MIRs from others, so fcitx can be lower in the list…
[15:41] <seb128> willcooke, ^ that might be an issue worth keeping an eye on
[15:41] <didrocks> (and I feel less confident that it's something we are supporting due to the lack of feedback/fix cycles)
[15:41] <willcooke> didrocks, seb128 happyaron - let me know if I can assist with the Fcitx work
[15:41] <willcooke> seb128, ack
[15:41] <willcooke> :)
[15:41] <seb128> willcooke, not sure how you can help, but we need to unblock that if we want to enable that support this cycle
[15:41] <willcooke> seb128, I'll chat to happyaron
[15:42] <willcooke> anyway, let's get this train wreck back on the rails.... didrocks please carry on
[15:42] <seb128> willcooke, thanks
[15:42] <willcooke> (meeting = train wreck, not fcitx)
[15:42] <didrocks> willcooke: hum, I don't have more than what I wrote on the pastebin ;)
[15:42] <willcooke> ahh, kk
[15:42] <didrocks> not enough? ;)
[15:42] <desrt> attente ready yet? :)
[15:42]  * desrt sees fcitx mention
[15:43] <attente_> yes
[15:43] <didrocks> so yeah, if you follow the links in the pastebin, you can see our daily udtc runs
[15:43] <attente_> proper migration of old ibus input sources for users switching to fcitx, thanks desrt for gperf advice
[15:43] <willcooke> didrocks, I send a copy & paste of the meeting notes to robert_ancell and TheMuso, so inline is probably easier for those guys, jus' saying
[15:43] <attente_> debugging a race between u-s-d and fcitx on session start
[15:43] <attente_> to-do: still need to debug sync issues between fcitx current IM and gsettings current input source
[15:43] <attente_> to-do: i-k icons don't look right in fcitx-qimpanel, not sure why
[15:43] <didrocks> willcooke: if seb128 & co stop complaining, I can do, let me repaste after attente_ then :)
[15:44] <seb128> lol
[15:44] <seb128> -q version? :p
[15:44]  * seb128 stops trolling didrocks
[15:44] <desrt> (we should just move the meeting to friday...)
[15:44]  * Sweetshark wonders why
[15:44] <didrocks> attente_: done?
[15:44] <Sweetshark> wondering about stopping not moving
[15:44] <attente_> didrocks: yes, sorry, (eof)
[15:45] <didrocks> for robert and themuso then, repasting:
[15:45] <didrocks> * Released Ubuntu Developer Tools Center 0.0.5 (trusty and utopic). This version is focused on better testing reliability in difficult conditions like slow CPU and network and jenkins environment. Details at https://github.com/didrocks/ubuntu-developer-tools-center/commit/8ab0fbda19627832b03ca9bbe3f2dabbc30b142b. Merged external translation contributions!
[15:45] <didrocks> * Setup jenkins daily tests on both i386 and amd64, with git or latest version (system) in a distro. Always install on a fresh install, running every 2 hours and report all results (https://jenkins.qa.ubuntu.com/job/udtc-trusty-tests/)
[15:45] <didrocks>   * running from trunk and dependencies from trunk: https://jenkins.qa.ubuntu.com/job/udtc-trusty-tests/34/
[15:45] <didrocks>   * running with a system setup (installed package from distro and dependencies + corresponding tests at rev from distro): https://jenkins.qa.ubuntu.com/job/udtc-trusty-tests/36/
[15:45] <didrocks>   * code coverage reports jobs: (trunk) https://jenkins.qa.ubuntu.com//job/udtc-trusty-tests-collect/20/label=ps-trusty-desktop-i386-1/console, (system) https://jenkins.qa.ubuntu.com//job/udtc-trusty-tests-collect/21/label=ps-trusty-desktop-i386-1/console
[15:45] <didrocks>   -> I'll write a blog post next week with more details on the testing setup.
[15:45] <didrocks> * TODO: medium tests are disabled for now (hence the red dots) due to firewall issues to get the docker image. RT in progress.
[15:45] <didrocks> * TODO: issues with the vm not reconnecting to jenkins after 3/4 of machine resets. fginther is adding a workaround.
[15:45] <didrocks> * TODO: system medium tests not supported (it would involve rebuilding everytime a docker container). Not a priority as large tests are passing.
[15:45] <didrocks> * Helped Kylin team on html/javascript and C++ calls.
[15:45] <didrocks> * Some help and discussion with the CI team + (very) quick bug fixing.
[15:45] <didrocks> * Patch piloting, including updating evolution-data-server in utopic + trusty.
[15:45] <willcooke> eof?
[15:45] <didrocks> yeah, eof
[15:46] <willcooke> thx didrocks - larsu, over to you
[15:46] <larsu> sure
[15:46] <larsu> - look into fixing gtk tests, but we decided to not warn on deprecated properties instead
[15:46] <larsu> - unitythemeprovider landed in staging. New patch: support .xpm icons and /usr/share/pixmaps
[15:46] <larsu> - gtk theme: fix popover menus (menuitems were rendered as buttons) and tweak background hacks for overlay-scrollbars
[15:46] <larsu> - investigated why unicode escapes in c/c++ string literals don't work in launchpad and worked around it in indicator-datime
[15:46] <larsu> - indicator-messages: investigate wakeups. Haven't been able to reproduce yet
[15:47] <larsu> I'm sure i-messages monitors XDG_DATA_DIRS, just gotta remove this with desrt's suggestion
[15:47] <larsu> eof
[15:47] <willcooke> excellent stuff, thanks larsu
[15:47] <desrt> larsu: i'm done with the systemd-shim stuff for now, i think (hallyn just tested it) so i may be able to look at inotify stuff today
[15:48] <desrt> i doubt i want to land a patch in glib upstream this cycle since we're on the eve of hard code freeze, but i could get something lined up for next cycle and we could vendor-patch it in
[15:48] <desrt> we need to slay this issue eventually...
[15:48] <larsu> desrt: cool. let's talk about this after the meeting
[15:48] <desrt> yup
[15:48] <willcooke> qengho, over to you...
[15:48] <qengho> - more Chromium-Mir work. I need to run mir, to test.
[15:48] <qengho> - setting up Cr contributed translations import/export.
[15:48] <qengho> - minor Cr bugs. Thinking about autopkgtest test for a fontconfig bug.
[15:48] <qengho> - dogfooding EN / ZH-pinyin fcitx.
[15:49] <qengho> EOF
[15:49] <willcooke> good work on the Mir work
[15:49] <qengho> willcooke: Too early to praise me. :)
[15:49] <willcooke> ha!
[15:49] <willcooke> I have faith
[15:50]  * willcooke is lovin' PDF in browser </soapbox>
[15:50] <attente_> qengho: are you using the transition PPA?
[15:50] <qengho> attente_: the PPA? You mean branches?
[15:50] <willcooke> qengho, it's good that the Mir work is  moving forwards though.
[15:50] <attente_> qengho: i mean for the fcitx dog fooding
[15:51] <qengho> attente_: Oh, no.
[15:51] <qengho> attente_: I read "transition" as translation. Sorry.
[15:52] <willcooke> seb128, you're up
[15:52] <qengho> attente_: I'm using the packages in U.
[15:52] <seb128> • ubuntu-system-settings for touch
[15:52] <seb128> ∘ quite some bugfixes (orientation plugin having wrong framing, some panels having scrolling issues, ui difference with design)
[15:52] <seb128> ∘ tested/reviewed changes from others
[15:52] <seb128> • made indicator-transfer translatable
[15:52] <seb128> • fixed typo in sync-monitor and made it translatable on launchpad
[15:52] <seb128> • tested the current phone rtm, filed a stack of bug reports, sent some easy patches for label wrapping issues in non english locales
[15:52] <seb128> • send patch to make indicator-display translatable on launchpad
[15:52] <seb128> • looked at indicator-datetime/utf string escaping/launchpad issue
[15:52] <seb128> • test work from robert_ancell on u-c-c/u-s-d to allow updating gnome-desktop in utopic, seems to work correctly now (Laney said he would get it approved when he comes back if things are working)
[15:52] <seb128> • started looking at new gedit and evince to see how they work under Unity, we can probably update, maybe next cycle would be better though
[15:52] <seb128> • usual share of bugs triaging and desktop discussions
[15:52] <seb128>
[15:52] <seb128> (that's it for the week)
[15:52] <desrt> seb128: christ man... ever heard of pastebins?
[15:52] <willcooke> thanks seb128
[15:52] <seb128> desrt, be nice, didrocks would feel alone if I was not doing that ;-)
[15:53] <larsu> seb128: gedit o/
[15:53] <larsu> I agree next cycle is better though
[15:53] <seb128> larsu, yeah, but the nice option are in 3.13 and that requires gtk 3.13
[15:53] <seb128> evince might be doable this cycle
[15:53] <larsu> nah, I'm fine with next
[15:53] <seb128> I have 3.13 working, it looks ok, I just need to turn on normal decorations instead of headerbar decorations
[15:53] <seb128> + the menubar issue
[15:54] <desrt> are we ever going to sync back up on gtk releases or is 1-behind our new normal?
[15:54] <larsu> seb128: do you need help with thaat?
[15:54] <larsu> *that
[15:54] <seb128> larsu, well, evince fixes a stack of bugs and add better hidpi support, so might still be worth asking a ffe for
[15:54] <larsu> desrt: new normal
[15:54] <larsu> seb128: ah, good point
[15:54] <seb128> desrt, no, we decided to do that because unstable gtk are creating too much work for us
[15:54] <desrt> oh well.  at least this gtk release is a good one, so next ubuntu release will be nice :)
[15:54] <desrt> too bad about this one, based on crap gtk :)
[15:54] <larsu> desrt: once *someone* fixed the theme
[15:55] <larsu> desrt: and o-s :/
[15:55] <larsu> it's not that crappy though
[15:55] <desrt> dialogs...
[15:55] <desrt> most of the fixes are now at least in the new one, but i guess we patch those anyway
[15:55] <larsu> we backported those changes
[15:55] <desrt> right
[15:55] <desrt> seems like things are getting a bit more calm upstream
[15:55] <seb128> yeah, I don't think we have issues with the current version
[15:55] <desrt> let's talk in october :)
[15:55] <seb128> indeed
[15:56] <larsu> until mcann comes back :D
[15:56] <willcooke> Sweetshark, over to you. How was the conference?
[15:56] <seb128> willcooke, can move on to the next one ;-)
[15:56] <desrt> larsu: this irc channel is logged :p
[15:56] <Sweetshark> - LibreOffice conference (see report for details in epic proportions)
[15:56] <Sweetshark> - some security aftershocks
[15:56] <Sweetshark> - reviewing mail merge patches upstream
[15:56] <Sweetshark> - some MIR rationale prose
[15:56] <Sweetshark> - also highly encouraged by the last trusty update: its been out for a week
[15:56] <Sweetshark>   - ignoring stacktraces that happend only once (because they might be background radition/hardware fail) we have only 3 stacktraces there:
[15:56] <Sweetshark>     - one with 33 occurrences (seems to be something on the startup)
[15:56] <Sweetshark>     - one with 23 occurrances (possibly unity itegration)
[15:56] <Sweetshark>     - one with 12 occurrances ("cannot copy extracted data...." -> packaging issue)
[15:56] <Sweetshark>     - everything else is 1 occurance or less
[15:56] <Sweetshark>     - compare that with the 3.5.7 package from precise with the following occurence counts: 144, 93, 82, 80, 39, 37,27, 25, 22, 21 for the top 10 in the last week
[15:56] <Sweetshark> - up next: some finishing touches for 14.10: reenable mergedlibs, autopkgtests
[15:56] <Sweetshark> EOF
[15:57] <Sweetshark> willcooke: conference as awesome and terribly exhausting -- as usual.
[15:57] <willcooke> :D
[15:57] <larsu> desrt: so? !calm doesn't mean bad necessarily
[15:57] <willcooke> Thanks for the trip report(s) , very interesting reading
[15:57] <willcooke> tkamppeter, over to you
[15:58]  * desrt notes libreoffice policy: it's not a bug until it affects 10 users
[15:58] <larsu> which is nothing for them
[15:59] <tkamppeter> - Posted student projects for VALS Semester of Code (http://vps.semesterofcode.com/), 8 projects which stayed "unsold" after GSoC 2014, plus mobile print dialog for Ubunt phone
[15:59] <tkamppeter> - Two phone meetings with Will Cooke and representatives of printer manufacturers, to present them Ubuntu andits printing stack and printing technologies currently under development. Especially Lexmark is very interested in th concept of auto-downloadable drivers.
[15:59] <tkamppeter> - system-config-printer: Updaed to 1.5.1
[15:59] <tkamppeter> - Bugs.
[15:59] <Sweetshark> desrt: unless one of them is a paying customer ;)
[15:59] <Sweetshark> (or a developer)
[15:59] <willcooke> thanks tkamppeter, and thanks again for your support in the conference calls.
[15:59] <willcooke> Ok, I have reports from robert_ancell and TheMuso.  Here comes cut & paste....
[16:00] <willcooke> == robert_ancell ==
[16:00] <willcooke> Worked on:
[16:00] <willcooke> - Released LightDM 1.11.8
[16:00] <willcooke> - Helped diagnose cgroup issue on krillin that was triggered by timing improvement in lightdm (bug was in systemd-shim)
[16:00] <willcooke> - Helped diagnose issues with non-free video drivers not tagging their devices so logind considers that seat to have graphics capability
[16:00] <willcooke> - Bug fixes and test improvements in LightDM
[16:00] <willcooke> - Backported changes from LightDM 1.11 to 1.10 in preparation to SRU into Ubuntu 14.04
[16:00] <willcooke> Currently working on:
[16:00] <willcooke> - Bug fixing in LightDM
[16:00] <willcooke> - Preparing LightDM 1.10.2 release
[16:00] <willcooke> Not blocked on anything.

[16:01] <willcooke> == TheMuso ==
[16:01] <willcooke> * Uploaded some fixes to make accessibility profiles get properly applied at install time.
[16:01] <willcooke> * Started researching more about US Section 508 and CVVA acts, relevant to our accessibility compliance. Everything I have found so far that summarises section 508 has been talkin about the web only, but I think the act applies to more than just web pages. The research continues, haven't checked out the CVVA yet.
[16:01] <willcooke> EOF
[16:01] <willcooke> Last and by no means least... any other business?
[16:02] <seb128> not from me
[16:02] <didrocks> nothing
[16:02]  * willcooke sets a 1m time out
[16:02] <seb128> willcooke, we want to discuss overlay-scrollbar, but doesn't need to be a meeting item
[16:03]  * Sweetshark whisles a tune by europe from the 1980ies ..
[16:03]  * desrt shakes fist at robert_ancell for creating work for him
[16:03] <willcooke> seb128, I've got something on the sprint plan for that
[16:03] <larsu> that will be a short meeting
[16:03] <seb128> still basically the same "it's work, keep creatings issues, inconsistent since it's only for gtk applications"
[16:03]  * willcooke beep beep beep.  Times up
[16:03] <desrt> willcooke: no status from you?
[16:04] <larsu> time's up
[16:04] <desrt> too bad :(
[16:04] <seb128> willcooke, or said differently "can we drop them, it would make mpt/some designers happy and decrease our workload/resolve some annoying issues"
[16:04] <desrt> 'some annoying issues' ~= every cycle they break and we spend a lot of time fixing them
[16:04] <desrt> 'workload' ~= when i say "a lot of time" ....
[16:05] <willcooke> I did speak to JohnLea about it last week, he wants to keep them. But I think we should take the time to explain why they are such a burden and get a consensus
[16:05] <seb128> willcooke, I'm curious to know how it justify that when they don't work in firefox/chromium/tb/libreoffice
[16:05] <seb128> qt apps
[16:06] <seb128> it->he
[16:06]  * larsu nods
[16:06] <seb128> like if we had them working on all our supported apps I would understand
[16:07] <willcooke> seb128, yup -I agree.  I still think the right course of action is to get all the "stake holders" sat down and to have a proper chat about it though.   Should be a fairly stress free conversation
[16:07] <seb128> willcooke, +1
[16:07] <willcooke> So, status from me....
[16:07] <seb128> that can wait, not going to change things a lot this cycle
[16:07] <willcooke> seb128, +1
[16:08] <willcooke> Went to the office and had a meeting with Richard Collins & John Lea about planning out the roadmap to 16.04.  Lots still to do there
[16:08] <willcooke> Did these printer makers calls with tkamppeter
[16:08] <willcooke> Did some HR stuf
[16:08] <willcooke> f
[16:09] <larsu> thanks for talking to those guys
[16:09] <willcooke> and then generic manager work.  Looking busy, walking around quickly, the normal
[16:10] <larsu> :D
[16:10] <seb128> good to have somebody figuring out the plans for us :-)
[16:10] <larsu> nd walking around quickly
[16:10] <willcooke> oh, I had a good meeting with kgunn about Mir & U8.  We bumped the keyboard input problems in the U8 desktop up in the priory list
[16:10] <larsu> someone's gotta do that
[16:10] <willcooke> *priority
[16:11] <willcooke> EOF
[16:11] <willcooke> Ok, I think that's a wrap.  Thanks all.
[16:11] <didrocks> thanks
[16:12] <didrocks> fginther: ok, the machines survived, let's see after this run (should reset in less than 5 minutes as the tests are finishing)!
[16:12] <seb128> thanks
[16:12] <kgunn> fwiw, gotta guy on unity8 team who's working on a very similar bug...but not that same one (e.g. keyboard/sidestage)...and he'll address that as soon as he finishes the one he's on
[16:12] <fginther> didrocks, watching
[16:12] <willcooke> awesome, thanks a lot kgunn
[16:13] <didrocks> fginther: I'm wondering if the same can happen after the dist-upgrade reboot though and so, a brutforce option in the vm would have workarounded that one as well
[16:14] <fginther> didrocks, yeah that's possible too. I can do the same workaround after the dist-upgrade though.
[16:15] <fginther> didrocks, will try to refine next time a new snapshot is needed
[16:15] <didrocks> fginther: excellent! thanks for keeping an eye on it!
[16:38] <JohnLea> seb128, hyia, just catching up on the overlay scroll bar conversation above
[16:39] <willcooke> hi JohnLea
[16:40] <JohnLea> seb128, overlay scroll bars were actually one of the first elements of the convergence design, the idea being that they enable touch and pointer control to happily co-exist.  On touch devices only the thin bar appears when when a user scrolls the view.  But if a pointer moves near the edge the thumb appears enabling scrolling of the same view with a pointer
[16:41] <JohnLea> seb128, totally agree about needing it implemented on key toolkits
[16:41] <JohnLea> seb128, moving forward though it is something that we want for native QML apps on our platforms
[16:43] <seb128> JohnLea, hum, ok, I though user testing showed that they don't work well for most users
[16:43] <seb128> like difficult to grab
[16:43] <seb128> especially on touch
[16:43] <JohnLea> no, that is not the case
[16:44] <JohnLea> works excellently for touch user because they don't have to grab anything!
[16:44] <JohnLea> the grab handles should never appear when the user is interacting via touch
[16:44] <JohnLea> basically when used just with touch it is identical to the scroll bars in ios today
[16:45] <JohnLea> what it adds that that it makes this also usable with a pointer
[16:45] <JohnLea> for touch user scrolls by just dragging anywhere at all in the viewport
[16:46] <JohnLea> the trade is more on the pointer side
[16:46] <JohnLea> but it works very well with mouse scroll wheels
[16:47] <seb128> JohnLea, right, it works well as long as you don't want to display the ui ;-)
[16:47] <seb128> e.g page up/down, mouse, flickering, etc
[16:47] <seb128> JohnLea, ok, anyway, if we want to keep those we need to invest in making them work in a non hackish way
[16:47] <seb128> so we need resources allocated to that
[16:49] <Cimi> JohnLea, plus, we might want to revisit the design, and put them inside the view, not outside as they are now
[16:49] <Cimi> JohnLea, also, I won't make them follow the mouse cursor, as I heard many times people not being able to scroll
[16:50] <willcooke> Cimi, JohnLea +1 for not following the mouse cursor.  That interaction does seem a bit broken IMHO
[16:50] <Cimi> in my opinion, I would do like in facebook sidebar, they work great
[16:51] <Cimi> it's a compromise with OSX where they are too hard to get
[16:53] <willcooke> let's talk more at the next sprint
[16:54] <JohnLea> seb128, the touch flick up/down is by far the most common use case on touch devices, and use of scroll wheel is common for those with mice.  So yes there is a bit of optimising for these input devices, and a bit of cost for the 'dragging with a pointer', but this trade is in line the direction Ubuntu touch as a whole is aiming
[16:55] <JohnLea> Cimi, have a play once you have finished with the Dash structure update prototyping we are going to talk about tomorrow ;-)
[16:56] <seb128> JohnLea, right, well as said it's fine, we just need resources to do a proper job at it, what we currently have is not maintainable and not done right
[16:59] <JohnLea> seb128, yes agreed, this is supposed to be part of the sdk so I suppose it falls on their plate
[17:06] <Cimi> JohnLea, I am in the office tomorrow btw
[17:06] <Cimi> JohnLea, but I am not planning to play any hack in gtk :)
[17:33] <Laney> I have eds on my list to do
[17:34] <seb128> Laney, hey, have->had, didrocks did it for you
[17:34] <seb128> Laney, how are holidays? ;-)
[17:34] <Laney> delayed
[17:34] <Laney> well he duplicated some work then, but okay ...
[17:36] <Laney> oh it was only eds itself, not everything else, I see
[17:39] <seb128> Laney, yeah, there was a git commit in the sponsoring queue and he though than he could do the update rather than cherry picking only one fix
[17:39] <Laney> nod
[17:39] <seb128> Laney, I don't think that took much effort, it's only 1 source
[17:39] <seb128> with small changes
[17:39] <Laney> it's fine, "eds" to me is like 6 packages
[17:39] <Laney> which turns out to be a bit of work
[17:40] <seb128> right
[17:40] <seb128> that's "evo" for me ;-)
[17:40] <Laney> :-)
[17:40] <seb128> Laney, "delayed" was about holidays? what happened?
[17:40] <Laney> calgary snowed
[17:40] <Laney> so we are delayed by 24 hours in canada
[17:40] <seb128> blame Canada!
[17:40]  * Laney stares at infinity
[17:45] <stgraber> maybe you could have stayed at infinity's if he wasn't decontaminating his place ;)
[17:46] <stgraber> also, it's just that weird side of the country that's the problem, here I'm enjoying a nice and sunny 25C
[17:46] <Laney> de...contaminating?
[17:46] <Laney> air canada put us up in a hotel anyway
[17:47] <Laney> speaking of, better go back and check out
[17:47] <Laney> pack
[17:51] <seb128> Laney, have a safe trip back!
[17:52] <willcooke> EOD.  ttfn
[17:52] <attente_> snow?
[18:13] <Laney> attente_: SNOW!
[18:13] <Laney> i'd say 2 inches
[18:17] <attente_> Laney: you're near banff, go skiing
[19:45] <seb128> kenvandine, where did you ping me about testing u-s-s? can't find the channel anymore it seems!
[19:45] <seb128> kenvandine, in any case, update works fine
[19:45] <seb128> I installed some click updates and the system update to r26
[19:45] <kenvandine> woot
[19:45] <kenvandine> thx!
[19:46] <kenvandine> it was in ubuntu-ci-eng
[19:46] <seb128> k, too much going on I gues
[19:46] <kenvandine> so you tested with r25?
[19:46] <kenvandine> updated to r26?
[19:47] <seb128> correct
[19:47] <seb128> I've installed it again on r26 and just change auth from swipe to pin
[19:47] <seb128> works fine
[19:47] <seb128> updates open fine
[19:47] <seb128> but no system update anymore
[19:47] <seb128> calendar is listed as a click update
[19:48] <seb128> bah
[19:49] <seb128> mterry, trying to security panel, I ended up in a situation where the osk doesn't show anymore :/
[19:50] <seb128> can't reproduce anymore, weird
[19:50] <seb128> kenvandine, well, in any case, +1 from me
[19:50] <kenvandine> i tested the same thing on krillin
[19:50] <kenvandine> worked well
[19:50] <kenvandine> same for the bluetooth fixes
[19:50] <kenvandine> i can finally pair my only bluetooth speaker i own :)
[19:50] <kenvandine> cyphermox_, thanks!
[19:51] <seb128> ;-)
[19:51] <cyphermox_> kenvandine: woohoo!
[19:51] <kenvandine> seb128, i also manually editor the battery level in the qml file so it would fail for < 98% :)
[19:51] <kenvandine> and confirmed it wouldn't let me update
[19:51] <seb128> kenvandine, I did that before ;-)
[19:51] <kenvandine> until i plugged in
[19:52] <seb128> yeah, I tried that as well
[19:55] <seb128> kenvandine, cyphermox_, should the bt icon change when an headset is paired?
[19:55] <seb128> should also dialpad sound go through the headset?
[19:55] <kenvandine> dunno.. i just got my first device ever paired :)
[19:56] <kenvandine> seb128, i would imaging not...
[19:56] <seb128> kenvandine, why not?
[19:56] <kenvandine> oh... i guess it would
[19:56]  * kenvandine just thought of music... not hands free
[19:56] <seb128> doesn't seem to work then
[19:57] <cyphermox_> seb128: I'm not sure about dialpad sound, maybe it should
[19:57] <seb128> cyphermox_, how do I test it?
[19:57] <seb128> I tried the ringtone in settings as well
[19:57] <cyphermox_> testing the paired device?
[19:57] <cyphermox_> you need to actually do a phone call, or play music
[19:57] <seb128> yes
[19:58] <cyphermox_> the ringtone should have worked, it does go through PA afaik
[19:58] <seb128> doesn't work
[19:58] <seb128> the headset is connected
[19:58] <cyphermox_> what device is this?
[19:58] <seb128> but icon doesn't change and music go through the speaker
[19:58] <cyphermox_> ok
[19:58] <seb128> krillin
[19:58] <seb128> header is nokia bh-104
[19:58] <seb128> header->headset
[19:59] <cyphermox_> rsalveti: do you know what to look for re: where you'd expect the music to be routed? can we still see everything with pactl list sinks?
[19:59] <cyphermox_> seb128: if you navigate out, and back to the bluetooth settings, could you check that the device still says it's paired?
[19:59] <cyphermox_> you know, just in case it lied :)
[20:01] <seb128> cyphermox_, it does
[20:01] <cyphermox_> ok
[20:01] <cyphermox_> then something might be off in pulse
[20:01] <cyphermox_> give me a second
[20:02] <mterry> seb128, odd about OSK on security panel...  But hopefully that wouldn't be USS-specific
[20:03] <seb128> mterry, yeah, likely not, still an issue
[20:03] <mterry> agreed
[20:23] <seb128> cyphermox_, do you need debug info from me?
[20:24] <cyphermox_> ah, pactl list sinks for starters
[20:24] <cyphermox_> could you file a bug for it? It's unclear whether it's bluez or pulse
[20:26] <seb128> sure, on what component?
[20:28] <seb128> cyphermox_, http://paste.ubuntu.com/8303026/
[20:29] <cyphermox_> seb128: make it pulse for now and I'll coordinate with rsalveti
[20:29] <seb128> cyphermox_, thank
[20:29] <seb128> s
[20:30] <rsalveti> hm, what is the issue?
[20:30] <seb128> rsalveti, connecting an headset to my krillin, music playing/dialpad sounds/ringtone still go through speaker
[20:30] <rsalveti> 		output-wired_headset: Output to wired headset (priority: 400, not available)
[20:30] <rsalveti> 		output-wired_headphone: Output to wired headphone (priority: 400, not available)
[20:30] <rsalveti> yeah, showing as not available
[20:30] <rsalveti> which could mean the hardware not identifying it
[20:31] <seb128> settings show it as connected
[20:31] <rsalveti> there's sysfs for that, 1 sec
[20:31] <rsalveti> settings?
[20:31] <seb128> u-s-s
[20:31] <seb128> the bluetooth panel, which I used to connect to the headset
[20:31] <rsalveti> seb128: oh, bt heatset?
[20:31] <rsalveti> *headset
[20:31] <seb128> yes
[20:31] <rsalveti> that makes a difference :-)
[20:31] <seb128> sorry for not specifying in my summary ;-)
[20:31] <rsalveti> seb128: is it a2dp + hsp?
[20:31] <rsalveti> or just hsp?
[20:32] <seb128> how do I tell?
[20:32] <seb128> it's a nokia bh-104
[20:32] <rsalveti> seb128: after you connected, pactl list cards
[20:32] <rsalveti> if hsp only, then that output you got is fine
[20:33] <seb128> hsp
[20:33] <rsalveti> right, then music playing still going to speaker is the expected behavior
[20:33] <rsalveti> hsp is just for voicecall
[20:33] <seb128> rsalveti, http://paste.ubuntu.com/8303059/
[20:33] <cyphermox_> hmm, there is that
[20:33] <seb128> ok
[20:33] <rsalveti> yeah, then you can only use it for voicecall
[20:33] <seb128> and that doesn't include dialpad sounds I guess?
[20:34] <rsalveti> nops
[20:34] <seb128> k
[20:34] <seb128> no bug then
[20:34] <seb128> rsalveti, thanks :-)
[20:34] <rsalveti> np :-)
[22:28] <TheMuso> willcooke: Actually, I don't mind loading up a link from a pastebin or some such for long updates, since it takes me longer to wade through the log due to timestamps.