[01:13] <fta> hm, i've lost subpixel with the new cairo
[09:19] <XioNoX> Hi !
[09:34] <asac> hi XioNoX
[09:35] <XioNoX> asac, I've just add the license block
[09:35] <asac> good ... everywhere?
[09:35] <asac> e.g. on all your branches?
[09:37] <XioNoX> not the 3rd
[09:41] <asac> fta: oh. dholbach voted for you ;) ... nice
[09:41] <asac> XioNoX:  ;)
[09:41] <asac> all good are three ;)
[09:41] <XioNoX> ok, nice
[10:01] <XioNoX> asac, What is the "awsome" think you told me yesterday ?
[10:02] <asac> XioNoX: hehe ;)
[10:04] <asac> XioNoX: what i want is a the application pane ... but just filtered by known plugin mime-types
[10:04] <XioNoX> do you think I'll have time ?
[10:05] <XioNoX> and what is the application pane ?
[10:07] <asac> XioNoX: preferences -> applications
[10:07] <asac> XioNoX: thats basically what we want to manage plugin mime-types
[10:08] <XioNoX> so I work in firefox code ?
[10:08] <asac> XioNoX: no
[10:08] <XioNoX> ubufox ?
[10:08] <asac> XioNoX: yes. for now
[10:09] <asac> XioNoX: i think all what we do for the altplugins things is kind of a prototype to show upstream that managing multiple alternatives can be nicely done
[10:09] <XioNoX> ok
[10:10] <asac> XioNoX: what we want is a new menu item in the right row: "Use other plugin ..."
[10:10] <asac> XioNoX: you think you can add that?
[10:10] <asac> try to overlay it i'd say
[10:12] <XioNoX> I don't understand :)
[10:12] <asac> XioNoX:  have you found that pane?
[10:13] <XioNoX> yes
[10:13] <asac> on the left there  are mime-types (e.g. shockwave flash)
[10:13] <asac> on the right there are options
[10:13] <asac> err "Action"
[10:13] <asac> XioNoX: got that?
[10:14] <XioNoX> yep
[10:14] <asac> XioNoX: ok ... in action there is a drop down menu?
[10:14] <XioNoX> yes
[10:14] <asac> for now we want "Use other plugin ..." there
[10:15] <asac> which triggers our plugin finder wizard with the proper mime-type!
[10:16] <XioNoX> it is this part that I don't understand :D
[10:17] <XioNoX> a new "action" element called "Use other plugin" ?
[10:17] <asac> yes
[10:17] <XioNoX> haaa
[10:17] <XioNoX> but nobody goes in this tab
[10:18] <asac> XioNoX: true
[10:18] <asac> XioNoX: however,
[10:19] <asac> the idea is to use the same UI in the addons manager ... just that it doesnt use the gnome-mime database, but the mime-types currently provided by plugins
[10:19] <asac> XioNoX: if you think thats too much we can also improve the "current" plugin finder wizard
[10:21] <XioNoX> I think it is a lot of work for a little thing, but I can be wrong
[10:22] <XioNoX> what do yo have in mind by "improve the "current" plugin finder wizard" ?
[10:24] <asac> XioNoX: only display plugins that are not currently used
[10:27] <asac> XioNoX: we also need to take care that if you install gnash after flahsplugin-nonfree that you will use gnash
[10:27] <asac> if you then install flashplugin-nonfree again, you want that to be used
[10:27] <asac> "install" select in alternative plugin finder
[10:27] <asac> "install" == select in alternative plugin finder
[10:28] <XioNoX> when you install flahsplugin-nonfree from repos, gnash is removed, etc...
[10:28] <asac> XioNoX: no its not
[10:28] <asac> XioNoX: currently we maintain alternatives ... but that is not really required imo
[10:28] <asac> well
[10:29] <asac> for global alternatives might be ok. but what we probably want to do here is to put the a link into the profile directory
[10:29] <asac> so the user can switch between installed alternatives
[10:30] <asac> but in the end we lack mozilla features in order to do it in a perfect fashion
[10:30] <XioNoX> i agree
[10:31] <asac> e.g. mozilla doesnt allow you to select individual plugins by individual mime-types
[10:31] <XioNoX> ok
[10:31] <asac> so we need to be innovative ;)
[10:32] <XioNoX> so first, filter plugins in the richlist ?
[10:32] <XioNoX> to show only installed plugins
[10:33] <XioNoX> err, non installd plugins
[10:33] <asac> XioNoX: we have a rich list?
[10:34] <asac> XioNoX: if you want to go for the application panel, yes.
[10:34] <XioNoX> not rich
[10:34] <XioNoX> radiolist
[10:34] <asac> yeah
[10:39] <XioNoX> I get a new version of ubufox ?
[10:39] <XioNoX> or I work on an existing one ?
[10:40] <asac> XioNoX: i think it belongs in the altplugins branch
[10:40] <XioNoX> ok
[10:41] <asac> XioNoX: what you can do is to check whether /usr/lib/<packagename> ... exists
[10:41] <asac> that is a bad hack ... but it probably gives you a quite accurate idea whether the package is installed or not
[10:41] <XioNoX> but this works only for packages :(
[10:41] <XioNoX> not for user-scale install
[10:45] <asac> radiolist, yes.
[10:46] <asac> XioNoX: well. for user based install we could try what i sadi ... e.g. create the proper link
[10:53] <XioNoX> it is a bad hack, no ?
[10:53] <XioNoX> it is like the plugin is installed twice, no ?
[10:55] <asac> no ... i think profile plugins will win
[10:55] <asac> but not sure
[10:56] <XioNoX> if it is like extentions, profile win
[10:58] <asac> not 100% sure ... i think plugins are rather stupid
[10:58] <asac> whatever is scanned first and matches mime-type wins
[10:58] <asac> so profile probably will win
[10:58] <XioNoX> and we can't use the about:plugin stuff ?
[10:59] <asac> fopr what?
[10:59] <XioNoX> to know what plugin is used
[10:59] <XioNoX> for wich mimetype
[10:59] <asac> XioNoX: you can iterate all plugins
[11:00] <asac> XioNoX: however, its hard to match what package each plugin is mapped to
[11:00] <XioNoX> and about:plugins don't make différence between pakages and profD plugins
[11:00] <asac> XioNoX: well ... we can find the install path
[11:01] <asac> pluginreg.dat
[11:01] <XioNoX> because it will be the same thing if we make links in te user dir
[11:01] <asac> in the profile
[11:01] <asac> not sure if it follows links
[11:01] <asac> if it does it becomes even trickier
[11:02] <XioNoX> using pluginreg should be easier, no ?
[11:03] <asac> XioNoX: well ... that info you can get through the navigator object
[11:03] <asac> in javascript
[11:03] <XioNoX> ?
[11:04] <XioNoX> there are mimetype, plugin name, and file location
[11:11] <asac> yes
[11:13] <asac> XioNoX: ok. how about this:
[11:13] <asac> we add the ability to set a pref modules.plugins.mimetypes.application/pdf = PATHTOPLUGOm
[11:13] <asac> to firefox core
[11:14] <asac> we add the ability to set a pref modules.plugins.mimetypes.application/pdf = PATH/TO/PLUGIN
[11:14] <asac> e.g. pref("modules.plugins.mimetypes.application/shockwave-flash", PATH/TO/PLUGIN)
[11:15] <asac> XioNoX: i guess that would be helpful right?
[11:16] <XioNoX> it wil be the same as the one present in the pluginreg.dat, no ?
[11:16] <XioNoX> and who will set this pref ?
[11:16] <asac> XioNoX: our wizard will set that pref
[11:16] <asac> XioNoX: (or the user manually if he wants)
[11:17] <asac> XioNoX: and yes: the path would be the one in pluginreg.dat
[11:17] <XioNoX> so why using an intermediate pref ?
[11:17] <asac> XioNoX: why? because the pluginreg.dat format doesnt know anything about preference
[11:17] <XioNoX> why we don't just ask pluginreg.dat when needed ?
[11:18] <asac> and there is no write-access interface available anyway
[11:18] <asac> XioNoX: pluginreg.dat has no information about preference when there are multiple plugins for the same mimie-type
[11:18] <XioNoX> but we don't have to modify it, just get values
[11:18] <asac> XioNoX: which value?
[11:18] <asac> there is no mean to express user-preference in pluginreg.dat
[11:19] <asac> thuse we would need to extend that format ... which i dont want -> thus the pref
[11:19] <XioNoX> ha ok
[11:19] <asac> and the reason why i dont want to extend that format is that there is no API to manage plugin registry at all
[11:19] <asac> so we would have to invent even more
[11:20] <XioNoX> you want that if there are many plugin for the same mimetype installed
[11:20] <XioNoX> the user can chose
[11:20] <asac> yes
[11:20] <asac> right
[11:20] <asac> the final idea is still to have the drop down box from prefernec -> applications where the user can switch easily when there are already multiple installed
[11:20] <XioNoX> and not if there are 1 installed and you install an alternative it remove the old one
[11:20] <asac> or install new ones thjrough "get other plugins ..."
[11:20] <asac> XioNoX: right
[11:21] <asac> XioNoX: doing that will cover the user install case i hope
[11:21] <asac> XioNoX: only thing that is tricky is to figure which path the "just-installed" plugin has
[11:21] <asac> for packages that should be more or less easy
[11:21] <asac> for .xpi installs that can be harder, but we will figure something i am sure ;)
[11:22] <asac> XioNoX: i can write the firefox core changes to honour such preferences
[11:22] <asac> you can write the logic that allows users to switch to other plugins ;)
[11:23] <XioNoX> this seam to be a big project
[11:23] <XioNoX> and there are some hope that this will be included upstream ?
[11:23] <asac> XioNoX: its not a big project
[11:24] <asac> XioNoX: the two parts are managable
[11:24] <XioNoX> ok
[11:24] <asac> XioNoX: if you use the current plugin finder wizard at least
[11:24] <asac> implementing it the applications panel way is more work
[11:24] <asac> and is what i suggested in the upstrewam bug
[11:24] <XioNoX> ok
[11:25] <asac> so whether this can land, depends on how well we make it work for us
[11:25] <asac> imo
[11:25] <asac> once the people see that it works, there is no real way to refuse to have the proper solution imo
[11:26] <asac> XioNoX: i think the clean solution would be to split the features apart:
[11:26] <asac> 1. choose which of the installed plugins to use
[11:26] <asac> 2. install more plugins -> which would end in a dialog for 1.
[11:28] <asac> makes sense XioNoX ?
[11:28] <XioNoX> when we clic on "Use other plugin" ?
[11:28] <XioNoX> or were ?
[11:28] <asac> fta: there? what new liferea is that?
[11:29] <XioNoX> asac, going to eat
[11:29] <asac> XioNoX: ok
[11:29] <XioNoX> see you
[11:32]  * gnomefreak hopes new gnome gives me back system bell
[11:45] <asac> gnomefreak: unlikely ;)
[12:19] <XioNoX> back
[12:21] <asac> XioNoX: ok. i think i have a first patch for the thing
[12:21] <XioNoX> already ?
[12:21] <asac> XioNoX: however, you probably need to spin your own xulrunner
[12:21] <asac> XioNoX: for the "select plugin by mime-type" ...yes.
[12:21] <asac> err
[12:21] <asac> for the preference things
[12:21] <XioNoX> spin your own xulrunner ?
[12:22] <asac> XioNoX: let me push it ;)
[12:22] <XioNoX> ok
[12:24] <asac> XioNoX: mkdir myxul; cd myxul; bzr branch lp:~mozillateam/xulrunner/xulrunner-1.9.head; cd ..; mkdir tarballs; cd tarballs; wget http://launchpadlibrarian.net/16695860/xulrunner-1.9_1.9.0.2%7Ecvs20080807t1327%2Bnobinonly.orig.tar.gz; cd ../xulrunner-1*/; sudo apt-get build-dep xulrunner-1.9; sudo apt-get install bzr-builddeb; sudo apt-get install built-essentials; edit debian/patches/series (enable the last patch here); bzr bd --merge --dont-
[12:24] <asac> err
[12:24] <asac> XioNoX: mkdir myxul; cd myxul; bzr branch lp:~mozillateam/xulrunner/xulrunner-1.9.head; mkdir tarballs; cd tarballs; wget http://launchpadlibrarian.net/16695860/xulrunner-1.9_1.9.0.2%7Ecvs20080807t1327%2Bnobinonly.orig.tar.gz; cd ../xulrunner-1*/; sudo apt-get build-dep xulrunner-1.9; sudo apt-get install bzr-builddeb; sudo apt-get install built-essentials; edit debian/patches/series (enable the last patch here); bzr bd --merge --dont-purge -
[12:24] <asac> thats  ;)
[12:24] <XioNoX> and what does it wo ?
[12:25] <asac> it builts the latest xulrunner-1.9 from our packaging branch ;)
[12:25] <asac> to do that it branches the packaging branch, gets the tarball
[12:25] <asac> installs the build-dependencies
[12:25] <asac> and bzr-builddeb
[12:25] <asac> and then you edit debian/patches/series to enable the my patch
[12:25] <asac> and build using the "bzr bd ..." command
[12:25] <asac> ;)
[12:25] <asac> all that is done in a directory called myxul ;)
[12:28] <asac> XioNoX: that isnt tested yet ... at best start with UI for selecting a plugin ;)
[12:28] <asac> applying that to the backend will be as easy as setting a pref ;)
[12:29] <XioNoX> ok
[12:29] <XioNoX> myxul ahve to be in the bzr working folder (ubufox plugin) or not
[12:29] <XioNoX> ?
[12:29] <asac> XioNoX: no ... my description was based on that you dont have anything
[12:29] <asac> ;)
[12:30] <asac> if you already have the xulrunner-1.9.head branch on your disk you can start with getting the tarball
[12:30] <XioNoX> ha ok
[12:30] <XioNoX> thx
[12:30] <asac> XioNoX: anyway. chances are 50% that this works out of box. so better start implementing the "select plugin for mimetype" dialog
[12:31] <asac> XioNoX: http://developer.mozilla.org/en/docs/DOM:window.navigator.plugins
[12:31] <asac> thats how you can access installed plugins (i hope)
[12:31] <asac> well ... i should work (looked at the doc)
[12:31] <asac> great
[12:32] <XioNoX> first i'm trying the xulrunner commands
[12:32] <asac> so what we want is a dialog that allows you to switch to another installed plugin that serves the mime-type
[12:33] <asac> XioNoX: sure. the built will take 20-45 minutes anyway ;)=
[12:34] <XioNoX> E: Les dépendances de compilation pour xulrunner-1.9 ne peuvent pas être satisfaites.
[12:34] <XioNoX> yeah, french :)
[12:35] <XioNoX> can't satisfy build deps for xulrunner...
[12:35] <asac> XioNoX: you forgot to run the apt-get commands
[12:35] <asac> at least the build-dep one
[12:35] <asac> ;)
[12:35] <XioNoX> sudo apt-get build-dep xulrunner-1.9
[12:35] <asac> if you did, let me know what dependency is missing
[12:35] <XioNoX> tell me this
[12:35] <XioNoX> ho
[12:36] <XioNoX> i don't know it just say that it can't
[12:36] <XioNoX> i don't know, it just say that it can't
[12:37] <asac> XioNoX: you need deb-src lines in your sources.list
[12:37] <asac> (apt)
[12:37] <XioNoX> I have them
[12:37] <asac> well. it would work then
[12:38] <XioNoX> here is the problem
[12:41] <asac> XioNoX: ?
[12:41] <asac> you just need to install the missing dependencies
[12:41] <asac> thats all
[12:42] <asac> if build-dep is broken for you do it manually ... but it works for everyone ;)
[12:46] <XioNoX> ok, the probleme come from the package python2.5...
[12:51] <asac> XioNoX: whats the problem?
[12:53] <XioNoX> I have python2.5....ubuntu5 and python2.5-dev need python2.5....ubuntu4.1 only
[12:53] <XioNoX> I've installed python2.5....ubuntu4.1 with dpkg, but now it is the pess in the pacakges
[12:53] <asac> XioNoX: dontgrade ;)
[12:53] <asac> downgrade  i mean
[12:53] <asac> is that a problem?
[12:54] <XioNoX> yes, but i can't
[12:54] <XioNoX> if i downgrade it wan't to remove the half of my system
[12:55] <asac> XioNoX: where did you get the python debs from?
[12:55] <XioNoX> ok fix
[12:55] <asac> good
[12:55] <XioNoX> I don't know
[12:55] <XioNoX> reps
[12:55] <XioNoX> repos
[12:56] <XioNoX> broken pakage manager have to be improved
[12:57] <XioNoX> build running
[12:59] <XioNoX> I'll see of it is true that 64bits compile faster
[13:03] <rbu> asac: morning! say, which system settings plugin do you use for NM in ubuntu then?
[13:05] <asac> rbu: in ubuntu i havent enabled ifupdown yet.
[13:05] <asac> rbu: tonight i made a break through though ;) ... so in the near future Ill enable it ;)
[13:06] <asac> so hopefully we will have: --plugins=ifupdown,keyfile
[13:07] <rbu> asac: ifupdown would store the settings in normal debian settings files?
[13:07] <asac> rbu: ifupdown is just legacy support ... i currently dont feel to implement a read/write approach. so for now its read-only
[13:08] <asac> keyfile would be used for write support
[13:08] <asac> i hope in this order it will automagically work ;)
[13:09] <rbu> asac: ah, so it would parse that /etc/network/interfaces file?
[13:09] <asac> rbu: yes
[13:09] <asac> rbu: when time permits i will also add support for wpa_supplicant.conf
[13:09] <rbu> asac: is mbiebl going with the same thing, or are you guys not talking to each other :-)
[13:09] <asac> but maybe to a separate read-only plugin
[13:10] <asac> rbu: mbiebl is waiting for my implementation iirc
[13:10] <asac> rbu: the idea is that it gets committed upstream asap
[13:10] <asac> i am overdue to deliver that
[13:10] <rbu> asac: lazy !$!§$%
[13:10] <rbu>  :-)
[13:10] <asac> rbu: well ... its a moving target
[13:10] <rbu> asac: yeah, but wpa_supplicant.conf would be cool :-)
[13:10] <asac> the system-settings thing was broken for quite some time (for connections that required secret)
[13:11] <asac> rbu: thats simple ... wpa_supplicant.conf alone is just to parse the setting and creating NMConnections with those settings
[13:11] <asac> (not bound to a mac address)
[13:12] <asac> not yet sure where to configure which setting to use. problem is that ifupdown also would need wpa_supplicant.conf imo. but thats something i have to figure out elsewhere
[13:12] <asac> and a wpasupplicant top-level plugin makes sense ;)
[13:13] <rbu> asac: well, you're in that swamp a lot deeper than me, i've just learned about what nm-settings is today, so ... way to go for me
[13:13] <asac> rbu: hehe ;)
[13:14] <asac> rbu: learning by doing. i am still learning as well ;) .... but if you want to help, you could probably implement a wpa_supplicant.conf parser
[13:14] <asac> (which would be independent from nm-settings)
[13:14] <asac> (and it would definitly speed this feature up)
[13:15]  * gnomefreak ran into issues ill be back when handled
[13:20] <XioNoX> asac, compillation done
[13:21] <asac> XioNoX: hehe ;)
[13:21] <asac> XioNoX: ok ... install the packages and see if firefox still works ;)
[13:22] <asac> XioNoX: then see if you get a crash when using any plugin
[13:22] <asac> then see if you can force gnash or something even though flashplugin-nonfree would be used by default
[13:22] <asac> XioNoX: but well :) ... at best just go and implement the dialog ;) ... that will be tricky enough. I will take care that the "force" works
[13:38] <XioNoX> asac, I was on tel
[13:48] <XioNoX> xulrunner works well ;)
[13:54] <fta> can anyone using my ppa confirm that lcd filtering is broken (or not) with my cairo 1.7.4 ?
[14:00] <asac> XioNoX: how does it work well?
[14:00] <asac> XioNoX: did you try to switch plugins?
[14:00] <asac> e.g. by setting manually the pref?`
[14:01] <asac> fta: i can try after lunch break
[14:01] <asac> (which i should really do now ;))
[14:01] <XioNoX> we can do that ?
[14:01] <asac> XioNoX: yes. thats what i added
[14:01] <asac> ;)
[14:01] <asac> XioNoX: read the patch for instructions
[14:01] <asac> XioNoX: i documented it on top
[14:01] <XioNoX> ok
[14:02] <asac> XioNoX: you can only switch between plugins that are in pluginreg.dat
[14:02] <XioNoX> ok
[14:02] <asac> so maybe you need to create a link to libgnashplugin.so in your profiles plugins/ directory
[14:02] <asac> (given that you use the nonfree thing by default on system)
[14:38] <fta> asac, no news of pitti ?
[14:39] <asac> fta: if he doesnt talk on #-devel he is probably on holiday
[14:39] <fta> ok
[14:45] <XioNoX> asac, I don't see any new plugin in the applications tab
[14:46] <XioNoX> no new choice for flash
[14:47] <asac> XioNoX: why would that happen
[14:47] <asac> there is no code for that at all
[14:47] <XioNoX> what does your code ?
[14:47] <asac> XioNoX: read the patch
[14:47] <asac> there is documentation
[14:48] <XioNoX> good idea :)
[15:00] <fta> http://www.glazman.org/weblog/dotclear/index.php?post/2008/07/29/Google-and-MPL
[15:01] <fta> (not new, i know. i'm still catching up with my 1000+ unread articles)
[15:01] <fta> asac, btw, did you see my xul1.9 issue with liferea yesterday ?
 checking for XulRunner 1.9+ support... checking for XULRUNNER... yes
 Fatal: XulRunner enabled, but XULRUNNER_HOME is empty!
 make: *** [config.status] Error 1
 asac, ^^ that's the new liferea
 asac, http://paste.ubuntu.com/38620/
[15:11] <fta> http://clarkbw.net/designs/dialog-invasion/dialog_invasion.ogg
[15:33] <fta> mozilla bug 408925
[16:00] <jtv> asac: ping
[16:04] <asac> pong
[16:05] <asac> fta: i did see the xul issue ... i asked you where you gto that new liferea from ;)
[16:05] <fta> upstream
[16:05] <asac> fta: what is XULRUNNER_HOME used for?
[16:05] <asac> -rpath?
[16:05] <asac> if so, just wipe it
[16:05] <fta> no idea
[16:05] <fta> i want this bug 203157 fixed
[16:06] <asac> fta: search the Makefiles for XULRUNNER_HOME usage ... i guess its again a -rpath thing which means that they are stupid ;)
[16:06] <asac> oh dear ... the rtl8187 driver just sucks
[16:07] <asac> ok that doesnt make any sense
[16:07]  * asac reboots to latest kernel again
[16:09] <fta> ./debian/patches/xulrunner-1.9:         gtk_moz_embed_set_comp_path(XULRUNNER_HOME);
[16:11] <asac> fta: yeah thats stupid
[16:11] <asac> fta: they can use the GRE_PATH they found
[16:11] <asac> or just leave that lone (if they use push_startup
[16:11] <asac> )
[16:12] <XioNoX> asac, how can I interract with the preferences dialog ?
[16:12] <fta> ./src/mozilla/Makefile.am:liblihtmlx_la_CFLAGS = $(XULRUNNER_CFLAGS) $(PACKAGE_CFLAGS)  -DXULRUNNER_HOME=\""$(XULRUNNER_HOME)\""
[16:13] <asac> XioNoX: why do you want that?
[16:14] <asac> fta: yes, drop that define ... and #ifdef XULRUNNER_HOME the set_comp_path above
[16:14] <fta> it's already in that patch
[16:14] <fta> so basically, it's not used
[16:15] <XioNoX> asac, I don't really know how to start..
[16:17] <XioNoX> I have to modify the list of options in the application tab for some plugins (like flash, etc...)
[16:17] <XioNoX> no ?
[16:22] <jtv> Hey asac
[16:37] <fta> E: stream.c: Assertion 'pa_atomic_load(&(s)->_ref) >= 1' failed at pulse/stream.c:948, function pa_stream_writable_size(). Aborting.
[16:37] <fta> Program received signal SIGABRT, Aborted.
[16:37] <fta> crimsun, ^^
[16:42] <asac> XioNoX: I'd suggest to overlay the element
[16:43] <XioNoX> but I have no clue to find it in the firefox sources
[16:44] <asac> XioNoX: use dom inspector
[16:45] <XioNoX> how ?
[16:45] <XioNoX> ok find
[16:52] <fta> asac, could you please test cairo ?
[16:58] <XioNoX> asac, I'll continue from home
[17:00] <fta> http://paste.ubuntu.com/38830/
[17:00] <fta> too bad i can't retrace post-mortem
[17:02] <asac> fta: what shall i test?
[17:02] <fta> lcd filter
[17:02] <fta> subpixel blabla
[17:02] <asac> not sure how that is testable
[17:02] <asac> whats the problem that gets fixed?
[17:02] <asac> e.g. how can i recognize that
[17:03] <fta> just a shift for an ubuntu patch to upstream support. for me, it regressed
[17:03] <asac> fta: how?`
[17:03] <fta> everything looks different once restarted
[17:03] <asac> libcairo - 1.5.4-0ubuntu1~fta3  ?
[17:03] <fta> no
[17:03] <fta> 1.7.4
[17:04]  * asac restarts X
[17:07] <fta>   samarium (xen-i386)  	 Building i386 build of xulrunner-1.9 1.9+nobinonly-0ubuntu2~gutsy0~jjv in ubuntu gutsy RELEASE [gnomefreak]
[17:07] <fta> oh, he's not here
[17:08] <asac> fta: i think everything looks better
[17:08] <asac> but i am using "best shapes" in font appearence dialog
[17:08] <fta> hm
[17:08] <asac> so the difference isnt that bad
[17:09] <asac> smoothing (LCD) always looked bad for me
[17:10] <asac> does that make a difference for you?
[17:12] <fta> i'm using lcd
[17:21] <asac> fta: lcd regressed a bit. but i am not 100% sure.
[17:21] <asac> hard to fix the difference for my eyes
[17:21] <asac> i think some lines are not of the same width with 1.7.4
[17:21] <asac> while they are more accurate in 1.6.4
[17:22] <asac> but best shapes is better in any case ;)
[17:22]  * asac reverts to that
[17:24] <fta> http://www.sofaraway.org/ubuntu/tmp/lcd.png
[17:24] <fta> i haven't restarted panel & chat yet, but gedit is fresh
[17:24] <fta> xchat
[17:26] <asac> i think my eyes are not made for fonts. i dont see any difference :(
[17:26] <fta> zoom in
[17:27] <fta> x4 or more
[17:27] <fta> compare "View"
[17:28] <asac> sorry. i think i see a difference, but thats due to the zoom i guess
[17:29] <asac> but as i said ... i saw some difference here too
[17:36] <fta> ok, sound for <video>/<audio> is as bad in 3.1 official nightlies as in my builds. i'm not crazy then.
[18:01] <fta> http://www.journaldugeek.com/files/2008/08/brando-zoom6x.jpg
[19:16] <francois_fon> 'soir
[19:17] <francois_fon> une personne a déjà eu un soucis (comme moi) pour ouvrir gmail sous firefox ?
[19:17] <sebner> francois_fon: english?
[19:17] <francois_fon> ok ooops
[19:17] <francois_fon> i try
[19:18] <francois_fon> i can't open gmail with firefox
[19:18] <francois_fon> it is not a problem from gmail
[19:18] <sebner> francois_fon: error?
[19:18] <francois_fon> i have delete cookies
[19:18] <francois_fon> no error
[19:18] <francois_fon> gmail is open
[19:18] <francois_fon> i note my login and password
[19:19] <francois_fon> and after gmail is working
[19:19] <francois_fon> but it never open
[19:19] <francois_fon> i can only open gmail "basic HTML as default view"
[19:20] <sebner> so you have a problem with the Javascript version?
[19:21] <francois_fon> hmm
[19:21] <francois_fon> http://img523.imageshack.us/my.php?image=capturepv3.png
[19:24] <sebner> francois_fon: I see. maybe someone else here can help you
[19:24] <francois_fon> i hope :)
[19:24] <francois_fon> i have test gmail with opera and no soucy
[19:24] <francois_fon> but opera is not open-source :/
[19:31] <francois_fon> remove firefox and install it again is a good idea ?
[19:42] <fta> https://wiki.ubuntu.com/MozillaTeam/Bugs
[19:45] <francois_fon> fta: thx, i look
[19:45] <fta> or try http://mail.google.com/mail/?ui=2
[19:47] <francois_fon> same problem
[19:48] <francois_fon> fta: it is a good idea if i remove firefox and install it again ?
[19:49] <fta> francois_fon, not if the issue is caused by one of your extensions/plugins, it will not change anything
[19:49] <fta> try with a new profile as described in the doc
[19:50] <francois_fon> ok thx
[21:33] <saivann> asac : ping
[21:37] <saivann> asac : In case you have time, I would absolutely need new thunderbird-locales to be uploaded to intrepid, since I'm about to release new 0.8 packages for lightning-extension-locales which will depends on new thunderbird-locales
[22:10] <ma10> i'm trying to debug a crash that looks xulrunner-related. bug 259533. but i need some help..
[22:26] <Jazzva> asac, I just read someone mentioned that nspluginwrapper 1.1.0 works for him. I'll see to package it after 23rd. Will we still have time to get it into intrepid (feature freeze is on 28th of August)
[22:38] <ma10> yuppp fixed!
[22:39] <ma10> fta, note that xulrunner-1.9 - 1.9.0.2~cvs20080807t1327+nobinonly-0ubuntu1~fta1 fixes an ugly crash in the new azureus
[22:42] <fta> excellent
[22:42] <fta> Jazzva, the liferea in my ppa fixes the 100% cpu issue
[22:43] <Jazzva> fta, yay :)
[22:43] <Jazzva> pushing to intrepid? :)
[22:43] <ma10> now i can sleep :)
[22:43] <fta> I will look for a sponsor
[22:45] <Jazzva> good :)
[22:45] <Jazzva> fta, aren't you a MOTU now?
[22:45] <fta> not that i'm aware of
[22:45] <Jazzva> ah.. well, soon to be, right?
[22:45] <fta> who knows
[22:55] <ma10> fta, should i assign the bug to mozillateam so you remember to close it in the new release?
[22:55] <ma10> also, you could notify me before the release so i can confirm it fixed
[22:55] <fta> bug id ?
[22:55] <ma10> bug 259533
[22:57] <fta> hm
[23:07] <asac> Jazzva: right. thats fine
[23:08] <asac> ma10: all fine?
[23:08] <ma10> it doesn't crash.. later i'll test it on another system
[23:09] <asac> k
[23:10] <fta> i can't find which bug moz fixed for that crash. looks like luck to me
[23:11] <asac> saivann: thats fine. are you here tomorrow. then just ping me and we can upload the whole lot
[23:11] <fta> liferea has a warning: http://lintian.debian.org/tags/quilt-patch-with-non-standard-options.html
[23:12] <ma10> could be.. i searched for it and i came uo empty.. but mozilla bugtraker is a mess.
[23:12] <fta> patches have been "converted" from dpatch to quilt just by a rename :0
[23:12] <fta> asac, should I fix that or ignore ?
[23:12] <saivann> asac : Great, my sunbird-locales and lightning-extension-locales packages will be ready tomorrow and includes many changes to make them easy to maintain and to prevent current problems in intrepid with sunbird and lightning-extension
[23:13] <ma10> also, it's not reported for debian
[23:13] <asac> saivann: great.
[23:13] <asac> fta: i'd say as long as we merge from debian we should diverge more
[23:13] <asac> fta: maybe ping debian maintainer and provide him with fix to get this fixed
[23:13] <asac> s/we should/we shouldn't/
[23:14] <fta> usually i know, but you said debian is frozen for a long time...
[23:14] <asac> true
[23:14] <asac> but lintian isnt important imo
[23:15] <asac> if there is a new upstream release, we can bump, but fixing cosmetic issues like this should be done in debian
[23:15] <fta> this is a new release
[23:15] <asac> oh
[23:16] <asac> well. but since the issue existed in the version before the same reasoning would be valid imo
[23:16] <fta> 1.4.16b-0.1ubuntu1 -> 1.4.18-0ubuntu1
[23:16] <asac> yeah. just do the upgrade. dont care about fixing lintian things taht existed in 1.4.16b
[23:17] <asac> thats my pov
[23:17] <asac> http://bugs.debian.org/release-critical/
[23:17] <asac> more than 200 bugs to go
[23:17] <asac> so probably will take some time for debian lenny to get releasd
[23:27]  * asac off ... g'night
[23:32] <fta> Jazzva, bug 259578
[23:32] <fta> let's wait now
[23:32] <fta> Jazzva, being motu wouldn't have helped, it's in main
[23:52] <fta> http://www.glazman.org/weblog/dotclear/index.php?post/2008/08/06/GRRRRRRR
[23:52] <fta> i agree with that.