=== chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [14:26] anyone can have a look at https://code.launchpad.net/~aacid/autopilot/precreate_keyboard15/+merge/254209 and https://code.launchpad.net/~timo-jyrinki/autopilot/ap1.5_dbus_search_no_seen_connections/+merge/254200 ? === daz_ is now known as dazza5000 [14:33] tsdgeos, best to ask on #ubuntu-autopilot. That said, it's late for the nz guys [14:42] k === alex-abreu is now known as alex-abreu|doc [16:11] ubuntu-qa, perhaps pitti? I'm trying to figure out how to best recommend using libgtest. Do I put it in the cmake file and have cmake pull it, perhaps like http://paste.ubuntu.com/10689076/. Or do I install the libgtest-dev package and manually compile and copy the libs to /usr/lib? [16:11] balloons, good q, would you be willing to work from an example? [16:12] balloons: I'd use the packaged version; in many environments you don't even have internet access [16:12] balloons, IIRC it's not built in the archive b/c of some symbol magic [16:12] pitti, balloons let me pull up an example [16:15] balloons, I'm going to bounce this to charles actually, looking at indicator-datetime [16:15] alesage, happy to work from an example. I like using the package, and currently that's what I've recommended. What I don't like is manually copying into /usr/lib, or the fact I must self-compile [16:15] pitti, good point about internet access.. it's a fragile dependency [16:18] balloons, just looking to compare how unity8 is doing it, one sec [16:22] balloons, right so in indicator-datetime we're not using those 'external' macros http://paste.ubuntu.com/10689882/ [16:24] balloons, and then those DIR vars are set in the base CMakeLists.txt to the debian-installed locations http://paste.ubuntu.com/10689892/ [16:28] balloons, pitti more background http://askubuntu.com/questions/145887/why-no-library-files-installed-for-google-test https://code.google.com/p/googletest/wiki/FAQ#Why_is_it_not_recommended_to_install_a_pre-compiled_copy_of_Goog [16:28] (for balloons' blog post ;) ) [16:29] alesage, :-) So is your example using the -dev package, but compiling it as part of the cmake build? [16:29] I see GTEST_SOURCE_DIR, but I don't see the definition [16:29] balloons, yes [16:30] alesage, that seems sane.. You have the full project source for viewing? [16:30] balloons, GTEST_SOURCE_DIR is defined in the root CMakeLists.txt, http://paste.ubuntu.com/10689892/ [16:30] balloons, this is all in lp:indicator-datetime, yes [16:31] gotcha [16:31] charles will be flattered if you use it as an example ;) [16:31] alesage, :-) I reserve the right to ask questions as well. Trying to keep cmake simple enough for us lesser folks to grok [16:31] but yea, this looks like what we want [16:32] balloons, great, yes I was new to it too, yes these native macros are better === alex-abreu|doc is now known as alex-abreu [19:46] hey guys, have 2 minor issues with 15.04 beta2. one is an installer issue. the other is a very minor (as in, nitpicky) issue at login. Should these be launchpad issues? [19:46] technically, it's 3 issues, but I suspect 2 of them are related. [19:47] have you looked to see if they're known? [19:47] yes, they don't appear to be. [19:47] if they're bugs then LP is the place yep [19:47] I'll doublecheck, of course. Was just more curious if launchpad is the correct place, or since it's a beta2, if there is another tracker. [19:48] ok, thanks. [19:48] things get put ON the image tracker [19:48] but they have to be bugs in the first place [19:48] I'd be interested to know what the installer one is [19:48] the others not so much - assuming Ubuntu [19:48] understood. so I report it on LP. then one of the ubuntu team decides if it gets escalated to image tracker [19:49] no not at all :) [19:50] 'people' test images - they report on the tracker [19:50] breifly, I'm installing on a 2013 macbook pro, retina. It looks like each of the screens is a seperate "pane" and part of it is extended below the bottom of the screen, so you can't see it. Originally, I thought it hung there indefinately, and I couldn't move it with my mouse. [19:50] if they find a bug - they can report that - and can also report it on the tracker [19:51] jpalmer: well I've not seen reference to anything like that for sure :) [19:51] on a second install attempt, I decided to move the "pane" before the hang point. then I noticed it is actually popping up a wanring about UEFI mode. and you have to click a button to continue. so, you can't see it unless you move the pane, and.. you can't move the pane after it's "displayed" [19:51] at a guess I would expect people to want to know that one [19:52] the other (and probably related) issue with the installer, is that same UEFI prompt pops up like 4 different times during the process. once seems sufficient. hehe [19:52] :) [19:52] yep, my thoughts exactly. 'Tis why I'm asking about the LP ;) [19:52] yep - understood [19:52] thanks for the info. I'll create an LP account now. [19:52] I'd not know what to report that against though [19:53] question, is "pane" the right way to describe that... panel? or is there a better/more descriptive name? [19:53] someone from qa-team might have more idea [19:53] window maybe [19:53] have any particular monsters I can poke? assuming they IRC? [19:54] well I pinged the qa team - if anyone's awake [19:54] If LP can accept pictures, I'll reinstall, and get some with my cell. [19:54] oh, thanks. [19:54] and others read the channel [19:54] jpalmer: you can add screenshots, images etc as attachments to bugs yep [19:57] perfect. In that case, I may hold off until I get home tonight, and get some photos of the install process. [19:57] thanks for the info, elfy [19:59] oh, hrm.. I may not get that wanring again. because I previously had 14.10 installed in bios campatibility mode. so, I may need to reinstall *that* first, to force the prompt/dialogue [20:04] well ... just make the best attempt at describing it I would say [20:04] I'd not, unless you really want to, go backwards now [20:05] I am not clear on if it is just the boot drive that needs to be uefi formated or can your still have /home on an mbr drive? [20:05] not_roasted: an elf? [20:05] oops [20:06] O_O [20:07] it could be worse, could be roasted: an elf? [20:25] elfy: 1437482 [20:25] bug 1437482 [20:26] bug 1437482 in xorg (Ubuntu) "Installer issue" [Undecided,New] https://launchpad.net/bugs/1437482 [20:26] if a QA person wakes up, and I'm not around, you can point them at that. I'll keep an eye on it if they need more info. and as I said, I'll add pictures in about 2 hours. [20:27] reading that it seems that by 'pane' you mean the steps during install [20:28] I'd expect that the package will get changed - but reporting is a good first step [20:28] yeah, I really don't know how to describe them. each "step during install" repopulates to the bottom right corner of the screen, and you have to redrage the.. modal? back up. [20:29] the pictures should explain it better. I hope. [20:30] I'm actually talking about the window that the "step during install" is redrawn onto. [20:30] you get more than one of those? [20:31] if you're talking about what I think you are then 'windows during install' would perhaps make sense [20:35] yeah, that UEFI warning/prompt pops up like 4 times. [20:36] on a whim, I just installed it on a VM.. and it's certainly different there. you don't see the screen I'm talking about, at all. [20:47] ok, I decided to take photos now with my crappy cellphone, and upload them. hopefully now it makes sense ;) [20:50] thanks again elfy. going to fight some traffic now. will post the other bug once I get home. [20:51] drive safe then - and obviously you're welcome :)