[00:45] <phillw> balloons: there are respins being kicked in, but no bugs as to why?
[00:49] <phillw> balloons: http://iso.qa.ubuntu.com/qatracker/milestones/314/history
[01:00] <balloons> phillw, new debian installer
[01:00] <phillw> balloons: NOOOOO!!!! I'm trying to unpick to have a non-pae variant :'(
[01:01] <phillw> Ah well, that prevents any chance of a sycn releas
[01:02] <phillw> balloons: I'm up to about http://pastebin.com/5bayZ205
[01:04] <phillw> but if the ubuntu team keep making changes I can not resonably offer an LTS for the kernel, and repo for updates....   :: SIGH ::
[01:05] <phillw> balloons:  Maybe I just tell people that *buntu keep changing things that I will drop the idea of a non-pae version for the older the XP machines and send them else where.
[01:07] <phillw> I can build the kernel... no worries :)
[01:13] <phillw> balloons: why has the lubutntu alternate builds been re-spun? I just did the i386 and amd64 ones on my test rig?
[01:13] <balloons> there is a new debian installer; the alt images will be respun for it
[01:15] <phillw> balloons: I wish I'd had chance for that to remove the pae flag test..... what reason did they respin?
[02:03] <veebers> Would anyone know which project I would file a bug against where my volume level isn't remembered between reboots and thus at start up it's _really_ loud?
[02:15] <phillw> balloons: who is this for? zsync http://cdimage.ubuntu.com/lubuntu/daily/20140416/trusty-alternate-i386.iso.zsync
[02:15] <phillw>  reports back could not read control file from URL http://cdimage.ubuntu.com/lubuntu/daily/20140416/trusty-alternate-i386.iso.zsync
[02:15] <phillw>  which means the file is not there correctly on the iso server?/?
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
[05:02] <pitti> Good morning
=== chihchun is now known as chihchun_afk
[07:09] <jibel> good morning
[07:10] <elfy> morning jibel
[07:10] <jibel> good morning elfy
[09:05] <jibel> could anyone test ubuntu gnome i386, automated tests all failed with a kernel panic
[09:05] <jibel> ?
[09:10] <davmor2> jibel: no new images yet?
[09:10] <jibel> davmor2, there are. 20140415 on the tracker
[09:12] <davmor2> jibel: so the test results are not reset then?  Or do the new images have the same internationalization issues?
[09:12] <jibel> davmor2, same issue with oem
[09:13] <jibel> davmor2, well, a bit different but still doesn't work as expected
[09:13] <davmor2> jibel: I'm assuming then there will like be another resping to fix that then
[09:14] <jibel> davmor2, very likely
[09:15] <davmor2> jibel: I'll make a start on netboot then and see how we go from there then :)
[09:19] <davmor2> jibel: I'm assuming that everyone has leapt into emergency fix it mode for the issue?
[09:20] <jibel> davmor2, don't need everyone, xnox is aware of the problem and its importance.
[09:24] <davmor2> jibel: fair enough :)
=== chihchun_afk is now known as chihchun
[10:13] <jibel> davmor2, I'll redo some multidisks install in UEFI and BIOS mode, and apart this language bug, the rest looks rather good
[10:14] <jibel> davmor2, anything on your side?
[10:14] <davmor2> jibel: i386 netboot just completed, amd64 is nearly done
[10:25] <davmor2> I never thought I'd see the day when wifi just worked on a netboot install /me hugs all the Ubuntu Devs that made that happen :)
[10:29] <pitti> davmor2: OOI, do you have a device with a broadcom wifi?
[10:31] <davmor2> pitti: no I think one was ralink and the other intel, the mac has broadcom you just install the binary and then that works not sure if netboot handles that yet
[10:31] <pitti> davmor2: right; I'm asking because current kernels are supposed to have a free broadcom driver (brcmsmac)
[10:31] <pitti> davmor2: and I wondered if it's using that now
[10:31] <pitti> davmor2: u-d-common isn't yet aware of brcmsmac, so it'll still install bcmwl
[10:32] <davmor2> pitti: not tested on the mac not even sure if there is an amd64+mac netboot mini.iso to be honest I'll have a dig and see
[10:33] <pitti> davmor2: nevermind, I was just curious
[10:33] <pitti> davmor2: oh, I thought amd64+mac wasn't needed any more?
[10:57] <davmor2> pitti: let me give it a go
[10:58] <davmor2> pitti: there is a still an amd64+mac build
[10:58] <davmor2> just no mini.iso for it
[11:02] <jibel> davmor2, are you testing amd64+mac images?
[11:03] <davmor2> jibel: I can in a second I was just checking if netboot worked on mac
[11:03] <davmor2> pitti, jibel: netboot doesn't work on mac with the standard amd64 mini.iso no wifi detected.
[11:07] <davmor2> jibel: right moving onto mac now, I'm assuming there is no point testing oem with non english language or do you want a confirmation that it is broken there too
[11:14] <jibel> davmor2, right you probably need to load the firmware for your card from another media
[11:16] <davmor2> jibel: Yeah I'm not too fussed as there is no specific amd64+mac mini iso anyway I just thought I'd try it
[12:07] <jibel> everything with Ubiquity in it will be respinned soon.
[13:03] <ePierre> Hi everyone!
[13:03] <ePierre> I'm testing today's build of Xubuntu
[13:03] <ePierre> I'm running this test case: http://iso.qa.ubuntu.com/qatracker/milestones/314/builds/66872/testcases/1303/results
[13:04] <ePierre> I would like to file a bug because I'm trying it in French, and some softwares have their names in English but are in French, whereas others have their name in French, but are in English (such as Thunderbird)
[13:04] <ePierre> under what component should I file this?
[13:04] <ePierre> xubuntu?
[13:12] <melodie_> hi o/
[13:15] <melodie_> hi, does someone here have good knowledge related to evolution and the different versions since Precise?
=== _salem is now known as salem_
[13:20] <ePierre> Hi melodie_
[13:20] <ePierre> I don't :(
[13:22] <melodie_> hi ePierre thanks for answering, at least I know one person read me :)
[13:38] <jibel> melodie_, #ubuntu-desktop would be more appropriate if you have a question about a specific version otherwise htere is a tool called rmadison that can give you the versions
[13:38] <jibel> melodie_, http://paste.ubuntu.com/7261531/
[13:39] <melodie_> hi jibel I know the versions
[13:39] <melodie_> jibel this is the issue:
[13:39] <melodie_> $ apt-cache policy libgcr-3.1
[13:39] <melodie_> libgcr-3-1:
[13:39] <melodie_>   Installé : 3.2.2-2ubuntu4.1
[13:39] <melodie_> noi
[13:39] <melodie_> no
[13:39] <melodie_> wait a sec sorry
[13:53] <jibel> xnox, I filed bug 1308530 any other info I could provide or other test I could perform? I'm currently retrying without an encrypted home to determine if the problem comes from that.
[13:53] <ubot5> bug 1308530 in ubiquity (Ubuntu) "Cannot login after an upgrade from Saucy to Trusty with Ubiquity" [Undecided,New] https://launchpad.net/bugs/1308530
[14:22] <davmor2> jibel, xnox: there might be an issue with binary packages on a live session install I'm going to try and replicate it and make sure it's not some freak accident and then I'll report.  I installed the wifi in the live session on mac then did an install including 3rd party drivers no wifi and I can't install the binary either
[14:24] <ePierre> question
[14:24] <ePierre> I received this e-mail:
[14:24] <ePierre> This bug has been reported on the Ubuntu ISO testing tracker.
[14:24] <ePierre> A list of all reports related to this bug can be found here:
[14:24] <ePierre> http://iso.qa.ubuntu.com/qatracker/reports/bugs/1308539
[14:24] <ePierre> ** Tags added: iso-testing
[14:25] <ePierre> is it an automatic process from the testing website because I added the bug number in the test report?
[14:25] <knome> yes
[14:26] <xnox> davmor2: depends on which drivers do you need.
[14:26] <xnox> davmor2: can you post lspci / lsusb to me?
[14:27] <xnox> jibel: cjwatson is looking into it.
[14:27] <xnox> jibel: i believe it is normal, as your ecryptfs is encrypted with the "old passphrase" and one cannot just magically change it by creating "new account with a different password".
[14:28] <xnox> jibel: otherwise that would be a trivial way to steal encrypted data.
[14:28] <davmor2> xnox: I will do as I say I'm just gonna double check it wasn't just some freak incident
[14:29] <jibel> xnox, right, that's what I supposed too. Do you remember if it has already been reported?
[14:30] <melodie_> does someone know of a ppa for Precise, to get a more up to date version of Evolution?
[14:30] <jibel> or maybe we should not allow the upgrade with an encrypted home
[14:30] <jibel> there is a high risk of data loss
[14:35] <ePierre> knome, thanks :)
[14:35] <ePierre> I'm off, ttyl people!
[14:38] <xnox> jibel: i have not seen that before.
[14:39] <xnox> jibel: bdmurray says we should disable the upgrade option full-stop =)
[14:39] <jibel> xnox, I share his opinion :)
[15:49] <davmor2> xnox, jibel: right I've been able to reproduce it, now I have to figure out where the hell to file it, I'm assuming ubiquity maybe partially to blame
[15:53] <davmor2> xnox: pastebin.ubuntu.com/7262212
[15:56] <xnox> davmor2: which drivers did you install to get it to work?
[15:58] <davmor2> xnox: so in the live session I installed the broadcom 802.11 Linux STA wireless driver source from bcmwl-kern  and then it goes off the page
[15:59] <xnox> davmor2: "goes off the page" as in you get wifi working and can connect to internet?
[15:59] <xnox> davmor2: possibly file / retarget bug against ubuntu-drivers-common
[15:59] <davmor2> xnox: as in the description of the driver goes off the page.
[15:59] <xnox> davmor2: all i need to know which packages you installed and if that resulted in working wifi.
[16:00] <davmor2> xnox: this is a binary driver
[16:00] <xnox> davmor2: i still do not understand what it means "goes off the page"
[16:00] <xnox> davmor2: from ubuntu archive?
[16:00] <xnox> davmor2: if it's not from ubuntu archive, it will _not_ persist to the installed system.
[16:00] <davmor2> xnox: stop
[16:01] <xnox> we have support for installing binary wifi drivers, but the package might not declare correct metadata. hence i need the card in question (which you did give me via pastebin) and the package names which resolve it.
[16:01] <davmor2> xnox: I open Software & Update I goto Additional drivers.  The box that lists the driver is too small for the name of the driver  So I see "broadcom 802.11 Linux STA wireless driver source from bcmwl-kern"
[16:02] <xnox> then i can verify if it's done correctly in the installer or not.
[16:02] <xnox> davmor2: ok, i see now. thanks. let me see what i can verify from that.
[16:03] <davmor2> xnox: let me write a bug with steps to reproduce and I'll add it too ubiquity now and then you can move after.
[16:04] <xnox> davmor2: ack, thanks.
[16:17] <balloons> knome, elfy xubuntu has some cool new stuff! Pretty slick. I'll have to try it
[16:22] <davmor2> xnox: bug 1308640  let me know if it makes sense
[16:22] <ubot5> bug 1308640 in ubiquity (Ubuntu) "Issue installing wifi if you have installed it in the live session" [Undecided,New] https://launchpad.net/bugs/1308640
=== bfiller is now known as bfiller_afk
[16:29] <psionikangel> Any autopilot test writers in here I could run a couples question by? I'm kind of stuck working with the autopilot visualisation of the introspection tree
[16:29] <balloons> psionikangel, sure thing, shoot
[16:29] <balloons> also, note there is a #ubuntu-autopilot channel as well :-)
=== maclin__ is now known as maclin
=== psivaa_ is now known as psivaa
[16:49] <elfy> balloons: it does that - they've all worked hard both to get stuff done and to stop me complaining :)
[16:49] <elfy> it's been a good but hard cycle
=== alex_abreu is now known as alex-abreu
[17:26] <Dj_Quality> Hello! It's the very first time I'm trying to perform a QA testcase (Desktop Upgrade -> Upgrade of type Mandatory) and I receive an error message 'An unresolvable problem occurred while calculating the upgrade.', but I'm not sure if I should use the command 'ubuntu-bug ubuntu-release-upgrader-core' to file a bug, because the first possible cause is met 'Upgrading to a pre-release version of Ubuntu'.
[17:26] <Dj_Quality> I've tried to remove  all Unofficial software packages not provided by Ubuntu, but I still receive this error message.
[17:29] <Dj_Quality> Upgrade tested from Ubuntu 13.10 (production release).
[17:29] <robotfuel> jibel ^ balloons ^
[17:30] <balloons> Dj_Quality, nice find.. are you saying you are not able to file a bug for it? There is a package which the upgrader can't transition and it would be interesting to see what that is
[17:31] <Dj_Quality> I think that I should be able to file the bug... I was unsure if I had to...
[17:32] <robotfuel> balloons: I think he is asking how to file the bug ie ubuntu-bug <package name here>
[17:37] <jibel> Dj_Quality, yes please file a bug and give me the bug number.
[17:38] <jibel> Dj_Quality, from the system with the problem, open a terminal and run the command: ubuntu-bug ubuntu-release-upgrader-core
=== roadmr is now known as roadmr_afk
[17:38] <Dj_Quality> I'm doing it at the moment, but I reading 1307904. I may be facing this exact problem. I'm checking that at the moment...
[17:38] <jibel> You'll need a launchpad account
[17:39] <Dj_Quality> I've got one.
[17:39] <jibel> Dj_Quality, this is a generic error message that can due to lot of different causes
[17:43] <Dj_Quality> Here comes the bug number : #1308657
[17:44] <Dj_Quality> Can this be due to the fact I've already made an upgrade in the past?
[17:49] <knome> balloons, soon you'll notice using it daily ;)
[17:49] <balloons> make me a link bugbot, bug 1308657
[17:49] <ubot5> bug 1308657 in ubuntu-release-upgrader (Ubuntu) "Ubuntu 13.10 to 14.04 desktop upgrade mandatory testcase failed with message 'An unresolvable problem occurred while calculating the upgrade.'" [Undecided,New] https://launchpad.net/bugs/1308657
[17:50] <balloons> Dj_Quality, what do you mean made an upgrade in the past?
[17:52] <balloons> Dj_Quality, from what I see you are upgrading from precise install, but you were on saucy
[17:53] <balloons> Dj_Quality, so you couldn't upgrade ubuntu-desktop meta package, which is bad :-)
[17:54] <Dj_Quality> On the machine on which I've performed the upgrade testcase, I've made successive upgrades in the past (from precise to quantal, then from quantal to raring, then from raring to saucy).
[17:54] <balloons> Dj_Quality, do you have ppa's for anything?
[17:54] <balloons> I see only wine ppa..
[17:55] <balloons> and phablet tools.. nothing that should cause issues
[17:55] <balloons> Dj_Quality, nothing wrong with going through multiple upgrades, it should work
=== psivaa is now known as psivaa-afk
[17:56] <Dj_Quality> balloons, I also have several private-ppas for software bought via Software center
[17:57] <balloons> Dj_Quality, right, which is no worries. I was thinking in regards to core desktop stuff
[17:57] <Dj_Quality> No, nothing
[17:58] <Dj_Quality> I have a few other repos, but none in regards to core desktop stuff, I think (videlan, virtualbox, steam, ...)
[18:00] <Dj_Quality> balloons, videolan*
[18:07] <jibel> Dj_Quality, it seems to be a real issue in the upgrade of libsmbclient and its new dependency in trusty samba-libs
[18:07] <jibel> Dj_Quality, I'll have to investigate more
[18:07] <phillw> ouch...
[18:08] <Dj_Quality> Ok, thank you!
[18:09] <balloons> jibel, any harm in confirming this by removing the package and retrying the upgrade? We have the logs now
[18:10] <jibel> balloons, removing libsmbclient will also remove core packages like software-center and ubuntu-desktop
[18:10] <jibel> I'm checking what is holding it back
[18:11] <Dj_Quality> ouch
[18:11] <jibel> maybe a third party package
[18:11] <balloons> jibel, ahh right you are
[18:12] <balloons> python-smbc?
[18:12] <davmor2> jibel: I see 16.1 has landed are these the images that are safe to test starting with the OEM in languages I guess?
[18:12] <jibel> davmor2, be careful the tracker is lying
[18:13] <jibel> davmor2, images are only available from pending/ not current/
[18:13] <jibel> http://cdimage.ubuntu.com/daily-live/current/ only have 16 for mac
[18:14] <davmor2> jibel: in that case I'll wait a bit and carry on breaking the phone :)
[18:14] <balloons> jibel I see python-smbc being held back, depending on an older version of libsmbclient.. or I'm reading it wrong
[18:14] <Dj_Quality> Don't know if it may be helpful, but I forgot to mention that I also have vmware workstation 10.0.1 on that machine...
[18:15] <balloons> but i don't see the same dependency requirement listed on the package, so color me confused :-)
[18:15] <jibel> balloons, this is the wrong part http://paste.ubuntu.com/7262928/
[18:16] <jibel> something's holding back python
[18:16] <balloons> hehe, markdelete python.. not so good
[18:19] <jibel> Dj_Quality, your system is 64bit, right?
[18:19] <Dj_Quality> jibel, Yes, exactly
[18:20] <jibel> Dj_Quality, I think it's a bug in apt, it's confused by multiarch because you have libsmbclient:i386 installed it tries to upgrade all the i386 stack and fails
[18:21] <jibel> Dj_Quality, I'll need to wait for the grand master of apt called mvo
[18:22] <jibel> libsmbclient 2:3.6.18-1ubuntu3.2 0
[18:22] <jibel> libsmbclient:i386 2:3.6.18-1ubuntu3.2 0
[18:22] <jibel> are the versions installed on your system
[18:22] <Dj_Quality> yes
[18:23] <jibel> Dj_Quality, if you try to uninstall libsmbclient:i386 what other packages does it try to remove? (don't remove anything, it is just to know what pulled it onto your sysmte)
[18:23] <Dj_Quality> no,
[18:23] <Dj_Quality> I've just tested it in synaptics
[18:23] <jibel> run: sudo apt-get autoremove libsmbclient:i386 and paste the output
=== roadmr_afk is now known as roadmr
[18:25] <Dj_Quality> jibel, packages to remove : libsmbclient:i386 libtalloc2:i386 libtevent0:i386 libwbclient0:i386
[18:25] <jibel> Dj_Quality, okay, so it is probably safe to uninstall, then try the upgrade again
[18:25] <Dj_Quality> ok
[18:29] <Dj_Quality> jibel, I'm retrying to upgrade now
[18:31] <balloons> elfy, I think we should change the screenreader testcase to use tab instead of arrow keys
[18:32] <Dj_Quality> You're uninstall workaround seems to work like a charm, jibel! I'm downloading new packages now!
[18:32] <elfy> balloons: ok - but without looking for it to read it I'd have no idea
[18:32] <jibel> Dj_Quality, Good, glad it helped. I'll update and confirm your bug report. Thanks for reporting it.
[18:33] <elfy> balloons: also we need to relook at upgrade testcase wording again
[18:33] <balloons> elfy, trying it now, it's better than it was, but there's still some missing pieces
[18:33] <Dj_Quality> You're welcome! Thanks to all of you for making such a good job!
[18:33] <balloons> elfy, ohh, what else with upgrades?
[18:33] <elfy> balloons: not upgrades themselves - panic ye not :)
[18:34] <balloons> ty Dj_Quality and jibel :-)
[18:35] <elfy> balloons: bug 1306221
[18:35] <ubot5> bug 1306221 in Ubuntu Manual Tests "Upgrade testcase written poorly" [Undecided,Fix committed] https://launchpad.net/bugs/1306221
[18:36] <balloons> elfy, I thought we took care of all that.. do I need to look again, lol?
[18:37] <elfy> afraid so - I did the broken command - but the bug is about more than that - check my last comment
[18:39] <elfy> balloons: but it will have to wait anyway - not mucking about with upgrades testcases now
[18:39] <balloons> I see the 4 scenarios and agree. I guess we'll muddle with them after to make it clear
[18:39] <elfy> yep
=== bfiller_afk is now known as bfiller
[18:39] <balloons> the funny part is we won't know if we've got it right till 16.04
[18:40] <elfy> anyway - screenreader - what testcase is it?
[18:40] <balloons> 1309
[18:40] <elfy> balloons: indeed :p - no rush now :D
[18:41] <elfy> oh - that one
[18:41] <balloons> yes, I guess I can file a bug
[18:42] <elfy> that'll take some checking - can look at it soonish
[18:42] <balloons> don't need to restart twice, step 32 is a bit off
[18:42] <balloons> and should check that screen-reader starts upon boot properly
[18:42] <balloons> it did for me, which is ;-)(
[18:42] <balloons> let me file a bug
[18:43] <elfy> ok - thanks - assign me to it - I'll look asap
[18:47] <balloons> https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1308687
[18:47] <ubot5> Ubuntu bug 1308687 in Ubuntu Manual Tests "Screenreader Testcase needs updating" [Undecided,New]
[18:51] <elfy> balloons: cheers
[18:51] <davmor2> I gave in and got them from pending now to start up the engines
[18:51] <balloons> aloha Letozaf_
[18:51] <balloons> happy release week to you!
[18:52] <Letozaf_> balloons, aloha, happy release week to you too :D
[18:53] <jibel> davmor2, I'm doing an oem nonenglish install
[18:54] <davmor2> jibel: i386, amd64 or both?
[18:54] <jibel> davmor2, amd64
[18:54] <davmor2> jibel: I'll do the same on mac
[18:59] <Letozaf_> balloons, hah! I picked the same exact test you are testing too :P... I better change and run another one :P
[18:59] <balloons> Letozaf_, lol
[18:59] <Letozaf_> balloons, :D
[19:46] <balloons> jibel, I still see this bug: https://bugs.launchpad.net/ubuntu/+source/localechooser/+bug/1307983
[19:46] <ubot5> Ubuntu bug 1307983 in ubiquity (Ubuntu Precise) "System not localized after an OEM or offline installation" [High,Confirmed]
[19:47] <jibel> balloons, it's partially fixed
[19:47] <jibel> i'm adding a comment
[19:49] <balloons> jibel, ack
[19:52] <davmor2> jibel: Meh I can't login
[19:53] <jibel> davmor2, how did you do that?
[19:53] <davmor2> jibel: I did English OEM French User setup on i386 with the password of 1 and it doesn't accept it
[19:55] <davmor2> jibel: I'll re-try it and confirm an then bug it
[19:57] <jibel> k
[19:58] <davmor2> jibel: I ofcourse completely blame the french keyboard layout ;)
[19:58] <jibel> davmor2, haha, yeah, French user over an English OEM, it cannot work :)
[20:04] <davmor2> jibel: okay so there are 2 things number one it selects Guest by default that seems wrong, secondly a french user with the password of 1 is still failing.  I have a mad idea though
[20:05] <jibel> davmor2, I confirm guest by default but didn't file a bug. I didn't try 'password of 1'
[20:05] <davmor2> jibel: Username a password 1 whose gonna hack that
[20:08] <davmor2> jibel: okay so if I ctrl+alt+F1 I can login,  With Q 1 (french keyboard putting all the wrong keys in all the wrong places ;) )  So I think it genuinely is a screw up with keyboard layouts in lightdm,  Maybe it is expecting A 1 not Q1
[20:10] <davmor2> jibel: okay so reboot and now it accepts the password no issues
[20:10] <jibel> balloons, why did you mark http://iso.qa.ubuntu.com/qatracker/milestones/314/builds/66906/testcases/1314/results failed? it is only in OEM mode otherwise it's working, right?
[20:11] <balloons> jibel, I noticed your bug used German as well.. I tried a German install and it was not localized
[20:11] <balloons> I assumed you would do french so I picked german :-)
[20:11] <balloons> jibel, ohh, no sorry I didn't notice.. no this was NOT an oem install
[20:12] <balloons> it was an offline install
[20:12] <davmor2> balloons: so I am doing a French OEM on another system and the password dialogue box is in english
[20:12] <balloons> jibel, the bug mentions either or
[20:12] <jibel> balloons, it is not localized in german or french because langpacks are not on this iso, try spanish or chinese
[20:12] <balloons> jibel, ohh really? I thought we put those back on
[20:13] <balloons> we're not constrained by space
[20:13] <jibel> balloons, after installation, when you connect to the network there is a notification to install missing langpacks
[20:13] <robotfuel> I am trying spanish on i386 now
[20:13] <jibel> balloons, I don't know I didn't follow which langpacks have been dropped/added and why
[20:13] <balloons> jibel, certainly the langpack box appears
[20:14] <jibel> I think at some point a decision as been made to drop languages in favor of chinese
[20:14] <jibel> has
[20:14] <balloons> I guess I'll ping release now -- is there a list for this image atm? I now it seems to change
[20:14] <robotfuel> It shouldn't list unsupported language packs.
[20:15] <jibel> balloons, the manifest says en, es and zh are on the iso
[20:16] <balloons> zh worked fine, I tested that
[20:17] <balloons> jibel, did we run through the other features test at some point? need a laptop for it
[20:17] <balloons> of which I don't have one capable to test
[20:18] <robotfuel> balloons: I have a pile of all kinds of laptops, what do you need?
[20:20] <davmor2> jibel: right French OEM is in English still, Installing a German User now
[20:21] <jibel> balloons, yes, I used my netbook
=== chihchun is now known as chihchun_afk
[20:22] <davmor2> jibel: same thing again going from french to german Invalid Password, please try again
[20:23] <davmor2> jibel: it's the number 1 it doesn't change damn it
[20:25] <jibel> davmor2, layouts are different between FR and DE, 1 is on the top (use shift) of the second key from the left of the 1rst row on a french keyboard, and bottom (without shift) on a german keyboard
[20:25] <davmor2> jibel: Yeah but the keypress isn't and it works on the cli just lightdm where it doesn't
[20:26] <davmor2> until you reboot
[20:28] <jibel> davmor2, ah, that might a bug I sometimes experienced, where the keyboard indicator says that active layout is FR (or whatever) but the actual layout is US.
[20:28] <jibel> I cannot reproduce it reliably
[20:28] <davmor2> jibel: I can now :)
[20:29] <davmor2> jibel: 3 machine 3 different layout 3 breakages
[20:31] <davmor2> Wow I can understand Home, Desktop, Recent, Trash, Computer, Browse Network and Connect to Server.  My german is either much better than I gave it credit for or these words in Nautilus are all English
[20:31] <jibel> davmor2, can you report a bug, and notify ubuntu-release
[20:31] <jibel> for the keyboard issue I mean
[20:32] <davmor2> jibel: sure what do I file against is it the indicator or ubiquity?
[20:33] <jibel> davmor2, by default ubiquity, so it'll contain the logs, and it'll be reassigned after analysis
[20:33] <davmor2> no worries
[20:38] <davmor2> jibel: Man I thought the French Keyboard Layout was Weird I take it back, German is even weirder :)
=== Ursinha is now known as Ursinha-afk
[20:47] <jibel> davmor2, I still cannot reproduce, I'm interested if you have a reliable way to do it
[20:48] <phillw> davmor2: can you post up the bug number when you get it logged. I have a french and german tester willing to confirm what the problem is.
=== Ursinha-afk is now known as Ursinha
[20:48] <davmor2> bug 1308752
[20:48] <ubot5> bug 1308752 in ubiquity (Ubuntu) "Oem install Login fails on first reboot to user when different keyboard layouts are used" [Undecided,New] https://launchpad.net/bugs/1308752
[20:50] <balloons> interesting, thus far easy install isn't working for me on ubuntu
[20:50] <balloons> max didn't have good luck either
[20:51] <Dj_Quality> jibel, the upgrade has completed successfully with your workaroud. I've filled in testcases. Thanks again for your help!
[20:51]  * jibel thinks we need more automated case, let them run all night, while I'm in my bed
[20:51] <jibel> Dj_Quality, you're welcome
[20:52] <robotfuel> jibel: how do I get a hardware profile? do I just leave that blank?
[20:52] <jibel> robotfuel, blank or a link to a wiki page
[20:52] <balloons> robotfuel, check the link at the top of the page
[20:52] <jibel> that's just free text
[20:53] <balloons> there's nice little links at the top: http://iso.qa.ubuntu.com/
[20:53]  * balloons feels no one reads anything anymore, hah!
[20:53]  * elfy doesn't bother with hardware profile
[20:53] <balloons> I also don't bother, but the info is there.. discoverable, I hope?
[20:53] <Dj_Quality> I've used : hardinfo -ram devices.so|sed '/\*\*\*\*\*\*\*/,/\*\*\*\*\*\*\*/d'|pastebinit|clipit -c
[20:54] <elfy> balloons: talking of reading - I read a bug about the history in iso.qa - I read it everytime my browser hangs while trying to get history :(
[20:54] <Dj_Quality> elfy, after sudo apt-get install hardinfo pastebinit clipit
[20:54] <jibel> I never saw these links =)
[20:54] <knome> if only the tracker was written in php... i would have fixed all of elfy's bugs
[20:54] <elfy> :)
[20:54] <davmor2> balloons: you do have the right image right the one from pending or has it moved across now?
[20:54] <balloons> knome, nice!
[20:54] <knome> wait, i think it is...
[20:55] <elfy> ahah - xubuntu is in channel hassling balloons :p
[20:55] <jibel> knome, php it is
[20:55] <knome> but it's drupal :|
[20:55] <knome> i'm just reeeally at loss with that
=== salem_ is now known as _salem
[20:55] <elfy> excellent - knome can fix all my bugs now :)
[20:55] <knome> heh
[20:55] <balloons> I'd prefer a static site.. just re-generate it and push... ohh, or cgi!
[20:55] <knome> well i'll definitely have more time for them after tomorrow ;)
[20:55] <knome> cgi? perl?
[20:55] <balloons> ohh yea!
[20:55]  * knome facepalms
[20:56] <balloons> aren't we talking about nonsensical things?
[20:56] <knome> balloons, the qa tracker?
[20:56] <jibel> balloons, a google spreadsheet :P
[20:56] <balloons> jibel, history would be repeating itself there
[20:57] <elfy> and mybrowser would crash again
[20:57] <balloons> brb
[20:57] <elfy> balloons must be checking some iso history ...
[20:57] <elfy> seen in 30 minutes
=== Ursinha is now known as Ursinha-afk
[21:00] <jibel> davmor2, did you quickly check that the rebuild didn't bust amd64+mac images and its still bootable?
[21:01] <davmor2> jibel: I've done the OEM install on i386, mac and amd 64, I'm just crap at multi-multitasking I'll be filling in the results any second
[21:02] <jibel> davmor2, awesome!
=== psivaa-afk is now known as psivaa
[21:06] <davmor2> jibel: of course it doesn't help that there is no OEM option for mac,  Like Apple wouldn't ship Ubuntu right :D
[21:07] <jibel> davmor2, Oh you're right, there might be a business opportunity there =)
[21:12] <balloons> ugh vmware player destroyed my pc
[21:12] <balloons> and indeed easy install does not seem to work
=== Ursinha-afk is now known as Ursinha
[21:18] <robotfuel> jibel: balloons is there a bug open for the incomplete language support message that pops up that you know of after installing in spanish?
[21:18] <balloons> robotfuel, is it localized?
[21:18] <robotfuel> yes
[21:18] <jibel> robotfuel, yes there is one for english I believe
[21:18] <balloons> the popup is fine
[21:18] <robotfuel> ok
[21:18] <robotfuel> thanks
[21:19] <davmor2> balloons: you spelt virtualbox wrong ;)
[21:22] <balloons> davmor2, vbox? :-)
[21:23] <davmor2> balloons: :D
[21:31] <elopio> balloons: could you run reminders on your phone?
[21:31] <balloons> from trunk or your branch?
[21:33] <elopio> balloons: anyone would be good. My phone is running clock tests so I can't use it.
[21:33] <elopio> https://code.launchpad.net/~elopio/reminders-app/test_go_to_accounts2/+merge/214163
[21:33] <elopio> balloons: if you could run ^ it would be great.
[21:35] <balloons> elopio, yes I will do it now
[21:38] <balloons> elopio, building now
[21:42] <balloons> elopio, still seeing "  Unknown CMake command "qt5_use_modules"."
[21:57] <elopio> balloons: :/
[21:57] <elopio> dpm should know more, but I haven't seen him.
[21:57] <balloons> elopio, installing the entire sdk in my chroot
[21:57] <balloons> we'll see what's missing
[21:59] <elopio> balloons: I'm about to leave my computer running the toolkit tests, so
[21:59] <elopio> http://xkcd.com/303/
[21:59] <elopio> I'll be back later.
[21:59] <balloons> hah
[22:46] <balloons> elopio, installing ubuntu-sdk meta package lets me build reminders now :-)
[22:46] <balloons> not sure which piece was missing, but the meta got it ;-)
[22:47] <balloons> I suppose you could have done a build-dep install too