a1faandyrock: +1 nice!01:09
Trevinhopitti: patch updated again.02:30
=== meetingology` is now known as meetingology
pittiGood morning06:06
seb128good morning desktopers!06:16
pittibonjour seb128 !06:19
seb128hey pitti, happy friday!06:20
seb128how are you?06:20
pittiand to you! I'm fine, thanks, how about yourself?06:20
pittiwhoa, where did all my armhf boxes go06:20
seb128I'm good thanks ;-)06:21
seb128happyaron, hey!06:44
happyaronseb128: hi06:44
seb128happyaron, how are you? happy friday!06:44
happyarongreat, :)06:45
seb128happyaron, how are those nm updates going? ;-)06:48
happyaronmet a problem on rebasing the policy patches to nm 1.2.2, still working on that06:49
seb128maybe it would make sense to do the -gnome update first?06:50
seb128it fixes some issues and should be more trivial06:50
happyaronyep I meant the applet package06:50
seb128oh well, we are not going to SRU things on friday and it's almost w.e time for you06:50
seb128oh, right, stupid me, 1.2.2 was already uploaded to y- :p06:51
happyaronalready done the merge with nm itself06:51
seb128I'm not fully awake yet it seems ;-)06:51
seb128happyaron, k, let me know if you need help with something06:51
seb128time for a coffee break, bbiab07:26
Laneyit's fririririrday08:01
willcookeappstreamcli is using 100% CPU this morning08:08
davmor2Morning willcooke08:08
seb128hey Laney, willcooke08:10
seb128happy friday!08:11
seb128how are you?08:11
willcookeReady for a weekend08:11
seb128willcooke, do you use it manually? or are we spawning that command in bg?08:11
willcookeseb128, must be running it in the bg08:11
seb128hum, k08:11
willcookeI killed it, but...08:12
willcookeay 20 09:10:50 malfunctioning-eddie sudo: pam_ecryptfs: pam_sm_authenticate: /home/will is already mounted08:13
willcookeMay 20 09:10:50 malfunctioning-eddie org.debian.apt[955]: Terminated08:13
willcookeMay 20 09:10:50 malfunctioning-eddie gnome-session[1981]: (gnome-software:2122): Gs-WARNING **: failed to call gs_plugin_refresh on apt: apt transaction returned result exit-failed08:13
willcookeMay 20 09:10:50 malfunctioning-eddie AptDaemon.Worker: INFO: Finished transaction /org/debian/apt/transaction/09c0faa447d24743841046c745027e1708:13
willcookeMay 20 09:10:50 malfunctioning-eddie org.debian.apt[955]: 09:10:50 AptDaemon.Worker [INFO]: Finished transaction /org/debian/apt/transaction/09c0faa447d24743841046c745027e1708:13
willcookeMay 20 09:10:50 malfunctioning-eddie gnome-session[1981]: (gnome-software:2122): Gs-WARNING **: failed to get updates: no results to show08:13
willcookesmells like this:  https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/158384508:16
ubot5Launchpad bug 1579712 in appstream (Ubuntu Xenial) "duplicate for #1583845 Refresh hangs indefinitely, appstreamcli using 100% CPU" [High,Fix committed]08:16
willcookeso might have been my internet connection crapping out for a moment08:16
willcookecorrection, this:  https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/157971208:16
ubot5Launchpad bug 1579712 in appstream (Ubuntu Xenial) "Refresh hangs indefinitely, appstreamcli using 100% CPU" [High,Fix committed]08:16
willcookewhich is fixed08:17
willcookein proposed08:17
andyrockmorning all08:17
willcookehey andyrock08:17
seb128hey andyrock, happy friday!08:19
seb128willcooke, if you can reproduce you might want to verify the SRU ;-)08:20
andyrockseb128: hehe :D08:20
Laneyhey seb128 & willcooke & andyrock08:23
seb128willcooke, though it seems that bug got enough users verifying it08:23
willcookeseb128, I think so.  Just trying to recreate it now08:23
* willcooke eyes the dropbox repo08:24
willcookehrm, not that08:25
willcookeah, backports08:25
seb128that's what others say on the bug as well08:26
willcookeyeah, just seen that08:26
seb128I wonder if something changed08:26
seb128because it's several people who have issues with backports today08:26
willcookethis could be an issue for upgrading then08:26
seb128does it block the apt index refresh for ever?.08:27
seb128in which case it indeed a problem08:27
willcookeseb128, running it manually now, let's see...08:27
willcookesudo appstreamcli refresh --verbose --details --force08:28
willcooke** (appstreamcli:5082): DEBUG: Refreshing AppStream cache08:28
willcooke** (appstreamcli:5082): DEBUG: Reading: /usr/share/app-info/xmls/org.freedesktop.fwupd.xml08:28
willcooke** (appstreamcli:5082): DEBUG: Reading: /var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial-backports_main_dep11_Components-amd64.yml.gz08:28
willcooke** (appstreamcli:5082): DEBUG: Reading: /var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial-backports_restricted_dep11_Components-amd64.yml.gz08:28
Laneydebugging a fixed bug?08:28
willcookeLaney, issue is that I wont get the fix because appstream cli hangs forever(?)08:28
seb128Laney, no, trying to reproduce to verify the SRU fix08:28
seb128Laney, also wondering how we get the fix to users if the bug prevent them to get updates08:28
Laneyrelease it08:29
seb128well, still08:29
seb128if they can't apt-get update08:29
seb128their apt is never going to list the update08:29
seb128so they are never going to see/be able to get it08:29
Laneyyou prevent updaters from getting it08:29
seb128you mean?08:30
seb128well, if people running release can't refresh their package index due to it, how do they get the fix?08:31
LaneyIf you release it then nobody new will get the bug08:31
LaneyDon't knwo08:31
seb128I was wondering if there is a specific issue with backports that triggers the bug08:31
LaneyI doubt it08:31
Laneythey are empty of appstream08:31
seb128k, just seemed a weird coincidence that several people mention backports as being an issue today08:32
LaneyMaybe it's an interaction with something else08:32
seb128like there are some on the bugs, willcooke and jtaylor on #ubuntu-devel08:32
LaneyIt doesn't mean it's backports itself08:32
seb128but yeah, the SRU is 7 days old and verified08:33
seb128need SRU team to copy it over08:33
LaneySomeone who has the bug could find out why08:33
Laneyand then we might be able to manipulate the appstream data somehow08:33
LaneyOtherwise, if it just started today, get the SRU out there08:33
seb128well those comments on the bug suggest that disabling backport "fixes" it08:33
seb128pitti, ^ can you get the xenial appstream SRU copied over to updates?08:34
LaneyThat doesn't help for an apt update08:34
pittiseb128: can do; I'm normally not doing SRU releases on Friday, but if that's safe, sure08:34
seb128pitti, well see backlog08:34
seb128pitti, we are concerned that the bug hits more users and block them to get updates08:34
pittibug 1574896 isn't verified yet08:34
ubot5bug 1574896 in appstream (Ubuntu Xenial) "appstreamcli: double free or corruption with certain metadata" [High,Fix committed] https://launchpad.net/bugs/157489608:34
seb128including the fix08:35
pittibut I suppose that's ok -- most importantly it shouldn't regress08:35
Laneylooks v-done to me08:35
Laneybut very recently so maybe the report didn't refresh08:36
seb128pitti, tahnks08:37
seb128Laney, I don't understand your " That doesn't help for an apt update" comment08:38
seb128btw I can confirm here08:38
LaneyYou can't make 'update' disable backports08:38
seb128right, that's not what I meant08:39
seb128just that backport creates the issue08:39
seb128confirmed here, enabling backport and I can't finish an apt-get update now08:39
seb128disabling and it's good again08:39
Laneybackports is empty08:40
seb128maybe that's what confuses it?08:41
LaneyIt's always been empty08:41
seb128in which case unsure why it started today :-/08:41
LaneyThat's what I'm asking to find out :-)08:41
Laneymain was published yesterday so maybe that did something08:42
seb128unsure how to debug that, but you probably can if you want, just enable backport with the xenial version and try to refresh apt :p08:42
LaneyI have that enabled and it works :(08:42
seb128you don't have the SRU version?08:42
Laneymirror is still refreshing08:43
Laneymaybe when that finishes it starts08:43
willcookeahh, Laney has a local mirror08:44
seb128that's cheating :p08:44
Laneyotherwise go gdb for you08:44
seb128disable your mirror and see if you get it?08:44
seb128I'm happy to help debugging08:44
seb128but I've no knowledge of the codebase/project08:44
Laneycould get a trace though08:44
seb128so learning curve is going to take some time08:44
seb128yeah, that's easy08:45
seb128let me do it08:45
willcookeis this anything?  http://paste.ubuntu.com/16517887/08:48
* willcooke is trying to work gdb 08:48
willcookealthough this is probably just debugging the fixed bug08:48
Laneymight be able to stop it happening for everyone08:49
seb128willcooke, install libappstream3-dbgsym for bonus points08:50
seb128#1  0xb732d998 in as_yamldata_parse_distro_data (ydt=0x9c72290 [AsYAMLData], data=0x9c73f88 "---\nFile: DEP-11\nMediaBaseUrl:\nOrigin: ubuntu-xenial-backports-restricted\nVersion: '0.8'\n\210", error=0xbfef1544) at /build/appstream-XJqxY1/appstream-0.9.4/src/as-yamldata.c:186108:52
seb128seems to stuck there08:52
LaneyI know how to fix it08:53
Laneyedit that file and add "Priority: 40" at the bottom08:53
Laneysee if it fixes it for you08:53
seb128let me try that08:54
Laneyhave to do it for all the backports ones08:54
seb128Laney, yeah, that works09:00
seb128did those files change recently/in which way?09:01
Laneybackpots/main got a backport09:01
Laneywhich made the file regenerate with a Priority value09:01
LaneyI guess that tickles the bug09:02
Laneywaiting for the current run to finish then will make it regenerate for the other components09:02
seb128happyaron, do you have a 3g stick or some hardware to have a look to that n-m applet/3g icon issue?09:37
willcookeif you don't please get one and expense it09:38
willcookethey're not expensive09:39
seb128oem team seems to be very eager to see that one moving09:41
seb128Dell seems to wait on it09:41
seb128happyaron, that should probably be higher importance that the version updates09:41
seb128or maybe we can get cyphermox to have a look today09:42
seb128I'm pretty sure he has hardware for it09:42
seb128shrug, and of course bugzilla.gnome.org is down when I want to upstream it09:44
davmor2willcooke, seb128: I noticed that my laptop was spinning up still after a hangout and not calming down turns out appstreamcli is running and using 100%cpu09:48
willcookedavmor2, indeed.  known issue.  Fix in the works09:49
seb128davmor2, see channel backlog09:49
seb128ok, since bugzilla is down and I'm done with what I was looking at let's do early lunch and continue with other things after that09:50
davmor2willcooke, seb128: ah awesome was busy in a meeting so hadn't kept an eye in here :)09:50
willcookel8r seb12809:50
willcookedavmor2, nw09:50
Laneyok appstream.ubuntu.com is updated09:54
Laneythe archive should get it soon09:54
Laneyhmm, or will it09:54
=== Drac0 is now known as Guest65576
pittiLaney: would that affect installs of xenial-release too?10:04
Laneyyes they have backports by default10:05
pittiLaney: I'm currently tryigng to install it into a VM (final image) and it hangs on apt-get update10:05
Laneytalking in #launchpad about a republish10:05
pittiah, ok10:05
happyaronseb128: no I don't have10:05
willcookehappyaron, please get one, I think it will be useful10:12
willcookejust expense it10:12
willcookeI picked up a ZTE MF112 on ebay for < 10 GBP10:13
happyaronwillcooke: will do, ty10:15
tjaaltonwillcooke: hi, is there someone assigned to work on bug 1417980?10:38
ubot5bug 1417980 in unity-control-center (Ubuntu) "Add support for unified Xorg input driver" [High,New] https://launchpad.net/bugs/141798010:38
* willcooke reads10:38
willcookeah, lib input10:39
willcooketjaalton, noone assigned yet, but it's on our list:  https://trello.com/c/4F2urkpx10:39
tjaaltonwillcooke: ok cool, I'm not on trello but good to know :)10:40
Laneyarchive should be fixed now11:02
willcookethanks Laney!11:07
willcookedavmor2, and we are fixed! ^11:08
davmor2willcooke: we are indeed11:13
seb128Laney, good job!11:24
seb128tjaalton, do we need that to happen? it's on our list but I doubt we are going to get to it this cycle11:31
seb128well we might11:32
seb128but we have quite some backlog and resources for y "feature" work is limited11:32
seb128it's likely going after packagekit 1 and gnome-software improvement and snap work11:32
davmor2Laney: what caused the issue in the end and is there a safeguard we can put in place to prevent it happening again?11:32
seb128which means I wouldn't count on it11:33
Laneythe bug is fixed11:33
seb128davmor2, I'm unsure appstream has a testsuit/an easy way to create and feed him the config that created the bug to make sure that's not coming back in a futur version, if that's what you ask11:34
davmor2seb128: right okay so we could randomly have this happen any time a new package it uploaded then11:35
seb128well usually fixed bugs don't reappear11:36
LaneyThe same way you could randomly have a bug in anything11:36
seb128but I guess it's a possibility that some future change lead to new bugs11:36
LaneyThis particular bug is fixed11:36
tjaaltonseb128: ok, kde & gnome will have it in y11:36
seb128tjaalton, good for them11:36
tjaaltongnome needs to depend on the driver11:36
seb128they can deal with the early adopter bugs11:36
LaneyIf you want to contribute a testsuite I'm sure ximion wouldn't say no11:36
tjaaltonthey dropped the old stuff11:36
tjaaltondebian switched already :)11:37
seb128tjaalton, wasn't that already the case in xenial?11:37
davmor2seb128, Laney: ah sorry I thought it was just a broken app profile that broke it11:37
seb128I though GNOME had dropped !libinput a while ago11:37
tjaaltonxenial has 3.18 still11:37
seb128tjaalton, ah, they added libinput support a way back but kept the old thing as well, just dropped that in 3.2011:38
seb128I see11:38
seb128thanks for the head up11:38
seb128if you want to work on the u-c-c fixes that would be welcome11:38
seb128but if you are too busy then back to what I said before11:39
seb128it's on the list but low enough that I'm unsure we are going to get to it this cycle11:39
tjaaltonsome of it is in mutter now11:39
seb128yeah, I expect for us it's going to be u-c-c/u-s-d only11:39
seb128I hope at least that there are no compiz changes needed11:39
Laneytjaalton: the desktop team is hiring ;-)11:42
Laneythis is my new troll version of patches welcome11:42
tjaaltonLaney: hehe :)11:42
tjaaltonis there any syncing done to u-c-c/u-s-d from upstream=11:44
tjaaltonyeah input config is all in mutter now, so it's not easy to port11:45
seb128well nothing regular/organized11:45
tjaaltonnot that it would help here anyway11:45
seb128we do cherrypick changeset and backport fixes11:46
seb128in principle those changes shouldn't be too difficult right?11:46
seb128change some X calls by others11:46
=== hikiko is now known as hikiko|ln
TrevinhoLaney: hey, could you publish https://requests.ci-train.ubuntu.com/#/ticket/1419 ?12:13
TrevinhoIt was blocked by the fact that unity is not built on the s390x again, but I think we need to whitelist this case again for yakkety (who can do that?)12:13
seb128Trevinho, why is usd still in there?12:29
seb128Laney, pitti, tedg, https://mail.gnome.org/archives/desktop-devel-list/2016-May/msg00005.html ... good timing ;-)12:30
=== hikiko|ln is now known as hikiko
Trevinhoseb128: is listed, but not in the ppa12:44
Trevinhoseb128: I did remove that from the list, but there are no packages to land12:45
seb128I think the silo needs to be reconfigured12:45
seb128you are going to hit an error on publishing12:45
seb128it still thinks usd is part of it12:45
Trevinhoseb128: I've made a build, but nothing changed and sil2100 told us that there was nothing else to do12:45
Trevinholet me try to remove it again12:45
seb128well, maybe it's going to work12:46
seb128but it looks wrong12:46
Trevinhoseb128: let's see if it works, in case it won't I try to rebuild the whole thing12:47
Trevinhoseb128: you can publish too?12:47
seb128Trevinho, yeah, but unsure about the s390x issue12:47
seb128what is that?12:47
Trevinhoseb128: basically unity never built in that arch, because the nux tests aren't passing in that arch12:47
Trevinhowhen it comes to use X to do some headless tests12:48
seb128but https://launchpad.net/ubuntu/+source/unity/7.4.0+16.04.20160415-0ubuntu1 has s390x build/binaries?12:48
Trevinhoso, we could maybe try to disable the tests there, but really thre's no need for unity there...12:48
pittiseb128: heh yes, I saw that the other day12:49
seb128Trevinho, https://launchpad.net/ubuntu/+source/nux/4.0.8+16.04.20160209-0ubuntu212:51
Trevinhoseb128: mh, i see these artifacts http://pastebin.ubuntu.com/16520312/12:51
seb128Trevinho, when doing what?12:51
seb128that seems a shotwell issue?12:51
Trevinhoseb128: that's in the brightray excuses12:52
Trevinhoseb128: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-ci-train-ppa-service-landing-028/yakkety/s390x/s/shotwell/20160519_160941@/artifacts.tar.gz12:52
Trevinhoyeah, sorry :-D12:52
Trevinhobrightray is something electron related :-D12:52
seb128where is the britney page for that silo?12:53
Trevinhoseb128: https://requests.ci-train.ubuntu.com/static/britney/yakkety/landing-028/excuses.html12:53
seb128Trevinho, "s390x: Always failed" so that's not a blocker12:58
seb128the issue is that you failed to build on s390x12:59
seb128Trevinho, " Missing build dependencies: libupstart-dev "12:59
Trevinhoseb128: I know, but still I'm getting "red ci-train" which isn't nice :-)12:59
seb128on https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-028/+build/975672512:59
seb128somebody retried upstart on https://launchpad.net/ubuntu/+source/upstart/1.13.2-0ubuntu2413:00
seb128oh, no, that seems stalled13:00
Trevinhoseb128: oh, actually the error on s390x is different from the one I had in the past: "Missing build dependencies: libupstart-dev"13:01
Trevinhoso it's another thing13:01
seb128Trevinho, read what I just said13:01
seb128see -devel13:02
seb128Trevinho, seems like you are blocked on xnox/slangasek to fix upstart build on s390x :-/13:03
Trevinhoseb128: yeah, sorry...13:03
Trevinhoin the mean time I noticed that there has been another direct push to nux, without ci-train :-/13:04
seb128doko, of course13:05
seb128feel free to tell him off on #ubuntu-devel13:05
Trevinhoseb128: yeah... But sil2100 fixed it in the branch... Same happened for compiz in yakkety. I really would lvoe to be notified before doing this.13:06
Trevinho... at least.13:06
seb128tell them13:06
seb128maybe if we tell them enough it's going to stick at some point13:07
Laneyso don't do anything then13:21
Laneyworks for me!13:21
Laneyjust got our poll cards for the referendum13:24
Laneyshit got real13:24
* willcooke is worried by how many brexit people he sees on facebook13:25
Laneyit's because that campaign has a stupid name13:25
Laneywhich is catchy13:25
Laneyunlike bremain13:25
seb128Trevinho, speaking about landing, what's the status of landing the bamf menu fix for xenial?13:27
Trevinhoseb128: I always waited things to go into devel before preparing SRUs... At least that was the policy I was thought, but I can basically prepare the same silo for X right nwo13:28
Trevinho(almost the same)13:28
seb128it's the policy yes13:28
seb128but it's ready for y13:28
seb128it's just blocked by upstart on s390x13:28
seb128I think we can talk the SRU team into taking the xenial upload13:29
seb128though probably not today13:29
seb128they don't like friday uploads13:29
seb128monday is fine13:29
Laneythey don't release to updates on friday13:30
Laneyproposed is ok13:30
seb128some SRU team members are a bit conservative with that as well I think13:30
seb128but anyway we can get it in the queue13:30
seb128when they review it is their business then ;-)13:30
seb128Trevinho, also we need to deal better with important issues, that missing menus one should have been more prioritized and probably got its own silo, it doesn't make sense to block it on unity things to get fixed...13:31
seb128like we could have landed bamf to fix menus in y and x13:31
seb128it's a much easier thing to land than compiz+unity13:32
Trevinhoseb128: I agree, it's just that the "fix" is probably not complete... And also I got some emails about not using tooo many silos (I had three around, because of trusty SRUs sitting there for months... And really I don't like bothering people about clearing the queue)13:33
Trevinhobasically I did this: silos with 1,2 sru fixes... but this is not liked.13:33
seb128don't bother about that13:34
seb128the infra is there to be used13:34
seb128if they don't want silo to be stucked they can nag SRU team for reviews13:34
seb128I agree we shouldn't abuse silos13:34
Trevinhoseb128: I'd like to know what's the best way to ping SRU team for reviewing a ci-train branch. Because it seems they don't get properly notified by sync queu elemenents13:35
seb128but fixing menus of LTS users is for sure justify using some CI resources13:35
Trevinhoand they tend to stay there forever13:35
seb128they do13:35
seb128it's just that the diff are not generated by the queue13:35
seb128so they need to go back to ppa, fetch the package, etc13:35
seb128more manually work13:36
seb128pitti, ^ right?13:36
seb128Trevinho, also we don't need to use CI train to land, we can manually upload and merge13:36
seb128in fact I did bypass the train for the u-c-c/u-s-d SRUs I did to xenial13:36
seb128too much annoyance to use it13:37
Trevinhoseb128: eh, yeah... you can. But I don't have the powers13:37
Trevinhoseb128: I would like to use the silo to build, then get someone who can just upload those13:38
seb128why do you need the silo to build?13:38
seb128well it's going to have a test build/ppa13:38
seb128but yeah, we can force merge then and manually dput13:38
seb128Trevinho, you should apply for a ppu for the unity stack so you could dput ;-)13:39
Trevinhoseb128: Ok, let me see... That isn't included if I apply for ~ubuntu-desktop, right?13:40
seb128ubuntu-archive-tools/edit-acl query -s unity -S xenial13:42
seb128== All uploaders for package 'unity' ==13:42
seb128Archive Upload Rights for ubuntu-desktop: archive 'primary', package set 'ubuntu-desktop' in xenial13:42
seb128Archive Upload Rights for ubuntu-core-dev: archive 'primary', component 'main' in xenial13:42
seb128 13:42
seb128Trevinho, it is in desktop set13:42
seb128tjaalton, do you know how to tell if libinput is enable?13:49
seb128tjaalton, I'm trying to use the libinput tests and I get "../../src/check_msg.c:80: No messaging setup" errors, unsure why13:50
Trevinhoseb128: that means that if you can get me in, I don't need the ppu, right?14:00
seb128Trevinho, yes, let's see next week14:00
LaneyStill think that you could become a lander for unity/compiz/bamf just by talking to sil210014:02
Trevinhosil2100: ^, make me a lander :-)14:02
seb128Laney, he can, but we were just saying that we want to not use the train forSRUs maybe14:02
TrevinhoSo i can freely break the desktop experience of everyone without having Laney to be my evil accomplice :-D14:03
Trevinho(without know it)14:03
tjaaltonseb128: the x driver? from the xorg log14:16
tjaaltonand basically just installing it means that it's used for mice/touchpads/touchscreens14:17
seb128k, any idea why the tests give me that error?14:18
cyphermoxseb128: get me to look at what?14:20
seb128cyphermox, hey14:20
seb128cyphermox, bug #157157414:20
ubot5bug 1571574 in OEM Priority Project "3G (WWAN) icon missing in network-manager-applet" [Critical,Confirmed] https://launchpad.net/bugs/157157414:20
seb128oem is nervous about it14:20
seb128and nobody in our team seems to currently have hardware14:21
=== Drac0 is now known as Guest71277
cyphermoxoh right14:22
cyphermoxyeah, I suppose that might be broken, lemme try it here real quick14:23
cyphermoxindeed, it's broke14:25
seb128cyphermox, any chance you could try to have a poke to it today?14:26
cyphermoxthat's what I'm doing now, I think I know exactly what's wrong14:26
seb128or do you know if I can easily emulate a 3g connection using dbusmock?14:26
seb128cyphermox, beer+=314:26
cyphermoxis that adjusted to drinker size? ;)14:27
Laneyone drink per g14:27
cyphermoxcan we go with one mL per g instead?14:29
Laneybut you're only fixing 3G14:29
Laneygo for LTE then you can have a little bit more14:29
cyphermoxit will fix LTE too14:30
Laney4 drinks!14:30
cyphermox*those* Gs.14:30
cyphermoxI thought you meant the Gs that usually follow ks. :)14:31
LaneyKO follows too many Gs of C2H5OH14:32
cyphermoxlooks like I had already spent some of this limited brainpower on my internet issues this morning14:32
cyphermoxLaney: indeed14:32
cyphermoxthat applies to most C**OHs anyway.14:33
tjaaltonseb128: no idea14:34
Laneysome funky stuff in there14:34
seb128tjaalton, no worry, thanks14:34
cyphermoxyeah. for instance C12H22O11 gets you diabetes, which will get you KO too14:35
cyphermoxseb128: ok, fixed it; I'll build to see but it's stuff that was missing upstream from their merge of my indicator patch14:43
seb128cyphermox, \o/14:43
seb128cyphermox, going to make oem happy, thanks a lot!14:43
pittiseb128: silo SRU review> right, takes a bunch of clicks to see the real diff, otherwise the mechanism is the same14:51
cyphermoxseb128: I raise you https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/158307514:54
ubot5Launchpad bug 1583075 in network-manager (Ubuntu) "Private Key .p12 do not show on selection dialog window" [Undecided,New]14:54
seb128pitti, k, what I though14:54
cyphermoxwas just brought up to me by a friend, it looks like p12 is already in the extensions but something else may be amiss14:55
seb128cyphermox, https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/157561414:55
ubot5Launchpad bug 1575614 in network-manager-applet (Ubuntu) "Can't select secret key for TLS auth on wired or wifi connection" [High,In progress]14:55
seb128cyphermox, backport https://git.gnome.org/browse/network-manager-applet/commit/?h=nma-1-2&id=037c5721d89b20c46ecc53e05d9867fd4d969412 with your fix14:55
seb128happyaron is looking at updating to 1.2.2 and I asked him to backport that14:55
seb128but we might want to do an upload with your fix + that14:56
cyphermoxseb128: ok, 3g signal thing fixed although the icons we ship look like wifi, but that's not new.15:06
seb128cyphermox, \o/15:07
seb128cyphermox, want to maybe upload to y? we can handle SRU next week15:07
cyphermoxyeah, I'll upload in a moment, just doing the p12 fix now15:08
seb128cyphermox, you saw the commit I pointed?15:15
seb128cyphermox, just checking if you "doing" means backporting or redoing :-)15:16
cyphermoxI don't write code if I can avoid it ;)15:17
ximionLaney: looks like the strup issue in appstreamcli became a big hit overnight :P15:19
ximionnot sure which cosmic fluke was responsible for users seeing it now, but fortunately the update is out now15:19
seb128tjaalton, just for the record my issue was permissions, need to use sudo15:20
seb128ximion, see channel backlog from earlier today if you want some details15:20
seb128but seems it was triggered by an update being published to backports15:21
Laneyfun one15:21
ximionseb128: is the backlog stored somewhere?15:21
Laneyximion: you get your "broke ubuntu" badge :P15:21
* ximion wasn't in the channel earlier15:21
ximionLaney: I would also need to get a "fixed Ubuntu before he broke it" badge ^^15:22
seb128ximion, http://irclogs.ubuntu.com/2016/05/20/%23ubuntu-desktop.html#t08:5315:22
seb128though I guess the discussion doesn't have much details on what Laney did15:22
ximionLaney: the priority value triggered it? Weird!15:23
ximionpreviously, no user experienced this bug, and it was in the code for a long time and run by users at Debian ^^15:24
cyphermoxseb128: fyi: https://mail.gnome.org/archives/networkmanager-list/2016-May/msg00066.html15:24
seb128cyphermox, https://bugzilla.gnome.org/show_bug.cgi?id=766709 btw15:25
ubot5Gnome bug 766709 in nm-applet "3G (WWAN) icon missing in network-manager-applet" [Normal,New]15:25
seb128I had it forward15:25
seb128sorry I didn't mention, but the launchpad bug had the bug watch15:25
cyphermoxah, sorry15:25
seb128cyphermox, thanks :-)15:25
cyphermoxI'm updating the bug15:25
ximionseb128: thanks!15:28
ximionbtw, we have an unittest for this bug upstream for a while now :-)15:28
seb128davmor2, ^15:28
davmor2seb128: oh nice15:30
ximionLaney: maybe important to know: this bug can *still* be triggered, even with the patch, if you feed appstream malformed YAML15:32
ximionwe resolved this upstream too, and Yakkety should be completely safe15:32
Laneysounds like a good one to backport15:33
ximionsince there usually is no broken YAML, triggering this bug should not happen though (you need to be root to install busted YAML)15:33
ximionyes, might still be useful to have15:34
Laneygenerator bug or third party repo15:34
ximionbackground is that the YAML parser wasn't checked correctly for errors which occur due to malformed YAML files, which sends appstreamcli into an infinite loop15:34
Laneythe apt hooks are a bad place to have a program hanging15:35
* ximion agrees15:35
Laneysince the repository can't give you a package to get you out15:35
ximionoh, it can - but only if you don't refresh the cache before attempting to upgrade :P15:35
ximionhttps://github.com/ximion/appstream/commit/f5a2f4da6e1bdce89124858d672e9ddea051b172 is the thing15:36
ximionit grew a bit bigger, because I wanted to fix other things too15:37
ximionwhen that other bug in appstream-glib is fixed, there should be no way to bring AppStream down anymore15:38
ximionPK >> 1.0 in Yakkety, nice :-)15:54
seb128not quite yet15:55
seb128it's in proposed like it was previous cycle15:55
seb128let's see if doko deals with aptdaemon and the other things in breaks15:56
ximionseb128: IMHO it would make a lot of sense to just drop the pkcompat layer from aptdaemon16:01
seb128yeah, probably, we discussed that before xenial16:01
ximionhave stuff which uses PK use PK, and things which use the aptd API use aptd - aptd mimicking PK is just a source of bugs16:01
seb128I don't remember what issues we had with changing that though16:01
ximionseb128: those would be interesting to know, because if they are easy to accomodate to on the PK upstream side, we might just do the changes16:02
seb128I think it was more distro technical debt16:02
seb128or fixing things that depends on the compat layer16:03
ximionthere's stuff depending on the compat layer?16:03
ximionthat'd be weird... (since everything is using it via libpackagekit-glib2...)16:03
seb128well, depends in the debian/control sense16:07
ximionright, that is a different thing16:07
seb128I think I remeber why we didn't drop it in xenial16:07
seb128it's because we said it wouldn't make sense to replace it by the outdate/buggy pkgkit 0.8 code16:08
ximion(but then I would argue that fixing a few packages is less work than adapting aptd - at least in Debian, there is only one package depending on aptd at time, which means everything doing so in Ubuntu must be due to Ubuntu-specific patches)16:08
seb128and we couldn't update packagkit because of click16:08
seb128now for y we decided to ignore click16:09
seb128so we can update packagekit16:09
seb128and probably drop the aptdaemon compat16:09
ximionyeah, GNOME Software with PK << 1.0 just doesn't work at all :P16:09
Laneyhappy weekend!17:01
Laneyflexiondotorg: I should probably share my CSS changes with you at some point, will give you that soon17:01
* Laney laters17:01
TrevinhoLaney: have nice WE17:02
=== alan_g is now known as alan_g|EOW
seb128Laney, have a good w.e!17:10
flexiondotorgLaney, great.17:13
flexiondotorgLaney, https://github.com/flexiondotorg/ubuntu-mate-themes17:13
flexiondotorgThat is where we are adapting the MATE themes to 3.18 for MATE 1.14 built against GTK3.17:14
flexiondotorgWhen that is done, we'll branch and start work on 3.20 in the same repo.17:14
willcookeEOW!  night all, have a great weekend17:40
seb128have a good w.e desktopers!17:44
Berethow does one fix the gnome software rubbish in 16.04? :)21:12
=== Drac0 is now known as Guest51138
=== JanC is now known as Guest59129
=== JanC_ is now known as JanC

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!