[08:05]  * apw yawns ...
[08:07]  * smb is reminded to get more coffee...
[08:09] <apw> smb, a fine plan indeed
[09:11]  * ppisati notes the keyboard in the nexus7 ubuntu image is much more usable than the phablet image counterpart
[09:12] <ogra_> heh
[09:12] <ogra_> you should say that in #ubuntu-touch so the right people see it 
[09:13] <ppisati> ogra_: :)
[09:13] <ppisati> ogra_: i just installed the nexus7 desktop img to the test yesterday's kernel
[09:13] <ppisati> ogra_: and i just noticed how good the keyboard is there
[09:13] <ppisati> ogra_: compared to the phablet one
[09:13] <ogra_> is touch working without the patch ?
[09:13] <ogra_> (on desktop)
[09:14] <ppisati> ogra_: touch kernel you mean?
[09:14] <ogra_> well, i mean the patch you discussed with jani 
[09:14] <ogra_> would eb good if the same kernel worked on both 
[09:14] <ppisati> ogra_: i'm testing it right now
[09:15] <ppisati> ogra_: just finished to reinstall
[09:15] <ogra_> ah, so touch still works even with that patch removed ?
[09:15] <ogra_> (iirc we added an xorg.conf.d snippet that should fulfill the same purpose)
[09:16] <ppisati> ogra_: the phablet/touch img had the touchscreen borked if that patch was present
[09:16] <ogra_> right
[09:16] <ppisati> ogra_: dunno about the dekstop img, since the patch landed there for this img
[09:16] <ogra_> well, it would eb good to use the same kernel on both 
[09:16] <ppisati> ogra_: besides, where's this snippet?
[09:16] <ppisati> ogra_: right
[09:16] <ogra_> somewhere in ubuntu-defaults-nexus7 iirc
[09:17] <ppisati> ogra_: if i flash tthis morning img, do i get it?
[09:17]  * ogra_ would have to look, but i have a vet appointment now, this will have to wait 
[09:17] <ogra_> (if my GF ever manages to catch the cat)
[09:18] <ppisati> ogra_: try with a net :)
[09:18] <ogra_> haha
[09:18] <ogra_> she's not a fish !
[09:19] <ppisati> ogra_: cat or GF? :)
[09:20] <ogra_> :P
[10:40]  * ogra_ is back
[12:03]  * apw tries to not imaging ogra_ with a fish for a g/f
[12:04]  * ogra_ wont comment on that since this is a family friendly channel 
[12:05] <apw> :)
[13:25] <ev> hiya. Does anyone know if our copy of the android kernel does something to prevent core dumps? I can't seem to force one despite killing debuggerd, setting the core ulimit to unlimited, and setting the core pipe appropriately.
[13:25] <ev> ppisati: ogra_ mentioned you might have an idea, having touched the config last :)
[13:26] <ogra_> :)
[13:30] <ppisati> ev: i know there was an option about core dump in the dekstop kernel (not in the android one), let me check
[13:33] <ppisati> ev: cat /proc/sys/kernel/core_pattern
[13:36] <ev> ppisati: neither "core", nor "/data/core.%e.%p", nor "|/path/to/apport" work
[13:36] <ev> been through them all :)
[13:36] <ev> and yes - I was in a writeable directory
[13:37] <ev> (for "core" that is)
[13:41] <ppisati> ev: and you tried with SIGABRT or gcore, right?
[13:41] <ev> gcore? I was sending SIGSEGV.
[13:46] <ev> SIGABRT also doesn't dump core. gcore on `sleep inf` works.
[14:02]  * ogasawara  back in 20
[16:58]  * smb -> eow
[17:25]  * rtg_ -> lunch
[17:41]  * henrix -> eod
[18:48] <rtg_> apw, ogasawara: pushed raring master-next rebase on v3.8.6. build testing, will likely upload tomorrow.
[18:48] <ogasawara> rtg_: ack
[19:40] <infinity> psivaa: Did the regression testing on ti-omap4/quantal get stalled?  Seems to be the only SRU currently not ready to be released.
[19:41] <infinity> psivaa: Oh, and linux-ec2/lucid, apparently.
[19:43] <infinity> zequence: Your kernels for P/Q are in -proposed now (will be true on mirrors in an hour or so, I suspect), if you want to do some quick smoketesting over the weekend, I'll release them on Monday with all the others and you'll be caught up.  \o/
[19:58] <bryce> sforshee, test patch on #1041790 could use a kernel I think
[20:01] <sforshee> bryce, is this the patch you're referring to? https://bugs.freedesktop.org/attachment.cgi?id=77475
[20:01]  * rtg_ -> EOD
[20:02] <bryce> sforshee, that's the one
[20:03] <bryce> sforshee, your call on what kernels worth building.  The issue appears to affect raring and quantal, and one precise user claims to see it (unverified so far)
[20:03] <sforshee> bryce, ack. I'll kick off some builds.
[20:05] <bryce> sforshee, this bug seems to be relatively widespread and severe (it's even hitting canonical employees a lot), so you might put this on a higher priority attention list for your team
[20:07] <bryce> sforshee, sounds like Intel flipped on a performance improvement too soon.  So if we were to carry this patch there is a possible performance impact to it.  
[20:13] <sforshee> bryce, I'm building raring and quantal to start, I'll follow up with precise if needed
[20:15] <bryce> sounds good