[08:54] <jibel> davmor2, Hey, what are the critical bugs on your list for the release of vivid?
[08:57] <davmor2> jibel: so it turns out that somehow zsync and mangled the images.  Checksums were well off.  So I killed them added them fresh.  Wifi is still playing up, not rebooting on hitting enter, and oem mode is still leaving the temporary user I'll grab you the bug numbers in a second
[09:00] <jibel> davmor2, shutdown is known, OEM I'm double-checking it was supposed to be fixed.
[09:01] <davmor2> jibel: might of been over the weekend maybe but certainly wasn't on Friday when I got the right image
[09:01] <jibel> davmor2, we are looking for someone from design for the vivid slideshow
[09:02] <jibel> davmor2, it was fixed 2 weeks ago
[09:02] <jibel> davmor2, so apparently the fix is incomplete
[09:02] <davmor2> jibel: they are in the office just lock the door around lunch and put on a sign that says you can't eat till someone gives me the slide designs ;)
[09:03] <davmor2> jibel: I'll check the yelp too and see if the artwork there is updated yet
[09:04] <pitti> jibel: bug 1445587
[09:04] <jibel> pitti, bug 1445592
[09:33] <davmor2> jibel: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1445481
[09:34] <davmor2> jibel: ^ that one bites me from time to time
[09:34] <flexiondotorg> jibel, davmor2 I can confirm the removal of the OEM user is still an issue - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1442679
[09:35] <davmor2> jibel: ^ that's the other one I'm looking for :)
[09:35] <davmor2> flexiondotorg: thanks
[09:35] <jibel> davmor2, flexiondotorg on it
[09:35] <jibel> still don't know what is happening there
[09:44] <davmor2> jibel: I'm assuming it is a final step of an upstart job that hasn't been ported to systemd, so just blame pitti ;)
[09:44] <pitti> davmor2: yes, please do; I'm on it
[09:44] <pitti> ah, actally I'm on bug 1445592 for now
[09:45] <pitti> it's likely that the OEM user bug is mine, too, but of course any help appreciated
[09:45] <davmor2> pitti: Yeah I'll be installing again, is there any info I can drag off the system that would be useful to you?
[09:48] <pitti> davmor2: I suppose this bug shold be fairly easy to reproduce, so as long as we have a bug which clearly documents what's wrong and how to get there I'm happy
[09:48] <pitti> easier to reproduce locally than ssh'ing to a remote one
[09:49] <davmor2> pitti: I think jibel is already testing it
[10:05] <flexiondotorg> davmor2, jibel I also confirm this - https://bugs.launchpad.net/ecryptfs-utils/+bug/1445198
[10:05] <flexiondotorg> davmor2, jibel I suspect this affects all flavours.
[10:12] <jibel> flexiondotorg, thanks, I'll look into it
[10:15] <flexiondotorg> jibel, Thanks.
[10:40] <davmor2> jibel: I'm grabbing netboot and starting there
[10:40] <jibel> davmor2, thanks
[10:41] <jibel> I'm trying to reproduce the ecryptfs issue, it seems it is not affecting ubuntu
[10:42] <jibel> davmor2, when you'll run an install on HW, can you click on the 'release notes' link and tell if it works
[10:42] <davmor2> jibel: will do
[10:42] <jibel> davmor2, in ubiquity-dm
[10:43] <davmor2> jibel: yeap
[10:47] <flexiondotorg> jibel, I confirm the ecryptfs issue doesn't affect Ubuntu.
[10:47] <flexiondotorg> jibel, It did used to work in Ubuntu MATE.
[10:47] <flexiondotorg> jibel, How is that script being invoked?
[10:47] <jibel> flexiondotorg, right, there is something missing from Mate, that's what I'm checking
[10:48] <flexiondotorg> jibel, I suspect xdg-open is missing MATE support.
[10:48] <flexiondotorg> jibel, Can you point me at the code that calls the script?
[10:49] <flexiondotorg> https://bugs.launchpad.net/ubuntu-mate/+bug/1001902
[10:54] <jibel> flexiondotorg, the problem is that xterminal-emulator doesn't support double-quotes to execute shell commands
[10:55] <flexiondotorg> jibel, Ah.
[10:55] <flexiondotorg> jibel, So why is Ubuntu not affected?
[10:55] <jibel> flexiondotorg, for example x-terminal-emulator -e sh -c 'echo hello && sleep 5' will work
[10:56] <jibel> for xterminal-emulator -e "sh -c 'echo hello && sleep 5'" won't
[10:56] <jibel> s/for/but/
[10:58] <flexiondotorg> jibel, Thanks for the info.
[11:02] <jibel> flexiondotorg, 2 options: change mate-terminal to support double-qoutes since -e is a command, or fix update-notifier hook to execute a command in move the current command executed in the hook to the script.
[11:05] <jibel> flexiondotorg, actually the bug occurs only if you invoke mate-terminal through x-terminal-emulator
[11:07] <jibel> flexiondotorg, the problem is probably in mate-terminal.wrapper
[11:08] <flexiondotorg> jibel, Please can you point me at the code that is invoking this?
[11:08] <jibel> flexiondotorg, it's in /usr/bin/mate-terminal.wrapper
[11:08] <flexiondotorg> jibel, No :)
[11:09] <flexiondotorg> jibel, The update-notifer stuff .
[11:11] <jibel> flexiondotorg, ah, the hook is /usr/share/ecryptfs-utils/ecryptfs-record-passphrase from ecryptfs-utils and linked into /var/lib/update-notifier/user.d/ to trigger the notification
[11:11] <jibel> flexiondotorg, but the bug is in the wrapper I think
[11:12] <flexiondotorg> jibel, I'm just curious as to why this had been working fine.
[11:14] <jibel> no idea
[11:14] <flexiondotorg> jibel, Thanks. I'll have a dig.
[11:14] <jibel> yw
[11:29] <flexiondotorg> jibel, I tracked the behaviour change down to the mate-terminal package. A few months back we changed from mate-terminal being the default to mate-terminal.wrapper.
[11:31] <jibel> flexiondotorg, in the wrapper you probably need to split oldargs to make it a list but don't split the quoted part of the command
[11:32] <jibel> a shell wrapper would be easier actually
[12:44] <davmor2> jibel: do you want server tests running on netboot aswell as desktop?
[12:46] <jibel> davmor2, wait there is a new kernel and a new debian-installer has just been uploaded
[12:46] <davmor2> shuggin fashin' dick dastardly
[13:13] <davmor2> pitti: so are we right is the oem removal just a missing systemd job?
[13:14] <pitti> davmor2: could be, I didn't look at it at all yet
[13:15] <pitti> davmor2: there is an oem-config.service which ought to do the same as the upstart job (calling oem-config-firstboot)
[13:16] <davmor2> pitti: right oem end user is setup, it's just the temporary oem user isn't removed and it auto starts that user :(
[13:16] <pitti> ………………………………………………………………userdel --force --remove oem || true
[13:16] <pitti> I see that in oem-config-firstboot, so perhaps that fails?
[13:16] <pitti> there might still be processes left from the oem user
[13:17] <pitti> although it has a "pkill -u oem || true" right above it
[13:31] <pitti> jibel: https://code.launchpad.net/ubuntu-seeds
[13:31] <davmor2> jibel: Release notes links to www.ubuntu.com/index_roadshow but that I'm assuming is because the page doesn't exist yet right?
[13:31] <flexiondotorg> davmor2, pitti - cyphermox has wored on the oem-config issue a few weeks back.
[13:32] <jibel> davmor2, it is a redirection server-side.
[13:32] <flexiondotorg> davmor2, pitti - cyphermox did add the required systemd support, AFAIK.
[13:32] <flexiondotorg> davmor2, pitti - The current issue is that the 'oem' user account is not always (as in rarely) removed.
[13:32] <jibel> flexiondotorg, it is on release team's radar
[13:33] <flexiondotorg> davmor2, pitti - The result being that after a system is prepared and the oem config is completed you are auto logged in as the 'oem' user.
[13:33] <davmor2> jibel: on a plus side it does open a browser and goto the above link
[13:33] <jibel> davmor2, thanks, in the test I did, it crashed the VM
[13:33] <flexiondotorg> jibel, Thanks. Just thought I share. I've been test the oem-config stuff for week. I was working for a brief period.
[13:34] <flexiondotorg> *it was working
[13:34] <pitti> flexiondotorg, davmor2: is that systemd specific? I. e. if you boot the first time with init=/sbin/upstart (use -snapshot!) does it work?
[13:34] <jibel> flexiondotorg, np, thanks.
[13:34] <cyphermox> after running oem-config-prepare and rebooting, there shouldn't even be starting anything as oem
[13:35] <flexiondotorg> pitti, I'm not sure what you asking?
[13:35] <pitti> flexiondotorg: if the failure to remove the oem user also happens under upstart
[13:35] <flexiondotorg> cyphermox, Correct. the oem-config is running as super user.
[13:35] <pitti> i. e. which direction we should debug this
[13:35] <flexiondotorg> pitti, I'll test it with upstart.
[13:36] <pitti> or maybe the oem-config thing has a log which might contain the error message from userdel?
[13:36] <flexiondotorg> pitti, Do I need any additional packages installed?
[13:36] <pitti> flexiondotorg: no
[13:36] <flexiondotorg> pitti, Thanks.
[13:36] <pitti> flexiondotorg: so I meant, normally you'd do a qemu install in OEM mode, and then you always boot the installation with -snapshot so that you can do it arbitrarily many times witohut having to reinstall
[13:37] <cyphermox> flexiondotorg: the big issue I see is that I still haven't been able to reproduce the bug you see
[13:37] <flexiondotorg> pitti, Understood.
[13:37] <flexiondotorg> cyphermox, I can reproduce everytime in VirtualBox and about half the time on laptop at home.
[13:37] <jibel> pitti, there is nothing in the log
[13:37] <jibel> nothing useful
[13:37] <flexiondotorg> cyphermox, The OEM I'm working with can only reproduce this on Broadwell NUC and Ultrabook.
[13:38] <cyphermox> flexiondotorg: only ever with ubuntu-mate or other images as well?
[13:38] <flexiondotorg> cyphermox, Ubuntu and Ubuntu mATE.
[13:41] <flexiondotorg> pitti, Do you want to install completed with upstart or just the first boot after the system is prepared?
[13:41] <pitti> flexiondotorg: the actual install sholdn't make a difference
[13:41] <flexiondotorg> pitti, OK.
[13:41] <pitti> flexiondotorg: so if you still have the orginal unmodified instal, or want to rnu oem-config-prepare again, you can use that
[13:41] <flexiondotorg> pitti, Understood.
[13:41] <pitti> flexiondotorg: i. e. we need to decide between "the .service runs at the wrong time" vs. "we broke oem-setup script"
[13:42]  * flexiondotorg is setting up a test environment.
[13:42] <davmor2> pitti: I install on hardware snapshotting it a little harder there ;)
[13:42]  * pitti introduces davmor2 to the wonderful world of VMs :)
[13:43] <davmor2> pitti: vm's are wonderful but if you only test on vm you don't know if things like real drivers work :D  Not often you get an nvidia vm ;)
[13:44] <pitti> right, but stuff like the above is easier to test in VMs
[13:44] <davmor2> pitti: also uefi + secure boot always works better on a device too :)
[13:44] <pitti> yeah, uefi in qemu works, but not secureboot
[13:45] <davmor2> pitti: wow that's impressive you got it to work in qemu it still failed for me :(  Vb's worked nicely though
[13:45] <cyphermox> pitti: it's not running at the wrong time; it's now running as the only thing in its own target
[13:46] <cyphermox> pitti: so the likeliest scenario is still that one oem-config gets removed, systemd decides to go and bring up the rest of the system, before all the scripts are done running
[13:46] <MacSlow> Greetings folks!
[13:54] <davmor2> cyphermox: oh that sounds like fun fun or not
[14:00] <pitti> cyphermox: that's not very plausible
[14:01] <pitti> cyphermox: it pkills all oem processes before it userdels
[14:01] <pitti> cyphermox: so we'd have that session been torn down, and/or userdel errors because of "busy user"
[14:01] <pitti> cyphermox: it's more likely that the cleanup code isn't run at all, jibel said that we don't get any userdel errors in the logs
[14:01] <cyphermox> well, who tells you it's not starting other things at the same time?
[14:01] <pitti> it could
[14:01] <pitti> but that doens't magically stop oem-setup
[14:01] <cyphermox> that's *exactly* what was going on before I made it its own target
[14:02] <cyphermox> hence why I'm also kind of surprised it would happen again, I tested this a lot and couldn't get it to fail again
[14:02] <pitti> well, let's just get an image, boot it with -snapshot, and set -x that script to see what's going on
[14:02] <cyphermox> but it could just be a matter of timing/speed now
[14:02] <pitti> little point in speculating
[14:03] <jibel> pitti, trying that right now
[14:03] <pitti> it seemed to work well enough when I ported it, so obviously something changed
[14:06] <MacSlow> rhuddie, hey there... can you point me to an ap/python-example explaining the correct use of scenarios?
[14:08] <MacSlow> rhuddie,  atm I'm looking at test_action_latency.py as guide... just wondering if that's good enough
[14:08] <rhuddie> MacSlow, hey. sure, I'll get back to you shortly.
[14:14] <flexiondotorg> pitti, If I try to use init=/sbin/upstart after the system is prepared oem-config doesn't not run at all. I get automatically logged in to an Ubuntu desktop as the 'oem' user.
[14:14] <flexiondotorg> I tested this with Ubuntu proper.
[14:14] <pitti> flexiondotorg: oh, fun
[14:15] <jibel> cyphermox, interesting, if I start oem-config-firstboot with --debug, the oem user is deleted
[14:16] <flexiondotorg> jibel, How did you invoke that via kernel options?
[14:16] <jibel> flexiondotorg, I changed the systemd job
[14:17] <jibel> and forced debug there
[14:17] <davmor2> jibel: so there's the fix then ;)
[14:17] <flexiondotorg> jibel, Thanks.
[14:22] <flexiondotorg> pitti, cyphermox jibel Just tested twice with systemd and Ubuntu and no debug. One worked, one did not.
[14:23] <flexiondotorg> Will try the --debug to see if it consistently works.
[14:23] <pitti> flexiondotorg: don't
[14:23] <davmor2> why is it things always work when you turn on debugging it's like the jinx from hell for qa :D
[14:23] <pitti> flexiondotorg: add set -x please
[14:23] <pitti> --debug changes teh behaviour of that script
[14:23] <flexiondotorg> pitti, To what?
[14:23] <pitti> flexiondotorg: to the scrip which does the userdel
[14:23] <flexiondotorg> pitti, Understood.
[14:23] <pitti> but jibel is on that ATM
[14:23] <pitti> we want to see a set -x in the failed case
[14:23] <flexiondotorg> pitti, I'll wait then.
[14:24] <flexiondotorg> jibel, The give Ubuntu MATE a test. I seems to fail a little more often than Ubuntu.
[14:28] <davmor2> jibel: yelp art-work is updated I think it look more like a Viking than a monkey though
[14:29] <jibel> davmor2, hehe
[14:29] <jibel> infinity, ^ :)
[14:36] <infinity> davmor2: It's not a viking, it's Wolverine.
[14:37] <davmor2> infinity: but that doesn't start with V :P
[14:37] <davmor2> infinity: maybe the next release will be Wicked Wolverine and then they can keep the mascot ;)
[14:38] <infinity> davmor2: wascawwy wabbit.
[14:39] <davmor2> infinity: We are going after the gaming community with the next release Worlda Warcraft release
[14:43] <rhuddie> MacSlow, for scenarios, you can see an example here: http://bazaar.launchpad.net/~phablet-team/address-book-app/trunk/view/head:/tests/autopilot/address_book_app/tests/test_delete_contact.py
[14:43] <MacSlow> rhuddie, thx... will take a look
[14:43] <rhuddie> MacSlow, you may also have seen the documentation: https://pypi.python.org/pypi/testscenarios/
[14:43] <MacSlow> rhuddie, ok
[14:55] <davmor2> jibel, infinity: meh empty wastebin is still opening a nautilus window :(
[15:12] <flexiondotorg> pitti, jibel I got oem-config to fail on Ubuntu with -x set. Where should I be looking for error logs?
[15:14] <flexiondotorg> jibel, That issue with the wastebin. Was that in the live session? - https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1445622
[15:14] <pitti> flexiondotorg, cyphermox: jibel found something, he'll update the bug
[15:14] <flexiondotorg> pitti, Thanks.
[15:15] <pitti> cyphermox: I finally understand bug 1445587 *phew*
[15:20] <cyphermox> pitti: ah, great
[15:21] <cyphermox> pitti: I think it should still be working as a proper dm, but I guess we can defer those changes to post-V
[15:22] <pitti> cyphermox: I made it work with a quick hack locally (defer the reboot by 5 s)
[15:22] <pitti> cyphermox: now seeing how we can fix this properly to avoid the race
[15:25] <jibel> cyphermox, added more info to 1436937, userdel fails because it cannot open /etc/subuid
[15:29] <cyphermox> jibel: if you haven't scrapped this yet, what was running as process 706?
[15:30] <cyphermox> while oem-config is its own "runlevel", I'm not sure what could have been started running as oem
[15:34] <jibel> cyphermox, systemd
[15:34] <jibel> ^
[15:34] <cyphermox> wha?
[15:34] <jibel> pitti, ^
[15:34] <cyphermox> pitti: ^
[15:34] <jibel> :)
[15:35] <cyphermox> no idea what that could be besides maybe a user session?
[15:35] <pitti> (target != runlevel, FTR)
[15:36] <cyphermox> pitti: inasmuch as it's the default target, and IIRC doesn't start multi-user OR graphical, for all intents and purposes, there should be nothing else running
[15:37] <cyphermox> pitti: feel free to check debian/ubiquity.target to see if I messed up
[15:37] <pitti> cyphermox: from what I see on jibel's machine this isn't related to service startup at all
[15:37] <pitti> cyphermox: one can re-run that userdel, and it keeps failing in exactly the same way, stumbling over /etc/subuid
[15:37] <cyphermox> then how do you explain any process starting as 706?
[15:37] <cyphermox> I mean, starting as the oem user
[15:38] <pitti> cyphermox: I don't know, does it? but that's not even why it fails
[15:38] <cyphermox> the expectations for oem-config are simple: nothing else should be running, especially not something as the oem user, and if something does and can't be killed for whatever reason, of course userdel will fail
[15:39] <pitti> it is apparently not failing because there's something running
[15:39] <cyphermox> if systemd wasn't running as oem, you wouldn't have trouble with /etc/subuid.
[15:40] <pitti> ah, I see jibel's log
[15:40] <pitti> he still has the VM, but he's in a meeting ATM
[15:40] <cyphermox> in any case, since you seem to understand all this better than I do, I can fix console-setup instead.
[15:40] <pitti> cyphermox: the debconf question? yeah, that'd be appreciated
[15:40] <cyphermox> yeah
[17:11] <pitti> cyphermox: so the oem user remove one is a really funny bug
[17:12] <pitti> cyphermox: wgrant just figured it out
[17:12] <pitti> (bug in shadow)
[17:13] <cyphermox> ok
[17:21] <balloons> wxl, assuming you are still kosher with it, I'm going to add the lubuntu lxqt session to the show and tell track for uos 15.05
[17:22] <wxl> balloons: yeah we'll figure it out :)
[17:22] <balloons> wxl, got a cool session title?
[17:22] <balloons> or preferred day / time?
[17:22] <wxl> ummmmmmmmmmm
[17:22] <wxl> "lubuntu, cuter"
[17:22] <wxl> :)
[17:23] <wxl> and sensible hours given the fact that i'm not utc :)
[17:25] <balloons> wxl, ok I'm make it late in the day
[17:26] <wxl> balloons: so yeah afternoon here is good :)
[17:27] <balloons> wxl, http://summit.ubuntu.com/uos-1505/meeting/22422/lxqt-next-generation-of-lubuntu/. Feel free to change the description or title :-)
[17:27] <wxl> thx balloons
[18:23] <cprofitt> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1445595
[18:24] <cprofitt> anyone available to triage that bug
[20:06] <elopio> veebers: hey, renato made a good comment in here: https://code.launchpad.net/~canonical-platform-qa/address-book-app/fix_base_class/+merge/256243
[20:07] <elopio> with the recommended way of launching the app, then we require to import the AddressBookApp custom proxy object, even if we don't use it.
[20:07] <elopio> or well, we don't use it directly.
[20:08] <elopio> it's one of the problems I see with the registry, we need the import which is not an explicit way of stating what we want.
[21:02] <knome> balloons, ping?
[21:03] <balloons> knome, pong
[21:04] <knome> this can't be right:
[21:04] <knome>     For a normal to normal upgrade, terminal will show Prompt=normal
[21:04] <knome>     For a normal to LTS upgrade, terminal will show Prompt=lts
[21:04] <knome>     For a lts to normal upgrade, terminal will show Prompt=normal
[21:04] <knome>     For a lts to lts upgrade, terminal will show Prompt=normal
[21:04] <knome> balloons, shouldn't everything but the last show normal, and the last one LTS?
[21:05] <balloons> knome, I remember going through this with elfy actually
[21:05] <balloons> or maybe I'm crazy. We spent time nailing this down so it would be right
[21:05] <knome> but that's very illogical...
[21:05] <balloons> all that said, it looks wrong :-)
[21:06] <knome> elfy, any last words? :P
[21:28] <balloons> knome, if you wouldn't mind righting our poor logic, we accept MP's; but also patches or simply corrected text :-) Bug reports welcome too
[21:28] <knome> or i can just push the new version in the branch and the tracker? :)
[21:29] <knome> and half of the point is that i'm not exactly sure what normal->LTS should do; my logic says "keep normal", but who knows...
[21:35] <balloons> knome, we like that option the best.. JFFI
[21:36] <knome> ;)
[21:40] <knome> balloons, done
[21:41] <balloons> <3 <3