[09:39] hello [12:17] Is Tim Lunn available on IRC? [14:25] popey, should the "Unity overlay hiding" task not be removed as the bug is set to "Fix Realesed" on Launchpad? http://pad.lv/1075207 [14:25] Launchpad bug 1075207 in Ayatana Design "[regression] Shortcut overlay does not hide when modifier key is pressed" [High,Fix committed] [14:33] hey, I'm trying to run the messaging-app using qmlscene but I keep getting the error that Ubuntu.* is not installed [14:34] Including Ubuntu.Components, Ubuntu.History, Ubuntu.Telephony [14:34] Does anybody know how I can fix this? [14:34] Nothing I've found on stack overflow or askUbuntu has worked [14:44] Also, can nyone tell me how to open the messaging-app as a project? There isn't a .qmlproject file or any other project file that the ubuntu sdk can open. [14:46] fazer, the messaging app has a CMake file that QtC should be able to open http://bazaar.launchpad.net/~phablet-team/messaging-app/trunk/view/head:/src/CMakeLists.txt [14:47] fazer, and things like Ubuntu.Components should have come with the SDK, unless you are running 1.2 rather than 1.3 or something ? [14:47] oh ok. [14:47] fazer, you may have to manually install cmake from the repos first though IIRC [14:51] I just updated ubuntu-sdk and checked the version, it gives me a whole lot of informtation about qt creator and otherstuff, but doesn't give me a version number. Also, I still get the same error. [14:51] fazer, what is the specific error it outputs? [14:52] ahayzen, http://paste.ubuntu.com/14281891/ [14:52] fazer, ah so Ubuntu.Components is ok? [14:53] fazer, you are probably missing the history and telephony from this list http://bazaar.launchpad.net/~phablet-team/messaging-app/trunk/view/head:/debian/control#L5 [14:53] for the messaging-app.qml file it seems. But for other files I had attempted to run earlier, Ubuntu.Components wasn't installed. May not have been messaging-app, but I remember gettign the error earlier. [14:54] fazer, you may be able to simply run $ sudo apt-get build-dep messaging-app if the messaging-app is in your repo [14:54] ok, I'll try [14:55] fazer, if it doesn't then just manually install the ones listed from lines 5->27 [14:56] ahayzen, ok cool. It works now. [14:56] thanks. [14:56] \o/ [14:56] no problem [15:34] ahayzen, what arguments should I use when opening the project using the CMake file? [15:34] fazer, what do you mean by arguments? [15:35] usually you can just point QtCreator to open the CMakeLists.txt file directly [15:35] (that's what I do with the music-app) [15:35] when I try to open the project using the cmake file in qt creator it opens up this cmake wizard asking for arguments and a generator [15:35] oh just hit "run" [15:35] or "Run CMake" or whatever it is [15:36] if I leave the arguments blank then I get an error. [15:36] hmm whats the output [15:36] ? [15:37] http://paste.ubuntu.com/14282601/ [15:37] This is the log file [15:38] fazer, does it tell you which bit is wrong? [15:38] ahayzen, this is what it says in the wizard: http://paste.ubuntu.com/14282622/ [15:39] ya it's the qt5_use_modules command and something in the cmake file [15:39] ah [15:39] hmm [15:40] fazer, i'm not sure about that, you'd probably have to ask one of the messaging-app developers what they do [15:40] ok thanks [15:41] fazer, which CMakeLists are you opening? [15:41] the one in the src dir [15:41] as there are quite a few, try using the one in the root instead [15:42] ok [15:42] it worked! Thanks [15:44] fazer, sweet \o/ [15:47] Does anybody know Tiago Salem Herrmann's nickname? [15:48] Is it tiagosh? [16:54] Hi [16:57] I have participated in Google code in 2015 and performed one of the tasks of Ubuntu I.e create new Wallpapers but [16:58] but one of the mentors is either not replying nor reviewing my project Tim Lunn Inoki [16:58] Please Help [16:59] Basar, how long have you had it submitted? He's probally sleeping [16:59] I has been 8.5 hours [17:00] Basar, I'd wait atleast 24 - most of the mentors have full time jobs from what I can gather [17:00] So how long I have to wait [17:01] It is taking a lot of time [17:01] and as a student I find it difficult [17:01] Depends on the person, they've got alot of work to checkout so just be patient, probally won't take more than 24 hours [17:02] You cannot make it fast so I could work on further tasks [17:02] I know he has different time zone [17:03] There's no reason you can't start another task while you wait [17:03] So,,,,,,,hmmmm OK I wait [17:03] thanks for ur suppor [17:03] #t [17:04] your welcome, least I can do :) [17:04] thanks [17:04] I will wait for tomorrow [17:05] Can u tell me what time zone Tim sir has [17:06] So can u reply [17:07] ........ [17:07] Basar, no clue [17:08] So how can u say that he must be sleeping [17:08] Basar, "probally" - that was my guess. [17:09] ok [17:12] OK bye Thanks for ur full support and sorry for inconvenience regretted(if) [17:13] I [17:49] Hello, I am installing Ubuntu for my first Google Code-in task. The task states to install the latest LTS or current development branch which will become the next LTS release. Does this mean I can install Ubuntu 15.10 or do I have to install one of the daily development builds? [17:50] mattpdl: that would mean either 14.04 or Xenial daily [17:50] Alright, thank you for your fast response. [19:26] wxl: can you look at the mkusb task? I don't know much about it... [19:26] already on it tsimonq2 thank you! [19:26] wxl: sorry :) [20:10] Hi, I am installing Ubuntu for Google Code-in. The description of the task says to "Write a complete description of installation of ubuntu using screenshots and tell us what version of ubuntu you installed and why." I have a couple of questions about this. What is a "complete description," length-wise? Also, what format should I submit it in? [20:11] mattpdl: hello and thanks for your contributions :) [20:11] mattpdl: "complete description" would probably best be described as a step by step. no particular length required, but be detailed [20:12] mattpdl: regarding format, i would suggest an open format like open document format or just text, but this is relatively unimportant as long as we can open it with libreoffice at worst :) [20:13] Ok, thank you for your fast response. [20:13] no problem. i'm not a mentor for that particular task, but am familiar with it and can help you out as needed [23:45] Anyone, If a bug can no longer be reproduced should the status be changed to 'Fix Released' or 'Invalid'? [23:46] fazer: i think some people have different philosophies on that. i am of the mind to make it 'incomplete' with a note that more information would be needed [23:46] balloons, will there be anymore autopilot test writing tasks? [23:47] i think 'fix released' sounds more like someone actually went out of their way to fix the bug which may be assuming too much :) [23:47] wxl, what if the specific version of ubuntu is specified? And it cannot be reproduced on the later versions? [23:47] fazer: there' [23:47] oops [23:47] there's still the possibility it might relate to some specific hardware or something. it's still a potentially valid bug [23:47] the nice thing about making them incomplete is that they will expire if no one provides any further info [23:48] fazer: do note that 'invalid' is for non-bugs, like support issues or the like [23:48] ok then. I guess that'll be what I do. [23:48] fazer: i say this as a member of the bug control team, but if you wish to inquire with others on the team for a second opinion, try #ubuntu-bugs [23:49] ok cool. I'll check there too. [23:49] fazer, this is also a good reference for bug statuses :-) https://wiki.ubuntu.com/Bugs/Bug%20statuses [23:50] wxl: since a bug is only confirmed after 2 people report that it affects them, is the same true for when a bug is no longer reproducible? [23:50] just wondering [23:50] adueppen: yes [23:50] wxl: cool