[00:00] <plars> asac: yeah, camera is very crashy... just taking a picture crashed it here
[00:02] <plars> asac: phone/sms works though
[00:08] <asac> plars: so camera is a real regression over what is in RO daily?
[00:09] <plars> asac: appears to be, yes
[00:09] <plars> asac: both maguro and mako failed twice in a row on it
[00:09] <plars> asac: previous images didn't
[00:11] <lool> asac, plars: Problem is that the directory has wrong permissions now
[00:11] <lool> it's read-write, but not usermetrics:usermetrics
[00:11] <lool> stgraber: ^
[00:14] <slangasek> sergiusens, lool: Debian bug #722045 for dh-python :any support; it's a rather big change which I haven't had a chance to test very broadly yet, so I'm hoping to get some feedback on it from Debian before pushing into saucy
[00:15] <asac> lool: which one?
[00:15] <asac> the camera?
[00:15] <asac> lool: did that regress from daily?
[00:15]  * asac had crashes on that as well in retrospect
[00:15] <asac> lool: note: in automation we use RW
[00:17] <lool> asac: it's the same thing I discussed earlier
[00:17] <lool> slangasek: thanks!
[00:17] <lool> asac, plars, sergiusens, stgraber: I've confirmed that "just" fixing the permissions of /var/lib/usermetrics to usermetrics:usermetrics works
[00:18] <lool> but I don't know how to do that properly in the initramfs
[00:18] <asac> lool: but when did that sneak in?
[00:18] <lool> asac: it's in the r/o images
[00:18] <asac> so the camera app is not a regression over latest daily?
[00:19] <lool> asac: It couldn't work with read-only images IMO
[00:19] <lool> I couldn't test on grouper since it doens't work there with frontcam for some reason
[00:19] <lool> but on mako, the directory permissions prevented it from working
[00:19] <Gsport> can i run ubuntu on a firefoxOS phone?
[00:20] <asac> lool: since THIS build
[00:20] <asac> we see crashes in automation for camera
[00:20] <asac> i think it never worked on RO
[00:20] <lool> how do they look like?
[00:20] <asac> so i guess it doesnt matter
[00:20] <asac> red
[00:20] <asac> lool: http://reports.qa.ubuntu.com/smokeng/saucy/image/4041/camera-app-autopilot/
[00:21] <asac> mediascanner crashed
[00:21] <asac> and of coruse that was let in
[00:21] <asac> so sigh
[00:21] <asac> thats the explain
[00:21] <Gsport> in what phone are you running ubuntu on?
[00:23] <slangasek> Gsport: http://wiki.ubuntu.com/Touch/Devices
[00:23] <asac> plars: lool: so i guess we can pack our things :)
[00:24] <asac> mediascanner would need a backout
[00:24] <asac> would take another half day
[00:24] <lool> does know why it crashed?
[00:24] <asac> lool: sure there was an update
[00:24] <asac> small/safe patch
[00:25] <asac> we let that in for thsi build
[00:25] <asac> 100% sure its that
[00:25] <asac> https://launchpad.net/ubuntu/+source/mediascanner
[00:25] <plars> is that libmediascanner-1.0-1:armhf or grilo-plugins-0.2-mediascanner:armhf? or both?
[00:25] <asac> plars: try both
[00:25] <asac> plars: but it wont fix it locally
[00:26] <asac> plars: in RO mode
[00:26] <asac> only in automation
[00:26] <asac> plars: RO is said to never have worked
[00:26] <asac> not sure if I want to go back
[00:26] <asac> we could then argue we ignore because it doesnt matter
[00:26] <asac> but you said that camear worked for you
[00:26] <asac> in previous build
[00:26] <asac> :)
[00:26] <asac> it didnt work for me though
[00:27]  * asac installs the previoyus image again
[00:27] <asac> folks were claiming that it worked for them
[00:27] <asac> but i never saw it working
[00:28] <asac> lool: plars: so i am tempted to publish this if the camera app never worked
[00:28] <asac> and sergiusens confirms that he uploads the fix above
[00:29] <asac> (e.g. fix RO)
[00:29] <asac> and we backout mediaservice somehow
[00:29] <plars> asac: I can try the previous image locally
[00:29] <asac> try mako
[00:29] <asac> i will try maguro
[00:29] <slangasek> I saw the camera working, but half the time I had my rootfs in read-write mode, and I've also seen my camera *not* working, wiw
[00:29] <plars> asac: I'm flashing it now
[00:29] <slangasek> f
[00:29] <plars> I won't put it in rw mode
[00:30] <lool> asac: getting a bt
[00:31] <asac> how can we backoutt he mediascanner change?
[00:31] <asac> https://code.launchpad.net/~mediascanner-team/mediascanner/trunk
[00:31] <asac> revert commit?
[00:31] <asac> :)
[00:31] <asac> inserve MP
[00:31] <asac> inverse
[00:35] <lool> asac: https://bugs.launchpad.net/mediascanner/+bug/1221984
[00:36] <lool> asac: Yes, bzr merge -r latestrev:previousrev
[00:36] <asac> lool: i somehow feel we just decide to let camera regreess in the RW images
[00:36] <asac> i am sure it worked before and now it will crash :)
[00:36] <asac> not good
[00:36] <lool> asac: video never worked for me if it's any confort
[00:37] <asac> err
[00:37] <asac> i am talking about photos :)
[00:37] <lool> I know  :)
[00:37] <lool> ok, really heading off now
[00:37] <asac> yeah i think we wont push this
[00:37] <asac> bad luck
[00:38] <asac> very depressing, but sometimes you just don't get lucky
[00:39] <asac> plars: sergiusens: so no go i guess. too late, too many problems. better not bust RW for those that were fortunate and didnt go to RO yet
[00:39] <asac> and more testing is just no time :)
[00:41] <Jagst3r15> will the ubuntu touch core apps become desktop core apps as well?
[00:41] <plars> asac: I am not quite to a booted ro image, but at the very least it got worse in rw mode
[00:47] <asac> plars: yeah the RO daily doesnt work camera hera
[00:47] <asac> so given that we risk regression what works its not a good deal
[00:47] <asac> RW will be a safe habour at least :)
[00:47] <asac> so good night:)
[00:54] <plars> camera seems to work on yesterdays ro daily
[00:55] <plars> for me on mako
[00:59] <AskUbuntu> nexus 4 bootloader only | http://askubuntu.com/q/342391
[02:51] <AskUbuntu> phablet-flash: error: too few arguments | http://askubuntu.com/q/342412
[07:51] <AskUbuntu> Ubuntu Touch not waking after standby and not booting after reboot | http://askubuntu.com/q/342483
[08:01] <Vic> yo
[09:42] <Bons> Hi there, can maybe someone help me with a flash command, i want to test the ubuntu touch for the first time on my nexus 7 WIFI only (2012), and i followed the wiki, everything goes well but one command that is specified on the wiki fails, maybe i running it wrong ?
[09:48] <asac> jppiiroinen: see mail
[09:48] <asac> jppiiroinen: i asked for a backout of mediascanner
[09:49] <asac> the last commit causes crashes and blocked us from releasing a critical fix last night
[09:49] <asac> :)
[09:49] <asac> thanks
[09:50] <lool> asac: hmm not 100% it's the last commit
[09:50] <asac> lool: it was only one commit that landed
[09:50] <lool> so this morning I tried to use the app scope on n4, and it was completely broken
[09:50] <lool> like search field at wrong place, no results
[09:50] <asac> lool: http://bazaar.launchpad.net/~mediascanner-team/mediascanner/trunk/revision/380
[09:50] <lool> then app scope didn't show any apps anymore
[09:50] <asac> thats the commit that landed
[09:51] <lool> so I pressed power button to shutdown
[09:51] <lool> but the device doesn't come back up...
[09:51] <lool> I might have mounted it rw, in which case it's my bad I guess
[09:51] <lool> would like to know how to check this though
[09:51] <lool> like, seeing boot log
[09:51] <asac> hmm. not sure :)
[09:51] <asac> i know the click/app scope was always a bit problematic
[09:52] <asac> throughout the whole day
[09:52] <lool> asac: yeah, I had seen the commit from the launchpad diff of the last upload, and the backtrace I extracted from the .crash didn't look the same
[09:52] <lool> https://bugs.launchpad.net/mediascanner/+bug/1221984
[09:52] <asac> lool: but tahts the only change and its now reproducible
[09:52] <asac> it must be that
[09:52] <lool> asac: yeah, I had the same impression in the last weeks (click scope)
[09:52] <asac> so even if unsure i would throw it out
[09:55] <asac> unity-webapps-qml:armhf from 0.1+13.10.20130904.2-0ubuntu1 to 0.1+13.10.20130907-0ubuntu1
[09:55] <asac> that landed in 07 imge
[09:55] <asac> i am not sure
[09:55] <asac> how that lands
[09:55] <asac> but i thought it wouldnt
[09:55] <asac> as we turned off all publishing
[09:55] <asac> http://people.canonical.com/~ogra/touch-image-stats/20130907.changes
[09:55] <asac> lool: so
[09:55] <asac> the whole boost stack got landed yesterday
[09:55] <asac> hell :)
[09:55] <asac> http://people.canonical.com/~ogra/touch-image-stats/20130906.1.changes
[09:56] <asac> so most likely it snot mediascanner alone
[09:56] <asac> but this stuff
[09:56] <asac> i thought we were in beta freeze
[09:59] <lool> asac: the boost changes don't look like they would cause bugs, but a bunch of uploads for small errors https://launchpad.net/ubuntu/+source/boost1.53/+changelog
[09:59] <asac> still worrying that folks did mass uiploads like this
[09:59] <asac> xnox: from now on please dont upload without talking here :)
[09:59] <asac> thx
[10:00] <DanielBeck> Hello! I'm the developer of the RSS Feed Reader "RamSamSam Reader" (Ubuntu App showdown). I wanted to ask for help: I want to know if the application adheres to the user interface guidelines and how I could improve the user interface.
[10:00] <asac> lool: i guess the experiemnt "lets see if we can get stuff under control" failed :)
[10:00] <lool> asac: the latest upload seems to be really minor; bdep fix, and prior to that control fix; no change in functionality of the provided packages
[10:00] <asac> so lets open floodgateds again on monday and cross our fingers until we have our engine improved so we can be in control about _all_ landings
[10:00] <asac> lool: i dont know
[10:00] <asac> everything seems minor
[10:00] <lool> asac: we have to root cause the regression before assigning blame IMO
[10:01] <asac> sure
[10:01] <asac> thats why i now looked at the whole change set
[10:01] <asac> lool: its not blaming... just told xnox to not upload anymore without coordinating with image producers
[10:01] <asac> i blamed the otherse - maybe falsly - because it was mediascanner we promoted
[10:01] <asac> as a "safe" landing
[10:01] <asac> and it crashes
[10:02] <asac> just tried to figure if they were not the cause
[10:02] <asac> and found the big boost update
[10:02] <asac> :)
[10:02] <lool> it's not big though
[10:02] <asac> lots of packages
[10:02] <lool> it's a lot of packages in the list
[10:02] <lool> but it's a minor change
[10:02] <lool> which we should be confortable doing
[10:03] <lool> can't have people come here for obvious minor fixes, wont scale
[10:03] <lool> maybe if you had a pager it could scale
[10:03] <lool> ;-)
[10:04] <lool> in other news, I cant find the branch of ubuntu-download-manager anymore
[10:04] <lool> it says Vcs-Bzr: https://code.launchpad.net/~ubuntu-system-image/ubuntu-system-image/downloader
[10:06] <asac> yeah, i knwo its ultimately all about not having any testing upstream :)
[10:07] <asac> lool: https://launchpad.net/ubuntu-download-manager probably here now?
[10:09] <asac> lool: oh 28:20130906.1:20130906.1
[10:09] <asac> thats the last proposed he had on ro?
[10:09] <asac> its weird because the last in touch is 20130906.3
[10:09] <asac> anyway :)
[10:10] <asac> lool: because here the camear is working: http://reports.qa.ubuntu.com/smokeng/saucy/image/4038/
[10:11] <asac> lool: guess we really didint test the latest yesterday night :)?
[10:13] <asac> ok so installed paending RW and camera clearly crashes
[10:13] <asac> now backing out media stuff
[10:15] <asac> lool: odd i installed just cdimage-touch and its not RW anymore
[10:15] <asac> W: Not using locking for read only lock file /var/lib/dpkg/lock
[10:15] <asac> E: Unable to write to /var/cache/apt/
[10:15] <asac> E: The package lists or status file could not be parsed or opened.
[10:16]  * asac installs one more time
[10:30] <asac> lool: so for sure using phablet-flash cdimage-touch doesnt give me a rw install anymore :)
[10:32] <sergiusens> asac: do a --bootstrap
[10:32] <sergiusens> asac: or --wipe
[10:32] <asac> ok
[10:32] <asac> will try :)
[10:33] <asac> err the latest RW pending one
[10:33] <asac> has the old mediascanner packages still
[10:33] <asac> oddish
[10:35] <asac> sergiusens: both options will delete $HOME?
[10:37] <asac> lool: check all the crashes we see since yesterdays image
[10:37] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/image/4038/
[10:37] <asac> like every test has something crashing
[10:37] <asac> you see the increase here: http://reports.qa.ubuntu.com/smokeng/saucy/touch/
[10:37] <asac> it started with 20130906.3
[10:37] <asac> but I CANT FIND a .3 :)
[10:37] <asac> at all
[10:37] <asac> neither in ogras changes
[10:37] <asac> http://people.canonical.com/~ogra/touch-image-stats/
[10:38] <asac> nor in the RO image version
[10:38] <asac> which was always .1
[10:38] <asac> how confusing
[10:38] <asac> how confusing :)
[10:39] <asac> ok its the unity click store
[10:39] <asac> its ALWAYS crashing :)
[10:40] <asac> lool: ^^
[10:40] <asac> that came in through unity-scope-click from 0.1+13.10.20130903-0ubuntu1 to 0.1+13.10.20130906.1-0ubuntu1
[10:41] <asac> i dfont know how that came in
[10:41] <asac> thoguht it would have gone through daily-release
[10:44] <sergiusens> asac: yes, both... sorry, was catching up with backlog
[10:46] <asac> hey its SAT :)
[10:47] <sergiusens> it is, and I have to get ready for travel, full 16 hours on a plane or in between airports, somehow this flight plan is 6 hours shorter than usual
[10:47] <asac> so guess unity-scope was this change http://bazaar.launchpad.net/~ubuntuone-hackers/unity-scope-click/trunk/revision/43
[10:48] <asac> sergiusens: hehe.. yeah. see you in boston
[10:48] <asac> dont worry :)
[10:48] <lool> asac: lol
[10:48] <asac> i wanted to write slides
[10:48] <lool> asac: there was also a download manager update
[10:48] <lool> asac: where are you?
[10:48] <asac> lool: at home
[10:48] <asac> tomorrow flying
[10:48] <asac> (i hope it was not today :))
[10:49] <sergiusens> asac: I always get that feeling too
[10:49] <sergiusens> asac: I have to be at the airport at 2AM, so I still have time btw
[10:49] <sergiusens> just seeing if I'm flying all ARM or taking an x86 too
[10:50] <asac> lol
[10:50] <asac> sergiusens: take an x86
[10:50] <asac> :)
[10:51] <asac> its odd... i thought nothing would go into the archive, but unity-click-scope made it
[10:51] <sergiusens> asac: you don't like arm? A chromebook is what I was talking about, not just tablets btw ;-)
[10:51] <asac> sergiusens: i like armrests in the plane ... if i can conquer them :)
[10:52] <sergiusens> asac: lol
[11:05]  * asac goes off to barber
[11:43] <lool> sergiusens: https://code.launchpad.net/~lool/phablet-tools/static-checkers/+merge/184432
[11:45] <rah> "you'll need the Ubuntu preinstalled image besides the one you're going to build with the instructions below."
[11:45] <rah> https://wiki.ubuntu.com/Touch/PortingFlippedInProgress
[11:45] <rah> for what?
[11:45] <rah> what am I supposed to do with them?
[11:45] <rah> they aren't mentioned in the porting guide
[11:49] <OrokuSaki> I have 'apparmor switch' line removed from click-applications.conf, and it doesn't seem to allow me to execute a click app.... Is that right?
[12:02] <OrokuSaki> I will just go for an upstart session that: sed "s/aa-exec.*-- //g" /home/phablet/.local/share/applications/*.desktop
[12:14] <sergiusens> OrokuSaki: look at the override file
[12:17] <sergiusens> lool: do you want to add phablet-flash to the files to check?
[12:17] <sergiusens> et.al.
[12:20] <sergiusens> slangasek: manually install python:any (if not python:armhf was picked up by default), changing the glib2.0-dev dep to python:any allowed me to fully install libnotify-dev:armhf
[12:22] <rah> what should I do with the Ubuntu preinstalled images?
[12:23] <rah> I have a system.img, boot.img, etc
[12:47] <paulabinasr> hello
[12:47] <paulabinasr> i am trying to install touch on a galaxy 10.1
[12:48] <paulabinasr> i have been through the tutorial and everything installed properly
[12:48] <paulabinasr> only problem is that android boots and not ubuntu
[12:49] <paulabinasr> i have used the pre-installed image under daily build touch (which is Saucy by now)
[12:49] <paulabinasr> should i have used the phablet-touch-preview ( which is old )
[13:00] <zeta> Русские есть?
[13:01] <zeta> hello
[13:05] <zeta> I am from Russia. I would like to find out firmware for Acer A700/7001?
[13:19] <mzanetti> zeta: https://wiki.ubuntu.com/Touch/Devices
[13:20] <mzanetti> https://wiki.ubuntu.com/Touch/Devices/a700
[13:24] <CRD> getting the following error: E: Package 'python-lzma' has no installation candidate ubuntu@ubuntu:~$ sudo add-apt-repository ppa:phablet-team/tools You are about to add the following PPA to your system:
[13:45] <CRD> where to get Python? The following packages have unmet dependencies:  phablet-tools : Depends: python-lzma but it is not installable                  Recommends: ubuntu-dev-tools but it is not installable
[13:46] <asac> sergiusens: so --wipe made my system now boot to busybox only
[13:46] <asac> i assume that means i need to start from scratch?
[14:05] <asac> lool: i am still super confused about the versioning:)
[14:05] <asac> lool: actually not
[14:05] <asac> i think... its just the dashboard that tricks me it seems
[14:21] <asac> so for me the camera works well on maguro
[14:21] <asac> rw latest
[14:21] <asac> interesting that we are so crashy then on the dashboard
[14:21] <asac> hehe
[14:22] <asac> plars: any idea why the 07 build isnt showing up?
[14:22] <asac> the touch_ro?
[14:22] <lool> sergiusens: Pushed r196, with love
[14:25] <lool> asac: system-image crontab got disabled
[14:25] <lool> asac: I think it was in manual mode friday evening, and we forgot to reenable it
[14:29] <lool> asac: I'm not confortable enough ensuring the right flags are set there, I'll mail stgraber
[15:03] <asac> lool: oh ... but the other images continue?
[15:03] <asac> thats interesting :)
[15:20] <nik90_> Do any of you guys know how to access the value of an enum variable?
[15:20] <nik90_> I am referring to http://paste.ubuntu.com/6075061/
[15:21] <nik90_> This is the alarms API provided by the SDK
[15:23] <netcurli> http://qt-project.org/doc/qt-5.0/qtqml/qml-enumeration.html
[15:24] <lool> asac: I think it was put into manual mode to generate the new daily-proposed channel
[15:27] <nik90_> netcurli: reading now. thnx
[15:31] <nik90_> netcurli: I understand there is a <Type> and <value>. I was able to assign text to a variable. So that variable got that respective enum value.
[15:31] <nik90_> netcurli: However I want to do the reverse. Which is from the enum value, I want to get the type
[15:32] <nik90_> netcurli: so in the code I pasted, I set the day to be Alarm.Monday which has enum value 0x01. When reading it now, I get the result 1. How do I translate that back to Alarm.Monday?
[15:34] <netcurli> nik90_: I don't know if you can do that without an explicit function for that
[15:35] <nik90_> netcurli: ah so I will have to create a function with switch cases to get back to Alarm.Monday? that's a pity
[15:38] <fcole90> hello, I need some help working on the N80xx series tablet :)
[15:39] <fcole90> after the first boot, the following won't lead to a working envirorment..
[15:40] <netcurli> nik90_: does something like Alarm.DayOfWeek(1) work?
[15:41] <mamenyaka> ogra_, hi, got a moment?
[15:44] <mamenyaka> sergiusens, can you help me a little?
[15:45] <nik90_> netcurli: will try now
[15:48] <rah> what should I do with the Ubuntu preinstalled images?  I have system.img, boot.img, etc.
[15:53] <nik90_> netcurli: nope that doesnt work
[15:53] <nik90_> netcurli: I tried Alarm.DayOfWeek(1), Alarm.DayOfWeek(daysOfWeek) and daysOfWeek(Alarm.DayOfWeek)
[15:53] <nik90_> none of them work
[15:53] <netcurli> ok
[15:54] <netcurli> was worth a shot
[15:54] <nik90_> yes
[15:54] <nik90_> hmm I am seeing no benefit of using enum for the api
[15:54] <nik90_> should ask the dev
[15:54] <nik90_> other than being able to assign by name like Alarm.Tuesday and so on
[15:55] <netcurli> why exactly do you need the value of the enum?
[15:55] <netcurli> to save it?
[15:56] <nik90_> no I need it to read when the alarm is set to ring
[15:56] <nik90_> so by getting the value of the enum which may be 1,2,4,8,10,20,40 and 80, I will be able to correspond it to whether the alarms rings on Monday, Tuesday or wednesday etc.
[15:57] <nik90_> and the reverse is needed for assigning the day
[15:57] <nik90_> for assigning the day, I do Alarm.Monday etc
[15:58] <netcurli> oh, there can be multiple days for the alarm?!
[15:59] <nik90_> netcurli: yup
[15:59] <netcurli> you can make comparisons against enums just fine
[15:59] <netcurli> but if you have to do some math stuff
[15:59] <netcurli> ..
[15:59] <nik90_> right now I did switch(enumvalue), case 1: return "Monday" and so on
[16:00] <netcurli> to get a string you would need something like that anyway
[16:01] <netcurli> the best idea however is probably to talk to the guys who designed the api
[16:01] <nik90_> yeah
[16:01] <netcurli> to ask how they imagined it to be used
[16:02] <nik90_> yeah I feel like I am coding the long way :D
[16:03] <OrokuSaki> if anyone could show me how to get apparmor working on clickapps by default I would.. really appreciate it.. my kernel doesn't have apparmor, and the .desktop files seem to get regenerated on every boot..
[16:04] <OrokuSaki> I know it is /usr/share/upstart/sessions/applications-click.conf and override related
[16:07] <mamenyaka> hi OrokuSaki, does your device have wake up problems?
[16:07] <OrokuSaki> no
[16:07] <AskUbuntu> Ubuntu Touch: Screen color tone | http://askubuntu.com/q/342615
[16:08] <mamenyaka> OrokuSaki, any idea why all of mine has? :D
[16:08] <OrokuSaki> got me on that one
[16:09] <mamenyaka> guess it's a bug
[16:18] <cwayne_> Kaleo, you around?
[16:29] <rah> what should I do with the Ubuntu preinstalled images?  I have system.img, boot.img, etc.
[17:00] <plars> asac: looks like there was no new image?
[17:01] <stgraber> plars: the cronjob to import to system-image was disabled until 30min ago, an import must be running pretty much now
[17:01] <plars> stgraber: ok
[17:21] <lool> asac: version 29 is up
[17:21] <lool> plars: ^
[17:22] <plars> lool: yep, testing has already kicked off on it
[17:25] <lool> stgraber: it's cool to see the small deltas
[17:25] <lool> like 13M today for me
[17:33] <stgraber> lool: http://paste.ubuntu.com/6075720/
[17:33] <stgraber> lool: that should fix the other bug, testing now
[17:34] <lool> stgraber: Do I understand correctly that we have to be careful to preserve the ordering of uids in images?
[17:34] <lool> stgraber: that is, if a rootfs has a new system user taking over the current number of usermetrics, it will take over ownership of its files?
[17:35] <lool> stgraber: nice that you got rid of the hardcoded phablet uid/gid though!
[17:35] <stgraber> lool: yeah, we unfortunately will have problems if uids start changing
[17:36] <stgraber> lool: once we have the boot time hooks, we'll be able to fix any problem in there though. So those packages that have non-root owned files divert to persistent storage should ship a hook to check and fix them
[17:36] <plars> lool, stgraber: I guess 20130907 won't have a different mediascanner?
[17:38] <stgraber> plars: if that's part of android, then no. The 20130906.1 => 20130907 is rootfs only
[17:39] <plars> stgraber: no, it's not... but when lool and asac and I were talking last night, I thought the working theory was that the new failures were likely related to mediascanner getting updated in 6.1
[17:40] <plars> the new camera test failures to be specific
[17:41] <stgraber> plars: http://people.canonical.com/~ogra/touch-image-stats/20130907.changes so no
[17:44] <lool> stgraber: ack; we should eventually add some kind of image tests to avoid getting hurt by this uid thing
[17:44] <stgraber> yeah, that'd be useful
[17:44] <lool> we might generally need to review other things, but hard to tell in advance
[17:45] <stgraber> AFAIK usermetrics is the first non-root directory (outside of /home obviously), but I guess probably not the last
[17:45] <lool> (e.g. maintainer scripts doing stuff that we need to do too)
[17:45] <asac> lool: plars: nice!
[17:45] <asac> lool: guess the chown for camera didnt land :)?
[17:47] <stgraber> root@ubuntu-phablet:/# ls -lh /var/lib/ | grep usermetrics
[17:47] <stgraber> drwxr-xr-x 2 usermetrics usermetrics 4.0K Sep  7 17:47 usermetrics
[17:47] <stgraber> root@ubuntu-phablet:/# touch /var/lib//usermetrics/abc
[17:47] <stgraber> root@ubuntu-phablet:/# rm /var/lib//usermetrics/abc
[17:47] <stgraber> root@ubuntu-phablet:/#
[17:47] <stgraber> lool: ^
[17:48] <stgraber> hmm, the mode is wrong, it should have been 750...
[17:49] <stgraber> ah of course if I forget the chmod that won't help...
[17:51] <stgraber> root@ubuntu-phablet:/# ls -lh /var/lib/ | grep usermetrics
[17:51] <stgraber> drwxr-x--- 2 usermetrics usermetrics 4.0K Sep  7 17:50 usermetrics
[17:51] <stgraber> now that's good! Uploading
[18:04] <lool> stgraber: cool
[18:04] <antman> hello
[18:04] <antman> ?
[18:05] <lool> hi
[18:17] <nik90_> does anyone know where I can find information on inverse mouse area? I tried searching on google and upstream qt docs but couldnt find them
[18:17] <nik90_> while I see the calculator app using it
[18:19] <user82> what is the newest way to install? anything special like flipped/nonflipped i need to know for phablet flash?
[18:20] <OrokuSaki> if anyone could show me how to get apparmor working on clickapps by default I would.. really appreciate it.. my kernel doesn't have apparmor, and the .desktop files seem to get regenerated on every boot..
[18:20] <OrokuSaki> I know it is /usr/share/upstart/sessions/applications-click.conf and override related
[18:42] <nik90_> boiko: ping
[18:42] <boiko> nik90: pong
[18:43] <nik90_> boiko: hi, I am not sure if you remember, but almost 2 months ago, you provided instructions for bug https://bugs.launchpad.net/ubuntu-clock-app/+bug/1179486
[18:44] <nik90_> boiko: your suggestion was to add the KeyBoardRectangle.qml file to the clock-app and anchors elements to it so that they are not hidden by the osk
[18:44] <boiko> nik90: ah yes, but that's not required anymore
[18:44] <nik90_> boiko: really?
[18:44] <nik90_> boiko: damn I just started working on that and copied that file :P
[18:45] <boiko> nik90: if your app has a MainView, you can just set anchorToKeyboard: true
[18:45] <nik90_> boiko: that's it?
[18:45] <boiko> nik90: should be it
[18:47] <nik90_> boiko: hmm, that doesn't seem to do it
[18:47] <nik90_> boiko: my textfield is still beneath the osk
[18:47] <nik90_> boiko: since you are here, do you also happen to know where I can find information about inverse mouse area?
[18:48] <boiko> nik90: well, it is an internal component, so obviously there is no documentation about it
[18:49] <boiko> nik90: but using it is pretty simple: you fill an area with that component, and then it will report a clicked signal that happens anywhere on screen but the area that is filled
[18:50] <nik90_> boiko: ah okay. Do you know what the propagateComposedEvents property does?
[18:50] <nik90_> boiko: I saw this being used in the calculator to remove focus from the textfield when clicking outside
[18:50] <nik90_> boiko: I need that same behavior for clock app as well
[18:51] <nik90_> boiko: so I copied the code and it seems to work. However wasnt sure what the propogatecomposedevents property was for
[18:52] <boiko> nik90: hmm, I would say it does the same as it does on MouseArea
[18:52] <boiko> nik90: http://qt-project.org/doc/qt-5.1/qtquick/qml-qtquick2-mousearea.html#propagateComposedEvents-prop
[18:52] <nik90_> boiko: ah thnx. did not know that it had that property :)
[18:52] <boiko> nik90: :)
[18:52] <nik90_> boiko: so regarding the textfield hidden beneath osk, does the textfield need to be anchored to bottom of the app?
[18:53] <boiko> nik90: either that, or if it is in a flickable, you need to scroll for it to be in view
[18:53] <nik90_> boiko: it is in a flickable
[18:53] <nik90_> boiko: but I was hoping it would scroll automatically
[18:54] <boiko> nik90: I used to have this in phone-app, let me see if I can find the code, just a sec
[18:54] <nik90_> boiko: http://bazaar.launchpad.net/~phablet-team/phone-app/trunk/view/head:/src/qml/DetailViewCommunication/CommunicationView.qml#L235
[18:54] <nik90_> boiko: I took this from our previous conversation 2 months ago :D
[18:54] <boiko> nik90: ah yes, that's it :)
[18:55] <nik90_> boiko: so in this file, you say anchor.bottom: keyboard.top
[18:55] <boiko> nik90: ah wait, well, I was looking for a different piece of code, let me find it here
[18:58] <boiko> nik90: so, that code (from the URL you pasted) is for the case of when your textfield is outside a flickable
[18:58] <boiko> nik90: but when it is inside a flickable, you need to get it on screen. I had a code for something similar here: http://bazaar.launchpad.net/~phablet-team/phone-app/trunk/view/head:/src/qml/DetailViewContact/ContactDetails.qml#L233
[18:59] <nik90_> boiko: which line should I be looking at?
[18:59] <boiko> nik90: well, that function I wrote is to jump the view to a position inside a repeater or something like that
[18:59] <nik90_> scrolltosectionposition() ?
[18:59] <boiko> nik90: yep
[19:00] <boiko> nik90: but I can help you with that on monday if you need
[19:00] <boiko> nik90: but right now I am running late for an appointment :/
[19:00] <nik90_> boiko: okay..go ahead
[19:00] <boiko> nik90: have a nice weekend! :)
[19:00] <nik90_> boiko: that's fine. thnx for the link
[19:00] <nik90_> u 2 boiko
[19:01] <iBotPeaches> if surfaceflinger is never loading, just "waiting..." on my new port, is that a bug on my porting side or not? (im using flipped images now)
[19:03] <asac> lool: stgraber: so 30 might contain the chown? great :)
[19:04] <asac> lool: stgraber: what is odd that the camera-app autopilot consistently succeeds on RW
[19:04] <stgraber> asac: I'm uploading android now to pick up the chown/chmod change, so any build done in 3+ hours should have it
[19:04] <asac> (even with crashes)
[19:04] <stgraber> asac: but I doubt it'll make it for the next tick (in an hour)
[19:04] <asac> right
[19:05] <asac> android takes 3 hours to build and propose?
[19:05] <asac> good to know
[19:06] <asac> lool: stgraber: camera app is crashy on RW as well, but the one test always fails on RO and always succeeds on RW
[19:06] <asac> compare: http://reports.qa.ubuntu.com/smokeng/saucy/image/4050/camera-app-autopilot/
[19:06] <asac> (RW)
[19:06] <asac> vs. http://reports.qa.ubuntu.com/smokeng/saucy/image/4058/camera-app-autopilot/
[19:06] <asac> RO
[19:06] <asac> really oddish
[19:07] <stgraber> probably more like 2 hours, it'll take me quite a few minutes to upload (the source is 150MB large), then the build takes around 50min and probably around 30min for the processing (copying files around, britney, ...)
[19:07] <asac> yeah. all good. guess tomorrows build is then pretty good
[19:07] <stgraber> I hope so
[19:07] <asac> i just cant see why a random test would fail on RO :)
[19:07] <asac> disable_shoot_button
[19:07] <asac> maybe that tries to save a pref?
[19:08] <asac> :)
[19:08] <stgraber> I just tried the camera app here on mako and it works fine
[19:08] <stgraber> both front and back camera, shooting cameras, switching flash on/off and video mode
[19:08] <asac> right. i did it too
[19:08] <asac> not sure what "disable_shoot_button" is though
[19:09] <asac> really weird that it fails 100% on RO and 0% on RW :)
[19:09] <asac> on both devices
[19:10] <sergiusens> asac: what's the full name of the test?
[19:13] <asac> sergiusens: test_capture.TestCapture.test_shoot_button_disable
[19:14] <asac> sergiusens: see http://reports.qa.ubuntu.com/smokeng/saucy/image/4058/camera-app-autopilot/
[19:14] <asac> vs http://reports.qa.ubuntu.com/smokeng/saucy/image/4050/camera-app-autopilot/
[19:23] <sergiusens> asac: that test is very fragile
[19:24] <sergiusens> asac: still in process of flashing latest to see why this happens, but it could be that taking photos is faster on touch_ro
[19:35] <asac> sergiusens: shoot_button_disable is about taking pictures?
[19:35] <asac> also i assume you wanted to say that touch is faster than touch_ro?
[19:35] <asac> or do yuou think touch_ro is fastre in this regards?
[19:36] <OrokuSaki> sed -i
[19:41] <sergiusens> asac: takes a picture, checks if the shutter button is disabled mid flight and enabled again
[19:42] <sergiusens> asac: but there is no guarantee an autopilot inspect would capture that at the right moment
[19:42] <sergiusens> asac: I think this test adds little value IMO
[19:42] <stgraber> sergiusens: testing here, the button is greyed out for <1s so seems like a potential race indeed
[19:43] <sergiusens> stgraber: yeah, very likely
[19:48] <sergiusens> stgraber: are you running daily-proposed with no mods?
[19:52] <stgraber> sergiusens: I'm ony daily-proposed with my initrd change applied locally (writable /var/lib/usermetrics)
[19:53] <sergiusens> stgraber: ah, let me do that
[19:58] <Vladman> Anyone have the link so I can download this on my sprint samsung galaxy s3?
[19:58] <lool> sergiusens, asac: So mediascanner crash is gone?
[19:59] <lool> hmm apparently not
[19:59] <Vladman> What really
[20:03] <Vladman> I'm going to keep on looking for it
[20:20] <lool> I wonder whether it's the removal of demo medias that causes the mediascanner to fail to start/init correctly
[20:21] <sergiusens> lool: demo content is still there
[20:23] <lool> I've posted a bt with symbols in https://bugs.launchpad.net/mediascanner/+bug/1221984
[20:23] <lool> and some debug logs
[20:23] <lool> I see gst_discoverer is NULL, but not sure why it isn't set
[20:31] <asac> lool: reliable on RO ... not on RW
[20:31] <asac> even though camera doesnt crash
[20:31] <asac> err works
[20:34] <sergiusens> asac: but should work with stgraber's fix, right?
[20:42] <asac> sergiusens: the chown? i dont think so
[20:42] <asac> the autopilots run in RW mode
[20:42] <asac> and without that fix it doesnt work at all her
[20:42] <asac> and autopilot succeeds, just for one test not
[20:45] <sergiusens> asac: thought you were talking about your device
[20:48] <cwayne> sergiusens: hey, is there any way to just wipe the userdata?
[21:02] <sergiusens> cwayne: not really, since the image builder constructs the users home too
[21:03] <sergiusens> cwayne: we can certainly write one for touch_ro
[21:07] <asac> sergiusens: no ... locally all is fine... just that test :_)
[21:07] <lool> asac: I get to crash mediaservice locally
[21:08] <asac> could be it happens here too
[21:08] <asac> but ... i can take photos :)
[21:08] <asac> etc.
[21:08] <asac> seems that the RW tests also produce crashes
[21:08] <asac> but still they all succeed
[21:08] <lool> right maybe the mediascanner thing is unrelated
[21:08] <asac> hence: wondere whats going on with that test :)
[21:08] <asac> feels its unrelated to the test
[21:08] <sergiusens> asac: that test http://bazaar.launchpad.net/~phablet-team/camera-app/trunk/view/head:/tests/autopilot/camera_app/tests/test_capture.py#L139
[21:08] <sergiusens> asac: is not good
[21:08] <asac> but since the day before the RO images passe
[21:08] <asac> d
[21:09] <asac> it is still one of the candidates i feel
[21:09] <cjohnston> asac: does something need to rerun?
[21:09] <sergiusens> asac: two asserts on the same thing at the end there
[21:09] <asac> cjohnston: dont think so for now
[21:09] <cjohnston> ack
[21:09] <sergiusens> asac: expecting two different results and nothing triggering the change
[21:09] <asac> sergiusens: hell
[21:09] <asac> how can that suceeed at all?
[21:09] <sergiusens> asac: not a good candidate for autopilot testing
[21:09] <sergiusens> asac: might of been slower before
[21:10] <sergiusens> asac: very race prone
[21:10] <asac> ah eventually waits
[21:10] <asac> i see
[21:10] <asac> so they try to figure if the button goes disabled
[21:10] <asac> and then comes back
[21:11] <asac> otoh i get a stall right after button is disabled if camear app crashes :)
[21:11] <sergiusens> asac: yup, but between the time you get to the point where you check it could have already happened
[21:12] <asac> sure? doesnt it just return if its true already?
[21:13] <sergiusens> asac: yeah but what happens with         self.assertThat(exposure_button.enabled, Eventually(Equals(False))) if it's already True?
[21:13] <sergiusens> it times out
[21:13] <asac> oh ic
[21:13] <asac> so we fail in the False line?
[21:13] <asac> but why would RO be faster?
[21:13] <asac> maybe it fails fast to save?
[21:14] <sergiusens> asac: that's a callback, the shutter disable has to do with the sensor being ready or not
[21:14] <lool> so IIUC, asac is looking after the failing autopilot test which is broken by design and needs to be fixed to not be racy, and I was looking at a mediascanner crash that is not a blocker for anything; in any case camera-app and gallery-app work, right?  :-)
[21:14] <cwayne> sergiusens: thatd be very helpful for me :D
[21:14] <sergiusens> asac: anyways, looking at the test, the return to True is what fails on utah
[21:15] <sergiusens> lool: latest install of daily-proposed doesn't have the camera-app working for me out of the box
[21:16] <lool> sergiusens: well still the chown missing, but that's uploaded, right?
[21:16] <sergiusens> lool: not sure, haven't been keeping track of that
[21:16] <lool> 20130905-0ubuntu4
[21:16] <lool> is still in proposed
[21:17] <lool> in fact still building!
[21:17] <lool> but near the end
[21:17] <lool> (android pkg)
[21:25] <lool> actually seems to be something wrong with this build
[21:36] <lool> build was stuck; doubt we will have time to sort this + build an image tonight
[21:36] <lool> next image tomorrow morning should be good though
[22:07] <slangasek> sergiusens: so the fact that you had to manually install python:any indicates a bug in apt; :any is definitely supposed to take the native version when possible
[22:07] <slangasek> sergiusens: and yeah, I saw the same behavior here
[22:39] <lool> hmm odd, on mako if I shutdown -h now from adb shell with full battery, it will restart after some secs into the "battery charging" screen, then again into the "full battery" screen, then after a longer while it automatically boots again
[22:47] <jochenh> Hey! I started ubuntu touch on my samsung galaxy tab 2 but after flashing only a blank screen shows up. Any Ideas how to solve it?
[22:48] <jochenh> Seems like Quantal Release is working but saucy dont: http://forum.xda-developers.com/showpost.php?p=45207701&postcount=358
[23:15] <jochenh> Any ideas?
[23:18] <plars> asac, lool, stgraber: looks like camera app is still failing on 7.1
[23:19] <stgraber> plars: yeah, I don't see what would cause it to suddenly work (except if you get lucky, assuming it's indeed a race)
[23:20] <plars> stgraber: ok, I misunderstood, I thought some sort of fix was landing for it
[23:21] <stgraber> plars: I pushed a fix to the initrd and android to make /var/lib/usermetrics properly writable
[23:21] <stgraber> but it's not in any image yet as we had some problems with Launchpad that prevented anything from publishing for a few hours
[23:21] <plars> ok, I thought lool was saying that just changing the permissions made it at least somewhat better for him yesterday
[23:21] <plars> ah, ok
[23:22] <stgraber> ah, if that's the case, then the next image will work better. Though I fail to see how the camera app would be related to that.
[23:22] <stgraber> I'll kick a rebuild once android is ready, so we should have a new image in ~1h30