/srv/irclogs.ubuntu.com/2010/05/18/#ubuntu-bugs.txt

atrusyofel: hrm. i seem to get that issue too.00:17
atruserm, maybe not.00:18
atrusi don't normally use notify-osd at all, and now i seem to have just flooded it with notifications, so it's not working well any more :)00:19
atrusddecator / yofel: yeah, it seems to give me that behavior. try running /usr/lib/notify-osd/notify-osd in a terminal, and watch its output when it happens, and report a bug with those contents?00:21
ddecatoratrus: i already filed a bug, but i'll try running that and seeing what results. thanks :)00:22
atrusddecator: can i get the url? i'm curious about following up with it :)00:22
atrusit seems to say something about the screensaver, but again, i don't normally use notify-osd, so i don't know what it might be doing.00:23
ddecatorbug 581991 | atrus00:23
ubot4Launchpad bug 581991 in totem (Ubuntu) "Notifications are suppressed when Totem is playing media (affects: 1)" [Undecided,New] https://launchpad.net/bugs/58199100:23
ddecatorhuh, you're right, it does mention the screensave, even though i don't have the screensaver option checked in the prefarances. thanks, i'll add it to the report00:25
atrusyeah, seems slightly goofy to me :)00:25
BUGabundo_Bonesguud nite00:26
ddecatorcya BUGabundo_Bones00:28
chotchkihey everyone, quick question, if i have a confirmed bug (sorta example #581134) and its a wishlist item for the ubuntu developement team, how should i indicate that status?01:36
chotchki(the example im going to send upstream but im curious about the ubuntu procedure)01:37
micahgchotchki: ask someone here to flag as wishlist01:37
chotchkicool thx01:38
micahgchotchki: s/flag/set importance to/01:42
chotchkicould someone set the following bugs to wishlist importance? 581452, 58199501:52
hggdhbug 58145203:12
ubot4Launchpad bug 581452 in software-center (Ubuntu) "Categorize search results (affects: 1) (heat: 8)" [Wishlist,Confirmed] https://launchpad.net/bugs/58145203:12
hggdhbug 58199503:13
ubot4Launchpad bug 581995 in dash (Ubuntu) "set -h not supported (affects: 1)" [Medium,Confirmed] https://launchpad.net/bugs/58199503:13
kermiacnigelb: pong!05:31
ddecatorkermiac: he's at work. i think he just wanted to ask if you're interested in learning how to write apport hooks05:53
kermiacddecator: thanks mate, I'm still at work too. I'll try to catch him later :)05:54
iflemaHello to all... got a packaging request here for an app called juxta. not in Ubuntu or Debian and not in progress or requested. The thing is... URLs and license info(s) are in the bug description... do I add this info as a comment or just set the 'needs-packaging' tag and request a switch to triaged?06:23
iflemabug 58198706:36
ubot4Launchpad bug 581987 in ubuntu "needs packaging: juxta (affects: 1)" [Undecided,New] https://launchpad.net/bugs/58198706:36
bbordwellI feel that this bug is ready to be marked as triaged with an importance of medium, could a member of BC please do so? https://bugs.launchpad.net/ubuntu/+source/totem/+bug/58204507:41
ubot4Launchpad bug 582045 in totem (Ubuntu) (and 1 other project) "Totem quits unexpectedly when doing a double search in the Youtube plugin (affects: 2)" [Undecided,Confirmed]07:41
* ddecator looks07:42
ddecatorhm, i wonder if apport would create a crash report with extra info it you enable it and reproduce the crash07:44
bbordwellddecator, I already attached a backtrace07:44
ddecatorbbordwell: right, but idk if a crash report would have any extra information, not sure what hooks totem has07:45
ddecatorok, doesn't look like it has crash-specific hooks07:49
ddecatorbbordwell: i think you or the reporter should still run apport-collect so there is system information on there, along with a few extra logs. i'm not sure if the backtrace alone is enough for the devs to know what the issue is and how to fix it. maybe have someone more experienced with gnome apps look at it, but at this point i'm not comfortable marking it triaged07:52
bbordwellddecator, alright I will run apport-collect in a while, as well as get an Strace07:54
ddecatorbbordwell: it might be easier to generate a crash report07:55
bbordwellddecator, I will look into it.07:56
ddecatorbbordwell: if you get a crash report, it'd just file a new bug, so you can mark the current bug as a dupe of the crash bug and then remove the upstream link on the original report and add it to the new crash report (with a note for the reporter so they know what's going on obviously) like i said, might not grab much extra information, but it should give more clues as to what caused the crash07:58
bbordwellddecator, okay thats for the advise07:58
bbordwells/thats/thanks07:58
ddecatorbbordwell: no problem. also, it's usually good to leave a link to the LP report on the upstream report if you have to create a new one since it won't be added right away by the link :)07:59
bbordwellddecator, Note apport does not trap SIGABRT signals08:10
bbordwellbacktrace shows a SIGABRT08:10
ddecatordoes it? i didn't read through the whole thing in detail, haha08:10
bbordwellddecator, haha well I was accidentaly a step ahead of you then :) that note links to a wiki telling you how to get a backtrace...08:11
ddecatoroh, and there it is08:14
ddecatorbbordwell: note?08:14
bbordwellddecator, ahh sorry08:14
bbordwellhttps://wiki.kubuntu.org/Apport#How%20to%20enable%20apport08:14
bbordwellthe last thing on that section08:15
ddecatorah, gotcha. yup, looks good. i was going to suggest a valgrind if you didn't want to do a crash report, but i guess that's not needed either. so a strace would be nice, and just running apport-collect for good measure :)08:17
bbordwellddecator, strace is already done08:17
ddecatorbbordwell: that's a lot of info...but yah, that confirms it's a SIGABRT08:20
bbordwellddecator, okay apport is done as well. In comment please say you set that as importance medium at my request. I just sent in an application for BC and I used this bug as an example. (I said i would mark it as medium since it was a severe impact on a non core application)08:22
ddecatorbbordwell: fair enough, i think that's all of the information we should need on our end. i would just add a quick comment on the upstream report saying that is was originally report on LP and that more logs are avaiable on the LP report (with a link to the report of course)08:24
bbordwellddecator, hmm I forgot to do that. I filed three GNOME bugs tonight and I did it on the others...08:25
=== alvin_ is now known as alvin
ddecatorbbordwell: ok, looks good, just one more thing i want to check real quick08:30
ddecatorbbordwell: ok, so i agree with medium, but totem is a core app, so why is it still medium?08:33
bbordwellddecator, well I figure that totem is a core app, but that the youtube plugin is not a core part of the app08:34
ddecatorbbordwell: ah, ok, so that kind of ties in with my reasoning. the bug isn't impacting the functionality for most users since, at this point, it doesn't seem that many users are likely having trouble with this. although i just realized, does only clicking search once work properly?08:36
bbordwellddecator, yes08:37
ddecatorbbordwell: ah, i'm leaning more towards low then since it's easy enough to avoid by just clicking once08:39
bbordwellddecator, you are correct, it should be low since it is easily worked around.08:40
ddecatorbbordwell: alright, i'll make a note on my comment that we discussed it since you said you included this on your app08:40
bbordwellddecator, alright thanks. I am going to go test a bug on fedora though since I have a gstreamer bug that i think may be ubuntu specefic08:44
bbordwellso talk to you later08:44
ddecatorcya08:45
BUGabundo_remoteI'm an ant,you're a bee08:58
=== iflema is now known as tremmons
=== tremmons is now known as iflema
=== wgrant_ is now known as wgrant
astraljavaBUGabundo_remote: I though AnAnt is an ant.09:44
=== plars is now known as plars-away
xelisterit would be really nice if ubuntu 10.04 would support fancy things, like say, a keyboard11:12
xelisterbecause lack of keyboard makes me a bit miss the 9.10 from which I upgraded. Bug exists on 2 out of 3 tested computers11:13
BUGabundo_remotelol11:13
xelisterusb keyboards, nothing speciall in dmesh11:13
xelisterdmesg11:13
xelisterhow to find similar bugs but only in lucid?  "keyboard not working lucid" or ?11:14
xelisterwhat would be the best way to report such a bug? against what project?11:18
BUGabundo_remoteproject: UBUNTU11:22
BUGabundo_remotepackage: some xorg x input ?11:22
xelisterkeyboard is not working in Lucid11:48
xelisterhow to report that better?  I see similar "reports" but mostlu in googles / forums11:49
xelisterok so my Lucid is BRICKED, keyboard does not work at all. any known solution?12:06
DrKenobiHi! I'm planning to request a mentor at the BugSquad Mentorship Program, but they ask me to have a wiki. Whats that? Where I get it?12:11
xelisteralso kmail dies all the time12:12
* xelister rushes to warn friends about installing 10.0412:13
xelisterseriously we should worn users to not upgrade yet, nothing works in this new ubuntu release12:16
zeroseven0183DrKenobi: You can setup your own Wiki Page at https://wiki.ubuntu.com/12:18
DrKenobizeroseven0183, anyone can do it? i thought you have to be someone important! haha I'll set my wiki right now!12:20
DrKenobithank u!12:20
=== radoe_ is now known as radoe
arandxelister: On your machine, mind you. lucid isn't all fail.12:26
xelisterarand: and for 26 other reporters on bugtracker, plus peoples on forums12:26
xelisterarand: on my _2_ machines (out of 3 tested)12:26
arandxelister: Indeed, but there seems to be a lot out there that don't have no problems at all either, just saying ;)12:29
xelisterhow come this bug is not GRAVE priority yet? https://bugs.launchpad.net/ubuntu/+bug/55516912:29
ubot2Launchpad bug 555169 in xserver-xorg-input-keyboard (Ubuntu) "[lucid] Keyboard and mouse freeze after grub, usb and PS/2 keyboard not working in X (affects: 27) (heat: 126)" [Undecided,Confirmed]12:29
xelisterplease set prio to critical12:29
arandxelister: On that I would agree though. By the way, if the acpi=off is a viable workaround, it would probably be very useful to add it to the top of the bug description.12:33
arandxelister: (but I'm not a bug-squadder, so I can't help setting the priority)12:34
xelisterother suggested workarounds include changing  XKBVARIANT = "us,phonetic"  to skip "us"12:34
arandAh, well if a workaround is to be in the description, go for whatever seems to have the highest success rate/confirms or working..12:36
arandIf its USB, it could be the kernel (My guess).12:37
xelisterwe think it could be also bad setting, like grub or console or other left-overs from previous version12:38
arandxelister: And if the kernel is indeed the issue, testing from mainline: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds and see if it's already fixed upstream might be a good idea...12:38
xelisterseb128: keyboard not working for dozen of users. can you set priority to high?12:41
xelisteror critical12:41
=== thekorn_ is now known as thekorn
arandxelister: Although, priority is not at all a garantee of solution, getting good debugging info, narrowing down (first of all is it xserver or the kernel?), getting a report upstream (if latest release hasn't fixed it), are far better ways to speed up the process.12:46
xelisterI hope more developers are assigned to help fix high priority bugs12:47
arandWell, if debugging info is lacking, I guess the amount of devs assigned doesn't matter. And if the bug is in the kernel, assigning twenty xserver-devs to it won't do much good either. Although in this case there seems to be at least a hefty amount of info given.12:53
=== pedro__ is now known as pedro_
=== txwikinger2 is now known as txwikinger
deuxpiGood day! Bug #580952 causes network file access to fail and has been reproduced with a mainline kernel13:20
ubot2Launchpad bug 580952 in linux (Ubuntu) (and 1 other project) "Log messages: "CIFS VFS: ignoring corrupt resume name" (affects: 1) (heat: 6)" [Undecided,Confirmed] https://launchpad.net/bugs/58095213:20
deuxpiYeah, this one13:20
deuxpiIt probably needs to be marked as Triaged, and, I guess, importance to Medium13:21
nigelbkermiac: still around?13:21
nigelbddecator: what did you find out about nautilius vs nautilius-data?13:24
ali1234how do i report a bug against the alternate installer?14:29
ali1234nevermind, someone already reported it14:30
maxbHas anyone observed suspend-to-ram hanging with lucid-proposed?14:42
xelisterkmail seems to die all the time after upgrade to lucid14:50
DrKenobido you think this https://bugs.launchpad.net/ubuntu/+bug/582206 is a duplicate of this https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/573957 ?14:51
ubot2Launchpad bug 582206 in ubuntu "Ubuntu crashes and automatically logout (affects: 2)" [Undecided,New]14:51
hggdhwe do have a meeting today, don't we?15:14
pedro_according to the schedule, yes15:15
pedro_1600 UTC15:15
hggdhthanks pedro_15:16
pedro_you're welcome ;-)15:16
pepsimanWhat would I report a bug against to get http://www.ubuntu.com/files/countdown/1004/countdown-10.04-1/00.png changed?16:12
=== nhandler_ is now known as nhandler
=== tremmons is now known as iflema
ddecatornigelb: nautilus gave no info, nautilus-data provided what appeared to be all of the non-default gconf settings16:52
nigelbawesome :)16:53
nigelbyou know how to package?16:53
ddecatoryes16:53
nigelbpackage hooks?16:53
ddecatorno, haha16:53
* nigelb hunts for last hook he uploaded16:53
pedro_Time for the BugSquad meeting folks!!17:00
pedro_who is around for it?17:00
pedro_I don't see any agenda item rather than the open discussion https://wiki.ubuntu.com/BugSquad/Meeting17:01
pedro_ping hggdh qense17:01
nigelbohh, meeting time ;)17:01
* yofel is around, purely by chance though ^^17:01
kklimondayay, meeting17:01
pedro_awesome!17:01
jibelhey pedro_17:01
pedro_so since we don't have an agenda item for this meeting, what about talking about the UDS sessions that might affect us?17:02
zaran_hello!  this is my first meeting!17:02
pedro_hello jibel!17:02
nigelbthe one were we talked about mentorship17:02
hggdh~o~17:02
yofelddecator: ping, meeting time ;)17:02
ddecatoryofel: i have to leave in 10 min :\17:03
pedro_ok so if you didn't went to UDS there's a few places where you can look for the sessions logs17:03
pedro_first one is gobby: gobby.ubuntu.com is the host name17:04
pedro_and this time we used the qa-m-blah format17:04
pedro_being blah the name of the session, they are some created as qa-maverick-blah though17:04
hggdhand, sometimes, qa-m-blah-blah17:04
pedro_right17:04
pedro_keep in mind that *anybody* can edit the gobby documents so please do not start doing crazy things like deleting them all17:05
* nigelb backs up just in case17:05
pedro_as a recommendation, the best thing to do is to save one locally and edit in your machine rather than in the server17:05
pedro_ok the other place to look for logs is17:06
pedro_is actually for the audio of the sessions http://uds.ubuntu.com/audio/uds-m/17:07
zaran_I don't see anything at gobby.ubuntu.com17:07
pedro_if you're interested in hearing the whole session, well that's the perfect place to make the connection between notes and audio17:07
pedro_zaran_, click on list documents button at gobby17:08
nigelbzaran_: you have to access through gobby application17:08
zaran_oh, thanks17:08
pedro_if you want to know which session to hear/read , have a look to the schedule http://summit.ubuntu.com/uds-m/17:08
pedro_i know that some of you attended to a couple of sessions on UDS remotely or to almost all of them like nigelb17:10
nigelb:)17:10
pedro_anybody else attended to uds remotely this time?17:10
nigelbyofel and ddecator perhaps17:10
yofelI attended a few, didn't have much free time :/17:10
pedro_oh charlie-tca was there too17:10
ddecatoryes, but i'm heading out :)17:10
kklimondaI've tried but once again it didn't work for me..17:10
pedro_ah yes ddecator as well ;-)17:10
pedro_One of the sessions that I personally enjoyed a lot was the BugSquad Roadmap17:11
pedro_if you look into the gobby document, you'll see a lot of tasks listed17:12
pedro_we're going to start adding those to the wiki page so anybody on our team can start picking from there and starting to work17:12
pedro_we created a blueprint for it here: https://blueprints.edge.launchpad.net/ubuntu/+spec/qa-m-bugsquad-roadmap17:12
=== yofel_ is now known as yofel
pedro_there's plenty of tasks so if you're willing to contribute, stay tune to the mailing list17:13
pedro_since we're going to start making a call for help shortly17:13
pedro_We also talked about the BugSquad Mentoring Program17:14
pedro_we reviewed the process and came out with some good ideas on how to improve it17:14
pedro_hggdh, qense want to say anything about that session?17:14
hggdhyes17:15
* pedro_ pass the mic to hggdh17:15
hggdha summary -- we (finally) realised it was not quite working, and decided to review the process. From then on pedro_ and qense took over17:15
hggdhand -- we hope -- we will have a more responsive process from now on. Amazingly, I ended up with *no* tasks to perform ;-)17:16
hggdhas such, I now defer to qense and pedro_ :-)17:17
pedro_heh ;-)17:17
pedro_thanks hggdh17:17
pedro_as you know we've been working on the Adopt an Upstream/Package initiative17:18
pedro_we had a session about that as well17:18
pedro_if you're interested on it the session was called community-m-upstream-contacts17:19
pedro_https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-upstream-contacts17:19
pedro_the name on gobby is: community-m-adopt-upstream17:20
pedro_another session that you might be interested in is the https://blueprints.edge.launchpad.net/ubuntu/+spec/qa-m-regression-bug-management17:21
pedro_at least as in an informative way, please have a look to the document and hear the audio too17:22
pedro_alright, from the folks who attended remotely or went to UDS any session  you may want to highlight?17:23
hggdhand -- please -- feedback is really appreciated. Do comment, discuss, and disagree (if needed)17:23
pedro_yes totally, please don't be shy we're open to comments :-)17:26
pedro_alright seems that's all for now from the uds topics17:27
kklimondais there a list of packages that could particularly use an adopter?17:27
kklimondasome packages in universe that had problems in lucid cycle due to lack of communication for example17:27
qenseSorry, was away during the previous remarks. There is nothing much I would like to add, just that I think it is awesome that some people have already decided to adopt certain smaller packages they like. If only some of you would get together to adopt a larger (core) package with a group I d be even mroe happy!17:27
kklimondaI remember a problem with audacious17:27
pedro_we have a list on the wiki https://wiki.ubuntu.com/BugSquad/AdoptPackage17:28
pedro_we need to update that though, we have an action item on that17:28
kklimondaone day the upstream developer has come to #-motu and asked us to remove audacious from archive completely :)17:28
hggdhkklimonda: in principle, any package is fair game17:28
nigelbok, someone just decided to rease the gobby doc it seems17:28
pedro_of course if you adopt openoffice.org we'll buy you thousand of beers ;-)17:28
nigelbI'm restoring it, please don't delete again17:29
qenseYeah, someone really should look after OpenOffice's many, many bugs.17:29
kklimondapedro_: on the other hand if I adopt OO.o I may have no time to drink them ;)17:29
pedro_haha good point17:29
pedro_qense, any highlight you might want to share?17:29
* hggdh has one point to raise17:30
pedro_hggdh, please go ahead17:30
qenseNothing else I'd like tell.17:30
* micahg needs help with Firefox bugs :)17:31
hggdhI have noticed that the busquad and control MLs are sort of idling. It might be a good idea to start using it more17:31
micahghggdh: ah, that came up in the bugsquad blueprint IIRC :)17:31
hggdhmicahg: yes... something like a monthly reminder of what this is all about, and more discussions17:32
hggdhwhich I have just tried to poke, with my "is BugControl dense" email17:32
yofeland a meeting reminder...17:32
nigelbWe seem to be using it only for applications lately17:32
hggdhyes. This is *wrong*17:32
pedro_yofel, and choose meeting times ;-)17:32
yofelyep17:33
pedro_did anybody filed their best time for the meeting to happen?17:33
hggdhI did17:33
qensee.g: If someone proposes an item for the meeting agenda (s)he should send a mail to the mailing list so it can be discussed.17:33
pedro_http://www.when2meet.com/?30657-7nGss <- please do it here17:33
pedro_that's really important for us17:33
qenseIf you make an important or large change to the wiki page, or plan on making one, please also send a mail to the mailing list.17:33
hggdhqense: indeed. If we can hash out the points before the meetings, it will be more productive17:34
vishqense: the bugsquad is already subscribed to the wiki , isnt it?17:34
pedro_yes, but a little explanation would be nice too17:34
kklimondapedro_: what timezone are those hours in? :)17:34
nigelbUTC17:34
qensevish: Most pages, but not all.17:34
vishah..17:34
qenseyeah, and the explanation17:34
pedro_like if you added a new stock response, say why you're adding it , maybe it was requested by a developer etc17:35
qensevish: e.g.: I recently created a new page in the BugSquad namespace and saw no notification mail for that on the mailing list17:35
pedro_so other can also say oh so i can contact the developers and make sure all their stock responses are up2date17:35
qenseIf you decide to adopt a package I'd also greatly appreciate if you'd notice the mailing list.17:35
vishqense: we might have to subscribe the team to bugsquad/* then17:35
qenseMaybe17:36
hggdhvish: I had set up an LP account to do that, will check on it17:36
pedro_thank you hggdh!17:36
vishhggdh: neat17:36
pedro_ok guys so please please please fill up your best times for the meeting17:36
* vish likes this time :D17:36
pedro_we need to decide that soon ;-)17:37
qenseThere are a lot of people unavailable at a lot of times.17:37
kklimondadone17:37
pedro_let's follow up with our "agenda"17:37
hggdhalso we are considering having more than one time-to-meet, alternating17:37
micahganyone have the time link handy?17:37
pedro_we can discuss further the meeting time on the bugsquad mailing list17:37
nigelbhttp://www.when2meet.com/?30657-7nGss17:37
hggdhmicahg: http://www.when2meet.com/?30657-7nGss17:37
hggdhMoving on?17:37
pedro_nigelb, you have an item to discuss, please go ahead17:37
nigelbok, thanks pedro_ :)17:38
nigelbWe all have seen bugs reported through apport and how they generally help us triage faster17:38
nigelbLast cycle I had written a few hooks, this cycle, I'd like to help others learn how to write them17:38
micahgthis doesn't seem to work, looks like almost everyone is unavailble all the time17:38
qenseMaybe we should make writing the hooks more structured.17:39
* hggdh pokes micahg, and laughs17:39
charlie-tcamicahg: it is not as easy as doodle17:39
qenseCan't we generate a report for the packages that do and don't have Apport hooks?17:39
nigelbIn this regard, I've poked ddecator and kermiac with 2 simple tasks which they completed in less than 12 hours17:39
nigelbqense: yes we can17:39
kklimondamicahg: well, we have other things to do but thursday, 8pm looks nice :)17:39
micahgheh, nigelb, hggdh and I were discussing that last night17:39
nigelbSo, I'll be leading an effort to get more learning how to write.  there are folks who know it.17:40
nigelbIf you want to help out, poke me and I'll get something you can work on17:40
nigelbmicahg: anything you want to add in?17:40
pedro_nigelb, are you planning to do a call for help on that regard?17:40
qensenigelb: I'm afraid I'm quite busy already, so I won't be of much help.17:40
nigelbpedro_: yes17:40
pedro_would be great to announce the effort widely ;-)17:40
micahgnigelb: well, hggdh and I were thinking that documentation on hook writing and training sessions would be good17:40
* hggdh humbly suggests using the MLs17:41
vishnigelb: you've setup a wiki ? , or is that already there17:41
micahgnigelb: also, trying to get the maintainers interested in writing hooks as well17:41
hggdhyes17:41
nigelbmicahg: yes, that too17:41
pedro_micahg, that'd be *awesome*17:41
nigelbvish: there is already a wiki from karmic cycle17:41
nigelbI feel us playing tag with maintainers isn't going to help.  Time to take things into our hands.17:41
nigelbIf we have a solid system where they can ask help, etc, it might help better17:42
hggdhwell, eventually the maintainers will have to review and approve17:42
micahgnigelb: well, if they don't respond, that's fine, but I think they should be addressed as well though17:42
pedro_yes sounds good, they have to review those later anyways17:42
nigelbI have a few plans, if someone can help me coordinate things, we can work something out17:42
micahgand here's an apport hook related blueprint for those that are interested: https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-browser-apport/17:42
pedro_awesome! thanks for this great initiative nigelb17:43
nigelbpedro_: :)17:43
pedro_is there any other agenda item for the meeting?17:44
hggdhyes17:44
pedro_hggdh, go for it ;-)17:44
hggdhback to mentorship, a bit more of data (well, actually *not* in the agenda)17:44
hggdhwe decided to create a small group of admins for the mentorship programme; these admins should cover all TZs17:45
hggdhwe are in need of one in the Asia TZ, we already have folks for Americas and Europe. Anyone insterested, please contact pedro_ , qense, charlie-tca or myself17:46
* nigelb can help17:46
* pedro_ hugs nigelb17:46
* hggdh accepts :-)17:46
qenseyay!17:47
charlie-tcayay17:47
nigelbabout time I taught stuff my mentor taught me ;)17:47
* hggdh blushes17:47
nigelbjust fyi, hggdh was my mentor :)17:47
* BUGabundo_remote checks he is in the proper #17:47
pedro_hahah17:47
pedro_alright folks anything else?17:47
hggdhnot from me17:48
nigelbas always patch review could use some help from bug squad :)17:48
qensenope17:48
pedro_what a great meeting :-)17:48
hggdhoh17:48
hggdhpatch review17:48
pedro_please guys remember if you need help with anything, we have a meeting list ;-))17:48
hggdhthis is a good thing. For those interested, we do need a lot of help reviewing patches17:48
pedro_a mailing list rather17:48
pedro_;-)17:48
hggdhyes, lets start using it more17:49
pedro_there's a lot of request to join the bugsquad team on lp, let's use it for other announcements/discussions/ideas/etc as well17:49
nigelbok, so #endmeeting?17:49
pedro_yeah let's wrap up :-)17:49
duanedesigncould i just say that i was reviewing the gobby doc and saw 'screencasts' mentioned. If the Screencat Team can be any assistance let me know.17:50
pedro_thank you guys! you're the best17:50
hggdhduanedesign: offer noted and (already) accepted. Thank you!17:50
pedro_duanedesign, great! we'll contact you shortly then ;-)) thanks a lot17:50
charlie-tcasorry I was late. Did I miss anything in the first 20 minutes?17:51
nigelbcharlie-tca: uds round up17:51
hggdhcharlie-tca: it was just a summary of UDS17:51
pedro_charlie-tca, yes, we assigned all the tasks to you ;-)17:51
charlie-tcaGreat!17:51
pedro_oops17:51
charlie-tcaI needed more to do17:51
hggdhwell, now that you say that...17:51
* charlie-tca is getting bored, with triaging, testing, xubuntu-leadership role, etc17:52
hggdhOK. I am done17:52
nigelbcharlie-tca: talk to jorge, he always has lots of tasks lying around17:52
charlie-tcagoing hide instead17:52
hggdhheh17:52
pedro_jibel, are you going to publish the slides of your presentation somewhere?17:52
nigelbok, since meeting is officially over, can we talk about stuff post meeting17:53
hggdhnigelb: most certainly17:53
nigelbhggdh: I was wondering if we could use a wiki page for membership instead of mail to bugsquad list17:53
pedro_jibel, would be amazing if you can send an email to the bugsquad if you do it ;-))17:53
nigelbadmins can subscribe to the page and they can remove people from list once accepted17:53
hggdhnigelb: perhaps we should change the requirement -- instead of emailing the ML, just requesting membership on LP17:54
nigelbbut we can get confirmation of 'read triage guide'17:54
hggdhthe team admins always get emailed on the request17:54
nigelb*can't17:54
yofelthe mailing list message was to make sure the people are subscribed to the list17:54
jibelpedro_, no problem,I'll attach upload it to the wiki and send an email17:54
pedro_is there any easy way to check if a person was subscribed to the mailing list?17:54
pedro_or that info is only available to the ml admins?17:54
hggdhpedro_: the list admin can look it up17:54
pedro_eek..17:54
hggdh:-)17:55
nigelbwell, only easy way is lp admin=list admin17:55
yofelhow about moving the ML to LP ?17:55
hggdhor we can just *trust*17:55
nigelbwell, what % of folks had signed CoC before we closed?17:55
yofelhggdh: we already did that... unsuccessfully...17:55
hggdhthis is, after all, about trusting people to Do The Right Thing17:55
nigelbthat should give an  idea of whether we can *trust*17:56
hggdhyes, I agree, yofel, but we can check if the CoC was signed17:56
hggdhand -- for good or for worse -- we can monitor the actions (somehow)17:56
yofelconsidering that we lost about 50% of the members on LP after the purge, not that many...17:56
nigelbOk, in that case, I have a suggestion17:56
nigelbwe use M/L more so that people end up subscribing to it to keep track of things17:57
hggdhyofel: we did not require the CoC before17:57
nigelband we trust them after checking CoC is signed17:57
hggdhnigelb: yes indeed. For example, a summary of this meeting, etc, etc17:57
yofelhggdh: we didn't? I thought we did... but I seriously can't remember how it was when I joined so I might be wrong...17:57
nigelbI dont remember having done so.17:58
pedro_yofel, there was no requirements, the team was an open one17:58
pedro_jibel, thanks!!17:59
hggdhCoC was only required for -control17:59
* yofel wonders why he signed the CoC then back then... can't remember anymore17:59
nigelbhggdh: perhaps you can talk to brian about having people only apply17:59
* hggdh points to pedro_ :-)17:59
* pedro_ whistle18:00
yofelwell, I knew the team was open, but I though it said so on some wiki page, whatever18:00
hggdhI am not a bugmeister, just a grasshopper18:00
nigelbheh18:00
hggdhbut yes, Brian, Pedro and I will discuss it18:00
charlie-tcayofel: I think you are right. I had to sign the CoC in 2006 when I joined the team18:01
deuxpicould be nice to have people "present" themselves to the ML instead of just applying18:01
nigelbok, so about the apport hooks18:01
hggdhdeuxpi: yes. Some of them nowadays do that, but it is not required18:01
* pedro_ -> lunch18:01
charlie-tcanigelb: I'm useless for that. I can not program these days18:02
nigelbcharlie-tca: hooks are easy.  pitti has done half the work.18:02
nigelbI was envisioning a wiki page where we can list package that need apport hooks, bug number for the wishlist bug, and info that needs to be collected18:02
charlie-tcaWhen I have some time, I'll get back to you and see if I can learn it18:02
nigelbif someone wants to help they can pick a bug from it and start working on it18:03
micahgnigelb: I suggest using tags rather than a wiki list18:03
yofel+118:03
duanedesignhggdh: pedro_ looking at the type of screencast mentioned looks like something that will be on the 'Developer Network'. If you have anything geared more for desktop users in the chute let me know. Please :)18:03
nigelbmicahg: that works too18:03
nigelbthe idea is maintianers can ask us to make it if they don't want to learn the whole apport thing18:03
nigelband we can have some low lying fruit for people who want to work on them18:04
* hggdh jumps around happily -- the ML poke sent is generating responses18:04
micahgnigelb: I think the first thing you should do is send an e-mail to ubuntu-devel explaining what you want to do and soliciting maintainer by-in either in the form of making the hooks or opening bugs with the required info18:04
nigelbmicahg: I can do that, but I'd like some help with coordination.  I have a big set of WI from UDS.18:05
hggdhWI?18:05
nigelbworklist items18:05
hggdhwhat's it?18:05
micahgnigelb: I'm still working on mine from last cycle :)18:05
hggdhoh18:05
nigelbmicahg: lol18:06
nigelbwell, then I'll do the stuff, can review?18:06
micahgnigelb: sure18:06
nigelbperhaps over the weekend we can get the groundwork done18:06
hggdhnigelb: send it over to all of us, we will be happy to review and help18:06
micahg+118:06
nigelbI find upstream devs in -desktop wanting pitti to review hooks etc.18:07
nigelbwe should be able to do that stuff18:07
micahgnigelb: not necessarily18:07
hggdhit is very much like a patch review, after all18:07
nigelbwell, most of the time, its not big things.  they know what info they want, but not how to get it18:08
nigelbbasically a lack of knowledge of the apport stuff18:08
nigelbthat is a void that we as bug squad can fill18:08
nigelbim sure a lot of folks know how to write one.18:09
nigelbi've play with it quite a lot.18:09
nigelbthoughts?18:10
hggdhwe should probably augment the docs with examples18:12
micahg+118:12
nigelbyeah.  mostly from /usr/share/apport/package-hooks18:13
hggdhand I still think the patch review team is the ideal place for initial screening18:13
nigelbthe reason why im hesitant is not all of the aptch review folks should know apport18:13
hggdhnigelb: BTW, I did my first (official) patch review -- and set it as needswork ;-)18:14
micahghggdh: the problem I see with that is that with patches, you can apply locally and test to see if the problem is resolved, it's harder w/hooks w/out opening a bug18:14
nigelbhggdh: woo! yaay!18:14
nigelbmicahg: well, you can file a bug against staging18:14
hggdhnot really. It *is* a patch to the package, and it can be tested against staging (or even locally)18:14
micahghggdh: k, well, as long as that is documented somewhere, I didn't even know we can file bugs against staging18:15
nigelbmicahg: I'll get that doc in a few.  I always misplace that particular thing18:15
micahghggdh: if that's the case, then I agree18:15
hggdhthere is also something that worries me a bit, the risk of private data being collected18:15
nigelbactually, the firsrt test should be done use apport-cli and set to save only18:16
yofelmicahg: man apport-bug says that you can set APPORT_STAGING so it files bugs there18:16
qensedinner, afk!18:16
qense(even more afk than I already was)18:16
hggdhheh18:17
nigelbhow about we take this to the mailing list and talk about it there?18:17
nigelbthat way we achive the secret task of getting it more active18:17
hggdhgood idea. Another point is most hooks agaisnt stable will need a SRU18:17
nigelbAlso, one of the old specs had some script to get most common packages for which the last 1000 bugs were filed18:18
nigelbsru for hooks should be no fuss18:18
nigelbI'll write a mail in the mornign when I'm more alert and we'll continue the planning there :)18:19
hggdhk. nigelb, are you going to send out an email? If so, to which ML?18:19
nigelbbug squad18:19
hggdhCOOL!18:19
=== JFo is now known as JFo-afk
laz0rhi, can I just confirm a bug on launchpad if I experience it too?18:22
laz0ror are there certain criterias that have to be met first?18:24
nigelblaz0r: well, are you reproducing it in the exact same conditions?18:27
nigelbmost of the time you can confirm18:27
micahglaz0r: if there are steps to reproduce and not an X, video card, kernel or sound bug, then yes18:31
laz0rhttps://bugs.launchpad.net/ubuntu/+source/udev/+bug/56706818:32
ubot2Launchpad bug 567068 in udev (Ubuntu) "udev rules with dot in key fails with Env must be KEY=VALUE pairs (affects: 5) (heat: 28)" [Undecided,New]18:32
laz0rthats the one I would like to confirm, it is somewhat X related18:33
laz0rplus there is a debian bug report linked that says that they won't fix the issue and you should use the xorg.conf instead18:33
=== erhesrhsrtb54vyh is now known as Elbrus
=== BUGabundo is now known as BUGabundo_DrWho
=== BUGabundo_DrWho is now known as BUGabundo_dinner
=== BUGabundo_dinner is now known as BUGabundo_FlashF
=== BUGabundo_FlashF is now known as BUGabundo_MythB
ddecatornigelb: so there is a problem with that hook. you around?23:17
=== odyi_ is now known as odyi
hggdhanyone here used NTP (not ntpdate) on Lucid?23:35
hggdhs/used/uses/23:35
=== BUGabundo_MythB is now known as BUGabundo_Naruto
BUGabundo_Narutono23:38
BUGabundo_Narutonptdate here in maverick23:38
charlie-tcaI tried to use NTP, but I don't really know how to set it up23:44
mrandmicahg: did you fill out some times that you're available for a meeting on the when2meet time map?  That app doesn't make it easy to see when one particular person is available, but I tried to move  my mouse over every time segment and don't see where you're available at all.23:46
hggdhcharlie-tca: pretty much all you should need to do is install it23:47
micahgmrand: no, but I'm available almost all the time except Sat 00:00 UTC to Sun 2:30 UTC23:47
charlie-tcaI am on static ip's23:47
hggdhno problem23:47
charlie-tcaIt kept giving me error messages about not being to able find the server23:48
mrandmicahg: hmm... it has you as unavailable for all times.  Could you perhaps go turn everything there green?23:48
hggdhcharlie-tca: this is strange. The default NTP install comes with ntp.ubuntu.com set as the server23:48
hggdhit should work23:48
micahgmrand: that requires clicking too many of those boxes, now I know why everyone else is only clicked a few :)23:49
ddecatormicahg: click and drag :p23:49
hggdhcharlie-tca: my issue is that NTP is not being started on boot (or when the net comes active)23:49
charlie-tcadon't you need a crontab entry for it?23:49
micahgmrand: UTC, right?23:50
mrandmicahg: yep!23:50
charlie-tcaI don't think it starts on boot, it goes off cron instead, doesn't it?23:50
micahgmrand: done23:53
mrandawesome.23:53
hggdhcharlie-tca: no, not the ntp server. ntpdate, yes, should be started via crontab every hour or so23:53
hggdhpure NTP (ntpd) should be started on NIC up23:55
=== BUGabundo_Naruto is now known as BUGabundo_SGU

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!