[02:17] <thewrath> is anyone in here
[02:17] <thewrath> i have a bug that i would like to see if someone can reproduce
[02:17] <thewrath> in 9.04 release from today
[02:20] <charlie-tca> What is the bug?
[02:24] <thewrath> desktop not able to connect to wireless taht is wpa2 enterprise
[02:24] <thewrath> issue in 8.10
[02:24] <thewrath> as well
[02:24] <thewrath> 8.10 was reported
[02:24] <charlie-tca> no wireless here
[02:25] <thewrath> ?
[02:25] <charlie-tca> Hard to confirm a wireless bug without wireless on the system
[02:25] <thewrath> oh k
[02:25] <thewrath> i see wat ur saying
[02:26] <thewrath> does anyone have wireless?
[02:29] <andresmujica> hi thewrath, sadly i don't have wpa2 enterprise
[02:29] <andresmujica> i'm using wpa2 personal...
[02:29] <andresmujica> one question for the team
[02:29] <andresmujica> with the new 5-a-day how are the tags handled?
[02:30] <andresmujica> and the LoCo Team tag?
[02:34] <greg-g> andresmujica: see https://wiki.ubuntu.com/Bugs/Events
[02:35] <greg-g> it will be done automatically based on that wiki page using a parser
[02:36] <andresmujica> ok, that's what i though... but the LoCo Team tag would be extracted from the launchpad account? or should i add it too...
[02:36] <andresmujica> and also, the applet still is go to use or is already deprecated?
[02:36] <greg-g> oh, right. umm, I don't know. That should be automatically extracted from the LP account, huh?
[02:37] <greg-g> that last question is better answered by dholbach
[02:38] <greg-g> dholbach will be making a more thorough announcement later, this was basically the "preview" release today.
[02:38] <greg-g> will all be finalized and ready to go before the GBJ though
[02:38] <greg-g> (from what he told me)
[02:39] <andresmujica> ok...
[02:40] <andresmujica> i wasn't online today.. the thing is that i'm giving an irc session for my tema (ubuntu-co) and i'm not pretty sure how it would work.. i'll be using the applet meanwhile and join the people to the 5-a-day team too...
[02:42] <greg-g> andresmujica: yeah, I say being in the team and using the applet won't hurt anything
[02:42] <andresmujica> yeap..  :)
[02:49] <thewrath> anyone have wpa2 enterprise
[02:58]  * maxb finishes venting about notify-osd
[02:58] <maxb> I filed 5 bugs in 5 minutes
[02:58] <maxb> that's not how 5-a-day is supposed to work :-/
[03:00] <greg-g> now go triage 10 bugs to make up for it! ;)
[03:06] <hggdh> only 10? ;-)
[03:31] <andresmujica> bug 331219
[03:31] <andresmujica> (just a demo=
[03:31] <andresmujica> )
[03:40] <thewrath> who has wpa2 enterprise encyrption on wireless
[05:40] <dholbach> good morning
[06:55] <d-b> thewrath: i might be able to set it up on my openwrt ... why ?
[07:01] <maco> dholbach: so that 5-a-day-participants team...is that the auto-reporting people were asking about before?
[07:02] <dholbach> yes
[07:03] <dholbach> the stats are not there yet, but I'm working on it and it'll be there for GBJ
[07:06] <maco> ok
[12:26] <pedro_> Hey Bugsquad! today is hug day! https://wiki.ubuntu.com/UbuntuBugDay/20090219 come on there's still a few bugs to be squashed
[14:15] <andresmujica> ping dholbach
[14:15] <dholbach> andresmujica: pong
[14:16] <andresmujica> hi Daniel what's up!
[14:16] <andresmujica> i've got a doubt about 5-aday
[14:16] <dholbach> what is it?
[14:16] <andresmujica> the appplet would still work?
[14:17] <dholbach> no
[14:17] <dholbach> you don't need it anymore
[14:17] <andresmujica> ok, so i must tell everyone at the LoCo to Join the new team...
[14:18] <dholbach> andresmujica: yes - nothing manual anymore, all automatic
[14:18] <dholbach> join the team once
[14:18] <dholbach> and "register for bug jams" once
[14:18] <dholbach> which is easier than the old thing was
[14:18] <andresmujica> register for bug jams is the wiki page Bugs/Events?
[14:18] <dholbach> yep
[14:18] <dholbach> just put your Launchpad ID there and all's good :)
[14:19] <andresmujica> and the tags how should be handled?
[14:19] <andresmujica> hmm i'll rephrase, so there'd be no more tags outside the ones at the wiki page?
[14:19] <dholbach> as far as I know, people just used it for events anyway
[14:21] <andresmujica> ok no prob.
[14:21] <dholbach> ok super
[14:21] <dholbach> thanks for talking to your team mates about it
[14:22] <andresmujica> yeap,  no prob.. but they were so excited with the  applet... :)  the 5, 4, 3, 2, 1, 0 was really fun for them...
[14:22] <dholbach> a lot of people told me "this is too complicated, people don't understand how to set it up" or "this is too much work for me"
[14:22] <dholbach> let's see how it works out
[14:24] <andresmujica> yeap, that's right!
[14:30] <andresmujica> dholbach, another thing.. this means that the bzr branch would be no longer updated, right?
[14:30] <dholbach> yes, no bzr branches - not necessary
[14:32] <andresmujica> the date at the wiki - the parsed section-  would be take into account for the stats?
[14:32] <dholbach> yes
[14:32] <andresmujica> (sorry for so many questions...   i'm willing to put those on the wiki)
[14:33] <dholbach> no worries
[14:34] <andresmujica> hmm ok, our team would be participating (i hope) during the 3 days and we would have a get together the 21st by the afternoon, should i put the 3 days??
[14:35] <MagicFab> dholbach, I think you removed too much from https://wiki.ubuntu.com/5-A-Day/Reporting in https://wiki.ubuntu.com/5-A-Day
[14:35] <dholbach> MagicFab: what's missing?
[14:35] <MagicFab> All command line options gone, which I find useful.
[14:36] <dholbach> MagicFab: like?
[14:36] <MagicFab> 5-a-day --update --html
[14:36] <MagicFab> And I prefer using the applet :)
[14:36] <dholbach> yes, I think about keeping it
[14:36] <dholbach> :-((((((((((((((((((((((((((((((((((((((((((((((((((((((((((8
[14:36] <MagicFab> well, actually, how are team submissions handled by the new team membership ?
[14:36] <dholbach> keeping the .signature thing
[14:37] <dholbach> I'll introduce them a few days later
[14:37] <dholbach> but nothing will be lost, no worries
[14:37] <MagicFab> don't get me wrong, I think the team memberhsip stuff is excellent!
[14:37] <dholbach> there's lots of people who didn't "get" the applet and command line thing
[14:37] <MagicFab> ok, team submissions is my only reason to keep that applet around.
[14:37] <dholbach> and requested stuff to be automatic
[14:37] <MagicFab> yes, I imagine for many it's impossible to follow that
[14:38] <dholbach> MagicFab: we will get all data from Launchpad - it will take me just a bit longer to set up the team statistics, but the data will be still around
[14:38] <MagicFab> komputes (David Bensimon) explained to me the UDS conversations around this
[14:38] <dholbach> so there's (apart from the nice .signature) no need to keep the applet and the other stuff
[14:38] <dholbach> and I'll make sure we'll still have that
[14:38] <MagicFab> when I mean team submissions I mean "I am submitting 5-a-day stuf for XXX team to rock"
[14:38] <dholbach> I know
[14:39] <MagicFab> k :D
[14:39] <dholbach> we'll have team stats next week - if you work on 10 bugs today, your team will have 10 bugs next week
[14:39] <dholbach> or maybe the week after it
[14:39] <dholbach> nothing will be lost if you don't use the "client" today
[14:41] <ormandj> if somebody gets to https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/284211 , you'll be the hero of a thousand souls :p thanks for doing this bug day, i can't wait to see the outcome :) you guys rock!
[14:42] <BUGabundo> ormandj: ping asac on that !
[14:46] <ormandj> Done! :)
[14:47] <BUGabundo> yeah, I already did the job for you... eheh
[14:48] <andresmujica> dholbach, would be some kind of problem if the people used to the 5-a-day applet or command line use it for the GBJ ?
[14:48] <ormandj> very nice :) :) my name is david, and whatever your name is - thank you very much!
[14:49] <dholbach> andresmujica: there's no reason to do that because it will be all automatic
[14:49] <dholbach> andresmujica: if they prefer to do that - I'm not going to stop them
[14:51] <andresmujica> dholbach: ok thks!!  great! i'll explain them !!
[14:51] <bddebian> Boo
[14:52] <BUGabundo> foo
[14:52] <BUGabundo> bahh you came to early today
[14:52] <BUGabundo> and never showed up, yesterday
[14:52] <BUGabundo> how can we scare bugs like that?
[14:52] <BUGabundo> bddebian: eheh
[14:53] <bddebian> Sorry, I'm slacking.. :)
[14:53] <BUGabundo> bugs don't give us slack...
[15:00] <asac> ormandj: i think its no going to happen for 0.7.1, but we are aware of that issue
[15:00] <asac> i will see what i can do
[15:01] <seb128> asac: btw they rolled nm 0.7.0.97 tarballs but you probably know that
[15:01] <ormandj> asac: i'd be willing to put 100$ of my personal funds on it, if it would help motivate people. it's blocking 500 or so people that i deal with on a day-to-day basis from using wireless, heh
[15:03] <BUGabundo> really?
[15:03] <BUGabundo> from reading it, it didn't seem such a big think
[15:03]  * BUGabundo reads bug report again
[15:03] <asac> seb128: yes. we are just 3 or 4 days before that (its 0.7.1~rc1)
[15:03] <asac> but i will roll that
[15:03] <ormandj> inner phase 2 GTC auth does not work, it was removed in nm 0.7.x, but was in nm 0.6.x (regression)
[15:03] <seb128> ok
[15:03] <asac> target for final is two or three weeks
[15:04] <asac> ormandj: are all those ubuntu users?
[15:04] <ormandj> asac: no, it's a mix of linux users. i don't have any hard numbers on that, but i suspect a fair number do use ubuntu
[15:05] <ormandj> the fix would affect upstream nm, so it would be beneficial to all
[15:10] <asac> yeah
[16:13] <sasara> join #ubuntu
[16:13] <Pici> you first.
[16:13] <BUGabundo> LOL
[16:13] <sasara> oops
[16:13] <Pici> :)
[16:13] <BUGabundo> sasara: forgot '/'
[16:14] <BUGabundo> heeheh
[16:14] <sasara> thx :P
[16:16] <hacktick> :)
[17:00] <dan> is this the right place for discussing NM v0.6 bugs too?
[17:01] <BUGabundo> dan its just about asac on the NM team
[17:01] <BUGabundo> so just shoot...
[17:01] <dan> BUGabundo, I'm running hardy and found a bug in NM v0.6
[17:02] <dan> I have a proposed fix, but not sure where to submit it
[17:02] <Pici> .22
[17:02] <dan> I've posted on the NM list, but didn't get any kind of accept or reject for it
[17:03] <dan> most of the NM list discussion revolves around v0.7, so I can see why people may not have been too interested
[17:03] <dan> is there a better place to submit/discuss my fix?
[17:03] <BUGabundo> dan launchpad would be great
[17:03] <BUGabundo> and then let asac know about it
[17:03] <asac> dan: plea check that bugs are resolved in ~network-manager PPA
[17:04] <asac> thats NM 0.7 pre snapshot
[17:04] <BUGabundo> dan is it ubuntu specific ? or upstream?
[17:04] <asac> e.g. the version we shipped in intrepid backported to hardy
[17:04] <dan> asac, it's resolved in v0.7, yes
[17:04] <asac> good
[17:04] <dan> is the plan to release 0.7 for hardy as well?
[17:04] <asac> dan: whats you fix
[17:04] <asac> dan: not officially
[17:04] <asac> what is that bug?
[17:04] <dan> asac, lowered the scan timeout down from 10sec
[17:04] <dan> just a sec, will get some refs...
[17:04] <asac> we only do SRUs to hardy for importance hihg bug
[17:06] <asac> dan: what are you trying to fix? i dont think we want to scan every 10 seconds
[17:06] <dan> http://mail.gnome.org/archives/networkmanager-list/2009-February/msg00074.html
[17:06] <dan> asac, that's the link to my patch in the archive, posted feb 8
[17:06] <dan> the fix is to reduce the scan timeout when we are scanning, not to scan every 10 sec
[17:07] <dan> at the 10 second mark, wireless extensions expires scan results
[17:07] <dan> so in my case, my desired connection came in right away and was expired before NM got a chance to see it
[17:07] <dan> which left me disconnected
[17:07] <dan> asac, I had an early post (referenced in the mail I linked to) which gave a very detailed explanation
[17:08] <asac> hmm
[17:08] <asac> didnt see that mail even though i am subscribed
[17:08] <dan> I suppose I didn't go through the official bug-logging process, but I'm new to ubuntu and open source bug fixing in general, sorry
[17:08] <asac> dan: if you have patches directly going to upstream mailing list is right
[17:09] <dan> ok, but that patch applies against the ubuntu-hardy derivative, so not sure what the next step is
[17:10] <asac> dan: i don think this part is different in hardy than in upstream 0.6 branch
[17:10] <asac> dan: first thought is that this is a driver bug
[17:10] <dan> asac, so can this be accepted and applied to both?
[17:10] <asac> e.g. expiring so soon
[17:10] <dan> asac, if you look at the first message, I found the code in the wireless extension source
[17:10] <asac> dan: i will wait for dan to comment on that mail. most likely he doesnt want this kind of tweakage in upstream tree
[17:10] <dan> well, at least I think so
[17:11] <asac> whats the first message?
[17:11] <dan> asac, dan only commented on my first message, suggesting that lowering the timeout like this would be fairly simple and safe
[17:11] <asac> ah its linked
[17:11] <dan> asac, the first message is quite verbose :)
[17:12] <asac> dan: have you addressed the suggestions from dan here: http://mail.gnome.org/archives/networkmanager-list/2009-January/msg00247.html
[17:12] <asac> ?
[17:12] <asac> well i dont think you have, but i wonder if you have considered that
[17:13] <asac> seems its related to non supplicant scans. hmm
[17:13] <dan> asac, which suggestion?
[17:13] <asac> what card are you using? ipw2200?
[17:13] <asac> The issue here is that you do want *some* batching of scan results,
[17:13] <asac> because there are drivers that emit scan events during scan processing,
[17:13] <asac> because some older drivers will clear their scan list when a client asks
[17:13] <asac> for access points.  Thus, you don't want to ask too often or you might
[17:13] <asac> not get a complete set of APs.
[17:13] <asac> However, you could try to modify wireless_event_handler() to, instead of
[17:13] <asac> only scheduling the scan result timeout when there isn't one already
[17:13] <asac> scheduled, cancel the outstanding scan results timeout *if* it will
[17:13] <asac> trigger later than now + 5 seconds.
[17:14] <asac> first paragraph says that its not best approach
[17:14] <asac> second gives suggestion how to fix
[17:14] <asac> that concern
[17:14] <dan> asac, my fix doesn't prevent batching
[17:15] <dan> in fact, by not mucking with the handler at all, we only collect the results at the timeout interval
[17:15] <dan> that timeout is 10 seconds at the moment, I suggest dropping it to 8
[17:15] <asac> why not 9 ;)?
[17:16] <asac> like what is in the thread ;)
[17:16] <dan> 9 should be ok too, but I didn't want to get too close to the margin
[17:16] <asac> 1 second is long in terms of computing
[17:16] <dan> I asked if there was any technical reason why it was even as high as 10, no answer
[17:16] <asac> anyway. i think the patch should be ok and should also go upstream
[17:16] <dan> I know :)
[17:16] <dan> all I can say is that it definitely fixed my problem
[17:16] <dan> I have an iwl4965
[17:17] <asac> i think the reason is that active scanning consumes power for some devices
[17:17] <asac> strange.
[17:17] <dan> when I first noticed the problem, my inclination was to force a manual rescan
[17:17] <asac> iwl4965 always worked for me on hardy
[17:17] <dan> turns out that's not the problem
[17:17] <dan> it may be a particular interaction between my card and the router
[17:17] <asac> so where is the code that has the 10 second limit?
[17:17] <asac> in wireless extensions?
[17:17] <dan> I'm no expert, but this fixed my case, and can hopefully help others
[17:18] <dan> yes, let me check my message for the reference...
[17:18] <asac> yeah. i have to reread that thread, but i think 9 should be ok
[17:18] <asac> if wireless really expires after 10 seconds ;)
[17:19] <dan> yup, I was just wanting a little more margin, and it makes the connection process a little shorter too
[17:19] <dan> Curious about how iw_set_ext() and iw_get_ext() worked, I dug a
[17:19] <dan> little and found this interesting bit in net/mac80211/ieee80211_sta.c
[17:19] <dan> function ieee80211_sta_scan_result():
[17:19] <dan> if (time_after(jiffies, bss->last_update + IEEE80211_SCAN_RESULT_EXPIRE))
[17:19] <dan>     return current_ev;
[17:19] <dan> Note that IEEE80211_SCAN_RESULT_EXPIRE is defined to be (10 * HZ).
[17:20] <dan> asac, that's WE right?
[17:20] <asac> that looks more like mac80211
[17:20] <asac> which is used by iwl4965
[17:21] <dan> oh, is it specific?
[17:21] <asac> mac80211 is shared by almost all modern drivers
[17:21] <asac> except the really old ones like iwl2200 or hostap
[17:21] <dan> yeah, thought that was the WE part of it shared by many drivers
[17:22] <dan> I guess WE and mac80211 are different
[17:22] <dan> but this affects many cards all the same, yes?
[17:22] <dan> WE or not
[17:24] <asac> yes
[17:24] <dan> asac, so this is still a valid fix?
[17:24] <asac> WE is a dying thing though. but that doesnt matter here
[17:24] <asac> i think so
[17:24] <dan> asac, I'd just like to see Hardy get fixed
[17:24] <dan> upgrading hardy's NM to 0.7 is fine too
[17:25] <dan> but this is certainly less invasive for existing hardy users
[17:25] <dan> change one number in two lines to slightly reduce a timeout
[17:25] <asac> dan: i am currently on a train. can you ping me tomorrow about this so i can properly look in the code and then commit it?
[17:25] <dan> asac, sure thing, thanks
[17:25] <asac> i think its fine
[17:25] <asac> i would like to accumulate more fixes for a hardy SRU though
[17:26] <asac> i think i already committed one other low importance ridealong to the hardy branch
[17:26] <dan> asac, ok, will email you tomorrow (or will you be here again?)
[17:26] <asac> but well ... i will see if i can find something else in bug tracker
[17:26] <asac> dan: i am alwys here ... maybe a bit earlier because at this time i might be out for weekend action
[17:26] <asac> its 1830 here
[17:27] <dan> asac, ah
[17:27] <asac> dan: but you can just ping me and i will get reminded when i come back
[17:27] <asac> dan: at best put the line with the bug number /url in the ping
[17:27] <dan> asac, sounds good, thanks
[17:52] <bdmurray> asac: have you looked at the top 3 bugs with patches in the hug day list?
[18:05] <asac> bdmurray: can you paste the url please? ;)
[18:06] <bdmurray> asac they are bug 330608 bug 330571 and bug 330526
[18:06] <asac> bdmurray: those are from dxteam right=
[18:06] <asac> ?
[18:06] <asac> i have them on my radar then
[18:06] <asac> bdmurray: maybe ensure that those bugs have dxteam tag
[18:06] <asac> but i think they already have
[18:07] <bdmurray> oh, they do.  I don't notice that
[18:16] <maco> asac: any idea when NM will start supporting Ad-Hoc connections? it currently shows that they exist then fails to connect to them
[18:19] <sasara> help
[18:22] <sasara> i'm very much a newbie, i've been looking around today's hugday page, and i can't confirm any of the bugs :(
[18:24] <sasara> is there maybe an easier place to start than nm-applet?
[18:26] <pedro_> sasara: we have collected a list of easy tasks for new triagers at https://wiki.ubuntu.com/Bugs/EasyTasks
[18:27] <pedro_> sasara: if you have questions regarding any of those just ask here in the channel
[18:27] <maco> bdmurray: have you noticed any problems when LP Greasemonkey Scripts are enabled? i can't report bugs if they're enabled
[18:27] <sasara> thx :)
[18:28] <bdmurray> maco: Wow, that's a neat benefit!  Do you know which script in particular?
[18:35] <maco> bdmurray: not sure
[18:35] <maco> bdmurray: i can tell you which ones i have installed
[18:36] <bdmurray> maco: its possible to enable and disable them individually w/o having to restart firefox.  just enable / disable one and reload the web page to help narrow it down.
[18:37] <maco> ah, ive been disabling the whole lot
[18:41] <asac> maco: are you on intrepid?
[18:42] <maco> bdmurray: nevermind. i think it was one of the ones i wrote. which i dont quite understand because it doesn't touch that part of the page....
[18:42] <maco> asac: no, jaunty
[18:42] <asac> maco: also it depends on the driver ... what kind of adhoc are you triying to setup?
[18:42] <asac> open net? or wpa?
[18:42] <maco> asac: trying to connect to dtchen's G1, i always have to /etc/init.d/NetworkManager stop, iwconfg wlan0 mode Ad-Hoc, iwconfig wlan0 essid...etc
[18:42] <maco> open
[18:43] <asac> maco: what ship does a G1 have?
[18:43] <asac> broadcom?
[18:43] <asac> ath?
[18:43] <asac> chip ;)
[18:44] <maco> Qualcomm's MSM7201A
[18:44] <maco> according to http://www.wirelessdesignasia.com/article-9338-qualcommdualcorechipsetpowerstmobileg1-Asia.html
[18:44] <asac> what driver is that?
[18:44] <asac> thats probably just a label for something different
[18:46] <maco> it says that's the chipset including G3 wireless
[18:46] <asac> maco: whats the driver
[18:46] <maco> i dont know. *my* driver is iwlagn
[18:46] <maco> but i dont knwo what the phone runs
[18:47] <asac> ah
[18:47] <asac> so the adhoc is not created on ubuntu
[18:47] <asac> thats strange then
[18:47] <maco> no no, i'm trying to connect *to* an ad-hoc network
[18:47] <asac> might be that it creates a special network type that is problemantic
[18:48] <asac> so do you see that net in NM?
[18:48] <asac> cant you connect to it?
[18:48] <maco> it's visible in NM, but it fails to connect
[18:48] <asac> i mean push the button ;)
[18:48] <maco> wireless tools handles it fine
[18:48] <asac> maco: paste the syslog then
[18:50] <asac> also check what iwconfig says while its trying to connect
[18:50] <asac> and if its correct
[18:51] <maco> what do you mean waht iwconfig says while trying to connect?  i didn't see anythign different from what it does when i connect to any other network with iwconfig
[18:51] <asac> out for a while
[18:51] <asac> yes thats what i mean
[18:51] <asac> when NM connects what iwconfig says
[18:51] <asac> ok off
[18:51] <asac> bbl
[18:51] <maco> oh
[18:51] <asac> 1 -2 h
[18:51] <maco> ok
[18:53] <maco> asac: when you get back, here's syslog http://paste.ubuntu.com/120237/
[22:13] <chrisccoulson1> hggdh - i'm seeing a few libical crashes being reported at the moment. it seems that libical aborts on many different errors, and i don't know if those bugs are a problem with libical or the calling applications. would you mind taking a look at bug 331428, for example?
[22:14] <chrisccoulson1> there's 2 separate backtraces in the report, both with the same end result but the initial errors that cause the abort are different.
[22:27] <mrooney> hahahahah bug 331767
[22:27] <mrooney> oh, that's neat
[22:28] <mrooney> New bug #331767 in ubuntu: "Please kill the Pedro Villavicencio bot" [Undecided, New] https://bugs.launchpad.net/bugs/331767
[22:28] <mrooney> what the
[22:33] <savvas> mrooney: it read two bugs, using the bug <number> and the link formats :)
[22:34] <mrooney> yeah, I figured
[22:34] <mrooney> I was more confused as to why it didn't work the first time
[22:34] <mrooney> I am not sure if that report is sarcastic or actually thinks pedro is a bot
[22:35] <chrisccoulson1> i think it is an attempt at being sarcastic
[22:35] <hggdh> chrisccoulson1, will do
[22:35] <chrisccoulson1> thanks hggdh
[22:42] <ccooke> chrisccoulson1: ... it looks completely serious to me. I like the comments about not reading the bug :-)
[22:45] <seb128> doesn't seem to be a joke bug
[22:54] <hggdh> it is not
[22:55] <hggdh> chrisccoulson1, I think the libical issue whould be dealt by Evolution upstream
[22:56] <seb128> agreed
[22:56] <chrisccoulson1> there's a build-time switch for libical to stop it aborting on error
[22:56] <chrisccoulson1> perhaps we could try that?
[22:56] <seb128>  /j #evolution on irc.gnome.org during work hour and ping mchra or open a bug on bugzilla.gnome.org
[22:57] <seb128> we can turn the switch before jaunty maybe but I prefer having errors raised now than ignored
[22:57] <seb128> otherwise bugs are not reported and worked
[22:58] <chrisccoulson1> yeah, i agree. i'll report these upstream tomorrow then
[22:58] <seb128> thanks
[22:59] <seb128> btw ted didn't reply to your fusa changes yet I think, I pinged him about those and he said he would look at that soon
[22:59] <chrisccoulson1> thanks, he did comment on another FUSA bug report earlier, and mentioned that you had pinged him
[23:05] <greg-g> ugh (re: pedro bug)