[10:15] <asac> tbird 3 dailies should be fixed in branch
[10:15] <asac> fta: ^^
[10:15] <asac> please reenable
[10:15] <asac> and maybe give it an extra run today
[10:39] <asac> fta: lease please pleaes test my fontconfig fixes
[10:40] <asac> i want to be sure about what kind of regressions folks that actually see font-issues (i am too blind for that) see before doing it
[10:40] <asac> fta: they are are ~mozillateam PPA
[10:49] <asac> fta: just assume that your obsolete files get removed by package  ... toherwise i plan to just upload it
[11:10] <fta> asac, the problem is that i have dropped one or two files in fontconfig, so i don't remember how to reproduce
[11:11] <asac> fta: yeah. just --reinstall fontconfig-config
[11:11] <asac> fta: then check the conffile list
[11:11] <asac> fta: oh. also run dpkg-reconfigure fontconfig-config
[11:11] <asac> and select the defaults
[11:12] <fta> one guy said the liberation fonts are ugly now
[11:12] <asac> liberation fonts?
[11:12] <asac> with my package?
[11:13] <fta> yes
[11:13] <fta> https://lists.ubuntu.com/archives/ubuntu-mozillateam/2009-February/000626.html
[11:42] <asac> fta: yeah. i think thats expected. I probably dropped some ttf tweakage
[11:42] <asac> well ... not expected, but now that someone complained i think i know what to look at
[11:47] <fta> asac, so for tb3, you basically did what sm2 is doing, i.e, drop the mega xpt and ship all the small ones individually. right?
[11:47] <fta> unlike xul and ff
[11:52] <fta> i still don't understand why my stuff was broken, <sigh> ..
[11:56] <LLStarks> rawr.
[11:57] <LLStarks> why is british spelling default for firefox spellcheck?
[12:01] <LLStarks> brb. ext4 is acting up again.
[12:25] <asac> fta: basically yes.
[12:25] <asac> and thats even supported by packager.mk
[12:26] <asac> so we just need to not make the test fatal
[12:26] <asac> and all is good
[12:26] <asac> currently have the hack in the removed-files
[12:26] <asac> we should make that sensible to STATIC or !STATIC too there
[12:26] <asac> instead of ifndef XP_UNIX ;)
[12:28] <LLStarks> asac, before i fire off 3 different bugs to the firefox packagers... i need your insight.
[12:28] <gnomefreak> why do i get the feeling that i would need to run autoconf2.13 when building for a different version of ubuntu?
[12:28] <LLStarks> why is en-gb the default?
[12:28] <gnomefreak> it is?
[12:29] <asac> LLStarks: cant remember right now
[12:29] <LLStarks> <___<
[12:29] <gnomefreak> i thought it followed the rules of the system default locale
[12:29] <asac> i think its rather random
[12:29] <asac> we ship both dics in the same package and ffox picks first seen
[12:30] <asac> gnomefreak: tbird 3 is fixed ;) ... so new tbird might be there tomorrow
[12:30] <gnomefreak> asac: thanks
[12:33] <thunderstruck> you have got to be kidding me
[12:34] <gnomefreak> crashes now connection. my day is starting to suck badly
[12:35] <asac> kidding?
[12:35] <asac> why ;)?
[12:37] <gnomefreak> first my timer crashed now my connection is bad i have been here for all of 5 minutes and this happens what else can go wrong
[12:37] <asac> fta: do you know why we dont do a static build? do we explicitly opt-out somehow or is that just not the default for tbird?
[12:37] <asac> i guess its the later ... but since folks in the bug sounded a bit like that they think static is right, that souds a bit wierd at the same time
[12:39] <LLStarks> ack. how do i reset fontconfig? the patch is breaking subpixel as much as it is fixing it.
[12:40] <asac> LLStarks: no change?
[12:40] <asac> LLStarks: so ... dpkg --query fontconfig-config | grep obsolete
[12:40] <asac> what files do you get there?
[12:40] <LLStarks> i'm getting the red tinge around my fonts
[12:41] <LLStarks> query is not a valid argument. <_<
[12:41] <asac> LLStarks: try --status ;)
[12:42] <LLStarks> http://pastebin.com/m57cc0dbc
[12:42] <LLStarks> thx
[12:42] <asac> LLStarks: ok. and ls /etc/fonts/conf.d/ ?
[12:43] <LLStarks> http://img291.imageshack.us/img291/7804/thehorrorofsubpixel.png
[12:43] <LLStarks> chew on that for a second
[12:43] <thunderstruck> oh this is going to piss me off. i may not be here long
[12:43] <LLStarks> look at the pastebin output box
[12:43] <LLStarks> (top box)
[12:43] <asac> LLStarks: ok. thats monospace font
[12:43] <asac> are all but the monospace fonts ok?
[12:43] <asac> LLStarks: does it help if you zoom in?
[12:44] <asac> e.g. ctrl-+
[12:44] <asac> (for two times)
[12:44] <LLStarks> WORSE
[12:44] <LLStarks> wait
[12:44] <LLStarks> nvm i was looking at the screenshot
[12:44] <asac> LLStarks: dont zoom the pic ;)
[12:44] <asac> lol
[12:44] <LLStarks> still worse for the actual window
[12:45] <LLStarks> actually, a bit better
[12:45] <LLStarks> want a screenie?
[12:46] <LLStarks> http://img510.imageshack.us/img510/3912/zoom2x.png
[12:46] <LLStarks> ls output: http://pastebin.com/m1af92e37
[12:46] <asac> LLStarks: what settings are you using in the fonts preferences?
[12:47] <asac> just the default "subpixel (best for LCD"
[12:47] <asac> or did you tweak something in the "Details..:"
[12:48] <LLStarks> http://img258.imageshack.us/img258/875/screenshotfonts.png
[12:48]  * gnomefreak away while update install than maybe email and i will work on seamonkey bullshit tomorrow
[12:48] <LLStarks> http://img258.imageshack.us/img258/9696/screenshotfontrendering.png
[12:48] <asac> LLStarks: can you please paste the content of /etc/fonts/conf.avail/53-monospace-lcd-filter.conf
[12:48] <asac> LLStarks: also did you paste the ls /etc/fonts/fonts.d yet?
[12:49] <LLStarks> yeah i did
[12:49] <LLStarks> ls output: http://pastebin.com/m1af92e37
[12:50] <asac> LLStarks: and the .conf?
[12:50] <LLStarks> one sec
[12:51] <LLStarks> http://pastebin.com/m1d2160a8
[12:51] <LLStarks> ny times rendering: http://img510.imageshack.us/img510/1774/screenshotadvertisingtr.png
[12:51] <LLStarks> notice the orange and blue tinge?
[12:52] <asac> LLStarks: yeah.
[12:52] <asac> (not the orange)
[12:52] <asac> the yeah was about something else
[12:53] <asac> please do: sudo ln -s /etc/fonts/conf.avail/53-monospace-lcd-filter.conf /etc/fonts/conf.d/53-monospace-lcd-filter.conf
[12:53] <asac> and see if things change
[12:53] <LLStarks> btw, was the times page monospaced?
[12:54] <LLStarks> no difference. do i need to do anything?
[12:54] <asac> yes
[12:54] <asac> restart stuff
[12:54] <LLStarks> system or applications?
[12:55] <asac> usually changing zoom also makes the new font stuff apply
[12:55] <asac> LLStarks: are you using ffox 3.0`
[12:55] <asac> ?
[12:55] <LLStarks> yah
[12:55] <LLStarks> damn it cnn. you guys are obsessed with tropicana too?
[12:55] <asac> LLStarks: well. then all this isnt for you
[12:55] <asac> its for those apps that really honour fontconfig/gnome
[12:56] <asac> LLStarks: better try ffox 3.1 or 3.2
[12:56] <asac> from ~ubuntu-mozilla-daily
[12:56] <asac> LLStarks: and also the gnome experience is what bothers me most. are there regressions over the previous package on the other desktop apps ;)
[12:56] <LLStarks> one sec..
[12:56] <asac> https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive
[12:57] <LLStarks> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090223 Ubuntu/9.04 (jaunty) Shiretoko/3.1b3pre
[12:57] <LLStarks> that's daily, right?
[12:57] <asac> would think so
[12:57] <asac> if thats installed as a pacakge at least
[12:58] <asac> if you downloaded fom mozilla it should be ok to test with it ... but i am not 100% sure
[12:58] <LLStarks> at any rate, 3.1 shares the subpixel woes.
[12:58] <LLStarks> the antialiasing is a lot better though.
[12:59] <asac> LLStarks: i think one issue is with small fonts
[12:59] <asac> e.g. bitstream vera does not support subpixel for small sizes (< 9?)
[12:59] <asac> so there is a rule that disables it for small fonts
[12:59] <LLStarks> lemme give you pic of the mozilla homepage with zoom
[13:00] <LLStarks> http://img254.imageshack.us/img254/7039/ughhhhhh.png
[13:00] <LLStarks> look at the text near the cursor
[13:01] <asac> yeah. i see that there is some color
[13:02] <asac> LLStarks: hmm ... maybe subpixel order setting is a rpboelm?
[13:02] <LLStarks> orange L
[13:02] <asac> check fonts details
[13:03] <LLStarks> http://img258.imageshack.us/img258/9696/screenshotfontrendering.png
[13:05] <LLStarks> full hinting seems to 'fix' the problem
[13:05] <asac> LLStarks: does this change on higher/lower zoom level
[13:05] <asac> seems i see a bit of red too at a certain zoom level
[13:05] <gnomefreak> quick bash script question: how would i launch a tab in terminal? i have it to launch gnometerminal but not sure how to make it open a tab
[13:06] <asac> but all other zoom levels dont have this problem
[13:06] <LLStarks> does what change?
[13:06] <asac> LLStarks: the colorful subpixel mess up ;)
[13:06] <LLStarks> with full hinting?
[13:07] <asac> LLStarks: no. zoom out or in a bit more
[13:07] <asac> do you see the same effect on all zoom levels?
[13:07] <LLStarks> with the default slight hinting?
[13:07] <asac> yeah
[13:07] <asac> maybe tune the hinting too
[13:08] <LLStarks> if i zoom in far enough with slight hinting, the colors dissipate slightly.
[13:09] <LLStarks> it still remains though, but less noticeable
[13:09] <LLStarks> but this is zoom x5
[13:09] <LLStarks> at least
[13:09] <asac> so seems we need full hinting for large font sizes
[13:09] <asac> medium for medium and slight for small ones
[13:11] <asac> LLStarks: btw, after changing settings, just zoom will really apply the new settings - at least for me ;)
[13:11] <LLStarks> sounds like a headache.
[13:11] <LLStarks> (with regard to hinting)
[13:11] <asac> its a bit of a problem to do that while still honouring gnome settings
[13:11] <LLStarks> btw, should i undo the edit made earlier?
[13:11] <asac> LLStarks: which edit?
[13:11] <LLStarks> *i made
[13:12] <asac> the monospace thing?
[13:12] <asac> well. i think we need it
[13:12] <asac> but i will think about it
[13:12] <asac> if you want to track the pristine package bheaviour remove it for now
[13:14] <LLStarks> if i wanted to revert to repo fontconfig, is there anything exotic i need to do?
[13:14] <asac> no
[13:14] <asac> LLStarks: so the difference is that the hinting doesnt differntiate for fontsizes?
[13:14] <asac> LLStarks: is that all that regressed next to the monospace thing?
[13:15] <LLStarks> i honestly wouldn't know what the expected behavior is.
[13:16] <asac> LLStarks: please keep using the package for a while and tell me i there are bad experiences
[13:16] <asac> besides from the above ;)
[13:16] <asac> if you can live with them at all
[13:17] <LLStarks> gnome-terminal seems to be afflicted somewhat
[13:17] <LLStarks> even xchat
[13:17] <asac> LLStarks: they changed of course. question is if its a problem ;)
[13:17] <LLStarks> lemme try using default ubuntu theme
[13:17] <asac> almost everything should look a bit different now
[13:18] <LLStarks> if i choose to downgrade, will mt2 settings linger?
[13:20] <asac> LLStarks: dont think so
[13:20] <LLStarks> there 4 or 5 packages to downgrade, right?
[13:20] <asac> LLStarks: the repo package has "more" config ... and the mozilalteawm package has less
[13:20] <asac> a strict subset ;)
[13:20] <asac> LLStarks: not sure
[13:20] <asac> just fontconfig stuff
[13:20] <LLStarks> and the libraries?
[13:21] <asac> if they are called fontconfig then yes
[13:23] <LLStarks> my eyes feel relieved now.
[13:23] <asac> LLStarks: because of the colorful bug for huge zoomlevels?
[13:23] <LLStarks> yeah.
[13:24] <asac> you zoom that much?
[13:24] <LLStarks> but firefox 3.0 still seems afflicted.
[13:24] <asac> i dont recognize it
[13:24] <LLStarks> lemme restart it.
[13:24] <LLStarks> that's better
[15:17] <asac> fta2: i think i already have the same version installed were i bumped the changelog to. thats why i ment tomorrow ;)
[15:18] <fta2> well, the bot fetched trunk so we're on par
[15:25] <BUGabundo> asac: ping
[15:25] <BUGabundo> how was lunch?
[15:25] <asac> BUGabundo: gone in two minutes
[15:25] <asac> BUGabundo: good ;)
[15:25] <BUGabundo> ehehe
[15:26] <BUGabundo> you manage to be faster then me
[15:26] <BUGabundo> LOL
[15:26] <asac> meeting o'clock
[15:26] <BUGabundo> ohh
[15:26] <BUGabundo> after if, do you think you can manage a bit of time to work on bug 329798 ?
[15:26] <BUGabundo> I have 2 laptops, that fail to work....
[15:26] <BUGabundo> I manage only ONCE to connect to it, with this laptop
[15:27] <BUGabundo> but it I need to hardreset the AP (la fonera) and my laptop
[15:27] <BUGabundo> other then that, it will always fail
[15:40] <fta2> 30 minutes just to pack the chromium tarball, my disks suck
[15:41] <fta2>      8  16:11   ./debian/rules get-orig-source LOCAL_BRANCH=../upstream/chromium-browser.svn
[15:41] <fta2>      9  16:40   date
[15:42] <BUGabundo> fta2 get a 16GiBs SSD
[15:53] <jagadeesh> is there any option to display number of unread emails in thunderbird?
[15:53] <BUGabundo> jagadeesh: on a ballon?
[15:53] <BUGabundo> right now NO
[15:53] <BUGabundo> damn it
[15:53] <BUGabundo> he went away
[15:55] <jagadeesh> BUGabundo: that should be ok
[15:56] <jagadeesh> when I minimize window I want to know if there is any unread email
[15:56] <BUGabundo> right now NO
[15:56] <BUGabundo> but I just saw a post on identica about evo
[15:57] <BUGabundo> jagadeesh: http://identi.ca/notice/2463547
[15:58] <BUGabundo> remember that many apps have to be patched to use libindicate
[16:03] <jagadeesh> BUGabundo: thanks. it is interesting
[16:15] <asac> improving notifications is on the agendafor tbird
[16:15] <asac> problem is that tbird folks need to make 3.0 release happen soon
[16:15] <asac> so most likely this will have to wait for 3.1
[16:15] <asac> notifications == indications
[16:20] <BUGabundo> fta gwibber daily bug
[16:21] <BUGabundo> it won't start by just isseing "$ gwibber"
[16:21] <BUGabundo> I have to state the full PATH
[16:21] <fta2> ?
[16:22] <fta2> works for me
[16:22] <fta2> BUGabundo, ^^
[16:23] <BUGabundo> $ gwibber
[16:23] <BUGabundo> bash: /usr/local/bin/gwibber: No such file or directory
[16:23] <BUGabundo> bugabundo@blubug:/$ whereis gwibber
[16:23] <BUGabundo> gwibber: /usr/bin/gwibber /usr/share/gwibber
[16:23] <BUGabundo> bugabundo@blubug:/$ /usr/bin/gwibber
[16:25] <asac> BUGabundo: exec bash
[16:25] <asac> see if its fixed then
[16:26] <fta2> BUGabundo, it's an old one then. 0.9.1~bzr247-0ubuntu1~daily1
[16:26] <asac> i mean, run: exec bash
[16:26] <asac> so bash updates his PATH cache
[16:26] <BUGabundo> done
[16:26] <fta2> if you still have one in /usr/local/bin, it's no longer one of mine
[16:27] <BUGabundo> now it starts
[16:27] <fta2> bash is evil
[16:27] <BUGabundo> I run --purge and install before I came here
[16:28] <fta2> purge doesn't purge what you install with sudo python setup.py
[16:29] <BUGabundo> just to be sure
[16:29] <BUGabundo> since I had a bzr a while back
[16:29] <BUGabundo> $ whereis gwibber
[16:29] <BUGabundo> gwibber: /usr/bin/gwibber /usr/share/gwibber
[16:30] <fta2> better
[16:30] <asac> BUGabundo: you got a gwibber update which remove dthe /usr/local/ thing and bash didnt notice because it caches the PATH completions
 bash: /usr/local/bin/gwibber: No such file or directory <= good, it's no longer the python2.6 bug then
[16:30] <BUGabundo> I just closed my terminals an opened new ones
[16:31] <BUGabundo> its running fine now
[16:31] <BUGabundo> but already saw two apport fires on it
[16:31] <BUGabundo> maybe I should go back to run it from cli to catch them
[16:31] <BUGabundo> how would I run a python based app with valgrind?
[16:32] <BUGabundo> it was fun to see gedit / seahorse-plugins bloat yesterday for seb128
[16:55] <asac> hi stefanlsd
[16:55] <asac> just ask what you want to discuss about gears 64
[16:55] <stefanlsd> k. thx
[16:55] <fta2> grr; this is getting on my nerves: http://paste.ubuntu.com/122453/
[16:55] <stefanlsd> i've noticed the wiki packages / tutorials on packaging extentions for mozilla. which is great. thx
[16:56] <stefanlsd> seems like this is to do the the resulting .xpi
[16:56] <stefanlsd> is this the preferred way of doing an extension?  Would we prefer to build the xpi from source?
[17:01] <fta2> asac, are the graphs mentioned by rickspencer3 public?
[17:02] <asac> fta2: https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-02-24/
[17:02] <asac> there are graphs
[17:02] <asac> if thats what you mean
[17:09] <stefanlsd> gonna go home quick. bbl :)
[18:01] <BUGabundo> asac: so you are already leaving?
[18:08] <asac> BUGabundo: now out. will look for a few minutes in 30 min ;)
[18:08] <BUGabundo> ok
[18:08] <BUGabundo> if you have the time, PLEASE, take a look at those FON logs
[18:09] <BUGabundo> thanks so much
[18:18] <surfaz> asac, there is any progress with pgo and firefox?
[18:18] <surfaz> If I can help tell me
[18:37] <stefanlsd> I am busy looking at packaging google gears for 64 bit. I patched the source, built against some 64bit libs (xpcom stuff) and have a resultant .xpi.  Is it ok to package this xpi as an extension now?
[18:40] <BUGabundo> stefanlsd: can you give me a link for it?
[18:40] <BUGabundo> I would love to test the XPI
[18:40] <stefanlsd> BUGabundo: sure, let me upload it somewhere for you. hang on
[18:41] <BUGabundo> thanks
[18:41] <BUGabundo> do you need feed back on it?
[18:41] <BUGabundo> can you get it on mozilla store?
[18:51] <stefanlsd> BUGabundo: http://www.lsd.co.za/files/gears-linux-opt-<IP_ADDRESS>.xpi
[18:53] <BUGabundo> big isn't it ?
[18:56] <stefanlsd> BUGabundo: a little. source code is 300mb
[18:56] <stefanlsd> a lot of 3rd party stuff tho
[18:56] <BUGabundo> xeee
[18:56] <stefanlsd> actual gears stuff is 18mb
[18:56] <BUGabundo> need to restart it now
[18:56] <BUGabundo> and test GR
[18:59] <BUGabundo> stefanlsd: humm google reader is not detecting it
[18:59] <BUGabundo> need to log out and login again?
[18:59] <stefanlsd> BUGabundo: let me try reader. i've tried gmail offline folders, and that was ok
[19:00] <BUGabundo> pressing Gears Setting from the menu doesn't do anything either
[19:00] <BUGabundo> FYI this is FF3.1
[19:00] <BUGabundo> from daily PPA
[19:01] <stefanlsd> BUGabundo: aah. i think its only FF3.0 atm. need to look at 3.1 support still
[19:02] <BUGabundo> GAFYD : "You will need Gears for offline access, and the installer will restart your browser."
[19:02] <BUGabundo> and 3.2
[19:03] <stefanlsd> BUGabundo: does addons display FF3.1 reports Gears not compatible?
[19:11] <BUGabundo> what addon doesn't?
[19:11] <BUGabundo> lol
[19:11] <BUGabundo> I use nightly tools, so ALL work
[19:11] <BUGabundo> do you want me to test it on a clean 3.2 profile ?
[19:13] <BUGabundo> stefanlsd: "Google Gears <IP_ADDRESS> could not be installed because it is not compatible with Minefield 3.2a1pre."
[19:15] <stefanlsd> BUGabundo: ok. so far its just 3.0 compatible. Will do some research on 3.1 and 3.2
[19:15] <BUGabundo> thanks
[19:15] <BUGabundo> :(
[19:16] <BUGabundo> ill have to keep waiting then
[19:16] <BUGabundo> ping me (here or on identica) when you have some news and need testing
[19:17] <stefanlsd> BUGabundo: kk. want to see if it will be possible to get this extension into jaunty. Will let you know.
[19:20] <BUGabundo> stefanlsd: its pass FF
[19:20] <BUGabundo> its gona be paperwork
[19:21] <stefanlsd> BUGabundo: yeah. although considering getting gmail offline and reader and some other? may be worth it. will check if i can get it done soon.
[19:35] <BUGabundo> fta: here is a daily regression for you
[19:36] <BUGabundo> opening a new Window with ctrl-N
[19:36] <BUGabundo> Script: chrome://tabmixplus/content/tab/tab.js:782
[19:36] <BUGabundo> something is messing tabmixplus addon
[19:36] <BUGabundo> and was working yesterday
[19:50] <BUGabundo> brb
[22:27] <[reed]> gnomefreak: http://weblogs.mozillazine.org/calendar/2009/02/even_more_on_the_sunbirdlightn.html
[22:34] <fta> BUGabundo, well, for regressions with the daily, it's better to report that directly to mozilla (aka [reed]) if you think it's an upstream bug (in opposition to a packaging bug). with the dailies, you immediately have two close rev-ids.
[22:35] <[reed]> I am Upstream Guy. :)
[22:35] <BUGabundo> need to start a new profile and test back
[22:35] <BUGabundo> but since this is with an addon
[22:35] <BUGabundo> .... grr I fall in the midlle
[22:35] <BUGabundo> the addon did not get upgraded
[22:35] <BUGabundo> and the only thing that changed was FF
[22:36] <BUGabundo> hi [reed]
[22:36] <[reed]> hi
[22:36] <fta> as the packaging didn't change in weeks, it's most likely an upstream change, and i think moz would love to know it's breaking something
[22:37] <[reed]> what are you running into?
[22:37] <fta> if moz doesn't care, it brings some water to my fountain :P
[22:37] <BUGabundo> [reed]: opening a new window seems to be giving an error with tabmixplus
[22:38] <BUGabundo> it makes FF take too long to fork
[22:38] <[reed]> what version of Firefox?
[22:38] <BUGabundo> and then a popup asks to kill or wait
[22:38] <BUGabundo> Script: chrome://osb/content/osb-main.js:5
[22:38] <BUGabundo> ff 3.1 from daily ppa
[22:38] <[reed]> which maps to what rev?
[22:38] <BUGabundo> 3.1~b3~hg20090222r23369+nobinonly-0ubuntu1~umd1
[22:38] <[reed]> hmm
[22:39] <BUGabundo> Script: chrome://tabmixplus/content/tab/tab.js:782
[22:39] <BUGabundo> Script: chrome://tabmixplus/content/tab/tab.js:821
[22:39] <fta> grab a previous daily from lp, test if it's still there, then isolate the rev ids
[22:39] <BUGabundo> great now I'm on an endless popup state
[22:40] <fta> that's the purpose of dailies, it's not just about running the newest ;)
[22:40] <[reed]> :)
[22:40] <BUGabundo> I know
[22:40] <BUGabundo> and I don't!
[22:40] <BUGabundo> for that I would be on 3.2
[22:40] <BUGabundo> but it messes a few of my NEEDED addons
[22:40] <BUGabundo> ok
[22:41] <BUGabundo> time to make a new profile and install tabmixplus to test it
[22:41]  * BUGabundo glad I got rid of the popup
[22:43] <BUGabundo> [reed]: new (clean) profile doesn't have it
[22:43] <BUGabundo> installing TB P now
[22:43] <BUGabundo> http://tmp.garyr.net/tab_mix_plus-dev-build.xpi
[22:44] <BUGabundo> no reports on their forum http://tmp.garyr.net/forum/viewtopic.php?t=9864&postdays=0&postorder=asc&start=100
[22:45] <BUGabundo> new profile with tabmix plus aint showing it either
[22:45] <BUGabundo> :(
[22:47] <BUGabundo> can't reproduce it now
[22:47] <BUGabundo> bbl
[22:50] <hyper_ch> fta: online?
[22:51] <fta> hyper_ch, yes
[22:51] <hyper_ch> fta: did you submit your ppa repo on the repo generator?
[22:52] <fta> repo generator? what is that?
[22:52] <fta> obviously, i didn't :P
[22:52] <hyper_ch> fta: http://repogen.simplylinux.ch
[22:52] <hyper_ch> fta: I just got a submission for your repo and for some reason for each entry on the submission form there was your name added.... which is quite odd as I have never received such a "wrong" submission before :)
[22:53] <fta> it's not me, that's for sure.
[22:53] <hyper_ch> fta: but if it was not you who submitted it, I wonder what description shall I use for it? The one you have in the PPA description? The submitted info for the description was "Firefox, XUL and other latest buildsFabien Tassi"
[22:54] <fta> this is no longer "latest builds", and my name is incomplete
[22:55] <hyper_ch> fta: well, what name shall I give to the repo and what description?
[22:55] <fta> difficult to say, it's my personal PPA and i have over 100 packages
[22:56] <hyper_ch> fta: you can also chose to not have it included on my repo generator :)
[22:56] <fta> this is the latest for mozilla: https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa
[22:57] <fta> yep, don't include mine, enough people are using it, it's spreading by itself already. and i'm slowly moving to dedicated PPAs
[22:57] <hyper_ch> fta: ok :) thx for pointint out the mozilla one, I'll add that one


[03:26] <kgunn> duflu: do you know if FSM stand for "finite state machine" in the context of this bp ? https://blueprints.launchpad.net/ubuntu/+spec/client-1404-mir-rootlessx
[03:26] <duflu> kgunn: Sounds like a good guess :)
[03:27] <duflu> I don't know any other "FSM"
[03:31] <duflu> I think the "synaptics FSM" is something I've proposed fixes to in the past actually. The touch stuff is obviously a state machine
[03:46] <duflu> kgunn: I'd just note Synaptics is a brand and most devices using that code are not Synaptics. So maybe libsomethingelse is more appropriate.
[03:48] <duflu> It would be awesome if more devices used Synamtics, but seems more common are the cheaper Alps and Elan
[06:02] <tvoss> duflu, you ok with me top-approving https://code.launchpad.net/~vanvugt/mir/fix-r1049-regressions/+merge/191776
[06:02] <tvoss> ?
[06:02] <duflu> tvoss: Yep
[06:02] <tvoss> duflu, done
[06:06]  * tvoss -> airport
[06:17] <duflu> alf_: Froze?
[06:19] <alf_> duflu: yes, back again
[06:19] <duflu> alf_: OK, meeting done I guess
[06:38] <duflu> alf_: I've never used a GL context in two threads simultaneously before like Mir does. How safe is it?
[06:40] <duflu> alf_: Oh. Apparently very safe as each DisplayBuffer gets a separate context :)
[06:40] <alf_> duflu: Mir uses different shared contexts in different threads, which is safe. The only caveat is that you need to synchronize the creation of resource ids (e.g. textures)
[06:41] <duflu> alf_: Yes it was the texturing that worried me. But that's OK if it really is a separate context per display
[06:48] <duflu> alf_: Seen this? 1234563
[06:48] <duflu> bug 1234563
[06:50] <alf_> duflu: let me try... is it consistently reproducible?
[06:50] <duflu> alf_: On saucy desktop it seems. Even after a full reinstall
[06:56] <alf_> duflu: confirmed
[06:57] <duflu> Joy
[06:58] <duflu> Huh. That race condition I thought I saw... would only exist if display buffer compositors shared a renderer. But they don't
[10:09] <duflu> Sigh. Maybe I can make better progress in the kitchen than I have in code today.
[14:06] <mterry> alf_, hello!  You around?
[14:07] <alf_> mterry: Hi!
[14:07] <mterry> alf_, OK, I have questions for you and/or alan_g about nested Mir...
[14:08] <alan_g> mterry: ask it then
[14:08] <mterry> alf_, so I tried to get a unity8 shell to talk to USC using the new-style MIR_SOCKET=fd://XX mode
[14:09] <mterry> And I ran into an error about Mir connection not being made.  Upon investigation, it seems like qtubuntu and friends are designed for either being mirserver or mirclient, but not both.  So I manually put in a mir_connect() call into unity8 for testing
[14:10] <mterry> Which presumably consumes the MIR_SOCKET fd.  But then it looks like part of qtubuntu does later want to use MIR_SOCKET for its server parts later
[14:10] <mterry> And I get a Bad file descriptor error
[14:11] <alan_g> mterry: there's an example of using the fd mode in the mir_demo_server_basic example.
[14:11] <mterry> alf_, alan_g: I guess my question is, have you guys only tested on pure Mir, or have you actually got a qtubuntu-using app to do nested server mode?
[14:11] <alan_g> I'm not sure what you're doing with USC - I know robert_ansell was working on it at one point
[14:12] <alan_g> mterry: we've only done testing with the mir_demo_*
[14:12] <mterry> alan_g, yeah he was.  USC is basically just the root Mir server.  He's got some branches where it talks to lightdm and passes back fds for lightdm to hand to other sessions as MIR_SOCKET
[14:13] <alf_> mterry: a qtubuntu app shouldn't care about whether it is talking to a nested or host server
[14:13] <mterry> I'm using those.  It seems to work a little bit, but qtubuntu doesn't anticipate this use case, and I'm trying to see the easiest way to make it work
[14:13] <alf_> mterry: or in this case app==unity8?
[14:13] <mterry> alf_, app==unity8
[14:14] <mterry> alf_, there are ubuntumirclient and ubuntumirserver QPA plugins.  And they each seem to assume it's only client or only server
[14:15] <mterry> I can propose a fix, I just am still uncertain what that fix is yet.  I guess I'll look at the demo code.
[14:17] <alf_> mterry: why does unity8 need both ubuntumirclient and ubuntmirserver? It does all the rendering in-process so ubuntumirserver should be the only one it needs. Mir hides the details of being nested or not.
[14:17] <mterry> alf_, well, I guess that's my problem.  It doesn't seem to
[14:18] <alan_g> mterry: does unity8 use both plugins in the non-nested case?
[14:19] <alan_g> Because it shouldn't know anything about being nested
[14:23] <mterry> alan_g, alf_: sorry, got disconnected.  Not sure what you saw latest.  But:  should a nested Mir need to call mir_connect?
[14:23] <mterry> (on app/shell-side code)
[14:23] <alan_g> mterry: no
[14:23] <mterry> alan_g, OK.  So my error I saw was probably unity-mir making assumptions and calling a piece of Mir code that required mir_connect...  I'll dig into that side of things
[14:24] <mterry> Rather than go down the road of calling mir_connect myself
[14:24] <alan_g> mterry: it shouldn't do anything differently than in the standalone case
[14:24] <mterry> alan_g, OK, good to know
[14:51] <racarr> Good mirning!
[14:56] <alan_g> Good afternoon
[15:16] <mterry> alan_g, so during mir::run_mir (called by unity-mir), I'm getting that "connect not called" error.  I think during DisplayServer construction.  I wouldn't expect such an error during a mir-internal call, right?
[15:19] <mterry> alf_, ^
[15:19] <alan_g> mterry: just looking for whre that comes from
[15:20] <mterry> sure
[15:21] <alf_> mterry: it sounds like mir is using the nested path, but something isn't going as expected
[15:22] <alan_g> mterry: sounds like the connection doesn't get established. Does the fd actually exist in the nested process?
[15:23] <mterry> alan_g, theoretically.  robert_ancell's branches do some clever fd passing around to make sure.  What posix call tests fd existence?
[15:24] <alan_g> mterry: is it feasible to launch unity8 using mir_demo_server_basic --launch-client unity8 - and avoid USC?
[15:25] <alan_g> Or does it need some other setup?
[15:26] <mterry> alan_g, I could, as a test, sure.  Let me get back to you
[15:27] <alan_g> mterry: obviously you need any switches to get it into nested mode
[15:27] <mterry> alan_g, well, mir_demo_server_basic sets MIR_SOCKET, right?  That should auto-switch to nested-mode.
[15:27] <racarr> fcntl(fd, F_GETFD is the FD test
[15:28] <mterry> racarr, ah cool.  I'll test that after this demo server test
[15:28] <alan_g> mterry: It does - I just didn't know if that was all you need
[15:29] <alan_g> racarr: Maybe we should use that to give a more helpful error message.
[15:32] <racarr> Seems useful.
[15:34] <racarr> The way the platform-api symbols are is a little weird for stuff like this
[15:34] <racarr> if you accidentally link libplatform-api-mirclient and libplatform-api-mirserver (nested unity8 shouldn't need platform API mirclient)
[15:35] <racarr> I guess you are going to get the wrong symbols?
[15:35] <racarr> maybe not, because we have the two different build QPAs with explicit linkage that are opened at runtime...
[15:35] <racarr> not sure how Qt loads them
[15:35] <racarr> *shrug*
[15:44] <mterry> alan_g, going through the demo, I get "Address already in use"...
[15:45] <mterry> alan_g, in about the same spot (DisplayServer constructor)
[15:45] <alan_g> mterry: try mir_demo_server_basic --standalone etc
[15:46] <mterry> alan_g, the server should fallback to standalone, since it doesn't have MIR_SOCKET, but ok
[15:47] <mterry> I'll also add --no-file
[15:48] <alan_g> mterry: Doh! that's the one I was thinking of
[15:50] <mterry> alan_g, aha!  OK.  That worked with --no-file.  So the fd being bad somehow leads to the "mir not connected" message?
[15:51] <mterry> alan_g, so lightdm/usc must be fucking up the fd passing
[15:51] <alan_g> mterry: It seems that way - but Mir should be giving a better diagnostic
[15:52] <alan_g> I suspect it is hanging  (or failing in some other bad way) in the connect call to a duff socket
[15:54]  * alan_g thinks he should log a bug
[16:10] <racarr> perhaps old news to other people but I finally figured out how to get a a good terminal on the phone. lol. adb shell is always weird with some terminal programs (i.e. text editors tend to not work). ssh over nexus 4 wifi sucks
[16:11] <racarr> adb shell service ssh start
[16:11] <racarr> is where it's at
[16:11] <racarr> adb forward tcp:2222 tcp:22
[16:11] <racarr> adb forward tcp:3768 tcp:3768
[16:11] <racarr> ssh<EMAIL_ADDRESS>-p 2222
[16:11] <racarr> err ignore the 3768
[16:11] <racarr> thats some unity qml debug stuff lol
[16:29] <alf_> kdub: @display-construction-overhaul2, do we need to access the native types outside of any of the other resources created with them?
[16:31] <kdub> the fb and the hwc?
[16:31] <alf_> kdub: yes the native android types
[16:33] <kdub> i don't think so (if i understand the question properly :) )
[16:41] <racarr> kdub: DisplayCommander, nice
[16:41] <kdub> hah :) i like that one too
[16:51] <alan_g> greyback: it's not immediately obvious to me which packages I need to compile unity-mir - so could you answer a quick question? Why does src/unity-mir/surfacecontroller.cpp need the line "#include <mir/surfaces/surface_stack_model.h>"? AFAICS it never uses the SurfaceStackModel definition.
[16:52] <greyback> alan_g:  "sudo mk-build-deps -ir debian/control" should install what you need, no?
[16:52] <alan_g> greyback: ack was just remembering that
[16:53] <greyback> alan_g: it's needed for the constructor of the SurfaceController, so ms::SurfaceStackModel is defined
[16:54] <alan_g> But it only needs a declaration
[16:54] <kdub> greyback, haven't tried in a while, but have we sorted out how to cross compile those components?
[16:54] <kdub> apologies for asking again :)
[16:55] <alan_g> greyback: I still see "qmirserverapplication.h:20:27: fatal error: QGuiApplication: No such file or directory"
[16:55] <greyback> kdub: tbh I've not tried since you last asked. But I agree we need to solve this story. A properly working pbuilder arm chroot would be very nice
[16:56] <greyback> alan_g: have you "qtbase5-dev" installed?
[16:57] <alan_g> greyback: yes
[16:57] <greyback> alan_g: make clean, re-run 'qmake' and see if that works
[16:57] <greyback> and make ofc
[16:59] <alan_g> greyback: no change (and no target ofc)
[17:00] <alan_g> greyback: I'm hitting EOD anyway. Maybe it will work in the morning. (But I'm pretty sure that header isn't needed)
[17:01] <greyback> alan_g: ok, talk tomorrow
[17:02] <greyback> alan_g|EOD: if I remove that header, it fails to build.
[17:02] <alan_g|EOD> What's the error?
[17:03] <alan_g|EOD> greyback: What's the error?
[17:04] <greyback> alan_g|EOD: error: invalid use of incomplete type 'class mir::surfaces::SurfaceStackModel'
[17:04] <greyback> alan_g|EOD: EOD, we can deal with this tomorrow :)
[17:04] <greyback> sorry :D
[17:04] <alan_g|EOD> np
[17:05]  * alan_g|EOD wishes for the line number. But has to take wife out to eat. ;)
[18:20] <kdub> racarr, (just bouncing naming suggestions around), how about "MonitorTraits" instead of "DisplayInfo"
[18:27] <racarr> kdub: I don't like monitor because monitors don
[18:27] <racarr> 't have a number_of_framebuffers_available
[18:28] <racarr> which is why I thought Output was nice.
[18:28] <kdub> yeah, but output is pretty overloaded
[18:28] <racarr> hmm
[18:29] <racarr> I think within the mga:: namespace it's relatively clear, Mir, graphics, android, output attributes
[18:29] <racarr> but not totally.
[18:30] <racarr> I didn't think DisplayInfo was that unclear
[18:31] <racarr> I think Attributes...to me carries a little more connotation that this is the configured information (i.e. the configured size, etc)
[18:31] <racarr> and not just the capabilities
[18:31] <racarr> which I think of as 'Info' but I'm not sure if the dictionary would back me up on that one aha
[18:32] <racarr> I think maybe it's just a struct instead of an interface
[18:33] <racarr> kdub: Hmm
[18:33] <racarr> is it just
[18:33] <racarr> the DisplayConfiguration?
[18:33] <kdub> eh, not quite
[18:34] <racarr> why?
[18:34] <kdub> i'd say a configuration would be the most expansive, so would include multimonitor configuration
[18:34] <racarr> an OutputConfiguration then perhaps
[18:34] <kdub> lets see what terms gbm has..
[18:34] <racarr> I mean, it's the configuration of a single display/output/monitor and some properties which resutl from that configuration (i.e. number of framebuffers available)
[18:34] <racarr> but the thing is, presumably in multimonitor scenarios
[18:34] <racarr> this changes
[18:35] <racarr> which is why I thought the word "Configuration" might make sense
[18:35] <racarr> you don't expect the information for a display to change but of course the configuration does
[18:37] <kdub> in multimonitor, it doesn't change
[18:38] <kdub> its just the class for the attributes/traits of each monitor
[18:38] <racarr> kdub: Are you sure? I mean
[18:38] <racarr> if I have an external display hooked up
[18:38] <racarr> am I guaranteed the same number of framebuffers
[18:38] <racarr> at various resolutions etc
[18:38] <racarr> also...the size can change right?
[18:38] <kdub> size can't really change
[18:39] <racarr> oh yeah
[18:39] <racarr> I forgot android hal doesn't really do sophisticated monitor configuration
[18:43] <racarr> kdub: I will let it toss around in my head a little more...DisplayInfo isn't bad though
[18:44] <racarr> I do think that a struct with constant data members
[18:44] <racarr> is perhaps a little more clear
[18:45] <racarr> because it's more like just some immutable piece of info than an object right
[18:45] <kdub> eh, have to think about that
[18:45] <kdub> essentially, thats what it is already
[18:46] <racarr> ? from the consumer perspective the values can chance
[18:46] <racarr> change
[18:46] <racarr> they are just const member functions now right? or did I misread
[18:48] <kdub> they are const member functions
[18:49] <kdub> even at that though, i'd rather have the interface
[18:51] <racarr> I think it's better to enforce the immutability, and the struct is a little better for tests
[18:51] <racarr> because you don't have to write these, mock the interface, set the getter functions to return values
[18:51] <racarr> type tests...which I think
[18:52] <racarr> are more strong coupling than good tests
[18:52] <racarr> in many cases
[18:56] <kdub> it makes for more test structure, but doesn't increase coupling in the production code
[18:56] <kdub> if i want to rename a struct member vs rename a class function, same amount of churn
[18:57] <kdub> i guess i could make a struct with its copy/assign deleted
[19:01] <racarr> kdub: Except, you don't have to update the tests that are passing in literals like {size, format, number}
[19:02] <racarr> I mean if you were writing the test first, you wouldn't write some class like Stub or MockDisplayInfo and set it up to return the three const values right
[19:02] <racarr> you would pass them as a literal tuple to the consumer
[19:02] <racarr> and then verify the state
[19:02] <racarr> as opposed to the interaction (consumer calls get_size(), which really isn't actually very interesting)
[19:03] <kdub> i'm sure i did just that at one point, but i probably wrote the DisplayInfo tests before the other ones
[19:04] <racarr> :) I mean at this point with an existing code base, and refactoring v new stuff writing the tests first of course becomes blurry
[19:04] <racarr> but I just mean, in the ideal, if you were sitting down to write some new class
[19:05] <racarr> and you knew it needed to do some computation based on the display size, pixel format, and number of frame buffers
[19:05] <racarr> well I feel like I would probably use a struct and literals and not an interface
[19:05] <racarr> but *shrug*
[19:08] <kdub> i guess i have to program that struct in different ways
[19:09] <kdub> and don't know if i want to have two constructors for the struct
[19:12] <racarr> ? If the values don't change shouldn't you initialize it with
[19:12] <racarr> the values themselves
[19:12] <racarr> and not the objects which contain the state
[19:12] <kdub> these classes are wrappers around two different HAL's (which actually own the state)
[19:14] <kdub> HWCInfo does a bit more than FBInfo
[19:28] <racarr> kdub: That seems kind of strange to me and it feels more like two different objects using the HALs should pack the same kind of struct
[19:28] <racarr> but
[19:28] <racarr> I will do a deeper read of the code
[19:28] <racarr> and comment on launchpad
[19:28] <racarr> because im not sure exactly how it all links up
[23:14] <racarr> I think it's something about powerd with the android integration tests failing
[23:14] <racarr> kdub: The symtoms are pretty weird. If you 'stop unity8' while the screen is blanked...about 9/10 times
[23:14] <racarr> integration tests will then fail with the error to post to fb device
[23:14] <racarr> unity8 will not start back, etc
[23:15] <kdub> yeah, i'm not convinced we have that architecture worked out just yet
[23:15] <racarr> if you press power button, even though unity8 is dead
[23:15] <racarr> something happens
[23:15] <racarr> because now the integration tests will all pass
[23:15] <racarr> except the binary will hang while exiting
[23:15] <racarr> and that's as far as I've gotten
[23:15] <racarr> you cant kill it at that point lol
[23:16] <racarr> reading through powerd now
[23:19] <racarr> static void update_internal_state(void)
[23:19] <racarr> ....
[23:19] <racarr> ....
[23:20] <racarr> that is not the best function name ;)
[23:30] <kdub> racarr, you know how to use powerd-cli?
[23:37] <racarr> kdub: Oh. I sort of do now :p
[23:40] <racarr> kdub: Maybe I dont :p I was hoping to turn the display on with it
[23:40] <racarr> but it hangs
[23:40] <kdub> i just do 'powerd-cli display on', seems to work
[23:41] <racarr> kdub: After stopping unity8 while the display was off?
[23:42] <kdub> i just do that to keep the display on once its gotten to the on state
[23:44] <racarr> oh I see