[00:10] <mhall119> Guest42302: the 2013 N7 isn't supported yet, no
[00:11] <mhall119> I'm not sure if anybody at XDA has built an image for it yet
[00:15] <Guest42302> ok, thanks
[00:33] <slide-guy> Hello is there a way to slide in from the side to reveal the launcher with regular ubuntu? does ubuntu touch have an iso i can make a live image with. Using an dell inspiron 15 7000
[00:39] <mhall119> slide-guy: you can auto-hide the launcher on the desktop,then pressing your mouse pointer against the edge will reveal it
[00:40] <slide-guy> but I want to use my touch screen :(
[00:40] <mhall119> slide-guy: Unity 8 (the Ubuntu touch shell) will have an testable session in 14.04's desktop ISO, but it's not there yet
[00:40] <slide-guy> cool :^)
[00:40] <mhall119> you can run Unity 8 in a windows right now, on your desktop, but not as the actual shell
[00:41] <slide-guy> is there a guide?
[00:41] <mhall119> http://unity.ubuntu.com/getinvolved/development/unity8/ has a guide to getting the code,compiling it and running it
[00:41] <slide-guy> cool thanks
[00:41] <mhall119> but if you just want to run it, I think there are packages to install in 13.10
[00:41] <slide-guy> true
[00:42] <mhall119> apt-get install unity8, I think that's all you need
[00:42] <mhall119> might need unity8-private and/or unity8-fake-env
[00:42] <slide-guy> can I do that in a live environment? I have a 16gb flash drive
[00:42] <mhall119> join #ubuntu-unity and ask in there for additional help
[00:42] <slide-guy> k
[00:45] <mhall119> running it I'm pretty sure
[00:45] <mhall119> don't know how compiling it would work out though
[02:01] <crocket> yop
[02:50] <shuduo> hello, where is right place to report bug for system-settings-touch? there is no 'report a bug' in lp:~system-settings-touch page
[04:06] <crocket> Will I see an ubuntu phone or tablet by April 2014?
[07:59] <dholbach> good morning
[08:52] <dholbach> didrocks, salut mon ami - do you know when the new ubuntu-system-image is going to land?
[08:53] <didrocks> dholbach: it should have landed, right? (2.0)
[08:53] <didrocks> I saw it was stalled in proposed for a long time
[08:54] <dholbach> didrocks, I couldn't find it in http://people.canonical.com/~j-lallement/touch/changes/
[08:54] <didrocks> dholbach: still in proposed indeed:  system-image-dbus | 2.0.2-0ubuntu1 | trusty-proposed/universe | all
[08:55] <didrocks> dholbach: I think we need barry to look at his packages to enter the release pocket :p
[08:55] <dholbach> ah ok :)
[08:55] <dholbach> thanks
[08:55] <dholbach> I'd like to help debug https://bugs.launchpad.net/ubuntu-system-image/+bug/1256229 - that's why I was asking
[08:56] <didrocks> dholbach: yeah, he reuploaded 2.0.2 apparently on Tuesday to fix a FTBFS (and that's why sytem-image was stalled for a week or two in proposed)
[08:56] <dholbach> it built yesterday, so can it be pulled in for the release now?
[08:56] <didrocks> autopkgtest for system-image 2.0.2-0ubuntu1: FAIL (Jenkins: public, private)
[08:56] <dholbach> oh ok
[08:56] <didrocks> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[08:57] <didrocks> dholbach: we really need to sensibilize people with upload rights to look at -proposed
[08:57] <didrocks> stuff are stalled for days and days sometimes
[08:58] <dholbach> didrocks, I don't know ... a short article on packaging.u.c? or is it on a wiki page already?
[08:59] <didrocks> dholbach: there is this excellent page: https://wiki.ubuntu.com/ProposedMigration
[09:01] <dholbach> didrocks, are mails sent out if something gets stuck in proposed?
[09:01] <didrocks> dholbach: I don't think so
[09:01] <dholbach> maybe it should be treated like a case of FTBFS
[09:02] <didrocks> dholbach: for autopkgtests failures, maybe yeah. For the other cases, like "no ready yet on <arch>", maybe that should be after a threshold time
[09:02] <didrocks> but I'm not a specialist ;)
[09:03] <dholbach> ok, I hope it's easy to fix, the test suite passed during the build
[09:04] <dholbach> I'll file a bug about the packaging guide anyway
[09:04] <dholbach> it'll be good to mention it
[09:04] <dholbach> and maybe we could have a session at the next UDW
[09:04] <dholbach> just so new developers know already know about it
[09:12] <didrocks> yeah ;)
[10:25] <Luclis> Bonjour ?
[10:26] <Oria> hi guy's, I'd like to up a problem on my mako. If you have a pin code with more than 4 digits it does'nt work.
[10:30] <mterry> Oria, we only support 4
[10:30] <mterry> Oria, oh
[10:30] <mterry> Oria, you mean with SIM?
[10:30] <Oria> yes mterry with sim
[10:30]  * mterry doesn't know much about how we handle SIM
[10:31] <mterry> Oria, sorry, I'm stuck in a world where PIN means login password, not SIM
[10:31] <Oria> ok :)
[10:32] <Luclis> Someone know if I can try it on my computer ?
[10:33] <Oria> mterry: why to limite
[10:33] <mterry> Oria, I don't know, I didn't do the SIM pin stuff
[10:35] <Oria> mterry: Is it possible to make a request to dev? Many people think it's a shame to limit to 4. Make a limit to 6 or more would be better?
[10:36] <mterry> mzanetti, did you do SIM pin stuff?   ^
[10:38] <mzanetti> mterry: yes
[10:38] <Luclis> Oria : maybe it's just a bug ; have you try with another SIM/phone ?
[10:40] <mzanetti> Oria: for SIM pin there is a fix coming in. for the phone lockscreen (not SIM PIN) it's a design decision to keep it to 4.
[10:40] <mzanetti> I'm not particularly happy with that
[10:40] <Oria> Luclis: I don't have another compatible phone or another SIM :)
[10:46] <Oria> ok mzanetti
[10:46] <Oria> To design, before security ... I find it illogical finally good in my opinion :)
[10:47] <mzanetti> Oria: well, if you want more you can use the passphrase one that gives you a full keyboard. but if you want to keep it to simple numbers, it's going to be limited to 4
[10:52] <raptor67782> hi
[10:53] <raptor67782> I would like to have  a LINUX phone, I was the home page of ubuntu touch, and it is insanely complicated to install ubuntu.
[10:53] <raptor67782> Haven't you a cdrom to install Linux directly from Windows 7?
[10:53] <raptor67782> (on the phone via usb cable)
[10:54] <pitti> a CD-ROM on a phone!?
[10:54] <raptor67782> Furthermore, the new phone arent compatible with ubuntu touch.
[10:54] <pitti> raptor67782: I'm afraid that doesn't work; unfortunately phones are quite a bit harder to install than desktops, but the phablet-flash tool makes this really easy and a single-command issue already?
[10:54] <raptor67782> no, you dont ujdersndatnd. I plug my phone on my windows ,and put in my cdrom ubuntutouch, and it installs it automatically.
[10:54] <raptor67782> I havent linux at all.
[10:55] <pitti> raptor67782: I think the honest answer is "nobody on our side is interested in doing it", and it would be loooots of work for very little gain
[10:55] <Oria> raptor67782: livecd
[10:55] <Oria> and phablet-flash
[10:56] <raptor67782> ah come on. too complicated
[10:56] <raptor67782> I regret but if users have to go through complicated processes, it will never work to get more interests.
[10:56] <raptor67782> It should be simple
[10:56] <pitti> it is simple
[10:57] <pitti> $ phablet-flash ubuntu-system
[10:57] <pitti> done
[10:57] <dadel> raptor67782, why do you want a linux on your phone?
[10:57] <raptor67782> You have windows xp or 7, you put your cdrom, and you install: SETUP NEXT...
[10:57] <raptor67782> dadel: linux is the future. Look Steam...
[10:57] <pitti> raptor67782: I'm afraid the people you are talking to here don't even have windows
[10:58]  * pitti hasn't had a windows box for 16 years
[10:58] <dadel> raptor67782, if you want the future now you may do some efforts
[10:58] <raptor67782> ha ha, really, you havent windows?
[10:58] <raptor67782> about 80 pct of machines are windows today.
[10:58] <dadel> you have a computer, you plug you liveCD, you run it, you launch the pitti command and it's done
[10:58] <pitti> I honestly tried to co-install it on my laptop, but it's way too big, and installing it is a royal pain, so I just gave up
[10:58] <raptor67782> world wide, about 5 - 10pct are linux
[10:59] <pitti> raptor67782: sure, I know the numbers; but that doesn't change the reason :)
[10:59] <dadel> it's not interesting to troll about that raptor67782 if you are happy with your win just stay with it
[10:59] <pitti> ^ fully agreed
[11:00] <dadel> i'm sure there are some #windows irc where you will find your happiness
[11:00] <raptor67782> thank you for your non-help :(
[11:00] <dadel> lol
[11:01] <pitti> well, we did tell you what the reason was and how to easily install an Ubuntu phone
[11:01] <pitti> *shrug*
[11:01] <raptor67782> Look https://wiki.ubuntu.com/Touch/Install    I have asked two shops
[11:02] <raptor67782> selling phones in my town, I printed this page, and they have looked and studied, and even them, have no single idea how to install ubuntutouch. so ...I mean. it means everth
[11:02] <raptor67782> g
[11:03] <davmor2> Morning all
[11:03] <dadel> i think that if you considere too complicated to run a liveCD to do so, you may wait that UbuntuTouch project is more advanced and propose windows installer
[11:03] <pitti> well, frankly this stuff is meant to be installed by OEMs (i. e. phone producers)
[11:04] <pitti> I would not ever expect a phone buyer or a shop to install and configure it
[11:04] <dadel> actually it is intended to linux users and courageous people not everybody
[11:04] <pitti> at this point this is very much a developer preview
[11:04] <dadel> the other users will be addressed when the project will be more mature
[11:05] <raptor67782> I would like a Linux phone. Today, which solution is available?
[11:05] <dadel> Android
[11:05] <dadel> is based on a Linux kernel
[11:05] <raptor67782> Android isnt a real linux
[11:05] <pitti> jolla
[11:05] <dadel> it's a Linux kernel
[11:05] <dadel> there is no real or false Linux
[11:06] <dadel> there are many distibutions
[11:06] <dadel> for every need
[11:06] <dadel> just take the one for you
[11:06] <raptor67782> Come on. Ubuntu is meant to be the best, so, why still no ubuntu on phones?
[11:06] <dadel> I think you should see android
[11:06] <dadel> there is no best
[11:07] <dadel> i use ubuntu/android/debian/raspbian/redhat
[11:07] <dadel> it depends on my needs and this is what I like in Linux worldf
[11:09] <dadel> good luck raptor67782 in your life that seems to be really complicated out of easy ways
[11:09] <raptor67782> I have an android tablet archos, but I have no idea how to install linux ubuntu on it
[11:10] <raptor67782> I am not working in informatic. Anytime
[11:11] <raptor67782> dadel: I do physics. I do regularly schrodinger equations. For me, it is simple, I could laugh trying to solve on. Furhtermore, physics pay well, probably better than a developer ;)
[11:11] <pitti> there is currently no ubuntu for the archos tablet
[11:11] <pitti> (only for the n7 and n10, and even these are only developer previews)
[11:12] <raptor67782> I didn't know, I shall try to sell it on ebay, to buy one compatible with ubuntu. Maybe for next year...
[11:20] <HCL> can i install ubuntu touch on  my HCL ME U-1
[11:23] <mzanetti> MacSlow: https://code.launchpad.net/~mzanetti/unity8/lockscreen-default-variable-pinlength/+merge/197848
[11:24] <mzanetti> MacSlow:  #ubuntu-unity btw?
[11:24] <MacSlow> mzanetti, on it
[11:37] <pitti> I'm about to write the first-ever automatic test for platform-api
[11:38] <pitti> any hints as to what our preferred C++ project test framework is? which of our projects would be a good example?
[11:38] <pitti> tvoss: ^ I think you might be able to answer this?
[11:39] <pitti> (it's also my first-ever C++ test, so bear with me..)
[11:39] <pitti> unless it's ok to write it using python3 unittest, which would make things a lot easier :)
[11:40] <tvoss> pitti, we use google test all over our projects
[11:40] <tvoss> pitti, let me find you a good example
[11:40]  * pitti looks at libgtest-dev
[11:41] <tvoss> pitti, http://bazaar.launchpad.net/~phablet-team/process-cpp/trunk/files/head:/tests/ has got a good overview, including the required CMake stuff
[11:43] <pitti> tvoss: nice and small, thanks!
[11:43] <tvoss> pitti, yup :) just let me know if you need anything else
[11:43] <pitti> tvoss: I guess gtest supports setup/teardown too, but I'll RTFM
[11:43] <pitti> tvoss: so "gtest" and "these examples" should be fine
[11:44] <tvoss> pitti, great. For setup/teardown: you probably want TEST_F(Fixture, ...), with you defining the Fixture and per-suite/per-case setup and teardown
[11:48] <pitti> right
[11:52] <t1mp> popey: did you say unlocking crashes your phone?
[11:52] <popey> it did earlier
[11:52] <t1mp> popey: does that mean it is not recommended for me to upgrade to the latest image now?
[11:52] <popey> uh, no, it was a one off
[11:52] <popey> and that wasn't latest, it was #47
[11:52] <popey> just updated to #48
[11:53] <t1mp> popey: ah, okay. Then I proceed with installing the new image :) thanks.
[11:57] <Laney> is there a way to know when the device was asleep?
[11:57] <Laney> https://wiki.ubuntu.com/Power#Phone asks for it
[12:02] <ogra_> Laney, powerd communicates through dbus ... might be possible to capture that from there
[12:05] <Laney> I don't think capturing would work; if necessary, powerd should store it and provide that information
[12:06]  * Laney will file a bug
[12:06] <ogra_> no, unity8 should
[12:06] <Laney> why?
[12:07] <ogra_> powerd runs as system service ... unity8 needs to handle its dconf settings already (i was told) ... so that info should go there as well i think
[12:10] <Laney> It sounds weird to do that, but someone can reassign if that is true
[12:14] <seb128> Laney, ideally that would be a feature we would add to upower?
[12:14] <ogra_> ++
[12:14] <pitti> Laney, seb128: upower doesn't do suspend any more
[12:15] <seb128> pitti, well, it records charge history with state, I'm sure it would be easy to listen to some suspend/resume signals and add those events to the record?
[12:16] <Laney> upower would be better and could listen to logind's signals
[12:16] <pitti> yes, you can listen to logind's PrepareForSleep signal, but I doubt that everything on the phone actually uses that
[12:16] <Laney> but I don't think that works with powerd
[12:16] <seb128> k
[12:16] <seb128> so we just can't do that doted line in the graph
[12:16] <Laney> not yet
[12:17] <seb128> seems another of those "too much work for the benefit it brings"
[12:17] <pitti> upower records the charge history, yes, but only if you actually have a battery
[12:17] <Laney> You just get events either side of the suspend afaict
[12:17] <seb128> we have more important things to do that make the charge graph indicate sleep times
[12:17] <Laney> nothing to say 'you were suspended in this period'
[12:17] <pitti> yeah, it's surprisingly difficult to find out when a machine went to sleep and came back :/
[12:17] <Laney> yeah, well, just filing bugs for things that we can't do
[12:17] <pitti> the kernel log obviously has it, but it doesn't send notifications
[12:17] <Laney> if they get fixed then hey presto we can do them :-)
[12:18] <seb128> pitti, if you don't have a battery you don't have a charge graph anyway ;-)
[12:18] <pitti> right
[12:18] <ogra_> dont we need something that monitors the power button anyway (for a shutdown menu)
[12:18] <seb128> Laney, right
[12:18] <seb128> ogra_, well, the device suspends by itself if you don't touch it
[12:18] <seb128> no need to press a button
[12:19] <ogra_> oh, roght ... forgot about that
[12:19] <pitti> seb128, Laney: the charge log already has real-time timestamps, doesn't it? this should have gaps while the device is suspended
[12:19] <Laney> yes
[12:20] <Laney> is there a reliable way to work that out from those?
[12:20] <pitti> for a gap, there are several possibilities: off, suspend, or upower crash :)
[12:20] <pitti> but on a graph they'd all show as the same time gap?
[12:22] <seb128> Laney, pitti, upower doesn't do regular recording, it just records changes
[12:22] <Laney> I seem to get it at the resolution of 1% changes
[12:22] <seb128> yeah, it writes datas when there is a change
[12:23] <Laney> let me file a bug for hadess to close ;-)
[12:23] <seb128> about?
[12:23] <seb128> I filed half a dozen
[12:23] <Laney> what pitti said, tracking sleeps
[12:23] <sticker> anyone get Ubuntu to worm on the note II yet?
[12:23]  * Laney slithers
[12:24] <seb128> Laney, k, I didn't file that one ;-)
[12:24] <seb128> I filed other about stuff like "if you are charging and unplug, you are getting the new status only on next % change"
[12:24] <seb128> so you might in a wrong state until that 1% is used
[12:26] <ogra_> !deviced | sticker
[12:26] <Laney> nod
[12:27] <ogra_> !devices | sticker
[12:27] <ogra_> (sorry for the typo)
[12:36] <t1mp> are there specific times when new images are created?
[12:36] <ogra_> t1mp, not atm, but we're working on that
[12:37] <t1mp> if I need to get something in an image before tomorrow afternoon (london time), when should it be in a UITK release?
[12:37] <ogra_> t1mp, if i trigger a build i announce it in #ubuntu-ci-eng (and if it is done as well)
[12:38] <ogra_> t1mp, best ask in the above channel, the guys there do the testing
[12:38] <ogra_> (before anything lands)
[12:39] <t1mp> ogra_: ok, thanks
[14:21] <ogra_> stgraber, didnt you add a fix for the "not able to make image writable" issue recently ? seems ricmm sees it on his grouper
[14:24] <stgraber> ogra_: yes, the initrd was changed for that
[14:24] <ogra_> stgraber, yeah, just found it
[14:25] <barry> dholbach, didrocks that's right.  there's no indication at all that things are stuck in proposed.  you only find out if you look, and it does not scale to look for everything you upload.  that really needs to be fixed.  an email when migration fails would *really* help
[14:26] <ogra_> stgraber, so it seems the install ricmm has is actually from the 3rd ... but still seems to have a readonly loop device
[14:26] <ogra_> mount: cannot remount block device /dev/loop1 read-write, is write-protected
[14:27] <dholbach> barry, maybe somebody should bring it up on u-devel?
[14:30] <ogra_> or just in #ubuntu-release ...
[14:31] <pitti> tvoss: is it some kind of policy to put all tests into <root>/tests/, or could the simulated-sensor test live in src/ubuntu/testbackend/ right next to the implementation?
[14:31] <ogra_> (wheer the maintainers of that bit of infrastructure live)
[14:31] <pitti> tvoss: the latter would avoid having to figure out an appropriate LD_LIBRARY_PATH, as cmake already sets an rpath (but that doesn't help us when calling it from another directory)
[14:31] <tvoss> pitti, not a strict policy, I would call it best practice
[14:31] <pitti> tvoss: I have my first test working BTW, so gtest/cmake are fine
[14:32] <pitti> tvoss: ok, thanks
[14:32] <pitti> tvoss: I can set LD_LIBRARY_PATH it in the CMakeLists.txt for the add_test definition, then calling the test program directly will fail; but not such a big deal, I think
[14:32] <tvoss> pitti, oh that's great
[14:33] <pitti> tvoss: http://paste.ubuntu.com/6524971/
[14:33] <tvoss> pitti, I think that's fine then for setting the LD_LIBRARY_PATH there. Perhaps put a comment in the CMakeLists.txt
[14:33] <pitti> tvoss: and that first test found the first bug :)
[14:34] <pitti> tvoss: yes, of course
[14:34] <pitti> tvoss: I guess usually people should call "ctest" or "make test", which will deal with that
[14:34] <tvoss> pitti, usually, you just call make test, yeah
[14:35] <tvoss> pitti, you can try make NightlyMemCheck, too
[14:35] <pitti> $ make -C obj && (cd obj; ctest --verbose)
[14:35] <tvoss> pitti, to run everything under valgrind automatically
[14:35] <pitti> that's my invocation for a turnaround
[14:35] <pitti> tvoss: ah, nice
[14:35] <tvoss> pitti, usually I do make && make test or make && make NightlyMemCheck
[14:35] <pitti> yeah, "make test" is horribly un-verbose
[14:36] <pitti> it doesn't show me the actual failures
[14:36] <pitti> tvoss: I guess I need some additional magic for NightlyMemCheck, doesn't exist here
[14:36] <pitti> but, that's for later
[14:37] <pitti> let's get these tests written
[14:37] <tvoss> pitti, +1
[14:38] <tvoss> pitti, you want include include(CTest) as opposed to enable_testing() in your CMakeLists.txt
[14:39] <pitti> tvoss: ok; I was following some stackexchange advice
[14:40] <pitti> tvoss: works fine
[14:41] <pitti> tvoss: http://paste.ubuntu.com/6525001/ with above change and the LD_LIBRARY_PATH setting
[14:42]  * pitti wonders if set() will set the environment var, too; would look nicer for multiple tests
[14:44] <pitti> no, it doesn't; and CTEST_ENVIRONMENT doesn't help either, so go ugliness
[14:47] <tvoss> pitti, looks good albeit the ugliness. I remember a lengthy cmake mailing list discussion about that specific part
[14:47] <pitti> tvoss: I was hoping for something like set(ENV{LD_LIBRARY_PATH} ...), but that doesn't work
[14:48] <pitti> I live too much in a make world..
[14:49] <tvoss> pitti, the above actually works, but not for ctest iirc
[14:49] <tvoss> pitti, let me quickly check
[14:49] <pitti> tvoss: right, only for make
[14:50] <pitti> tvoss: the other bit of ugliness is that it currently hardcodes the gtest path; but the other alternatives of including huge amounts of boilerplate don't look any better to me..
[14:50] <tvoss> pitti, yup, agreed. And it will at least fail early and with a sensible error message
[14:55] <cwayne_> zsombi, ping
[14:55] <zsombi> cwayne_: pong
[14:56] <cwayne_> zsombi, is there a plan to let the user choose their app theme from system settings?
[14:56] <cwayne_> rather than editing an ini file
[14:56] <zsombi> cwayne_: that's mostly a question to design I think :)
[14:57] <pitti> tvoss: thanks for the review; I'll commit that to my branch then, and flesh out the tests
[14:57] <zsombi> cwayne_: settings will anyway edit the ini file :)
[14:57] <pitti> tvoss: we can discuss the finer details in the MP (I'm a C++ n00b and probably do a lot of things wrong :) )
[14:57] <cwayne_> zsombi, ah, so there's no plan to move to a gsettings key or something like that?
[14:58] <zsombi> cwayne_: so if design thinks that it should be there, it's up to seb128 to have it implemented :)
[14:58] <seb128> zsombi, cwayne_: there is no design for a such feature
[14:59] <zsombi> cwayne_: yet we do not have such plans, however changing the system theme would also have to have a setting UI element... and as sebq128 says, so far there's no UI element in Settings app
[14:59] <tvoss> pitti, happy to help :)
[14:59] <zsombi> cwayne_: however UITK does not provide API yet for that purpose
[15:00] <cwayne_> zsombi, seb128 ACK, thanks
[15:00] <zsombi> cwayne_: yw
[15:20] <pitti> tvoss: argh, not enough; I need to run each test case in a forked subprocess, as with the current sensor API there is no way to "reset" everything (unload the library, free all existing sensors, etc.)
[15:21] <barry> dholbach: hope my email captured the problem without being too negative ;)
[15:21]  * barry now goes to fix the bug
[15:25] <stgraber> ogra_: http://paste.ubuntu.com/6525209/
[15:25] <nic-doffay> robotfuel, hey got your mail. Here's the MP: https://code.launchpad.net/~nicolas-doffay/ubuntu-ui-toolkit/fix-1231939/+merge/197899
[15:25] <nic-doffay> literally just proposed it now.
[15:26] <ogra_> stgraber, yeah, weird, not sure why that doesnt work for ricmm
[15:26] <ogra_> though he tries to remount /system
[15:26] <ogra_> to put some changed android binaries in place
[15:26] <dholbach> barry, yep, thanks!
[15:30] <stgraber> ogra_: ah yeah, /system is another block device and may suffer from the same problem. I don't think I changed that one in the initrd.
[15:30] <stgraber> ogra_: I believe I didn't bother since the system.img file has 0 byte free anyway, so it's not like you could write anything to it
[15:30] <ogra_> ah
[15:30] <ogra_> ricmm, ^^^
[15:31] <the__> I've been trying to get a,'My Notebook', to work on a Ubuntu after using it on the window's, without any success, does anyboay know how to...?
[15:32] <glfados> is there anyway i can compile ubuntu touch image myself?
[15:32] <stgraber> ricmm: so your best bet is probably to copy system.img somewhere, dd some free space to it, then resize2fs it to get the new extra space, then loop mount it, add your stuff and finally overwrite the original system.img + reboot
[15:32] <asd__> asd
[15:33] <ogra_> stgraber, he went for a cdimage image now :)
[15:34] <ogra_> stgraber, oh, btw, i was told you will fix the isotracker so didrocks' team can trigger image builds, any ETA for that ?
[15:37] <robotfuel> nic-doffay: re-flashing my phone to test now.
[15:37] <nic-doffay> robotfuel, cool ta
[15:38] <nic-doffay> glad to hear it was ok too :P
[15:45] <stgraber> ogra_: yeah, asac poked me about it, should be done at some point today
[15:45] <ogra_> perfect, thanks
[15:45] <stgraber> ogra_: except that even if you have access it apparently won't work
[15:46] <ogra_> ugh, why
[15:46] <stgraber> because they're not showing up on the tracker at the moment
[15:46] <ogra_> whats the way to make them show up ?
[15:47] <stgraber> there's probably some mismatch between nusakan and the tracker, looking for errors now in the logs
[15:48] <stgraber> No iso.qa.ubuntu.com product found for ubuntu-touch/daily-preinstalled/trusty-preinstalled-touch-armhf; skipping.
[15:48] <stgraber> right, so we'll need to tweak that a bit :)
[15:49] <ogra_> yeah, thats a weird name :)
[15:49] <stgraber> ogra_: so I'll disable all of the current Ubuntu Touch Preinstalled <device> products on the tracker and add a single "Ubuntu Touch armhf" one and link it with nusakan
[15:50] <ogra_> yeah
[15:52] <stgraber> ogra_: so I'll need at least two touch builds to confirm that this works once I've done the changes
[15:52] <ogra_> stgraber, ok, we'll likely do one in a few hours ... the next probably only tomorrow morning though
[15:53] <cwayne_> zsombi, so would it be a possibility to switch the theme to at least a gsetting?  It just seems the more 'correct way' of doing things
[15:55] <zsombi> cwayne_: most probably would... we could have this as future task for theming
[15:56] <user82> did anyone get the emulator running on ubuntu 13.10? i just downloaded the "android-emulator_20131202-2236-0ubuntu1_i386.deb" package and ran the commands from the wiki. however the screen was black in the emulator
[15:56] <cwayne_> zsombi, if we could add that as a task that would be perfect, we're trying to minimize copying files into ~ for customization in favor of gsettings keys, this would be a big help for us :)
[15:56] <ogra_> user82, the first boot takes over 10min
[15:57] <stgraber> ogra_: so the change I just landed "should" (completely untested and not really testable short of spinning an image) at lesat push the build to the tracker
[15:57] <user82> ogra_, oh...that might be it ;)
[15:57] <stgraber> ogra_: once that's done, I'll look at the ACL and trigger of the build from the tracker (that's where we'll need a second build)
[15:57] <ogra_> user82, subsequent ones are faster
[15:57] <user82> the terminal did not move and i got impatient..but it sounds like a clue
[15:58] <ogra_> stgraber, ok, i'll bring that up in the landing team meeting, we can probably spare a build
[15:58] <user82> ogra_, even after the login already appeared?
[15:58] <user82> "ubuntu phablet login"
[15:58] <ogra_> yeah
[15:58] <user82> allright
[15:58] <user82> so i log in as "phablet" and keep on waiting?
[15:58] <zsombi> cwayne_: not sure when are we going to have time for that though...
[15:59] <user82> yey its up :)
[15:59] <cwayne_> zsombi, well as always, i'm happy to help with any testing if that helps you guys out at all
[15:59] <zsombi> cwayne_: thx ;)
[16:00] <cwayne_> zsombi, thank you :) this was one of our last files copied into ~, will be a big win for us, so again, happy to help :)
[16:04] <zsombi> cwayne_: any preference on the key?
[16:06] <cwayne_> zsombi, maybe something like com.ubuntu.touch.app-theme?  I don't have any strong preference
[16:07] <zsombi> cwayne_: ok, we'll come up with sthing then :)
[16:08] <cwayne_> zsombi, sounds good to me :D
[16:15] <zsombi> cwayne_: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1258209
[16:26] <asac> stgraber: thanks for checking this out for us
[16:26] <ogra_> asac, not done yet :)
[16:26] <barry> dholbach: s-i 2.0.2-0ubuntu2 just uploaded.  it was an out-of-date autopkgtest dep
[16:27] <asac> ogra_: hence i didnt say "sorting" :)
[16:28] <ogra_> lol
[16:28] <ogra_> janimo`, you sole my WI !
[16:28] <ogra_> *stole
[16:28] <ogra_> (thanks !!)
[16:29] <janimo`> ogra_, well, I just want to leave you more time for the hard stuff (cdimage) :)
[16:29] <ogra_> heh
[16:31] <tedg> tvoss, Chatting with charles here about whether LTTng in UAL should be enabled by default.  Curious what you think.
[16:31] <dholbach> barry, *crossing fingers* :)
[16:41] <tvoss> tedg, charles I would make it a build option, with that we can easily generate instrumented packages if required
[16:42] <tedg> tvoss, My concern there was that we'd not be able to get data on images then...  only custom stuff.
[16:42] <tedg> In theory we'd never need timing data.
[16:43] <tvoss> tedg, alternatively, you could make it a command line option
[16:43] <tedg> tvoss, Won't the kernel tell me if it's enabled?
[16:43] <tvoss> tedg, I would need to check that
[16:43] <tvoss> tedg, a command line option is more explicit and self-documenting though
[16:44] <tedg> tvoss, Sure, but that doesn't really help the can't use an image problem.
[16:45] <tvoss> tedg, I think I'm not following :)
[16:45] <tvoss> tedg, if the kernel does not support it, the call to updating the probe will just fail
[16:45] <tedg> tvoss, http://twitter.com/tedjgould <- Click on "Follow" ;-)
[16:46] <tvoss> tedg, so enable in build by default, but make it optional at runtime
[16:47] <tedg> tvoss, I guess for me, do you see any reason that we'd use the tracing on a production image.  Or is that not a useful requirement.  I'm undecided on that.
[16:48] <tvoss> tedg, hmmm ... I think it's undecided so far. That being said, I would enable it in the build by default
[16:49] <tedg> tvoss, Okay, so we'll enable it and I'll look to see what happens at the kernel level.  It might be faster to check there than to do any other command line parsing or environment variables.
[16:49] <tvoss> tedg, but still: having it in the kernel might not necessary mean: do the actual tracing
[16:50] <tedg> tvoss, Sure, I'm hoping they'll tell us both.
[16:50] <tvoss> tedg, I think a command-line flag would be the best approach
[16:51] <tedg> tvoss, The problem is that we're not running any of the tools directly, but via the upstart jobs.  So I think injecting an environment variable into upstart might be easier.
[16:52] <tvoss> tedg, cool
[16:53] <charles> ted, the current MR always enables it; IMO making it optional is a nice middle ground between that and disabling it in production
[16:55] <charles> I agree about using an env variable even if it's less self-documenting -- it doesn't matter how documenting the command-line args are if we're not always able to get the arg passed in
[16:55] <mardy> greyback: hi! Any news about bug 1254333?
[16:56] <greyback> mardy: hey. I've not been able to look at it this week. I've good idea why it fails, but the fix isn't easy.
[16:59] <tedg> tvoss, Looking at man lttng-ust and there's a var LTTNG_UST_REGISTER_TIMEOUT.  Seems like we could just set that to zero by default.  And then allow overriding it to something more reasonable if we want to trace.
[17:01] <tvoss> tedg, makes sense, and people actually use it for that purpose, see http://lists.lttng.org/pipermail/lttng-dev/2013-July/020968.html
[17:01] <tedg> tvoss, Ha, I was just there :-)
[17:15] <nic-doffay> robotfuel, could you leave a comment here that the fix works? https://code.launchpad.net/~nicolas-doffay/ubuntu-ui-toolkit/fix-1231939/+merge/197899
[17:15] <nic-doffay> Wouldn't mind fast tracking it now that the tests have been run.
[17:17] <robotfuel> nic-doffay: sure I am installing the debs on my phone now.
[17:18] <nic-doffay> robotfuel, cool
[17:34] <cjwatson> cwayne_: bug 1253855 - could you please attach the /usr/share/click/hooks/ file and the click package manifest that reproduces this?
[17:35] <cjwatson> cwayne_: specifically it's not clear to me why the trailing slash is on that path
[17:36] <cwayne_> cjwatson, sure thing
[17:36] <cjwatson> thanks
[17:40] <cwayne_> cjwatson, added.  shall i try it without the trailing slash? ( i think i had tried it previously, but happy to do again to be sure)
[17:41] <cjwatson> cwayne_: yes, please do, the error shown here is because of the trailing slash
[17:41] <cwayne_> cjwatson, ok, will remove it from the hook and try it out
[17:42] <cjwatson> cwayne_: it's perhaps not widely known, but the most important semantic effect of a trailing slash is "even if this is a symbolic link, force it to be treated as a directory anyway"
[17:42] <cjwatson> I mean, force resolution
[17:42] <cjwatson> cwayne_: precisely the opposite of what you want here ...
[17:42] <cwayne_> ah, of course
[17:42] <cjwatson> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_12
[17:43] <cjwatson> so if that's a sufficient fix, I can probably strip the trailing slash to be friendly or some such, but you'll be able to move on
[18:10] <cwayne_> cjwatson, that seems to have done it!
[18:11]  * cwayne_ feels like an idiot now :P
[18:11] <cjwatson> ok, cool
[18:11] <ogra_> ogra@sabre:~$ rmadison kpartx
[18:11] <ogra_> rmadison: you must have the liburi-perl package installed
[18:11] <ogra_> to use this script
[18:11] <ogra_> hmpf ...
[18:12] <ogra_> why isnt that a hard dep of devscripts (i installed with --no-install-rcommends, but would still expect shipped scripts to work)
[19:48] <Crimson_Rogue> Hello. Could someone point me to the file that I need to edit for ubuntu-touch to recognize my phone's partitions?
[20:07] <Crimson_Rogue> hardware/qcom/audio-caf/mm-audio/aenc-qcelp 13/qdsp6/inc/omx_qcelp13_aenc.h:52:34:
[20:14] <adam__> Hey, quick question. Is there a version of touch out that I can actually modify and use a terminal in?
[20:26] <adam__> anyone?
[20:27] <t1mp> adam__: what do you mean? for your phone/tablet?
[20:27] <t1mp> adam__: ubuntu touch has a terminal app
[20:28] <t1mp> or you can ssh to your device if that's what you meant
[20:28] <adam__> oh okay so ssh is enabled by default
[20:29] <t1mp> adam__: it is on my device. I don't remember that I did anything to enable it
[20:29] <t1mp> so I think yes :)
[20:29] <adam__> think it would be advisable to try to install a new window system or will it break the display config or fail due to drivers?
[20:30] <t1mp> adam__: you want to install ubuntu touch on a device and replace unity8 by something else?
[20:30] <t1mp> that would be a lot of work
[20:30] <adam__> wanted to run gnome and use my tablet for configing my Cisco IOS racks
[20:31] <adam__> for fun... not in live systems
[20:31] <t1mp> I don't think gtk apps are supported yet
[20:31] <adam__> hmm
[20:31] <t1mp> its all qt5 now
[20:31] <t1mp> for graphics I mean
[20:31] <adam__> hmm
[20:31] <adam__> well ty
[20:32] <t1mp> perhaps you can install a "regular" ubuntu built for ARM?
[20:32] <adam__> oh? will it install using adb?
[20:33] <t1mp> adam__: I have no idea, I just saw desktop ubuntu on tablets in youtube videos
[20:34] <t1mp> adam__: if you can configure the racks in a webbrowser then ubuntu touch will do
[20:52] <iBelieve> popey: ping
[20:53] <lotuspsychje> any device working flawless yet with ubuntu touch?
[20:55] <t1mp> lotuspsychje: these should work quite well https://wiki.ubuntu.com/Touch/Devices#Working_with_phablet-flash
[20:55] <lotuspsychje> t1mp: tnx lemme see
[20:58] <lotuspsychje> t1mp: so if i buy a nexus7, touch would work rather good on it?
[21:00] <t1mp> lotuspsychje: actually that's a good question. Those are the devices that we test on, but there are two versions of nexus 7.
[21:00] <t1mp> popey: ^ do you know if the new nexus7 is supported?
[21:01] <lotuspsychje> if the web browsing and terminal work flawless i would buy :p
[21:30] <popey> t1mp: no.
[21:45] <dkessel> ogra_, hey... what do you think about these autopilot test startup failures on the emulator? http://paste.ubuntu.com/6526692/
[22:25] <sergiusens> dkessel, if things are still as they were; autopilot would need some work I think to setup the uinput device
[22:25] <sergiusens> dkessel, we would also need to peek a bit more inside the emulator and check
[22:27] <dkessel> sergiusens, well all I have seen is that /dev/uinput is definately missing...
[22:29] <dkessel> well if someone could look into the problem that would be great. there is currently no way for me to run those autopilot tests in the emulator
[22:30] <sergiusens> dkessel, it would probably be me
[22:33] <sergiusens> dkessel, you can subscribe to https://blueprints.launchpad.net/ubuntu/+spec/core-1311-touch-emulator ;
[22:33] <sergiusens> dkessel, do you have a launchpad id?
[22:33] <dkessel> sergiusens, sure... and sure
[22:33] <sergiusens> dkessel, I'll add your name to the last item if you want ;-) (which you already did anyways)
[22:34] <dkessel> sergiusens, heh. ok do so
[22:35] <sergiusens> dkessel, can you tell me what your launchpad id is?
[22:35] <dkessel> sergiusens, id is: d-kessel
[22:36] <sergiusens> dkessel, ty