[00:51] <[reed]> fta: ping
[00:51] <fta> yep (i'm not there for long)
[00:52] <[reed]> fta: see if these urls work:
[00:52] <[reed]> moz-icon://.txt?size=16
[00:52] <[reed]> moz-icon://txt?size=16
[00:52] <[reed]> use separate tabs
[00:52] <[reed]> let me know what they return (if anything)
[00:54] <fta> the 1st, nothing
[00:54] <fta> the 2nd, a small white page with a folded corner
[00:54] <[reed]> http://weekinthenee.wordpress.com/feed/
[00:54] <[reed]> under "media files"
[00:54] <[reed]> do you see broken images?
[00:54] <fta> yes
[00:54] <[reed]> ok, thanks
[00:56] <fta> [reed], http://www.sofaraway.org/ubuntu/tmp/broken-icons.png
[01:20] <[reed]> too many Linux-specific image bugs lately
=== micahg1 is now known as micahg
=== micahg1 is now known as micahg
=== asac_ is now known as asac
[13:30] <asac> http://paste.ubuntu.com/317786/
[13:30] <asac> fta: ^
[13:30] <asac> chromium failed after finished building ... that feels weird
[13:30] <asac> errors occurred during ubild
[13:30] <asac> why desnt it fail where the errors happen :)
[14:26] <fta2> asac, because i use --keep-going
[14:26] <fta2> asac, so i can report several problems with just 1 build
[14:27] <fta2> it's very useful with -Werror
[14:28] <fta2> asac, plz file a bug
[14:29] <fta2> if you feel like fixing it, submit the patch to codereview and add the url to the bug
[14:34] <asac> fta2: i dont know where it failed because the error seems to have happened long before
[14:39] <fta2> then just dpkg-build* -nc, you should just see the failure
[14:39] <fta2> or log your session and search for Error
[14:43] <asac> k ... rebuilding
=== ripps_ is now known as ripps
[14:53] <asac> In file included from /home/asac/chromium-browser-4.0.245.0~svn20091111r31665/build-tree/src/native_client/src/include/nacl_elf.h:48, from /home/asac/chromium-browser-4.0.245.0~svn20091111r31665/build-tree/src/native_client/src/include/nacl_platform.h:41, from /home/asac/chromium-browser-4.0.245.0~svn20091111r31665/build-tree/src/native_client/src/shared/platform/nacl_host_desc_common.c:38:
[14:53] <asac> /home/asac/chromium-browser-4.0.245.0~svn20091111r31665/build-tree/src/native_client/src/include/elf.h:68:3: error: #error "NACL_TARGET_SUBARCH must be defined to be 32 or 64"
[14:53] <asac> /home/asac/chromium-browser-4.0.245.0~svn20091111r31665/build-tree/src/native_client/src/include/elf.h:75:3: error: #error "NACL_TARGET_SUBARCH must be defined to be 32 or 64"
[14:53] <asac> scons: *** [/home/asac/chromium-browser-4.0.245.0~svn20091111r31665/build-tree/src/sconsbuild/Release/obj/platform/platform/nacl_host_desc_common.o] Error 1
[14:54] <asac> Compiling /home/asac/chromium-browser-4.0.245.0~svn20091111r31665/build-tree/src/sconsbuild/Release/obj/platform/platform/linux/nacl_threads.o
[14:54] <asac> /tmp/cczbKiNK.s: Assembler messages:
[14:54] <asac> /tmp/cczbKiNK.s:210: Error: bad instruction `lock'
[14:54] <asac> /tmp/cczbKiNK.s:210: Error: bad instruction `xaddl ip,[r4,#0]'
[15:16] <asac> jcastro: see msg
[15:16] <asac> ;)
[15:18] <jcastro> I didn't get one
[15:18] <jcastro> did you msg jcastro_ ?
[15:18] <asac> jcastro: yes
[15:18] <asac> one second
[15:19] <asac> jcastro: sent again (canonical server)
[15:56] <fta2> asac, most probably, nacl is not ready for other arches. you should disable it
[15:57] <eagles0513875> hey asac
[15:57] <eagles0513875> hey fta2
[15:57] <fta2> hey
[16:03] <asac> fta2: what is nacl=
[16:03] <asac> ?
[16:06] <fta2> native client
[16:06] <fta2> it allows you to run native binaries in the browser
[16:06] <fta2> with the perf of the host
[16:09] <asac> hmm ok.
[16:09] <asac> native binaries, like plugins?
[16:09] <fta2> no
[16:09] <fta2> http://code.google.com/p/nativeclient/
[16:10] <fta2> hmm "Some ARM and x86-64 support is implemented in the source base, and we hope to make it available for application developers later this year"
[16:11] <fta2> you can run quake inside the browser, even firefox
[16:21] <fta2> asac, i wanted to package nacl as a plugin (like o3d) but that's just one more huge package that will never enter the repo :(
=== yoasif_ is now known as yoasif
[18:11] <micahg> asac: are you around
[18:38] <asac> micahg: yes for a few minutes
[18:39] <micahg> asac: any ideas for bug 481702
[18:39] <ubottu> Launchpad bug 481702 in firefox-3.5 "firefox doesn't start because of sqlite version" [Undecided,Incomplete] https://launchpad.net/bugs/481702
[18:43] <asac> micahg: i would guess he has a manually installed sqlite in /usr/local or something ... asked for strace
[18:44] <micahg> ok, thanks
[18:45] <asac> micahg: so when he submits that check for from where libsqlite is loaded etc. and educate him then
[18:45] <micahg> ok, will do
[18:52] <micahg> hmmm
[18:52] <micahg> xul193 still took 40 minutes
[18:52] <micahg> asac: I need to bump cairo on both xul and ff, right?
[18:59] <fta> yep, my bad
[18:59] <fta> i'm testing a fix
[19:00] <micahg> fta: I should bump ff3.6 along with xul, right, it'll probably fail today?
[19:04] <asac> micahg: i would hope that ffox --with-libxul-sdk shouldnt need cairo decision
[19:04] <asac> but if we have the bound in rules there then probably yes
[19:05] <micahg> well, it's in there
[19:06] <asac> yeah then do both
[19:06] <asac> assuming they did that upstream ;)
[19:06] <asac> ok off ... preparing travel for UDS etc.
[19:07] <fta> asac, you were supposed to do something to m-d
[19:09] <fta> micahg, fixed
=== kenvandif is now known as kenvainde
=== kenvainde is now known as kenvandine
[20:33] <jcastro> fta, when does your chromium build kick off?
[20:35] <fta> jcastro, 4pm UTC (4+h ago), but today's builds failed
[20:36] <jcastro> ah right
[20:36] <fta> why?
[20:36] <jcastro> fta, just wanted to let you know that with upstream r31928 --enable-sync works
[20:36] <fta> ok
[20:46] <fta> chromium-browser                 19664   1.49%      3473    8906    7281       4
[20:46] <fta> google-chrome-unstable           16391   1.24%      4411    5906    6056      18
[20:46] <fta> jcastro, ^^
[20:47] <jcastro> hah
[20:47] <fta> that was yesterday, should turn 20k in a day or two
[20:51] <jcastro> that is sweet
[21:02] <fta> jcastro, we have strange bug reports from people that are apparently using hardy without even the security or updates repos but yet, are upgrading chromium. that's scary.
[21:11] <jcastro> indeed
[21:38] <bdrung> asac: ping
[23:06] <fta> [reed], wrt the  imacro_asm.js seg fault at build time, do you have a bug id?
[23:08] <fta> [reed], lpia only, regression window is 20091030r34417 - 20091031r34440; and no backtrace, i don't have access to a lpia machine