=== _salem is now known as salem_
=== maclin__ is now known as maclin
=== salem_ is now known as _salem
[05:51] <pitti> Good morning
[06:49] <DanChapman> good morning
[07:24] <dkessel> Good morning
[07:25] <elfy> morning dkessel
[07:32] <dkessel> morning elfy
[07:46] <jibel> Good morning
[07:47] <elfy> morning jibel
[07:52] <jibel> morning elfy
=== maclin_ is now known as maclin
=== _salem is now known as salem_
[12:56] <davmor2> jibel: uefi+sb first issue discovered I'm hitting ENTER and RETURN on the keyboard after ejecting the cd and nothing is happening :(
[12:57] <davmor2> jibel: looks like the keyboard is completely disabled ctrl+alt+Fx isn't working either
[13:02] <davmor2> jibel: and now the second clicking on the cross on the keyboard shortcuts doesn't actually close the keyboard shortcuts other than that perfect install
=== roadmr_afk is now known as roadmr
[13:43] <davmor2> jibel: if you open say launchpad and a webapp you get 2 firefox windows and 2 markers to the left of the FF icon in the Launcher correct?  If you then close the webapp but keep the launchpad window open do you still see the 2 markers to the left of the FF icon?
[13:47] <jibel> davmor2, I do.
[13:47] <jibel> davmor2, this is a bug in bamf
[13:48] <jibel> davmor2, actually it happens only on first try, if you try again is works properly
[14:16] <davmor2> jibel: confirmed
[14:16] <jibel> davmor2, file a bug but I think it's minor
[14:17] <davmor2> oh indeed just something I noticed :)
[14:28] <pitti> jibel: darn; so after hours of debugging I finally found the cause of bug 1283966 (testing fix now), and it's not the same as bug 1267116 :(
[14:28] <ubot5> bug 1283966 in autopilot-gtk (Ubuntu) "Looping while selecting the same object is causing the application to die raising a dbus no reply exception" [High,Triaged] https://launchpad.net/bugs/1283966
[14:28] <ubot5> bug 1267116 in autopilot-gtk (Ubuntu) "ubiquity crashed with SIGSEGV in GtkNode::MatchStringProperty()" [High,Confirmed] https://launchpad.net/bugs/1267116
[14:28] <pitti> so back to the drawing board
[14:29]  * davmor2 hugs pitti it sounds like he needs it
[14:29] <pitti> davmor2: thanks
[14:30]  * davmor2 also passes pitti a new marker for the drawing board, also sounds like he'll need it :)
[14:30] <pitti> davmor2: I also need a drawing board in the first place :)
[14:30] <jibel> pitti, great! do you think 1267116 and 1284671 are really duplicates? traces are slightly different and the bucket in errors.u.c corresponds to 1284671
[14:31] <davmor2> pitti: sorry I don't keep spare drawing boards request one from msm I'm sure the office have extra ones :)
[14:31]  * jibel hands pitti white paint to repaint his office
[14:32] <davmor2> hahaha
[14:32] <davmor2> yeah use the walls and repaint once a month :D
[14:32] <pitti> jibel: they look similar enough to me; as long as we don't have a practical reproducer (i. e. environment where one can debug this, and where turnaround time is only a minute or less),  I think we can treat them the same
[14:32] <pitti> jibel: I doubt that for a memory corruption like that the traces will always be identical
[14:32] <pitti> jibel: haha
[14:39] <pitti> jibel: ah, but indeed http://paste.ubuntu.com/6725605/ also has a critical
[14:40] <pitti> jibel, DanChapman: how reliably can bug 1284671 be triggered?
[14:40] <ubot5> bug 1267116 in autopilot-gtk (Ubuntu) "duplicate for #1284671 ubiquity crashed with SIGSEGV in GtkNode::MatchStringProperty()" [High,Confirmed] https://launchpad.net/bugs/1267116
[14:40] <pitti> any chance this could be run with G_DEBUG=fatal-criticals and "ulimit -c unlimited" to get a proper core file for this atk_object_set_parent: assertion 'ATK_IS_OBJECT (accessible)' failed
[14:40] <jibel> pitti, easy, I can remove the workaround (uninstall ubiquity slideshow) and run the tests
[14:41] <pitti> jibel: how much effort is it to set up this testing rig locally?
[14:42] <DanChapman> pitti there is the test runner in ubiquity trunk, (just so you know i have only managed to reproduce locally 3 or 4 times out of 100's of attempts)
[14:42] <pitti> jibel: but yeah, if it's not too much effort for you to run the test under that environment, a core file would be great
[14:43] <jibel> pitti, I forwarded you what I sent to veebers with the instructions to run locally
[14:43] <jibel> pitti, but locally I can reproduce it like 10% or less of the time
[14:43] <pitti> jibel: well, I can of course just poke around on albali or wherever that's running
[14:45] <pitti> jibel: ah, thanks for the mail
[14:49] <jibel> pitti, where will the core file be generated?
[14:51] <jibel> pitti, also do I need to reset core_pattern to disable apport?
[14:52] <jibel> or I just leave everything as it is and let apport do its work
[14:53] <pitti> jibel: apport checks the crashing processes' ulimit and create core files just like the kernel would, so no need to touch
[14:53] <jibel> ok
[14:53] <pitti> jibel: core file will be in the cwd of the crashed processs (ubiquity), so probably /root or /home/ubuntu
[15:01] <davmor2> jibel: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1297886 can you do the honours please
[15:01] <ubot5> Ubuntu bug 1297886 in bamf (Ubuntu) "two marker on FF after closing a webapp" [Undecided,New]
[15:06] <jibel> pitti, tests running, without the workaround + G_DEBUG + ulimit -c unlimited
[15:19] <jibel> pitti, not sure what it means but with G_DEBUG ubiquity crashed almost immediately https://jenkins.qa.ubuntu.com/job/ubiquity_ap-ubuntu_devel_daily-test_english_default/ARCH=amd64,label=rabisu/128/
[15:20] <jibel> well, stopped with SIGTRAP
[15:21] <jibel> /var/local/autopilot//logs//autopilot.log: [Gtk] UNKNOWN: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed
[15:21] <jibel> /var/log/syslog: Mar 26 15:07:46 ubuntu kernel: [   77.614241] traps: ubiquity[4827] trap int3 ip:7fd8aac19c13 sp:7fff30156970 error:0
[15:36] <pitti> jibel: ah, crap; yeah, I guess if there's tons of "expected" criticals that G_DEBUG approach won't get us very far :(
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== bfiller is now known as bfiller_afk
=== roadmr is now known as roadmr_afk
=== roadmr_afk is now known as roadmr
[18:11] <jibel> jamespage, hi, some server tests are not covered for this milestone, particularly MaaS and iSCSI. Could the server team test those?
[18:17] <jamespage> jibel, sure
[18:25] <davmor2> jibel: right back from tea images downloading I'll hit uefi and mac first
=== bfiller_afk is now known as bfiller
[18:33] <jibel> davmor2, did you download them from pending/ ?
[18:33] <jibel> davmor2, because only latest mac is available from current/
[18:33] <davmor2> meh
[18:34] <jibel> stgraber, the script updates the tracker when images are not yet in current/
[18:34] <jibel> for example in http://cdimage.ubuntu.com/daily-live/current/ there are both latest and previous builds depending on the arch
[18:39] <stgraber> jibel: nusakan updates the tracker once it has asked all mirrors to sync from it
[18:39] <stgraber> jibel: we have no way to know when the rsync is actually done so that's as good as it gets...
[18:57] <davmor2> jibel: oh so hang on queuebot said Builds for ubuntu had been updated does that not mean released then
[20:42] <davmor2> jibel: does it take ages to get from the requirements check to the partitioning step
[20:45] <jibel> davmor2, no, it should be almost immediate
[20:46] <davmor2> jibel: it's taking like a minute or so here.  I wonder if the TB drive has anything to do with it :)
[20:47] <jibel> davmor2, you can open a terminal and check what it is doing. also /var/log/syslog and /var/log/installer/debug might give you an indication if something went wrong
[20:47] <davmor2> jibel: I'll have a look next time
[20:48] <jibel> so ubiquity-dm and encrpyted home are working now.
[20:48] <jibel> I'm now verifying oem installationds
[20:48] <jibel> -d
[21:17] <davmor2> jibel: yeah setup of the tools and then scan of the drive by the look of it
[21:17] <davmor2> jibel: that would slow it down a on 1TB drive I guess :)
[21:18] <jibel> davmor2, who needs a 1TB drive now that everything's on the cloud :)
[21:19] <davmor2> jibel: well when you need a machine that can install the entire myapps for 6 versions of ubuntu you need a bit of space
[21:20] <davmor2> jibel: the mac with it's smaller drive is much quicker there, but I'm assuming you in vm have like 23 GB driver or something
[21:20] <jibel> davmor2, exactly
[21:21] <davmor2> once that is loaded the installer is rapid it's just that one step that is slow
=== roadmr is now known as roadmr_afk
[21:43] <davmor2> jibel: is it me or is there no option for encrypted home on 64bit?  I see encrypted lvm disc but not just home unless I'm reading them wrong
[21:44] <jibel> davmor2, it is in the user setup step. I tried it earlier tonight
[21:44] <jibel> let me verify again
[21:45] <davmor2> jibel: no I mean a test listed for it
[21:48] <davmor2> jibel: I can confirm that there is a encrypted home option I just don't see a test to mark it against
[21:48] <jibel> davmor2, ah on the tracker, there is a gap in the test plan. It would be worth adding a mandatory test for this
[21:48] <jibel> I added an automated test this afternoon, just not deployed yet.
[21:49] <davmor2> jibel: I think so being as it is available as a default option.
[21:49] <davmor2> jibel: I'll add it to other features I think
[21:52] <jibel> sounds good
=== salem_ is now known as _salem