[00:10] <micahg> fta: should sunbird be a new bzr repo?
[00:14] <fta> there's already a branch somewhere
[00:14] <fta> if you feel like maintaining it, go ahead
[00:15] <fta> BUGabundo, indeed, it's a bit small :P
[00:16] <micahg> fta: the current branch is labeled 0.x, should I just modify the name?
[00:16] <BUGabundo> LOLOLOLOL
[00:16] <BUGabundo> fta: on a 15 "?
[00:16] <micahg> sunbird 1.0b1 was just tagged
[00:17] <fta> micahg, no need to make a new project, jsut bump on top. the old one will die along with tb2
[00:18] <kenvandine> fta, we removed the font size selector
[00:18] <kenvandine> their is currently nothing in the viewer that lets us actually change that
[00:18] <kenvandine> so it has been removed from the prefs
[00:18] <kenvandine> so it just follows the system font settings
[00:22] <fta> kenvandine, http://www.sofaraway.org/ubuntu/tmp/gwibber-fonts.png
[00:22] <BUGabundo> kenvandine: my system fonts are bigger then that
[00:22] <fta> me too
[00:22] <BUGabundo> actually all my system fonts are set to 10 points
[00:22] <BUGabundo> and gwibber is 8pt, at max
[00:23] <BUGabundo> I bet its smaller then that
[00:23] <kenvandine> so maybe that bug still exists?
[00:23] <kenvandine> ryan said that bug was fixed
[00:23] <kenvandine> but i can't confirm
[00:23] <kenvandine> so you think we should consider going back to +2?
[00:24] <kenvandine> seems arbitrary though
[00:24] <BUGabundo> you just got two users on lucid confirming it :D
[00:24] <BUGabundo> kenvandine: I can't read what's on my screen
[00:24] <BUGabundo> its useless to me like this
[00:24] <kenvandine> i meant i can't confirm that the webkit bug was really fixed
[00:24] <fta> (I'm still with karmic, not lucid)
[00:25] <fta> maybe our webkit is just too old
[00:25] <BUGabundo> oh I though you said you were upgrading
[00:25]  * BUGabundo checks
[00:25] <fta> BUGabundo, for the 1st time this cycle, i didn't jump at day one
[00:25] <BUGabundo> libwebkit-1.0-2:
[00:25] <BUGabundo>   Installed: 1.1.16-3
[00:26] <kenvandine> other people have been complaining that the fonts were just huge
[00:26]  * micahg will get to upgrade a month early this cycle :)
[00:26] <BUGabundo> http://webkit.org/
[00:26]  * kenvandine needs to run... will look more later
[00:27] <BUGabundo> http://svn.webkit.org/repository/webkit/releases/WebKitGTK/
[00:27] <BUGabundo> webkit-1.1.16/1
[00:27] <BUGabundo> fta: kenvandine: we are up to date
[00:28] <fta> hm, so maybe, just maybe, it's committed upstream but not released
[00:28] <fta> or just not fixed
[00:28] <BUGabundo> put a trunk on your PPA
[00:28] <BUGabundo> and ill test it
[00:29] <fta> it's python-webkit btw, not libwebkit-1.0-2
[00:29] <fta> 1.1.5-1
[00:30] <BUGabundo> python-webkit:
[00:30] <BUGabundo>   Installed: 1.1.5-1
[00:30] <BUGabundo> what's the upstream for that?
[00:30] <fta> upstream is 1.1.7
[00:30] <BUGabundo> https://launchpad.net/bugs/328576
[00:30] <fta> http://code.google.com/p/pywebkitgtk/
[00:31] <BUGabundo> 	 pywebkitgtk-1.1.7.tar.bz2	
[00:31] <BUGabundo> I guess we need a sync :) or packaging
[00:32] <fta> !info pywebkitgtk sid
[00:32] <fta> stupid bot, ignoring debian
[00:32] <BUGabundo> https://edge.launchpad.net/~webkit-team/+archive/gwibber is dead :(
[00:32] <BUGabundo> LOLOL
[00:32] <BUGabundo> !info pywebkitgtk debian sid
[00:33] <fta> that's the thing with automated dailies, people stop doing manual updates
[00:35] <BUGabundo> right
[00:43]  * BUGabundo ln -s /dev/person /media/sleep
[09:04] <micahg> [reed]: do you want me to add See Also links upstream for long closed bugs?
[09:05] <[reed]> micahg: sure, why not
[09:05] <micahg> bug noise on old stuff?
[09:05] <[reed]> don't worry about it
[09:05] <micahg> ok
[11:25] <asac> dtchen: i assume you have no idea what the reason could be for my capturing being broken in all alsa/voip apps? ;)
[11:26] <asac> you think porting stuff to pulse might help? ... is there anything one can/cannot do in alsa apps which i should look for?
[11:29] <micahg> asac: what do you think of milestoning the firefox project to track landed bug fixes upstream?
[11:41] <asac> micahg: not sure ;) ... probably makes sense :)
[11:42] <micahg> asac: I saw qbittorrent using it and it looked cool
[11:42] <asac> hmm someone created them for 3.0.14 etc.
[11:43] <asac> problem is that those will be targets in upstream milestone ...
[11:43] <asac> can we actually change the target milestone for bugs that are connected to an upstream bug?
[11:43] <micahg> idk
[11:43] <micahg> i wonder who created the current milestones
[11:44] <asac> anyone from the mozillateam can do that ;)
[11:44] <micahg> looks like someone just did it last week
[11:44] <micahg> should I try one?
[11:44] <asac> you ;)?
[11:45] <micahg> nope
[11:45] <asac> well. you can definitly check if we can target bugs using those currently created
[11:45] <asac> if that works we can do that i guess
[11:46] <micahg> those were releases....
[11:46] <asac> thats pretty much the same, isnt it?
[11:46] <asac> just that its "done"
[11:46] <asac> rather than future
[11:46] <asac> hmm
[11:46] <micahg> for our purposes
[11:46] <micahg> I think I'll test milestones
[11:46] <asac> feel free to try one on the 3.0 branch ... we already have a bunch so we can add a future one too there
[11:46] <asac> i dont like the naming though ;)
[11:46] <asac> just 3.0.14 would have been enough
[11:47] <micahg> well, those I think are releases
[11:47] <asac> ok changed
[11:47] <micahg> ?
[11:47] <asac> micahg: releases are milestones that are done
[11:48] <micahg> ah
[11:48] <asac> first you create a milestone ... then you make a release afaik
[11:48] <asac> i changed the name of the release to be just 3.0.15 rather than 3.0.15-source
[11:48] <asac> feel free to create one in the future ;)
[11:49] <asac> for 3.0
[11:49] <micahg> I'm going to test on 3.7 since I know I have a bug to target
[11:49] <asac> and see if that works wrt to targetting bugs that have upstream bug etc.
[11:49] <micahg> I can delete it if it doesn't work
[11:49] <asac> hmm
[11:49] <asac> 3.7 has no milestone
[11:49] <asac> maybe beta
[11:49] <micahg> right
[11:49] <asac> but its just trunk
[11:49] <asac> and for trunk we usually dont even know what the first relesae name will be
[11:49] <asac> atm its 3.7 ... but maybe it will be 4.0 ;)
[11:49] <micahg> I was just going to do releases since we don't really care when during the release it happens
[11:50] <asac> but ok
[11:50] <micahg> we can always change it
[11:50] <asac> ok go ahead
[11:50] <asac> i think 3.7.0 then?
[11:51] <micahg> is the initial release .0?
[11:52] <asac> i think they would title it 3.7
[11:53] <asac> so no ;)
[11:53] <asac> if it ever gets released ;)
[11:53] <micahg> and now you can have a list when you go to release a version: https://edge.launchpad.net/firefox/+milestone/3.7
[11:53] <micahg> this is a lot nicer than tagging :)
[11:54] <asac> sure .... if it works
[11:54] <micahg> it does :)
[11:54] <asac> which i am really not sure about ... for bugs that have an upstream task ;) ...
[11:54] <micahg> I just tested it
[11:54] <asac> for bugs that have an upstream task with a bugzilla bug conneted?
[11:54] <asac> good
[11:54] <micahg> bug 66015
[11:55] <micahg> also, if it lands on multiple versions to be released, I can add multiple tasks for the series upstream
[11:55] <asac> hmm ok. and what would we do if it now lands on 3.6 branch etc.?
[11:55] <asac> ah
[11:55] <asac> good
[11:55] <micahg> move if to 3.6 if it's before 3.7 is released
[11:56] <micahg> otherwise, I think we can nominate for multiple series like we do in ubuntu
[11:56] <micahg> and have two upstream milestones
[11:57] <micahg> ah, there's a target to release :)
[11:58] <micahg> if you have the project in the URL
[11:58] <micahg> this will be cool
[11:58] <asac> kk
[11:58] <micahg> I assume I should do the same for xulrunner?
[12:01] <asac> feel free ;)
[12:30] <dtchen> asac_: TBH, it isn't at the top of my priority list. I have a rather nasty linux + alsa-plugins regression that I'm chasing.
[12:30] <dtchen> asac_: are all these apps ALSA, or are any of them native pulse?
[12:31] <dtchen> asac_: did you try setting the playback level for Capture as I suggested?
[12:32] <asac> dtchen: all sip phone apps use alsa
[12:33] <asac> dtchen: playback level for capture? let me check your comments again
[12:33] <asac> where would i set that?
[12:34]  * asac tries to get latest ekiga/opal/ptlib stuff to build which supposely has native support for pulse
[12:34] <asac> lets hope
[12:35] <asac> the odd thing really is that arecord just works perfectly ;)
[12:35] <asac> i dont know what magic those apps do
[12:37] <dtchen> sorry, not Playback level but Playback mute toggle
[12:37] <dtchen> Mono: Playback 23 [72%] [34.50dB] [off] Capture 12 [75%] [18.00dB] [on]
[12:37] <dtchen> amixer set 'Mic' unmute
[12:38] <dtchen> (which is different to the Capture mute toggle, which you would need "amixer set 'Mic' cap" if it showed muted)
[12:38] <asac> hmm
[12:38] <asac> that thing isnt shown as muted in sound preferences
[12:39] <dtchen> it wouldn't be; Sound Preferences only exposes the Capture toggle, most likely
[12:39] <dtchen> that's arguably a defect in gnome-media and/or PA
[12:39] <dtchen> however, it's really, really confusing to show both Playback and Capture toggles for essentially a Capture element
[12:41] <dtchen> so, I can see two defects here if unmuting 'Mic' Playback is the culprit
[12:41] <dtchen> 1) the mixer paths for PA in /usr/share/pulseaudio/alsa-mixer/paths/analog-input* need to be updated
[12:42] <dtchen> 2) the alsa-lib abstraction for these sorts of toggles needs to be massively overhauled
[12:42] <asac_> dtchen: so that makes me hear myself ... but still nothing gets captured by the app
[12:43] <asac_> its really really strange ;)
[12:43] <asac_> arecord works ... sound recorder works ;) ... everything works except i think its ptlib
[12:43] <asac_> and it worked for the full UDS week
[12:43] <asac_> then stopped working
[12:44] <dtchen> and this is all through your usb headset, correct?
[12:45] <dtchen> I can dig some today while I'm at the airports
[12:46] <asac> yes
[12:46] <asac> its usb headset
[12:47] <asac> _but_ ... it doesnt matter
[12:47] <asac> internal mic has same issue
[12:47] <dtchen> well, yes and no
[12:47] <asac> you can try any of the three voip apps we have: ekiga, twinkle and linphone
[12:47] <asac> all three do not work ;)
[12:47] <asac> no sound input ;)
[12:47] <asac> dtchen: is there a way to reset everything?
[12:47] <asac> e.g. all config, all stuff that might be non-default here?
[12:48] <dtchen> it matters in the sense that usb audio devices have known issues with A) hw dB info being completely fscked, B) PA settings not being stored correctly
[12:48] <dtchen> rm -rf ~/.pulse*
[12:48] <asac> hmm
[12:48] <asac> yes. i removed that
[12:48] <asac> dtchen: where is the alsamixer stuff saved?
[12:48] <asac> i played around with that ... maybe thats a problem now
[12:49] <dtchen> you need to "killall pulseaudio" afterward to let it respawn fresh
[12:49] <asac> yeah
[12:49] <asac> i used pulseaudio -k
[12:49] <dtchen> pulseaudio -k is unreliable
[12:49] <asac> and then started it from command line even
[12:49] <asac> hmm
[12:49] <asac> ok
[12:49] <asac> but second run told me it was dead
[12:49] <asac> i can try killall though
[12:50] <dtchen> as for sound card state (at least I think that's what you're referring to), that's a bit more difficult
[12:50] <dtchen> you need to disable PA autospawn first, then use alsa force-reload, then reenable PA autospawn
[12:50] <asac> pasuspender?
[12:50] <dtchen> echo autospawn = no|tee -a ~/.pulse/client.conf
[12:51] <asac> ah
[12:51] <dtchen> rm ~/.pulse/client.conf
[12:51] <dtchen> etc.
[12:51] <asac> ok ... but reboot doesnt help?
[12:51] <dtchen> no, the only sure-fire way is a physical powerdown, wait 2-3 minutes for capacitors to drain, then power back up
[12:52] <dtchen> state is cached in the sound hw
[12:52] <dtchen> it's really quite nasty
[12:52] <asac> oh
[12:52] <dtchen> that's only for your internal
[12:52] <dtchen> for your usb headset, it's a non-issue
[12:52] <asac> hmm
[12:53] <asac> ok. lets hope i get ekiga going with pulse support somehow
[12:53] <asac> feels like the best way to do this
[12:53] <dtchen> hmm
[12:53] <asac> currently fails because something is flaky on one of the trunk things i had ;)
[12:53] <dtchen> unstable has 2.6.5-1
[12:53] <asac> yes. but thats not new enough
[12:53] <dtchen> of ptlib, that is
[12:54] <dtchen> ok, you need a checkout/snapshot?
[12:54] <asac> i think 2.7.0 is pulse
[12:54] <dtchen> ugh
[12:54] <asac> or trunk
[12:54] <asac> and latest tag from opal too
[12:54] <asac> then ekiga trunk fails because of some C++ oddities :(
[12:54] <asac> usr/include/boost/function/function_template.hpp: In member function ‘boost::function0<R>& boost::function0<R>::operator=(const boost::function0<R>&) [with R = void]’:
[12:54] <asac> ../lib/engine/gui/gtk-core/optional-buttons-gtk.cpp:109:   instantiated from here
[12:54] <asac> /usr/include/boost/function/function_template.hpp:828: error: exception handling disabled, use -fexceptions to enable
[12:54] <asac> so now i am also checking out latest boost :(
[12:56] <asac_> right so atm i have ptlib2.7.0 opal 3.7.0 ... and ekiga trunk :/
[12:57] <asac> and boost-trunk is building
[14:16] <asac> dtchen: now i got ekiga with native pulse running was kind of annoying
[14:16] <asac> anyway. ... didnt change a thing
[14:16] <asac> input -> zero
[14:16] <asac> output -> works
[14:16] <asac> on usb headset that is
[14:57] <BUGabundo_work> hey
[14:57] <BUGabundo_work> asac: why didnt i ever heard about this bug ? https://bugs.edge.launchpad.net/ubuntu/+source/firefox-3.5/+bug/444449
[15:20] <asac> BUGabundo_work: lots of slowness bugs i heard of ;)
[15:22] <BUGabundo_work> WFM
[15:22] <BUGabundo_work> but then again i'm on daiyl ppa
[15:22] <BUGabundo_work> and 3,7
[15:22] <BUGabundo_work> annnddd chromium more and more
[16:22] <ejat> BUGabundo_work: did u produce this bug 398840 in gnome ?
[16:52] <BUGabundo_work> ejat: looking
[16:54] <BUGabundo_work> ejat: based on the date, i would say i'm sure it was on ubuntu
[16:54] <BUGabundo_work> gnome, yes
[16:54] <BUGabundo_work> dont use another WM
[16:54] <ejat>  owh .. ok ..
[16:54] <ejat> maybe .. gwibber team should check about it .. since choqok doesnt have similiar like gwibber
[16:56] <BUGabundo_work> i'm sure it can be closed
[16:56] <BUGabundo_work> losts changed, and i cant reproduce anymore
[16:56] <BUGabundo_work> asac: ^^^^^^
[18:20] <pwnguin> anyone care to review the minor patch in bug #488851?