[08:19] <didrocks> popey: hey, once you are around: are you on latest nux/unity (and if so, it's not crashing for you I guess, on the x220?)
[08:20] <popey> didrocks: morning!
[08:20] <popey> didrocks: I'm on saucy on my laptop, trusty on nvidia desktop
[08:20] <popey> so sure, can test latest of whatever on desktop
[08:26] <didrocks> popey: that would be excellent if you can confirm :)
[08:27] <popey> kk
[08:27] <didrocks> popey: or even maybe just a usb stick in live mode for the laptop?
[08:27] <didrocks> popey: I think testing on the x220 like that would be helpful :)
[08:29] <popey> I have been resisting moving to 14.04
[08:29] <popey> I will when I migrate to btrfs, probably on the weekend
[08:31] <didrocks> popey: yeah, so live usb seems to be the way to go for now :)
[08:32] <popey> didrocks: unity is fine on my trusty desktop
[08:32] <didrocks> ensure on the live that you have unity 7.1.2+14.04.20131106.1-0ubuntu2 and libnux-4.0-0 4.0.3+13.10.20131011-0ubuntu2
[08:32] <popey> ah
[08:32] <didrocks> popey: I'm interested on the x220 (hence the live usb so that you don't scratch your system)
[08:32] <didrocks> glew isn't used on nvidia
[08:32] <popey> ah
[08:33] <popey> meh
[08:33]  * popey moves to 14.04
[08:37] <didrocks> popey: just use a live session, don't break your laptop!
[08:37] <didrocks> :)
[08:37] <popey> I am outraged that you suggest upgrades don't work!
[08:43] <didrocks> ahah, I'm not. I just don't want you to end up in a session where you can't use your laptop :p
[08:45]  * popey installs gnome-shell ☻
[08:47] <didrocks> popey: heh, I fallbacked to it as well!
[08:53] <popey> The upgrade has completed but there were errors during the upgrade
[08:53] <popey> process.
[08:53] <popey> bah!
[08:54] <didrocks> argh, something else then ;)
[08:54] <didrocks> if you can note them :p
[08:54] <popey> http://paste.ubuntu.com/6784779/
[08:54] <didrocks> waow, more information on those?
[08:54] <didrocks> like overwriting files?
[08:55] <popey> apt-get -f install, it wants to pull in another truckload of packages
[08:55] <popey> http://paste.ubuntu.com/6784782/
[08:56]  * popey continues with teh configuring
[08:56] <didrocks> yep
[08:57] <didrocks> I'm pretty sur eyou had an overwrite
[08:57] <didrocks> which blocked
[08:57] <didrocks> (would be great to get your apt full logs of the previous update)
[08:57] <didrocks> once you finish your update ;)
[08:57] <popey> from dpkg.log?
[08:58] <popey> oh, there's a dist-upgrade log too, handy
[08:58] <didrocks> popey: /var/log/apt/term.log rather
[08:58] <didrocks> oh ;)
[09:28] <tsdgeos> fginther: the inexplicable otto crashes that went away are now back :'( https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/2150/?
[10:19] <vila> tsdgeos: fginther is not up and today is a US holiday IIUC, so better ping the vanguard in the topic line ;)
[10:19] <vila> tsdgeos: that said, a quick look in the log file (https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/2151/consoleFull) reveals :
[10:19] <vila> tsdgeos: /home/ubuntu/.xsession-errors: init: unity8 main process (7403) killed by SEGV signal
[10:19] <tsdgeos> i know
[10:20] <vila> tsdgeos: /var/log/syslog: Jan 20 09:34:02 trusty-amd64-20131210-1707 kernel: [842034.353231] QThread[30955]: segfault at 1cf16 ip 000000000001cf16 sp 00007f50255e0228 error 14 in unity8[400000+c000]
[10:20] <tsdgeos> i was not really asking for help
[10:20] <tsdgeos> i was just telling fginther
[10:20] <tsdgeos> it crashes
[10:20] <tsdgeos> just on those machines and noone else can reproduce
[10:20] <vila> tsdgeos: I didn't sync with fginther since Friday but I think it's a different issue
[10:20] <vila> ha
[10:20] <tsdgeos> this was happening a few weeks ago
[10:20] <tsdgeos> then it went away
[10:20] <tsdgeos> and now is back
[10:21] <vila> tsdgeos: unity8 crash ? (Making sure we're indeed talking about the same thing)
[10:21] <tsdgeos> yes
[10:22] <vila> ok, I didn't heard about that then, sorry
[10:23] <sil2100> huh
[10:23] <sil2100> After flashing to the latest image, it seems my unity-system-compositor dies
[10:24] <sil2100> terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
[10:24] <sil2100>   what():  could not activate surface with eglMakeCurrent
[10:24] <sil2100> I guess it might be the same issue discussed?
[10:25] <tsdgeos> not sure
[10:25] <tsdgeos> can't find that line in any of the logs of the build
[10:25] <tsdgeos> but might be
[10:26] <sil2100> tsdgeos: actually, nevermind, misread the discussion just now ;) Carry on!
[10:28] <sil2100> ogra_: hm, I remember that on the meeting just now there has been some mention of mir session env variable not being set properly, yes?
[10:28] <ogra_> sil2100, for adb sessions, yeah
[10:29] <sil2100> ogra_: since u-s-c fails on my device after stating: Unable to set active session, unknown client name session-0
[10:29] <ogra_> that was fixed in 136
[10:32] <sil2100> I wonder why it's crashing here
[10:33] <ogra_> sil2100, thats an unmodified image 137 ?
[10:34] <ogra_> (system image that is ... we know the cdimage install seems to have issues, but thats lower prio)
[10:35] <sil2100> ogra_: system image, unmodified, 137 (just downloaded and installed) - maybe it's some user config data?
[10:36] <ogra_> shouldnt, but try the fix we are discussing in -touch since a while
[10:36] <ogra_> we know there seems to be a race with setting the QPA_PLUGIN var
[10:36] <ogra_> err, QPA_PLATFORM
[10:48] <sil2100> ogra_: yeah, that fix helped - so it seems MIR_SOCKET thing was the problem
[10:49] <ogra_> yep, we see that in the test rrsults between 136 and 137
[10:50] <ogra_> thanks for confirming
[12:23] <silDroid> didrocks: had to jump out for a short while, my girlfriends dog is at the vet dying, so had to take her there so she can say goodbyes
[12:23] <silDroid> didrocks: but regarding ubuntu-keyboard
[12:23] <silDroid> didrocks: it seems its broken ;/
[12:23] <didrocks> silDroid: argh, just ping directly bfiller_away with those once he's around
[12:24] <didrocks> (probably tomorrow)
[12:24] <silDroid> didrocks: the new version just segfaults on start...
[12:24] <didrocks> silDroid: thanks for the catchup
[12:24] <rsalveti> ogra_: hey, did we already got an image after reverting the nested support?
[12:24] <ogra_> rsalveti, building ...
[12:24] <bfiller_away> silDroid: what are you testing? you need new seed if you're using new keyboard
[12:25] <didrocks> silDroid: you will be able to do the rest after a while
[12:25] <bfiller> ogra_: did you have a chance to look at the MR I sent you? https://code.launchpad.net/~bfiller/ubuntu-seeds/ubuntu-touch.trusty-keyboard-english/+merge/201879
[12:25] <didrocks> bfiller: isn't today a national holidays for you? :)
[12:25] <rsalveti> ogra_: great
[12:25] <ogra_> rsalveti, not really
[12:25] <didrocks> silDroid: as bfiller suggested, you installed all ubuntu-keyboard-<locale> packages, right?
[12:25] <bfiller> didrocks: yes but I'm working part of it anyway, capetown sprint going on..
[12:26] <ogra_> bfiller, sil2100 is on it ...
[12:26] <didrocks> bfiller: ah ok
[12:26] <silDroid> bfiller: hi! I was testing the ubuntu-keyboard from the ppa
[12:26] <ogra_> bfiller, he is testing your package changes first before i make the seed changes
[12:26] <bfiller> silDroid: make sure to install ubuntu-keyboard-english
[12:26] <rsalveti> ogra_: sure, just wanted a cdimage that could have a working shell at least
[12:27] <silDroid> bfiller: hm
[12:27] <rsalveti> but not sure anymore if that was because of the nested merge
[12:27] <ogra_> rsalveti, well, we'll land it again ... after the UI ordering issue is fixed i suppose
[12:27] <rsalveti> right
[12:27] <ogra_> rsalveti, though by experience that ight take another 8 weeks
[12:27] <silDroid> bfiller: will try, but then I guess we need to modify the packaging
[12:27] <rsalveti> yeah =\
[12:28] <ogra_> rsalveti, it was ... something is racy in setting MIR_SOCKET apparently
[12:28] <silDroid> bfiller: since it leads to a situation that without it installed (which can be done) it crashes on start
[12:28] <ogra_> rsalveti, http://ci.ubuntu.com/smokeng/trusty/touch/ ... image 136 and 137 are identical ... no changes at all ... 137 has the same error messages as you reported ... 136 doesnt (and local tests here dont either)
[12:29] <silDroid> bfiller: I installed ubuntu-keyboard-polish, set the key language to polish in settings, rebooted and it was the same
[12:29] <rsalveti> ogra_: hm, right
[12:29] <bfiller> silDroid: you need to set the active-language key
[12:29] <ogra_> rsalveti, so it looks like cdimage hits that race condition harder
[12:30] <bfiller> silDroid: actually 2 keys need to be set
[12:30] <silDroid> bfiller: system settings doesnt do that when switching keyboard layouts?
[12:30] <bfiller> silDroid: it's not been updated yet, I talked to attente about it
[12:31] <bfiller> silDroid: gsettings set com.canonical.keyboard.maliit enabled-languages "['en','pl']"
[12:31] <bfiller> silDroid: gsettings set com.canonical.keyboard.maliit active-language pl
[12:32] <silDroid> bfiller: ok, I will try that once back, but I guess we'll have to wait with osk to be released with system-settings then, not to break existing functionality
[12:32] <bfiller> silDroid: the existing functionality in system settings doesn't work already
[12:32] <bfiller> silDroid: so don't know if we need to wait for it
[12:33] <bfiller> but fine with me
[12:41] <ogra_> rsalveti, cdimage part is done
[12:42] <rsalveti> ogra_: great, thanks
[12:52] <ogra_> didrocks, fyi ... http://people.canonical.com/~ogra/touch-image-stats/20140120.1.changes
[12:52] <ogra_> (seems we dragged in new e-d-s and a bunch of other bits
[12:52] <ogra_> )
[12:52] <didrocks> ogra_: ok, so we grabbed latest systemd as well
[12:53] <ogra_> yep
[12:53] <didrocks> let's see… :p
[12:53] <didrocks> the diff isn't published yet on system-image
[12:53] <didrocks> for mako
[12:53] <ogra_> yep, still running
[12:54] <didrocks> ogra_: I'm anxious now :)
[12:54] <ogra_> why ?
[12:54] <didrocks> well, I hope the image will be back in shape, e-d-s and systemd… let's see :p
[12:55] <ogra_> we built images for years like that :) 90% of them worked
[12:55] <didrocks> I think the pass rate is lower for touch though of promotable images :)
[12:55] <davmor2> didrocks: why do we have systemd installed? Is it just that half the components we need are integrated into it now?
[12:56] <didrocks> davmor2: we do have for sure udev coming from systemd
[12:56] <didrocks> systemd package itself, hum…
[12:56] <ogra_> davmor2, systemd swallowed all important plumbing sources
[12:56] <didrocks> ah, we do use logind
[12:56] <didrocks> davmor2: so that's why ^
[12:56] <davmor2> ogra_: yeah that is what I thought
[12:56] <ogra_> oh, wait, the binary shouldnt be there !"
[12:57] <ogra_> ah, only -services
[12:57] <ogra_> that might be for hostname changing
[12:57] <davmor2> ogra_: it isn't I just saw about pulling in systemd and wondered why sorry
[12:57] <didrocks> ogra_: yeah, hostname (and maybe logind is using it too)
[12:57] <ogra_> right
[12:59] <davmor2> ogra_, didrocks: did you see the announcement that systemd is soon to start running gnome soon too (opt in/out, by all accounts)
[13:00]  * ogra_ only knows the discussion about that from 2 years ago 
[13:01] <davmor2> ogra_: https://plus.google.com/+LennartPoetteringTheOneAndOnly/posts/iCNySJKFseo there was a better one somewhere on google plus too I think
[13:01] <ogra_> well,let them
[13:02]  * ogra_ doesnt care what gnome uses to be honest 
[13:02] <didrocks> well, we do that with upstart as well, we have session support
[13:02] <didrocks> (but no kdbus)
[13:03] <ogra_> there we go
[13:03] <ogra_> [13:05] <didrocks> yeah \o/
[13:05]  * didrocks upgrades
[13:05] <didrocks> hum, should reset to vanilla config first
[13:06] <ogra_> nah, that tears out all excitement :P
[13:06] <didrocks> ahah :)
[13:07] <didrocks> I'm still unsure what I shold kill from /userdata
[13:07] <ogra_> just flasdh with --wipe/--bootstrap/--whatever-is-the-wiping-option-of-the-day
[13:07] <davmor2> ah infact here you go https://plus.google.com/115250422803614415116/posts/apZrj54GYee
[13:07] <didrocks> well, I would prefer to start being smarter :)
[13:08] <ogra_> pfft, your phones is already smart ...
[13:08] <didrocks> heh
[13:08] <didrocks> ok, trying to rm -rf /usrerdata/*, let's see what happens :p
[13:08] <didrocks> at worse, I'll reflash
[13:09] <davmor2> ogra_: it was smart with android it has to be smarter now it has ubuntu on right?
[13:10] <rsalveti> ogra_: cdimage on maguro still failing with 'Failed to load platform plugin "ubuntu". Available platforms are...'
[13:10] <rsalveti> with 138
[13:11] <ogra_> rsalveti, properly wiped ?
[13:11] <rsalveti> ogra_: yup, flashed with -b
[13:12] <rsalveti> ogra_: trying to run with SF
[13:12] <rsalveti> let me see with mir now
[13:12] <ogra_> stacking issue is gone here on maguro
[13:12] <ogra_> account creation still has issues for me though
[13:13] <rsalveti> cool, worked with mir, let me try what slangasek said on that thread
[13:13] <didrocks> flash in progress here with -b
[13:13] <ogra_> rsalveti, he reverted that stuff in 135already
[13:13] <ogra_> err 136
[13:14] <davmor2> ogra_, didrocks: maguro still rebooting, mako bbc news installed
[13:14] <ogra_> 136 and 137 both have his change ...
[13:14] <ogra_> davmor2, did you try removing and re-adding the U1 account ?
[13:14] <didrocks> davmor2: I guess while we are getting a test for wifi, you will need a "wipe data and connect to a wifi hotspot, enter WPA/WEP"
[13:14] <davmor2> ogra_: no I'm going to try that on maguro
[13:15] <ogra_> hmpf, now system-settings doesnt even get me into accounts anymore
[13:15] <davmor2> popey: why is there a big gap at the top of the bbc news app
[13:15] <ogra_> thats where popey will place his ads soon ;)
[13:15] <popey> there is?
[13:15] <didrocks> hum, lot of failures when copying…
[13:16] <ogra_> didrocks, copying ?
[13:16] <didrocks> failed to copy '/home/didrocks/Téléchargements/phablet-flash/imageupdates/pool/ubuntu-dbad0141353e07914b8a6fdf462ac9a4e18994eb768c9f4a5c1d0e27e5500c5b.tar.xz' to '/cache/recovery/': Is a directory
[13:16] <ogra_> wow
[13:16]  * didrocks retries
[13:17]  * ogra_ reboots again, i definitely cant create a U1 account here 
[13:18] <ogra_> yay
[13:18] <didrocks> ok, passed it seems
[13:18] <ogra_> so after 3 reboots it allowed me to
[13:19] <davmor2> so I was able to remove the account and add it back again and managed to crash unity8 in the process
[13:19]  * ogra_ installs an app
[13:20] <rsalveti> ogra_: right, tried to check the qtubuntu package split, but it fails with both qtubuntu-android and qtubuntu-desktop
[13:21] <rsalveti> SF support is definitely broken
[13:22] <ogra_> rsalveti, well, then it is time to call it dead i guess
[13:22] <rsalveti> ogra_: I'm not that sure yet
[13:22] <ogra_> or do you want to invest time into it
[13:22] <rsalveti> I don't, but I know we had a plan to drop it
[13:22]  * ogra_ doesnt think it matters if we do it now or in two weeks
[13:23] <rsalveti> if so, we should just warn the porters and give them directions for proper mir support
[13:24] <ogra_> right
[13:24] <ogra_> i think the plan to drop SF was definite ...
[13:24] <ogra_> so i would say it doesnt matter if we drop it a few weeks earlier
[13:25] <ogra_> but thats an asac decision indeed
[13:25] <rsalveti> right, I know we want to drop it, but we wanted it to be planned :-)
[13:25] <rsalveti> not as a side effect :-)
[13:26] <ogra_> rsalveti, well, we would have to find out as side effect of *what* first
[13:26] <ogra_> which will eat time
[13:26] <ogra_> ... and then fix it as well ...
[13:27] <asac> keeping SF around was done because of phonedations team think it is a) cheap and b) useful for bringup... once it is a) expensive and b) not really useful anymore, I don't see a reason to keep it around
[13:27] <asac> :P
[13:27] <rsalveti> asac: sure, but we should first sync with the oem team
[13:27] <didrocks> ogra_: ok, both setting up wifi and associating an account works here
[13:27] <rsalveti> if they are ok, then fine
[13:27] <rsalveti> aka achiang
[13:27] <asac> rsalveti: yeah, we could check tomorrow on the sim call
[13:27] <ogra_> asac, b) is definitely always true
[13:28] <ogra_> going step by step via SF to Mir makes porting surely easier
[13:28] <didrocks> davmor2: popey: can you try image #138 and test it on maguro/mako?
[13:28] <ogra_> but it doesnt lok like a) is still cheap
[13:28] <asac> sure, but if SF doesnt deliver a UX that is anywhere useful, we dont need to support it anymroe in unity etc.
[13:28] <popey> didrocks: ya
[13:29] <asac> you can still bring up ubuntu touch
[13:29] <asac> and run an example app that works on SF for instance
[13:29] <ogra_> rsalveti, when did you try SF last ? can we even make out a point when it stopped ?
[13:29] <davmor2> didrocks: I am
[13:29] <didrocks> thanks popey, davmor2
[13:29] <rsalveti> ogra_: last week or sure, probably before the qtubuntu package split
[13:29] <didrocks> psivaa: tests started on #138?
[13:29] <ogra_> ok
[13:30] <ogra_> so we would only have to bisect a week
[13:30] <popey> davmor2: did you change the permissions on that spreadsheet?
[13:30] <rsalveti> ogra_: I know because I was using SF with 4.4
[13:30] <asac> http://ci.ubuntu.com/smokeng/trusty/touch_sf4p/
[13:30] <ogra_> yeah, just remembered that
[13:30] <asac> seems it was last time safelyy green
[13:30] <davmor2> popey: nope
[13:30] <rsalveti> ogra_: and MIR support for it is still not merged
[13:30] <asac> fro build 121
[13:30] <popey> davmor2: i can't access it.. it's "comment only" for me
[13:30] <ogra_> asac, we're at 138
[13:31] <ogra_> thats quite a few images to check
[13:31] <asac> right. you asked if we know when ti was last working
[13:31] <asac> dashboard says 121 or maybe 124
[13:31] <ogra_> yeah, thannks
[13:31] <asac> 126 :)
[13:31] <ogra_> i had forgotten we still do sf tests
[13:31] <davmor2> popey: try it now
[13:32] <popey> thanks
[13:32] <davmor2> popey: it was on comment only but I hadn't touched it
[13:32] <popey> odd. nvm
[13:32] <asac> rsalveti: so what do you think?
[13:33] <asac> resurrect SF or good bye?
[13:33] <asac> can it even be resurrected? in particular with this nested stuff coming etc.
[13:33] <asac> what everyone surely agrees is that we shouldnt start hacking SF itself :)
[13:33] <rsalveti> asac: probably, but as I said, not my call, we should sync with people that are doing bringups
[13:34] <asac> rsalveti: ok lets suggest to achiang and folks tomorrow that we kill it and see
[13:34] <rsalveti> alright
[13:34] <asac> rsalveti: i think you could try answer this question yourself if you ask "would i be screwed if i dont have SF to bringup a N5"
[13:35] <asac> (assume you really shoot for MIR and are wiling to invest what it takes anyway)
[13:35] <rsalveti> asac: yeah, personally I'd prefer to invest my time with MIR
[13:36] <ogra_> yeah
[13:36] <ogra_> its just easier to get some success feedback with SF currently
[13:36] <ogra_> since it will just work
[13:36] <ogra_> (well, used to)
[13:37] <ogra_> while Mir needs extra work added
[13:37] <ogra_> but would likely be a good thing to get used to that extra work
[13:37] <ogra_> for us as well as for the porters
[13:37] <ogra_> (so we can answer their questions)
[13:45] <popey> didrocks: mako seems okay at first pass
[13:46] <didrocks> popey: great!
[13:56] <psivaa> didrocks: yes, tests are running with 138
[13:57] <ogra_> oh, and all 100%
[13:57] <ogra_> stop them now !
[13:58] <ogra_> :)
[13:58] <didrocks> ahah ;)
[14:14] <davmor2> popey: for you on your bbc new app do you see a grey block at the top of the app where the header should be (like a blank title bar)
[14:15] <ogra_> davmor2, hmm, might be the new webapp-container thingie
[14:15] <ogra_> did you try another webapp ?
[14:15] <davmor2> ogra_: no I'm just running tests now
[14:16] <davmor2> g+ is alright but that has it's own config iirc
[14:16] <ogra_> davmor2, i see it in all webapps apparently ... just checked
[14:16] <ogra_> G+ doesnt use the webbrowser-app webapp mode
[14:16] <ogra_> use IMBD
[14:16] <ogra_> or dict.cc
[14:16] <ogra_> thats definitely broken :(
[14:19] <davmor2> ogra_: indeed
[14:19] <ogra_> davmor2, see -touch ... talking to osomon
[14:29] <popey> davmor2: yes
[16:30]  * popey afk
[16:36] <davmor2> ohhh I want popey 's telepathy hat if he can type and not be at the keyboard
[16:47] <ogra_> i guess thats only a telepathic macro ... only says "afk"
[17:49] <sil2100> Ok, webbrowser-app is good
[17:50] <ogra_> let it in then :)
[17:51] <sil2100> Pushing ze button
[17:51] <sil2100> \o/
[19:11] <ogra_> [19:26] <asac> ogra_: did we get all blockers fixed in that?
[19:26] <asac> e.g. regressions are under control?
[19:36] <davmor2> asac: I think it fixes the blockers between this and reverting nested mir iirc
[19:38] <asac> davmor2: not sure i understand... i think you say "no, it doesnt fix all promotion blockers"
[19:38] <asac> what blocker do we expect to be still in?
[19:39] <davmor2> asac: No I think it fixes all the blockers
[19:39] <davmor2> asac: between reverting nested mir in 138 and the webbrowser-app fix in 139 I think all the blockers are fixed
[19:41] <davmor2> ogra_: do you know if didrocks was going to promote 139 if everything was fixed?
[19:41] <davmor2> asac: ^
[19:41] <davmor2> or are we looking to tomorrows images now?
[20:05] <popey> davmor2: i asked this and in all likelyhood we won't promote this one because the next one will arrive and we'll be testing in the morning
[20:06] <popey> but if it's good in the morning and the next one 140? is bad, then sure, we could
[20:25]  * popey updates to #139
[20:40] <asac> davmor2: didrocks would decide tomorrow morning based on findings