[06:20] -lugito:#lubuntu-devel- [Lubuntu CI] jobgenerator just failed after succeeding: https://ci.lubuntu.me/job/jobgenerator/901/
[13:33] <tsimonq2> Poking jobgenerator then cleaning up shop.
[13:35] <kc2bez[m]> Nice, thanks.
[13:35] <tsimonq2> Of course.
[13:35] <tsimonq2> Manually bringing node-2 online.
[13:36] <kc2bez[m]> @teward001 the bridge is repeating itself
[13:36] <tsimonq2> Echo
[13:36] <tsimonq2> XD
[13:37] -lugito:#lubuntu-devel- [Lubuntu CI] jobgenerator just succeeded after failing: https://ci.lubuntu.me/job/jobgenerator/902/
[13:38] -lugito:#lubuntu-devel- [Lubuntu CI] merger_sddm FAILURE: https://ci.lubuntu.me/job/merger_sddm/277/
[13:51] <tsimonq2> It's not to blame anyone, but when I was doing LXQt releases by myself, I made sure all the jobs passed before it hit the archive.
[13:51] <tsimonq2> What happened?
[13:52] <The_LoudSpeaker> we don't have an app to install fonts.
[13:53] <The_LoudSpeaker> we can always put them in ~/.fonts and the appearance app will notice them but nothing pops up when I double click a font.
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/397/
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/397/
[13:53] <The_LoudSpeaker> something to add to wishlist?
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab just failed after being unstable: https://ci.lubuntu.me/job/focal_stable_screengrab/820/
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab just failed after being unstable: https://ci.lubuntu.me/job/focal_stable_screengrab/820/
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/260/
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver just failed after being unstable: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/608/
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_screengrab/127/
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_screengrab/127/
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_screengrab/389/
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab just failed after being unstable: https://ci.lubuntu.me/job/groovy_stable_screengrab/390/
[13:53] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-admin just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-admin/622/
[13:54] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver just failed after being unstable: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/608/
[13:54] <tsimonq2> <The_LoudSpeaker "something to add to wishlist?"> Please. Task and all.
[13:55] <The_LoudSpeaker> sare.
[13:55] <tsimonq2> I'm upgrading Lintian and debhelper on the Jenkins nodes so we get an accurate reading. Do we have a maintenance checklist or ... something ... somewhere I can add this to?
[13:56] <kc2bez[m]> <tsimonq2 "What happened?"> Noobs I guess. Nobody has been giving ci the love it needs.
[13:56] <tsimonq2> It will now. ;)
[13:56] <The_LoudSpeaker> also tsimonq2, what was that about making jobs pass before hitting archive? e: context not found
[13:57] <The_LoudSpeaker> kc2bez[m]: CI is tough to love. :P
[13:58] <kc2bez[m]> <tsimonq2 "I'm upgrading Lintian and debhel"> I don't think so, maybe the ci wiki page?
[13:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab just failed after being unstable: https://ci.lubuntu.me/job/focal_stable_screengrab/820/
[13:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-admin just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-admin/622/
[14:00] <tsimonq2> Sounds about right.
[14:00] <tsimonq2> I'm going to manually up the executors on node-2 and poke it until it's all flushed through.
[14:00] <tsimonq2> I'll just be following the dependency order at that point.
[14:02] -lugito:#lubuntu-devel- [T202: GUI app for installing fonts.] The_LoudSpeaker (Raman Sarda) just created this task: https://phab.lubuntu.me/T202
[14:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-admin just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-admin/622/
[14:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/620/
[14:09] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/261/
[14:09] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-notificationd just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-notificationd/356/
[14:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/621/
[14:09] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-notificationd just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-notificationd/356/
[14:16] <The_LoudSpeaker> also, we don't have a default camera app ?
[14:17] <The_LoudSpeaker> and trojita is seen twice. once under internet and once under office. should not be under office imo.
[14:22] <kc2bez[m]> 🤷♂ Feel free to make a task for trojita. The desktop file just needs some adjustment.
[14:23] <kc2bez[m]> I don't think we need an app for everything.
[14:23] <kc2bez[m]> Do folks really use camera apps?
[14:24] <tsimonq2> It's like AAA. I don't know why I have it until I really really need to use it.
[14:24] <tsimonq2> We should have a "recommended solution" maybe in the manual or something, but yeah, by default we can keep it limited.
[14:25] <kc2bez[m]> <tsimonq2 "It's like AAA. I don't know why "> Hopefully the camera apps are more dependable.
[14:25] <kc2bez[m]> XD
[14:26] <tsimonq2> >XDDDDDDDDDDDDDDDDd
[14:29] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/621/
[14:44] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/396/
[14:45] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/618/
[14:45] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/125/
[14:45] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/618/
[14:45] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/397/
[14:45] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/125/
[14:48] <tsimonq2> Flushed jobs that were waiting for an executor to node-2.  I am guessing we can't add it to seed because it being a part of another package but maybe we can?
[20:34] <wxl> kamoso?
[20:34] <wxl> don't think we really need a camera app tho, do we?
[20:35] <The_LoudSpeaker> only in edge cases.
[20:35] <The_LoudSpeaker> but it's good to have.
[20:35] <RikMills> don't think we currently seed one
[20:35] <wxl> i'm disinclined towards it
[20:35] <The_LoudSpeaker> RikMills: kaay. we should ship it tho right? feels like a more complete offering on our end.
[20:36] <RikMills> dunno. camera apps tend to be bug magnets
[20:36] <The_LoudSpeaker> ^ wxl read last sentence here.
[20:37] <wxl> The_LoudSpeaker: you could also argue that we'd have a more complete offering if we shipped mono, too
[20:37] <wxl> or wine
[20:37] <wxl> or…
[20:37] <The_LoudSpeaker> nope. coz not everyone uses that
[20:37] <wxl> and not everyone uses a camera app
[20:37]  * RikMills seeds the whole universe pocket for lubuntu
[20:37] <RikMills> now you are complete!
[20:38] <kc2bez[m]> It is all a `sudo apt install` away from being yours.
[20:38] <The_LoudSpeaker> people who might need a camera app >>>>> no of people that might use wine
[20:38] <wxl> i mean these days people use their camera ALL THE TIME and yet no camera app is needed
[20:39] <wxl> teleconferencing apps are what people need/use and for that, they get an app from the teleconferncing solution
[20:41] <The_LoudSpeaker> whatever. just wanted to point a small nitpick. offerring complete set of apps including multimedia and camera ones make gnome/KDE feel more polished than others imo.
[20:41] <wxl> did you not hear that kubuntu doesn't seed one?
[20:42] <wxl> and besides, we're not trying to be everything-including-an-industrial-size-kitchen-sink ubuntu
[20:42] <The_LoudSpeaker> okay then remove KDE from above sentence. what I said still holds.
[20:43] <wxl> you can honestly make an argument that ANYTHING that's not included is keeping us from being "complete"
[20:43] <wxl> but there's got to be a point where you draw the line
[20:43] <wxl> i'd say we need to focus on *essentials*. what things are being used by people constantly?
[20:44] <The_LoudSpeaker> yes we are not. but we are trying to provide a lighter alternative for ubuntu. we should provide lighter alternatives for all apps that ubuntu provides imo.
[20:44] <RikMills> what do you actually mean by 'camera app' anyway?
[20:44] <wxl> and i'm telling you, there are very, very few people that are using camera apps.
[20:44] <The_LoudSpeaker> cheese on ubuntu RikMills
[20:44] <wxl> ESPECIALLY in the day and age of cell phones
[20:45] <RikMills> gotcha.
[20:46] <RikMills> as said, webcam apps are bug magnets
[20:46] <wxl> feel free to poll the community and see how important it is. there are such things as discourse polls
[20:47] <RikMills> ship it, you support it
[20:47] <The_LoudSpeaker> yes. A discourse poll is a nice idea.
[20:48] <The_LoudSpeaker> RikMills: yes. many apps are bug magnets. if we ship a camera app we will have to consider that.
[20:58] <wxl> The_LoudSpeaker: you may want to supplement the poll with a series of suggestions for appropriate applications and their relative pros and cons
[20:59] <The_LoudSpeaker> noted.


[01:45] <mup> Bug #1952156 opened: Deleting a dynamic range and recreating it may fail <MAAS:New> <https://launchpad.net/bugs/1952156>
[10:33] <mup> Bug #1952216 opened: Erorr from websocket if machine has no disks <MAAS:Triaged> <https://launchpad.net/bugs/1952216>
[12:43] <mup> Bug # changed: 1936749, 1943051, 1947128, 1947629, 1948743, 1949455, 1949625, 1949681, 1949949, 1949960, 1949961, 1949963, 1950318, 1950447, 1950694, 1950827


[08:01]  * apw yawns
[09:01] <psivaa> apw: Updated bug #1195710 with some more information, not sure it will help. Have time to look into it?
[09:01] <ubot2`> Launchpad bug 1195710 in linux (Ubuntu Saucy) "'Kernel bug - invalid opcode: 0000 [#1] SMP' is reported at 'Preparing linux-image-extra-3.10.0-0-generic' stage of multi-lvm installations of amd64 saucy server " [High,Confirmed] https://launchpad.net/bugs/1195710
[09:03] <apw> psivaa, oh hmmm, increasing memory helped ...
[09:04] <apw> psivaa, as neither smb nor I could reproduce it, but 1G is my default size
[09:04]  * ppisati -> reboot
[09:05] <psivaa> apw: isn't 512 the minimum allowed for server?
[09:09] <apw> psivaa, oh quite probabally, i just mean the default in the box when i make new instances
[09:09] <smb> By default I use 1G but I probably have done 512 as well
[09:09] <smb> Cannot remember right now
[09:09] <apw> is 1G and that sems 'small' and therefore wasn't going to hit it ... doh
[09:17] <apw> /srv/images<IP_ADDRESS>/24(ro,sync,no_subtree_check)
[09:17] <apw> /srv/images <IP_ADDRESS>/24(ro,sync,no_subtree_check)
[09:33] <apw> Error creating pool: Could not start storage pool: cannot open path '/var/lib/libvirt/images/iso': Permission denied
[09:39] <psivaa> apw: is this one of the utah errors in trying to reproduce the above bug?
[09:45] <apw> psivaa, oh no, this is me trying to export some images so i can start some new vms with less ram
[09:45] <apw> psivaa, i am chatting with smb about how retarded libvirt is and how much i would like to meet its mother
[09:46] <psivaa> apw: ack :)
[09:47] <apw> (with and axe)
[10:22] <apw> psivaa, do you have the whole preseed you are using for this install ?
[10:26] <psivaa> apw: it's here: http://bazaar.launchpad.net/~ubuntu-server-dev/ubuntu-test-cases/server-tests-raring/view/head:/preseeds/multi-lvm.preseed
[10:27] <psivaa> attached to the bug as a file as well now
[10:27] <apw> psivaa, brilliant ..
[10:43] <apw> smb, ok so using the preseed manually is pretty easy, just change the kernel command line and remove the file=fooo.preseed and replace it with like url=http://192..../foo.preseed
[10:49] <apw> psivaa, ok with that i was able to repro this, i think ... thanks
[10:50] <psivaa> apw: ack, thank you
[10:51] <apw> psivaa, will see what i can find
[11:03] <apw> psivaa, ok yeah made it do it twice, seems to happen later without utah, utah must be consuming a chunk of memory i recon
[11:05] <psivaa> apw: that's probable. I always used utah. the client logs are saved in there before retrieving to the server
[12:09]  * ppisati -> out for lunch
[12:14]  * henrix follows ppisati
[13:16] <jjohansen> rtg: so I have a branch with the aa3 sync against pure upstream 3.11, so it doesn't have the ubuntu configs as part of it. Do you want a pull request using this or do you want to point me to your 3.11 rebase?
[13:19] <rtg> jjohansen, a pull request agsint the saucy unstable branch would be nice
[13:20] <jjohansen> rtg: ah, got it. I'll have that for you in a few minutes
[13:20] <rtg> jjohansen, no rush. we won't transition to 3.11 until about rc3 or 4
[13:21] <jjohansen> rtg: ack
[13:25] <jjohansen> rtg: okay, I've pushed it to my saucy tree on zinc, I'll do some build testing etc, before sending out the request
[13:25] <rtg> jjohansen, ack
[13:27] <FernandoMiguel> howdy
[13:27] <FernandoMiguel> ever since kernel  3.9.0-7, I haven't managed to get a proper CPU scheduler management
[13:27] <FernandoMiguel> 3.10 only offers two states
[13:27] <FernandoMiguel> and seems to use much more battery
[13:41] <rtg> sforshee, re: bug #1190225. Is that in drivers/power/smb347-charger.c ?
[13:41] <ubot2`> Launchpad bug 1190225 in linux-grouper (Ubuntu) "opening /sys/devices/platform/tegra-i2c.4/i2c-4/4-006a/reg_status (as user) causes immediate reboot" [Undecided,New] https://launchpad.net/bugs/1190225
[13:49] <Sarvatt> FernandoMiguel: update again, i think that was fixed a few weeks ago?
[13:50] <FernandoMiguel> Sarvatt: every kernel I get, I boot into it, and all are the same
[13:50] <Sarvatt> or boot with intel_pstate=disable
[13:52] <sforshee> rtg: looking
[13:52] <rtg> sforshee, I'm pretty sure that it
[13:53] <rtg> root@ubuntu-phablet:/# dmesg|grep charger
[13:53] <rtg> [    2.096531] smb347_charger: [smb347_init] project_id=0, pcba_ver=3, dock_in_gpio=164
[13:53] <rtg> [    2.098920] [charger] Disable AICL, retval=93 setting=83
[13:53] <rtg> [    2.099397] [charger] set cahrger limmit, limit=900 retval =73 setting=73
[13:53] <rtg> [    2.099802] [charger] re-enable AICL, setting=93
[13:53] <rtg> [    2.627268] smb347_charger: [cable_type_detect] Reg39 : 0x10
[13:53] <rtg> [    2.627539] smb347_charger: [cable_type_detect] Reg3F : 0xc0
[13:53] <rtg> [    2.627681] smb347_charger: [cable_type_detect] USB_IN
[13:53] <rtg> [    2.627949] smb347_charger: [cable_type_detect] Reg3E : 0x0c
[13:53] <Sarvatt> apw: didn't you make that default to off? i'm not seeing it in the changelog
[13:53] <apw> Sarvatt, yeah that was disabled in the 3.9 kernel, the rumours were that 3.10 was 'better'
[13:54] <rtg> Sarvatt, also NO_HZ_FULL=n
[13:54] <apw> Sarvatt, so it wasn't switched there, on the assumption we would never ever test it there
[13:54] <apw> Sarvatt, unless it was on, ... are we seeing issues now we are in 3.10
[13:54] <Sarvatt> oh 3.10 made it start working on ivybridge too and it was bad here once that kicked in
[13:54] <apw> Sarvatt, so still shit in 3.10 yes
[13:54] <Sarvatt> yeah, 15C higher idle even in power save mode :(
[13:54] <apw> if so i can pull that change up to there, and leave it off in 3.11 which rtg is managing
[13:55] <apw> Sarvatt, well i call that tested in the negative ...
[13:56] <FernandoMiguel> Sarvatt: what will that parameter do ?
[13:56] <sforshee> rtg: looks like it is smb347-charger
[13:56] <apw> Sarvatt, what the heck was the bug number
[13:56] <rtg> sforshee, yep
[13:56] <FernandoMiguel> apw: so it's a known bug/limitation ?
[13:56] <Sarvatt> i think they expect you to use that intel thermal management daemon to control fans if you use intel_pstate (https://01.org/linux-thermal-daemon)
[13:57] <FernandoMiguel> cause with 40ºc here, I can't just leave it in 3.10 Power Save ... it will kill kittens
[13:57] <apw> pstate_idle being pants, it is 'known of' in 3.9, and now 3.10 yeah
[13:57] <apw> FernandoMiguel, sounds fun indeed
[13:57] <FernandoMiguel> apw: it works fine in <IP_ADDRESS>
[13:57] <apw> FernandoMiguel, and pstate_idle=off or whatever Sarvatt said it was, did the trick for you
[13:57] <FernandoMiguel> and all before that
[13:57] <apw> FernandoMiguel, well it was
[13:57] <FernandoMiguel> the few after and 3.10 broke
[13:58] <apw> FernandoMiguel, well it was not enabled for some your kit at all in 3.9
[13:58] <FernandoMiguel> there was a 3.10.1 that worked too. but broke again on .2
[13:59] <FernandoMiguel> so the advice is to pass a kernel option for 3.10 till this is improved, correct?
[13:59] <FernandoMiguel> any bug # I can track?
[13:59] <Sarvatt> hmm its not on https://bugs.launchpad.net/~adconrad/+reportedbugs so it must have been closed
[13:59] <Sarvatt> FernandoMiguel: still trying to find it..
[14:00] <FernandoMiguel> thanks
[14:00] <apw> Sarvatt, found it ... bug #1188647
[14:00] <ubot2`> Launchpad bug 1188647 in linux (Ubuntu) "Please change intel_pstate default to disable" [High,Fix released] https://launchpad.net/bugs/1188647
[14:00] <FernandoMiguel> GRUB_CMDLINE_LINUX="intel_pstate=disable"
[14:00] <FernandoMiguel> how will this affect 3.9.x kernels?
[14:01] <FernandoMiguel> thanks guys!
[14:02] <apw> FernandoMiguel, if you arn't using there they won't notice it
[14:02] <FernandoMiguel> apw: the bug is fix released, but it's not fixed in 3.10.x
[14:02] <apw> rtg, i have pulled that pstate_idle change up to master-next, but _not_ applied it to unstable as per discussion above
[14:02] <apw> FernandoMiguel, reload the bug
[14:03] <FernandoMiguel> ah :9
[14:03] <sforshee> rtg: the offending function is smb347_reg_show. One thing that is obvious is that it's reading more data than what its buffers are sized for.
[14:03] <FernandoMiguel> apw: need any info on my system to help triage it ?
[14:03] <apw> FernandoMiguel, the fix was deliberatly applied and releasd against the v3.9 kernel but not applied to unstable (v3.10 based) at the time
[14:04] <apw> FernandoMiguel, nope, i have turned it off, we suspected it was not ready for mainstream in v3.10 and your confirmation that is sucks is sufficient for me to just disable it pending it getting less crap
[14:04] <rtg> apw, so 3.11 should work better ?
[14:04] <apw> rtg, i think the bigger question is "is v3.11 any better", for v3.10 we left it not applied in unstable so we would find out, i am proposing the same for v3.11
[14:04] <FernandoMiguel> apw: how many users actually even change schedulers, like I do ?
[14:05] <apw> rtg, as infinity as an avid user of affected kit we find out pretty smartly if it is utter crap
[14:05] <rtg> apw, ack.
[14:05] <apw> FernandoMiguel, heh dunno, but this is a default change so anyone with the kit is getting it by default
[14:05] <apw> it is new and shiney and meant to give you yet more performance for less power consumption
[14:05] <apw> which it clearly fails dismally to do
[14:06] <FernandoMiguel> on battery, it sure changes a lot
[14:06] <FernandoMiguel> I've gonne from 5h+  to 2h
[14:06] <sforshee> rtg: that function has so many things wrong with it
[14:06] <FernandoMiguel> and that's ondemand
[14:06] <rtg> sforshee, off by one everywhere
[14:06] <FernandoMiguel> now I need to track down unity folks.... unity service is hogging a core.... :\
[14:06] <apw> FernandoMiguel, heh only one, you are lucky
[14:06] <FernandoMiguel> bye! if you need any update or testing, I'm subbed to the bug and can be found on #+1
[14:07] <rtg> sforshee, do you suppose it _ever_ worked ?
[14:07] <sforshee> rtg: I doubt it
[14:07] <FernandoMiguel> apw: $ killall -9 unity-panel-service
[14:07] <FernandoMiguel> that's how I've been surviving
[14:07] <FernandoMiguel> everytime I hear the fans go crazy
[14:07] <rtg> sforshee, well, I'm gonna hack on it to see if I can get it to stop faulting
[14:08] <sforshee> rtg: I added a comment to the bug, definitely looks like stack corruption
[14:08] <rtg> sforshee, agreed
[14:10] <apw> FernandoMiguel, hopefully the peeps on #ubuntu-unity have it covered
[14:10] <FernandoMiguel> thanks
[14:52] <jsalisbury> **
[14:52] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[14:52] <jsalisbury> **
[15:13] <Quintasan> Hi, I've recently discovered that my system stopped reading blanks DVDs. Since I didn't want to open up a new bug without any searching I did some digging around and last time anyone had a problem with it was Lucid. I did check the disk itself on another PC and it's blank for sure. I also did check it on Windows, blank there too. Output of `sudo /lib/udev/cdrom_id --debug /dev/sr0` is  http://paste.ubuntu.com/5858658/ and output of `sudo
[15:13] <Quintasan> strace -vvfo /tmp/cdrom_id_new.trace -s 1024 /lib/udev/cdrom_id --debug /dev/sr0` is http://paste.ubuntu.com/5858660 . The bug I found was bug #561585
[15:13] <ubot2`> Launchpad bug 561585 in udev (Ubuntu Lucid) "Blank cd/dvd not recognized [LUCID] " [High,Fix released] https://launchpad.net/bugs/561585
[16:16] <rtg> jdstrand, I'll have a look
[16:16] <jdstrand> rtg: thanks! :)
[16:18] <rtg> jdstrand, hmm, I would have expected all netfilter options to have been enabled. I'll look closer.
[16:21] <jdstrand> yeah
[16:21] <rtg> its not like the LOG target is new
[16:22] <Sarvatt> apw: so I'm on 3.10.0-0 that has # CONFIG_NO_HZ_IDLE is not set CONFIG_NO_HZ_FULL=y, i'll verify intel_pstate is still crazy on -2 now
[16:23] <apw> rtg, grouper was missing a few last i looked, that was one of the patches i did, out of date now of course
[16:23] <Sarvatt> ah 3.10.0-2 still has that combo, someone responded on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647/comments/6
[16:23] <ubot2`> Ubuntu bug 1188647 in linux (Ubuntu) "Please change intel_pstate default to disable" [High,Fix committed]
[16:25] <rtg> apw, I thought I normalized all netfilter config options. 'UBUNTU: [Config] Enable and modularize all netfilter matches'
[16:26] <rtg> jdstrand, CONFIG_NETFILTER_XT_TARGET_NFLOG=y for mako
[16:28] <apw> rtg, ahh so you did
[16:28] <jdstrand> rtg: [    0.000000] Linux version 3.4.0-3-mako (buildd@tritons) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-5ubuntu2) ) #13-Ubuntu SMP PREEMPT Tue Jun 25 17:07:54 UTC 2013
[16:28] <jdstrand> rtg: is that too old? ^
[16:29] <rtg> jdstrand, nope, thats current
[16:29] <rtg> jdstrand, maybe I'm looking at the wrong option. 'CONFIG_IP_NF_TARGET_ULOG is not set'
[16:30] <jdstrand> this isn't ulog
[16:30] <Sarvatt> i'm building a kernel with CONFIG_NO_HZ_IDLE=y CONFIG_NO_HZ_FULL=n CONFIG_NO_HZ_FULL_ALL=n to test that guys theory
[16:30] <jdstrand> ufw doesn't support ulog. I was going to, then no one did it for ipv6 and said it was bad or something, and so I said forget it
[16:31] <jdstrand> rtg: my desktop generic kernel has:
[16:31] <jdstrand> CONFIG_NETFILTER_NETLINK_LOG=m
[16:31] <jdstrand> CONFIG_NETFILTER_XT_TARGET_LOG=m
[16:31] <jdstrand> CONFIG_NETFILTER_XT_TARGET_NFLOG=m
[16:31] <rtg> jdstrand, yeah, looks like I missed some
[16:31] <jdstrand> CONFIG_NETFILTER_XT_TARGET_LOG is what we want I'm quite sure
[16:31] <jdstrand> NFLOG is the successor for ULOG
[16:31] <rtg> jdstrand, 'This option adds a `LOG' target, which allows you to create rules...'
[16:31] <jdstrand> ok, cool
[16:43] <ogasawara> apw, rtg: bug 1196597, I've a one line patch to shove in for Saucy, I'll submit the SRU for Raring
[16:43] <ubot2`> Launchpad bug 1196597 in linux (Ubuntu Raring) "nic-modules udeb does not contain the qlcnic driver for Qlogic" [Medium,In progress] https://launchpad.net/bugs/1196597
[16:44] <rtg> ogasawara, ack
[16:44] <rtg> ogasawara, get it in both master-next and unstable for saucy
[16:44] <ogasawara> rtg: just want to make sure I won't mess anyone up if I shove this up
[16:44] <ogasawara> rtg: ack
[16:46] <apw> ogasawara, not touching anything here, shove away
[16:55] <jsalisbury> ##
[16:55] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:55] <jsalisbury> ##
[17:15]  * ppisati -> gym
[17:34]  * rtg -> lunch
[18:25]  * henrix -> EOD
[19:24] <rtg> bjf, is there a Raring bug for 'UBUNTU: [Config] CONFIG_ARM_ERRATA_643719=y' ? Shall I do the same for saucy ?
[19:25] <bjf> rtg, i didn't create a bug. it was a FTBS fix :-(
[19:26] <rtg> huh
[19:26] <rtg> because of a stable update ?
[19:26] <bjf> rtg, yes
[19:26] <bjf> rtg, i forgot to run updateconfigs before submitting
[19:27] <bjf> rtg, i'd have to go look at where it came it
[19:27] <rtg> bjf, no big deal. I just wanna be sure saucy is consistent
[19:27] <bjf> ack
[19:31] <bjf> rtg, it came in the <IP_ADDRESS> upstream stable release  bug 1199100  "ARM: 7752/1: errata: LoUIS bit field in CLIDR register is incorrect"
[19:31] <ubot2`> Launchpad bug 1199100 in linux (Ubuntu Raring) "Raring update to <IP_ADDRESS> stable release" [Undecided,New] https://launchpad.net/bugs/1199100
[19:31] <bjf> just fyi
[19:31] <rtg> bjf, I've got it set in both saucy branches
[20:10]  * rtg -> EOD
[20:46] <hallyn_> apw: just fyi, that sigchld delivery weirdness?  I can't reproduce it in 3.2, 3.5 or 3.7.  (mind you what we found before was a usage bug, but fixing that in lxc didn't help - so it looks like i ws facing one kernel and one userspace bug)
[20:46] <hallyn_> hopefully i don't offend when i say that bisecting ubuntu kernels is something i like to avoid
[20:46] <apw> hallyn_, it is something we all like to avoid
[20:47] <hallyn_> "Bisecting: a merge base must be tested"
[20:48] <hallyn_> so i'm just sort of manually bisecting by Ubuntu-3.7.0-7.15 versions, then i'll try and do upstream git commit (when i can nail down a reasonable ubuntu-ified config)
[20:50] <hallyn_> actually i guess i must be just about there.  3.7..3.8 shouldn't require too much config wrangling
[21:06] <apw> hallyn_, sounds sane
[22:35] <xnox> so grouper kernel is old, such that avahi doesn't work out of the box, and needs it's parameters tweaked for kernels << 3.9.4 or something like that.
[22:36] <ohsix> what.
[22:37] <ohsix> since when does avahi have 'parameters', and since when does it do anything but very basic network access


[05:35] <Mirv> janimo: no I've just run other tests on the desktop so far like Qt Creator
[06:27] <guest123> evening. got a few questions if any one has time to answer.
[06:27] <guest123> having an issue installing trusty on a nexus 4.
[06:27] <guest123> Had saucy installed but went back to android wanted to test trusty and am having issues flashing boot
[06:28] <guest123> verified the md5 and still get invalid boot image. running 4.4.2 currently
[06:28] <guest123> yes its "LOCK STATE - unlocked"
[06:29] <guest123> Got the same error when trying to flash the stock JWR66Y boot loader as well from developers.google.com
[06:38] <guest123>  Writing the most recent bootloader (krt16s) is successful
[06:57] <Jazzy_> hi
[06:57] <Jazzy_> Anyone know which OS of Ubuntu is used to install mobile version?
[06:57] <guest123> any os with android sdk installed
[06:58] <guest123> https://wiki.ubuntu.com/Touch/Install#Manual_Download_.26_Installation
[06:58] <guest123> scroll down to manual install
[06:58] <Jazzy_> I going to install on micromax a100
[06:58] <Jazzy_> Thanks
[06:59] <guest123> np
[07:50] <guest123> am now getting this: [  258.059484] pil pil3: dsps: Failed to locate dsps.mdt
[07:50] <guest123> [  258.059758] dsps_load: fail to load DSPS firmware dsps.
[07:51] <guest123> from dmesg on devices
[07:52] <guest123> from a clean load of 4.4.2 i was able to flash everything. would only boot to a black screen and sit there for ~15 minutes. am now flashing jwr66y and am going ot try installing from there.
[08:00] <varunbhat> guest123: are you using the precompiled images for booting ubuntu touch?
[08:01] <guest123> yes from manual install instructions
[08:01] <varunbhat> Do you have any idea about compiling the images from cyanogenmod images?
[08:03] <guest123> havent done but could figure it out
[08:04] <guest123> booting to a black screen after restoring jwr66y and this: http://pastebin.com/sQ7Agujr
[08:04] <varunbhat> ok.. i have the same issue, the device boots into a black screen and stays in the boot loop.. im not sure how to get the boot logs..could you please point me in the right direction?
[08:04] <guest123> i ran dmesg and got an issue with dsps firmware
[08:04] <guest123> try adb shell while black screen
[08:04] <guest123> then dmesg
[08:06] <varunbhat> it gives me permission denied..
[08:06] <guest123> on dmesg or adb shell?
[08:06] <varunbhat> adb shell
[08:06] <guest123> run as root
[08:07] <guest123> prolly started adb server as root and trying shell as user
[08:07] <guest123> issue with the pre compiled image?
[08:07] <varunbhat> yes tried that.. but somehow the demsg and all system logs are giving me permission errors when i try to read them
[08:08] <guest123> pastebin?
[08:08] <varunbhat> i'm not sure.. that was the reason i was trying to compile the cyanogenmod to ubuntu touch..
[08:09] <guest123> pastebin the errors you are getting
[08:10] <varunbhat> i dont have the device with me now.. would you be available at a later time to help me with the issue?
[08:10] <guest123> probably not but someone will be here im sure
[08:11] <varunbhat> ok.
[08:12] <guest123> what android version was your device on
[08:13] <varunbhat> android 4.1.2
[08:13] <guest123> what device
[08:13] <varunbhat> note 2
[08:14] <guest123> so the issue is in touch ui
[08:14] <varunbhat> it gives me something like this
[08:14] <varunbhat> http://pastebin.com/3jS4zhFr
[08:14] <guest123> run as root?
[08:14] <varunbhat> yes
[08:15] <guest123> try (as root) kill `pgrep adb` && adb
[08:16] <guest123> coming from jwr66y i got a full boot into ubuntu touch, however, no UI
[08:16] <guest123> recognizes power button wakeup and switches the backlight on however no gui
[08:17] <guest123> meh ill wait a couple of days then try again
[08:17] <guest123> assuming the issue gets fixed that is
[08:26] <dholbach> good morning
[08:26] <guest123> morning
[08:27] <guest123> 6 hours behind you here
[08:27] <guest123> so pardon the lag :)
[09:27] <diroots> Hi there
[09:29] <diroots> New to ubuntu touch, I found latest builds, and I noticed the different names for different devices : manta, mako, maguro and grouper, but what is goldfish?
[09:29] <Stskeeps> the emulator in android, typically
[09:30] <diroots> oh ok!
[09:30] <diroots> I was hoping it was a pre-version for nexus 7 flo/deb :'(
[09:42] <Laney> sforshee: did you see my message on friday about the powerd brightness api?
[09:54] <sforshee> Laney: I just saw it a few minutes ago, I was off on friday and travelling over the weekend
[09:59] <Laney> sforshee: okay, the one about getting the current state is more important to me
[09:59] <Laney> (it's a checkbox in the UI)
[10:04] <sforshee> Laney: what state information are you after?
[10:05] <Laney> sforshee: https://wiki.ubuntu.com/Brightness#Phone
[10:05] <Laney> if "auto brightness" is enabled or not
[10:06] <sforshee> Laney: but shouldn't you be _telling_ powerd about the state, since you know the user settings and powerd does not?
[10:06] <sforshee> fwiw autobrightness is always going to be disabled at boot until you tell powerd to turn it on
[10:08] <Laney> the settings application doesn't know if it's 'at boot' or not
[10:08] <Laney> we will tell powerd to turn the setting on or off, but it should also be able to tell us what the current state is
[10:09] <Laney> it's a d-bus api, someone else could have toggled it
[10:09] <Laney> (which is one thing that using properties allows us to have - change notification)
[10:09] <sforshee> Laney: well something is going to have to tell powerd the user settings initially, because powerd doesn't know what to use when it starts
[10:09] <sforshee> there isn't an api to get the current settings, so if it's really needed then it will have to be added
[10:09] <Laney> why don't you store them?
[10:10] <sforshee> why should a system service store user settings?
[10:10] <sforshee> what if different users have different settings?
[10:10] <Laney> then you load the right one
[10:16] <Laney> I'll report a bug
[10:17] <sforshee> Laney: I don't think user settings belong in powerd, but you should take it up with ChickenCutlass if you feel differently
[10:18] <Laney> something needs to set it so that when the phone is restarted the right settings are applied, and there needs to be a way to query the state
[10:22] <ChickenCutlass> Laney, sforshee so from my understanding the settings should live in the settings app.
[10:22] <Laney> what does 'live' mean?
[10:22] <rsalveti> yeah, and it should set the right config once the unity8/user session is started
[10:22] <rsalveti> I'd guess powerd would have it disabled by default, until the user session is fully up
[10:23] <sforshee> rsalveti: correct
[10:23] <Laney> system-settings is an application, not a mechanism for initialising settings
[10:23] <rsalveti> right, not necessarily system-settings
[10:23] <rsalveti> but something else
[10:23] <rsalveti> powerd is a system daemon, shouldn't have to know anything user specific
[10:23] <Laney> I think it'd be a strange design, but at the end of the day what I need is a place to query the current state
[10:25] <Laney> and powerd has to know that to apply the setting, so it seems like it should be on its d-bus api
[10:25] <Laney> initialisation is a separate question I guess
[10:26] <sforshee> Laney: the api could be added to powerd, but at boot the settings are just defaults
[10:28] <sforshee> Laney: so if system-settings asks powerd instead of pulling up the save user settings then the user settings just get reset every time the device reboots
[10:28] <Laney> right, I get that - but something (that's not system-settings) has to initialise it /anyway/
[10:29] <Laney> otherwise the user has the wrong settings
[10:29] <Laney> and at that point powerd knows the value, so can be queried for it
[10:29] <sforshee> so you just hope that something has initialized them with powerd and is giving you back the saved user settings?
[10:29] <sforshee> seems like you should just ask whomever saves the settings
[10:30] <Laney> It's asking powerd about the policy that powerd is applying currently
[10:30] <Laney> hmm, but there's a problem if setUserBrightness isn't going to store its value
[10:31] <Laney> erm, userAutoBrightnessEnable I mean
[10:31] <Laney> sigh
[10:31] <sforshee> Laney: it's not going to store it across reboots
[10:31] <sforshee> it knows the current value it's using
[10:31] <seb128> is that setting an user one or a system one?
[10:31] <Laney> should we just define a gsettings key? someone needs to set it; who's that going to be?
[10:31] <Laney> unity8?
[10:32] <Laney> it's a user setting
[10:32] <seb128> if that's an user setting I guess unity8 should apply the value on session start/store it when it changes
[10:32] <sforshee> yes
[10:33] <seb128> Saviq, ^ wdyt?
[10:33] <Laney> I'm going to define a key and file a Unity8 bug to have it synchronised with powerd
[10:33] <Laney> means less cpp in that panel at least
[10:34] <Saviq> Laney, seb128, sounds fine I think
[10:34] <seb128> Saviq, thanks
[10:34] <Laney> ty
[10:44] <diroots> flo version for multirom : http://forum.xda-developers.com/showpost.php?p=49759813&postcount=308 nice!
[10:47] <sergiusens> changed
[10:56] <davmor2> Morning all
[11:06] <om26er> if I flash ubuntu touch after flashing android 4.4 on the device will radios work ? or should I first go back to 4.3 ?
[11:07] <WebbyIT> om26er, couple of weeks ago I had to go back to 4.3, don't know if now is fixed
[11:07] <ybon> you can just reflash radio with 4.3 (what I've done) after install with 4.4, but it seems better to downgrade properly before
[11:08] <ybon> https://wiki.ubuntu.com/Touch/DualBootInstallation#Android4.4Radio
[11:21] <seb128> mpt, hey
[11:21] <seb128> mpt, https://wiki.ubuntu.com/SoftwareUpdates#Phone ... should the "Install <n> Updates" button be "update" (lowercase)?
[11:27] <brendand> hi, i have a question about low-power states in the phablet image
[11:27] <brendand> which ones are there - how are they entered/when, and do they have any analogue to traditional s3/s4 power states?
[11:34] <mardy> jdstrand: hi! Under apparmor, if an app has access to a symlink file, does it gets access to the symlinked file too (even if normally it wouldn't be able to access it directly)?
[11:43] <FuLgOrE> I'm flashing Ubuntu Touch on my Nexus 5 now :)
[11:45] <mardy> Mirv: hi! I suspect that the reason of the failures with Qt 5.2 (signond and signon-ui, at least) is that Q_ASSERTs were a no-op in the previous builds
[11:46] <mardy> Mirv: did you enable them yourself in Qt 5.2, or is it something we inherit from upstream?
[11:52] <brendand> ogra_, any ideas ^ (my question)
[11:59] <FuLgOrE> it works. just basic, but it works :)
[11:59] <cwayne> FuLgOrE, :_
[11:59] <cwayne> oops, :)
[12:00] <cwayne> FuLgOrE, i've found that pretty much everything works except audio
[12:00] <FuLgOrE> cwayne: I have some trouble with touch screen. sometimes I cannot go back to the homescreen
[12:00] <FuLgOrE> but I made a reboot now
[12:00] <FuLgOrE> and I have trouble to connect to my wifi on the regular way (maybe I edit the config file later)
[12:01] <FuLgOrE> for a 24h old alpha version it works very nice :)
[12:03] <Mirv> mardy: I shouldn't have touched anything related to those. tsdgeos might have bumped into the Q_ASSERT behavior change already possibly. well, hmm, of course it might also matter that as per request the PPA Qt builds are done using debug options to get better backtraces in case of crashes.
[12:04] <tsdgeos> Mirv: well, stuff should not rely on Q_ASSERT being noops :D
[12:04] <mardy> Mirv: most likely that's the case
[12:04] <tsdgeos> nor the other way around
[12:04] <Mirv> mardy: but no other packages seem to have exactly that kind of problem
[12:04] <mardy> tsdgeos: agreed
[12:04] <tsdgeos> Mirv: actually i fixed a bug somewhere about that
[12:04] <tsdgeos> don't remember where
[12:04] <tsdgeos> can check
[12:05] <mardy> tsdgeos: you fixed accounts-qml-module, and now I found another case in signon-ui
[12:05] <tsdgeos> this one
[12:05] <tsdgeos> https://code.launchpad.net/~aacid/qtubuntu-sensors/temporary_open_file/+merge/202874
[12:06] <mardy> tsdgeos: the problem is that the one I found now cannot be fixed, because QtDBus lacks some APIs
[12:06] <tsdgeos> ah
[12:06] <tsdgeos> that one
[12:06] <tsdgeos> yes
[12:06] <tsdgeos> i reached the same conclusion
[12:06] <tsdgeos> sorry i did not report :D
[12:06] <tsdgeos> you have invalid messages
[12:06] <tsdgeos> and you can't really create fake ones
[12:06] <mardy> tsdgeos: yep, to mock an interface
[12:06] <tsdgeos> right?
[12:06] <mardy> tsdgeos: correct
[12:06] <tsdgeos> mardy: that's the outcome of Mirv building the ppa pckages with debug enabled instead of release
[12:07] <tsdgeos> but i think we should still have stuff work on debug
[12:07] <mardy> tsdgeos: I'm filing a bug on QtDBus to see if we can add some specific APIs to enable mocking, but I'm afraid that in the meantime I'll just have to disable the tests
[12:07] <tsdgeos> thing is, that assert seems "too much" to me, i.e. stuff works without the assert
[12:07] <tsdgeos> so why is the assert there?
[12:11] <FuLgOrE> hmm, if I use 'adb shell' I'm directly connected as root. Is that correct?
[12:12] <ogra_> FuLgOrE, right
[12:13] <FuLgOrE> ok
[12:13] <ogra_> we'll drop that soon so you will end up as phablet user and have to use sudo (like on a desktop)
[12:13] <FuLgOrE> ok, good to kno
[12:13] <FuLgOrE> w
[12:15] <FuLgOrE> the phone stays a bit hot, sometimes if I want to type something, some letters are missing and if I go back from somewhere (e.g. dialer) to the home screen, the little preview shows strange things (pixel party :D)
[12:15] <FuLgOrE> but the most things are working
[12:15] <FuLgOrE> very nice :) where can I find the terminal app?
[12:17] <FuLgOrE> and sometimes I have a big vertical stripe in middle/left side of the screen
[12:17] <davmor2> FuLgOrE: under applications?  but there are keys there that aren't working currently known bug that needs fixing
[12:17] <cwayne> FuLgOrE, that's the side-stage messing up.  that's fixed in later versions (with an update to ubuntu-touch-session)
[12:19] <FuLgOrE> cwayne: thx | davmor2: when I tried to enter my wifi password, once I had no "v". the field was working but I couldn't see the letter. when I switched to numbers and back to letters it was okay again
[12:24] <mardy> tsdgeos: FYI: https://bugreports.qt-project.org/browse/QTBUG-36475
[12:24] <mardy> Mirv: meanwhile I'll disable the failing tests, then
[12:25] <Mirv> mardy: ok, makes sense at this point I guess.
[12:27] <FuLgOrE> it looks like unity8 eats 50% cpu
[12:27] <FuLgOrE> o.O
[12:27] <FuLgOrE> 1650 phablet   20   0<PHONE_NUMBER>80  57600 S  48.0  6.1  13:27.13 unity8
[12:45] <boiko> fginther: is there anything wrong with jenkins, or is this something related to dialer-app itself somehow: http://s-jenkins.ubuntu-ci:8080/job/dialer-app-ci/135/
[13:06] <FuLgOrE> brighness control is not working on N5 (just for your information, not important for me)
[13:07] <cwayne> ah
[13:07] <cwayne> FuLgOrE, just confirmed here
[13:07] <Mirv> if anyone (yes, please!) wants to try out seeing the problems and filing bugs for whatever components when running Qt 5.2, one can break his/her Nexus 4 quite well with the instructions at http://pastebin.ubuntu.com/6808355/ -> but Unity 8 will run at least to an extent. ppa-purge (or image updater) works to downgrade.
[13:12] <boiko> Laney: hey, about your MR for telephony-service, is the other MR already landed? I mean the system-settings one
[13:13] <Laney> boiko: no, it's preferred to do them in sync
[13:14] <Laney> if you want to review the code / approach then we can think about landing afterwards
[13:14] <boiko> Laney: ah ok, but is it ready for reviewing/merge already? I just don't want to merge code in telephony-service that might block it from releasing
[13:14] <Laney> seb is reviewing u-s-s ~today
[13:14] <Laney> so comment but not top approve if you want
[13:15] <boiko> Laney: nice! I will review that in a couple hours then (almost lunch time here)
[13:15] <Laney> cool, thank you
[13:15] <FuLgOrE> I sent myself a sms. the sms symbol changed to blue color. but the "lock screen" shows "no data sources available"
[13:17] <ybon> have you enabled stats on settings? just in case ;)
[13:19] <FuLgOrE> ybon: no. do you know where I can get a manual for ubuntu touch? :D I have some simple questions a manual could answer I guess
[13:19] <FuLgOrE> I don't want to bother you guys for nothing
[13:20] <cwayne> FuLgOrE, it's not a bother, you've been quite helpful in fact :)
[13:20] <FuLgOrE> I cannot believe that I was helpful :D I didn't do anything :D
[13:23] <ybon> FuLgOrE: I don't know any use manual, sorry ;) But some says that a device that needs a user manual has a bad UI, so... ;)
[13:24] <ybon> user* manual
[13:24] <ybon> Anyway, the stats on  welcome page settings in on "privacy"
[13:24] <FuLgOrE> thanks
[13:24] <cwayne> wow
[13:24] <cwayne> i didnt even know that
[13:26] <FuLgOrE> cwayne: yes, it's activated
[13:26] <FuLgOrE> german: Status auf dem Startbildschirm :D
[13:29] <FuLgOrE> I'm still searching the terminal app. I saw in settings that it is installed but it's not on one of the home screens
[13:31] <ybon> Elleo: is that you https://twitter.com/mikesheldon ? :)
[13:31] <ybon> re: Canal person hacking Ubuntu Touch ;)
[13:32] <Elleo> ybon: yep :)
[13:32] <ybon> aaaaahh :)
[13:32] <ybon> So I was already following you
[13:32] <Elleo> heh, small world :)
[13:32] <ybon> And so you know Richard from OSM too, right?
[13:32] <shiggitay> rsalveti, are you around?
[13:33] <Elleo> ybon: yeah, I don't know him massively well but we've chatted about canal + OSM stuff in the past
[13:33] <ybon> fun :)
[13:33] <jdstrand> mardy: hi! symlinks are resolved before evaluation, so the actual file is used
[13:34] <ybon> Elleo: I think I remember him pigging both you and me on Twitter about the waterway rendering I'm working on ( http://fluv.io/ )
[13:34] <Elleo> ahh, that was you, awesome
[13:35] <ybon> So, next step, a waterway navigation app on UT :p
[13:35] <Elleo> yeah, I think it was around the time richard mentioned getting locks rendering properly
[13:35] <Elleo> hehe, yeah :)
[13:35] <mardy> jdstrand: OK, so if a click package has a certain file, and uses a click hook to symlink it to a file in ~/.local/share/accounts/services/ (which is supposed to be readable by all click apps), other click apps won't be able to read this, right?
[13:35] <Elleo> I notice your map is missing a lof of UK canals, I wonder if they've been tagged differently
[13:35] <Elleo> lot*
[13:36] <Elleo> well "missing" as in not as highlighted as most
[13:37] <fginther> boiko, It appears to be a transient issue, the failures are caused because the touch device couldn't contact launchpad, but other test runs are passing. I'll experiment a bit
[13:37] <ybon> Elleo: yes, I should investigate
[13:37] <FuLgOrE> each reboot I have to type in my wifi password again. And each time a new config file will be generated (with serial number 1, 2, 3, ...)
[13:39] <boiko> fginther: thanks
[13:42] <FuLgOrE> is there a way to use ssh-server on the UT-phone ootb?
[13:43] <FuLgOrE> I tried "ssh root@ip" and "ssh phablet@ip"
[13:43] <FuLgOrE> both times connection refused
[13:43] <popey> FuLgOrE: adb shell start ssh
[13:43] <FuLgOrE> thx :)
[13:44] <popey> actually
[13:44] <popey> that'll start it as root, you may want a user-started sshd
[13:46] <FuLgOrE> actually it works fine for me!
[13:46] <jdstrand> mardy: right, cause they won't have access to the file in /opt
[13:47] <jdstrand> (or wherever the click package is installed to)
[13:48] <jdstrand> mardy: it will probably need read access to the ~/.local/share/accounts/services/ directory though, so it could potenentially get information from there
[13:48] <Mirv> tsdgeos: ok unity-scope-click was getting uninstalled because ubuntu-purchase-service was not set to recipe build. after that one gets built it's possible the apps start to work. there are still a small handful of packages that need to be uninstalled when upgrading.
[13:49] <jdstrand> mardy: we've tried to minimize info leaks of this sort, but it isn't always possible. In the case of online accounts, it can get a list of account types from the API iirc, so there isn't a real issue there
[13:49] <jdstrand> (correct me if I'm wrong)
[13:49] <Mirv> I also built cordova today which resolved that one and html5 container packages, and I'll continue looking at the remaining problematic packages tomorrow (although I believe most of them are due to qt-videonode)
[13:49] <tsdgeos> Mirv: cool
[13:52] <mardy> jdstrand: the online accounts API to enumerate the providers and services is implemented as a library, so it uses the permissions of the app
[13:52] <mardy> jdstrand: but I think that's fine
[13:52] <mardy> dbarth: ^
[13:53] <FuLgOrE> rsalveti: As you could read before, I flashed UT on hammerhead. At first many thanks for creating that nice image! How can I support you to solve some issues? In which way you would prefer something like a bug report? Or does anybody else from the community have to do that now?
[13:57] <dbarth> mardy: reading the backlog
[13:58] <tsdgeos> mardy: otoh you could have a fake dbus server for your tests, but of course, that's a bit more of a work :D
[13:58] <dbarth> mardy: ok, so we're clear then
[13:58] <dbarth> mardy: objection dismissed ;)
[14:02] <FuLgOrE> ups! Each time I reboot, I will have to set up wifi again. And each time I get a new wifi interface (wlan7 at the moment)
[14:05] <fginther> boiko, I reran the mako test job, this time it executed but hit a dailer-app crash: http://s-jenkins.ubuntu-ci:8080/job/generic-mediumtests-runner-mako/4858/
[14:19] <FuLgOrE> could you please do me a favor and check the ut-mailing list if you got an email from me (Georg Schmitz) with this subject: Re: [Ubuntu-phone] Call for testing: experimental 4.4.2 based images
[14:24] <cwayne> FuLgOrE, i dont see one
[14:25] <FuLgOrE> cwayne: thanks. the chinese internet connection makes me crazy -.-
[14:26] <FuLgOrE> I try it with vpn, brb
[14:31] <FuLgOrE> cwayne: Is my mail there? It should have worked. Damn Internet connection. Sorry for making trouble...
[14:31] <cwayne> FuLgOrE, yep
[14:31] <FuLgOrE> thx :)
[14:38] <FuLgOrE> regarding the "several wlan devices" issue, did that happen on other devices than Nexus 5 as well? Each reboot I have to manually set up the wifi connection and each time I get a new wifi interface
[14:40] <davmor2> FuLgOrE: works fine here on a non 4.4.2 system so might be an issue on that version
[14:41] <dholbach> salut didrocks, do you know when the bot releases a new ubuntu-html5-theme? I think you answered a similar question in the past, but I can't quite remember the answer
[14:42] <didrocks> dholbach: it will be once ubuntu-html5-theme upstream put a new landing ask on the spreadsheet and we assign a slot (and we can promote the next image which isn't the case right now)
[14:42] <dholbach> ok cool, thanks
[14:42] <mardy> kenvandine: any idea on how to coordinate the landing of the app-access branch of u-s-s-o-a with friends-app and other apps using online accounts? (such as the Reminders app)
[14:43] <didrocks> dholbach: yw! :)
[14:43] <dholbach> didrocks, I thought the package uploads to the archive were (sort of) unrelated to things landing on the image
[14:43] <mardy> kenvandine: if the app-access branch lands before these apps get updated, they will still be able to use the accounts they've been using so far, but not any newly-created account
[14:43] <kenvandine> mardy, will landing the app-access branch break any of the apps?
[14:43] <kenvandine> ah
[14:43] <mardy> kenvandine: because by default new accounts will be created with an empty ACL
[14:44] <didrocks> dholbach: they are totally related, we don't want to introduce new regressions if already we can't promote an image
[14:44] <dpm> hey tedg, on this MP, https://code.launchpad.net/~ted/ubuntu-calendar-app/url-dispatcher/+merge/201543 would you mind merging trunk and re-pushing? I'll then top-approve
[14:44] <kenvandine> mardy, is it just friends-app and reminders?
[14:44] <tedg> dpm, Sure
[14:44] <dpm> great, thanks!
[14:44] <kenvandine> mardy, and are they all ready to be merged?
[14:45] <mardy> kenvandine: AFAIK, but I don't really know
[14:45] <dholbach> didrocks, thanks
[14:45] <mardy> kenvandine: no, I didn't propose a branch for the Reminders app yet
[14:45] <kenvandine> mardy, any risk to the desktop?
[14:45] <mardy> kenvandine: I don't think so, this code is not used on the desktop
[14:46] <kenvandine> ok, well lets make sure all the branches are ready to be approved
[14:46] <kenvandine> and get them on the landing plan
[14:48] <cwayne> mardy, should we wait til after it's all landed and confirmed working before we do the click-hooks merge?
[14:49] <mardy> cwayne: good idea
[14:49] <cwayne> yeah, makes sense
[14:49] <cwayne> although there's nothing particularly dangerous about that MR, i'm happy to wait to make sure stuff's working :)
[14:51] <elopio> ping mardy. You are back right? When you have some time, I have some questions about online accounts and autopilot
[14:55] <mardy> elfangor: yep, feel free to ask
[14:55] <mardy> elopio: ops, that was for you ^
[14:55] <mardy> elfangor: sorry for the noise :-)
[14:57] <elopio> mardy: welcome back. I hope you are having a nice time with your child :)
[14:57] <elopio> mardy: I'm trying to start system settings like this:
[14:57] <elopio> $ system-settings online-accounts
[14:57] <elopio> but I get: file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/ListItems/SingleControl.qml:59: Unable to assign [undefined] to bool
[14:59] <tedg> dpm, Updated, also switched to be more like the desktop stuff that had been changed.
[15:00] <mardy> elopio: are there more messages?
[15:00] <dpm> tedg, ah, nice, thanks!
[15:01] <elopio> mardy: http://paste.ubuntu.com/6826589/
[15:01] <elfangor> mardy: no problem :)
[15:02] <mardy> elopio: OK, I tried it just now and I get the same error, which means I'll hopefully fix it soon
[15:03] <timp> mardy: the control has no pressed property?
[15:03] <timp> the SingleControl seems to assume that, but doesn't really check for it
[15:04] <elopio> mardy: OK, I'll file a bug for you.
[15:04] <elopio> mardy: I'm trying to add an ubuntu one account from autopilot to test the click scope. Is there a way to do that with the accounts CLI?
[15:04] <timp> you could work around it by adding the pressed property, or by setting SingleControl.pressed: false
[15:08] <elopio> mardy: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1273262
[15:11] <attente> bfiller, hi
[15:11] <bfiller> attente: howdy
[15:11] <mardy> elopio: thanks
[15:12] <mardy> elopio: yes, you can, using the account-console tool
[15:12] <attente> bfiller, talking with seb128 about if it makes sense to not use the spell-checking-languages key
[15:12] <bfiller> attente: we have no support for it in the code currently
[15:12] <StephenGregory> Hey guys. Is it possible to port Ubuntu Touch to the BeagleBone Black? If so, what steps would be involved? Thanks!
[15:12] <seb128> bfiller, do you plan to support it?
[15:13] <bfiller> seb128: don't think so, the spell checking is tied to the current keyboard language
[15:13] <seb128> bfiller, that sucks :/
[15:13] <bfiller> seb128: so the spellchecker when enabled automtically uses the proper language
[15:13] <bfiller> seb128: not sure of it's value..
[15:14] <bfiller> it will use the active language's dictionary
[15:14] <mardy> elopio: account-console create --help
[15:14] <seb128> bfiller, well, as a french user I'm using azerty layout only, because that's what I'm used to
[15:14] <seb128> bfiller, but I need to write in english all day long because you guys don't want to write french to me :p
[15:14] <elopio> mardy: I gave it a try and got stuck after the login:
[15:14] <elopio> http://paste.ubuntu.com/6826645/
[15:14] <elopio> I suppose I'm missing something.
[15:14] <seb128> bfiller, on my desktop I've english and french dict both available all the time on my azerty layout, since I keep switching languages
[15:14] <bfiller> seb128: yeah that makes sense
[15:15] <bfiller> seb128: so we'll look into adding that then, but definitely don't have it now
[15:16] <bfiller> seb128: shouldn't be too hard I don't think
[15:16] <mardy> elopio: does U1 actually use a different authentication than plain password?
[15:16] <seb128> bfiller, thanks, do you want a bug report for it?
[15:16] <bfiller> seb128: would be good
[15:16] <elopio> mardy: it uses oauth, I think.
[15:17] <mardy> elopio: I think that your paste shows that you got it working: you are successfully reading the password
[15:17] <mardy> elopio: AFAIK, no, but let me double check
[15:17] <bfiller> seb128: and I know supporting the spell checking langs was part of the design, unfortunately thomas didn't implement it that way - so we'll need to do some rework
[15:17] <elopio> mardy: so, maybe it's just that the UI is not showing me the account info.
[15:17] <mardy> elopio: nope, no oauth (see "cat /usr/share/accounts/providers/ubuntuone.provider")
[15:18] <elopio> I'll try to continue the test with this.
[15:18] <mardy> elopio: maybe you just have to enable it (account-console edit 18 --enable)
[15:18] <bfiller> seb128: so basically you want to be able to switch what spell checker you are using and not have that tied to the current keyboard layout, correct?
[15:18] <elopio> mardy: which brings another request. It would be really nice if we expose account-console as a python module, so we can import it and use its methods, instead of run the command.
[15:19] <bfiller> seb128: like french layout with english spell checker dictionary
[15:19] <seb128> bfiller, yes, I think in really most users use 1 keymap (why change when you are used to something) but can type in different language
[15:19] <mardy> elopio: maybe, but if you look at account-console, it's actually just a small script written using the accounts python bindings, so I'm not sure it's worth
[15:20] <seb128> bfiller, right, I write in english/french/german on my azerty layout for example
[15:20] <bfiller> seb128: makes sense
[15:20] <elopio> mardy: hum, I didn't notice that. Ok, so I'll give it a try before asking for a package.
[15:20] <elopio> thank you!
[15:20] <mardy> elopio: yw
[15:21] <bfiller> seb128: one change we'd need to make is decouple the hunspell packages from the keyboard-language plugin packages currently they are deps of the keyboard-language package
[15:21] <FuLgOrE> N5 and USB otg makes a lot of fun :D
[15:22] <bfiller> seb128: actually maybe not, they are all currently installed anyway but mightnot be in the future
[15:22] <bfiller> attente, seb128 : can we land the changes we've already discussed in u-s-s then work on enabling spell-checking-languages next?
[15:24] <bfiller> attente: or just have spell-checking-language always default to the active-lang for now until we add support in the backend
[15:24] <seb128> bfiller, https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1273275
[15:24] <seb128> bfiller, sure, we can land the switch to enable/disable and keep the other options hidden until we get support for those
[15:25] <bfiller> cool
[15:25] <attente> ok, i'll just revert some of those deletions
[15:26] <annerajb> is the 4.4 code up on gerrit?
[15:28] <jgdx> oSoMoN_, \o. You've mentioned switching to oxide in [1]. When do you expect this to happen? https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1269846
[15:30] <oSoMoN_> jgdx, there are high hopes this can happen in time for 14.04, but we’re not exactly there yet, we’ll be sprinting on oxide next week and it should give us a much clearer idea of whether this is doable
[15:30] <oSoMoN> jgdx, short answer: ASAP :)
[15:32] <mterry> Cimi, you are working on the welcome wizard yeah?  I think that merge proposal is in your court right now
[15:32] <Cimi> mterry, currently on preview widgets
[15:32] <jgdx> oSoMoN, okay thanks. :) Good luck
[15:33] <oSoMoN> thx
[15:36] <Wardane> The lastest ubuntu touch daily build is not booting on my nexus 4. All I get is a black screen.
[15:37] <ogra_> which channel do you use ?
[15:37] <ogra_> (trusty/devel is definitely fine here ... )
[15:38] <Wardane> I did a manual flash
[15:38] <Wardane> I probably will just reinstall android and flash it the conventional way
[15:38] <ogra_> hmm, might be that you need to touch /home/phablet/.display-mir for that to work (via adb shell)
[15:39] <ogra_> we havent tested manual in a while
[15:40] <Wardane> Sorry for being a noob but what do you mean by 'touch'?
[15:41] <ogra_> what i wrote :)
[15:41] <ogra_> adb shell touch /home/phablet/.display-mir
[15:41] <ogra_> adb reboot
[15:41] <ogra_> and see if the UI comes up then
[15:41] <Wardane> Got it thank you
[15:42] <ogra_> if that doesnt work, use the normal method via phablet-flash ... that definitely works and gets regular testing
[15:43] <Wardane> Touching /home/phablet/.display-mir worked! Thank you
[15:43] <ogra_> great
[15:43] <ogra_> note that you can not do over the air updates of such an isntall
[15:44] <Wardane> Oh I didn't realize that. I am going to phablet-flash then
[15:48] <davmor2> Wardane: touch is a command that just updates the timestamp on a file or creates an empty file if one doesn't exist in order to update it's timestamp.
[15:54] <Mad_Halfling> Hi, quick question, please - sorry if I'm being stupid, but how do you install apps, now? As I understand it, they should appear as search results, now, rather than there being an explicit app search/install programs, correct? If so, then I don't seem to be able to find any - I've got the Click Packages enabled, am on 14.04 r144 and have internet connectivity as the music app just updated.  Does anyone have any new apps I c
[15:54] <kenvandine> tedg, how will upstart_app_launch_start_multiple_helper deal with apps with SingleInstance=true in the .desktop file?
[15:55] <tedg> kenvandine, It doesn't know anything about desktop files, so it'll ignore it.
[15:55] <ogra_> barry, bug 1273288 for you :)
[15:55] <kenvandine> tedg, great
[15:55] <ogra_> (and probably seb128 too, not sure where the thing should be blocked)
[15:55] <tedg> kenvandine, untrusted helpers are indepenent there.
[15:56] <barry> ogra_: thanks, looking
[16:00] <seb128> ogra_, is that a supported usecase/scenario?
[16:01] <ogra_> seb128, developer mode is supposed to get a UI switch at some point (and i guess also a switch to make the img rw), once this is set, OTA should be disabled
[16:02] <seb128> ogra_, I've been using image updates with rw one for a while, seems to work fine?
[16:02] <seb128> ogra_, what is "OTA" btw?
[16:02] <ogra_> seb128, the cdimage images/zip installs are indeed not a supported usecase, but all ports currently (and likely for a while) use this install method ... which means they all get this behavior
[16:02] <ogra_> seb128, Over The Air updates :)
[16:02] <OttOmanTR> over the air updates
[16:02] <OttOmanTR> :)
[16:03] <seb128> ogra_, well, I'm fine having a spinner just spin on non supported images, but if you can support from the backend to check for those case and a design I'm fine doing the UI changes
[16:03] <seb128> ogra_, I'm not going to go out of my way to do that though, ETOOMUCHTODO already without trying to solve non supported cases
[16:03] <ogra_> seb128, they replace parts of the system ... if you made changes that gets you weird results ... (install htop in a rw image, do an upgrade, then do dpkg -l htop .... you will notice htop is gone from the dpkg db ... but the binary is still there)
[16:04] <ogra_> seb128, ok, i'll stop filing bugs then
[16:04] <FuLgOrE> regarding each reboot=new interface (Nexus 5): it always changes the mac-address
[16:04] <seb128> ogra_, right, that works fine enough for my usecase (installing new settings to test them)
[16:04] <OttOmanTR> ogra_: Are you just a volunteer or you're from Canonical?
[16:04] <seb128> ogra_, if I had to redownload/do a new install every day I would be really annoyed (or stop testing on the device and keep the image ro)
[16:04] <ogra_> OttOmanTR, i'm working for canonical
[16:05] <ogra_> seb128, well, it will eventually break if you do OTA upgrades over a rw image ... note that i didnt say it needs to be fixed soon or anything ...
[16:05] <OttOmanTR> ogra_:  I appreciate your work guys, thanks a lot to the team
[16:06] <ogra_> but well, bugs seem to not be wanted ... i thought it might help to have it noted down
[16:06] <ogra_> (on a sidenote i filed it on request of one of the download-manager devs sitting here at the table)
[16:07] <seb128> ogra_, it's not that bugs are not wanted, but as said we have too much to do atm ... anyway, set it as wishlist let's see if we ever get to it ;-)
[16:08] <FuLgOrE> http://paste.ubuntu.com/6826897/ <-- dmesg | grep wlan
[16:09] <FuLgOrE> I think I got it
[16:09] <FuLgOrE> [    1.805180] bcm_wifi_get_mac_addr: Failed to get information from file /persist/wifi/.macaddr (-2)
[16:10] <FuLgOrE> the path /persist doesn't exist...
[16:10] <ogra_> rsalveti, ^^
[16:11] <FuLgOrE> this image is RW. could somebody cat me the information from /persist/wifi/.macaddr?? :D
[16:11] <FuLgOrE> I will inform rsalveti via mail later
[16:12] <FuLgOrE> than I hopefully get my wifi working, without typing the password every time. that makes me crazy :D
[16:13] <FuLgOrE> wlan936 also makes me crazy :D
[16:14] <FuLgOrE> or /etc/udev/rule.d/70-persistent-net.rules = 50mb is also strange ;-)
[16:14] <FuLgOrE> I'm just joking...
[16:29] <Wardane> How do you take a screenshot?
[16:30] <ybon> phablet-screenshot from your desktop :)
[16:31] <ybon> (when your devide is plugged in, of course ;) )
[16:32] <Wardane> Perfect thank you
[16:36] <ogra_> rsalveti, bug 1273308
[16:43] <boiko> fginther: trying to check what's in the backtrace
[17:12] <Laney> seb128: where do we put shared components in u-s-s?
[17:12] <Laney> we had the SettingsCheckEntry before but I forgot where it was - can you remember?
[17:13] <seb128> Laney, https://code.launchpad.net/~laney/ubuntu-system-settings/remove-settingscheckentry/+merge/188320
[17:13] <seb128> Laney, src/SystemSettings in seems
[17:13] <seb128> it
[17:13] <Laney> oh ok
[17:13] <Laney> we had them compiled in
[17:14] <Laney> ah no, that isn't
[17:14] <Laney> nod
[17:25] <auro> Hi, is there a seperate forum for Nexus 7 issues or this is it?
[17:32] <ogra_> auro, this channel is for all ubuntu touch related issues ...
[17:35] <auro> orga_, my first time on IRC. I used the ubuntu touch instructions and bring it up on 13.10 on Nexus 7. Is a 8GB machine. I wanted to report some behaviour.
[17:37] <attente> dpm, kalikiana, i've run into a hiccup trying to get the dynamic language switching to work across the entire device
[17:38] <attente> mainly there's seems to be an issue with apps in general being unable to access the user's language through accountsservice (permissions problem it seems)
[17:38] <dpm> hi attente, oh, what was it?
[17:38] <dpm> oh
[17:40] <attente> in accountsservice, a call to sd_pid_get_session() is made which returns EACCES
[17:51] <hedz09> Hey guys. Is it possible to port Ubuntu Touch to the BeagleBone Black? If so, what steps would be involved? Thanks!
[17:54] <popey> hedz09: have you seen the porting guide?
[17:55] <popey> hedz09: https://wiki.ubuntu.com/Touch/Porting
[17:57] <hedz09> Yes, I've seen it but Cyangenmod hasn't been ported yet to the Beaglebone Black (not that I'm aware of).
[18:05] <hedz09> Looking for some advice from those experienced with porting on where to start.
[18:10] <popey> hedz09: that might be a problem then
[18:18] <boiko> Laney: where can I get accountsservice-ubuntu-touch-schemas from to test your changes?
[18:32] <hedz09> Trying to port Cyangenmod would be the first step?
[18:43] <balu360> please help to install for 1777
[18:49] <labsin> popey, Could you try my app again? http://ubuntuone.com/2ECSspw1A5N1RwKdcTh1BM
[18:50] <popey> labsin: sure thing!
[18:51] <wardane> Can anyone give me  a link or tell me how to install a click package to Ubuntu Touch?
[18:52] <achiang> what do we use these version tarballs for? https://system-image.ubuntu.com/devel/mako/
[18:52] <achiang> cwayne: ^^
[18:52] <popey> wardane: adb push foo.click /tmp
[18:52] <popey> wardane: adb shell sudo -u phablet pkcon install-local /tmp/foo.click
[18:53] <wardane> Thank you
[18:53] <popey> labsin: http://paste.ubuntu.com/6827786/ that looks unwell
[18:53] <cwayne> achiang, IIRC it's always unpacked on top of the rootfs, and contains just the version info
[18:53] <cwayne> stgraber, ^
[18:54] <labsin> popey, It was a test to add qml modules. It works on the desktop in confinement -.-
[18:55] <labsin> I'll try the emulator
[18:55] <popey> labsin: sorry
[18:56] <labsin> popey, no problem. Is qmlscene totally different on the phone?
[18:56] <cwayne> cyphermox, https://code.launchpad.net/~cwayne18/ubuntu/trusty/lxc-android-config/pretty-hostname/+merge/203400
[18:57] <popey> labsin: we may want to move to #ubuntu-app-devel
[18:58] <achiang> cwayne: right, but... why?
[18:58] <achiang> cwayne: this is just part of understanding more about the overall system architecture
[19:02] <achiang> ondra: do you know why? ^^
[19:04] <cwayne> achiang, sorry, digging through logs, i think i saw stgraber explain it once
[19:06] <achiang> cwayne: like... i'm kinda curious why it can't be part of one of the other existing tarballs.
[19:07] <achiang> cwayne: i could go look at the system-image code again. maybe that will explain
[19:09] <achiang> cwayne: mmm... i think i'll wait for you to dig out of logs, or for stgraber to just shed some light ;)
[19:12] <cwayne> achiang, i *think* it's so that it's autogenerated, and is always part of an OTA update
[19:13] <achiang> cwayne: interesting
[19:14] <cwayne> so if any of the other tarballs changed, a new version.tar.xz is created, to make sure those files are always accurate
[19:18] <achiang> cwayne: that's a plausible theory :)
[20:21] <Sprotni> Hi! Speak Hungarian?
[20:24] <Noskcaj> !hungary
[20:47] <shiggitay> kutya fazs.
[21:49] <a_muva_> I get this: (pkcon:2938): GLib-CRITICAL **: Source ID 3519 was not found when attempting to remove it
[21:49] <a_muva_> Fatal error: Error while installing package: unable to make backup link of `./lib/udev/rules.d/70-android.rules' before installing new version
[21:50] <a_muva_> Can someone tell me what's wrong?
[21:52] <w-flo> a_muva_, when do you get this? generally you shouldn't use deb packages when dealing with ubuntu touch unless there's a good reason to do so
[21:54] <a_muva_> w-flow: I tried pkcon refresh, and pkon update
[21:55] <a_muva_> I guess I shouldn't  upgrade like that
[21:55] <popey> yeah
[21:55] <a_muva_> Ok thanks
[21:55] <w-flo> use image-based upgrades instead (from system-settings app or "system-image-cli" command line tool)
[21:55] <popey> update manager for apps updates
[21:55] <popey> or system settings -> updates, for system image updates
[21:56] <popey> or system-image-cli as w-flo says
[22:05] <Tassadar> Can I somehow get to the shell in android's container? There was some script, "android-chroot" or something like that, but I can't find it anymore
[22:08] <w-flo> Tassadar, yes..I think it was something like lxc-console -n android
[22:08] <w-flo> and some magic key combo (screen-like) to leave the container environment
[22:10] <Tassadar> yeah, that says it connects to tty1 of that container, but the shell isn't there (it doesn't respond to any command)
[22:11] <Tassadar> "lxc-console -n android --tty 0" is the right one
[22:11] <Tassadar> thanks
[22:11] <w-flo> ah. /me hopes to finally remember the arguments list now
[22:12] <Tassadar> or just echo "lxc-console -n android --tty 0" > /usr/local/bin/android-chroot, so that it is like before ^^
[22:12] <w-flo> heh, someone should definitely add that to the rootfs :)
[22:13] <Tassadar> w-flo: by the way, the reason why it took so long for adb to start on n5 is kinda funny
[22:14] <Tassadar> init tries to write some debug/info messages to "console", which is serial console during boot
[22:15] <Tassadar> but when nothing is connected to physical UART on the device, the driver in kernel will try to write to it and timeout after 30s
[22:16] <w-flo> that makes sense.. difficult to find out for sure (unless there's some "time out waiting for ..." message in dmesg)
[22:17] <Tassadar> I have the HW-thingy (just a voltage converter) to communicate with UART on N5, so I can just connect it, and it no longer hangs
[22:17] <Tassadar> (UART is inside of headphones jack on nexus devices, quite handy indeed)
[22:18] <Tassadar> and the "fix" is to set console=tty0 instead of console=ttyHS0somethingserial in cmdline
[22:18] <w-flo> that's cool... since I don't have hardware like that (and I'm not sure where/if I'd connect it to the HTC vision) I had to figure out early boot issues blindly :)
[22:20] <w-flo> I remember there was some issue with console, too.. resulting in a boot loop. a missing kernel option for VT_CONSOLE or something like that
[22:20] <Tassadar> if there is something I'd want to hug google engineers for, it's that serial console - it is usually just on some pins on the board, or not even that, and they put it directly into the headphones jack, so I don't have to even disassemble it)
[22:20] <w-flo> yeah that sounds look a very good feature
[22:21] <w-flo> uhm.   I should do texts next, I think that's a separate code path
[23:43] <boiko> mterry: yes, the code for it is in the indicator/ folder