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