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