/srv/irclogs.ubuntu.com/2010/10/12/#ubuntu-bugs.txt

BUGabundoahhh my pillow called... she wants me back. see you tomorrow µfriends00:17
charlie-tcagood night, BUGabundo00:18
snadgehmm.. thats pretty fail, when you dist upgrade to maverick.. it says welcome to ubuntu 10.10! then underneath it it says.. Welcome to Ubuntu 10.04.1!02:16
snadgeso which is it? :P02:17
snadgewhats the name of the program which is supposed to update the login banner?02:28
snadgeahh /etc/motd02:29
snadgehttps://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/40046202:31
ubot2Launchpad bug 400462 in update-motd (Ubuntu) "package update-motd (not installed) failed to install/upgrade: no package named `update-motd' is installed, cannot configure (affects: 36) (dups: 5) (heat: 9)" [High,Fix released]02:31
snadgecan someone explain to me how to get the fixed version of update-motd for maverick?02:48
snadgeon the launchpad bug page, it says it was fixed in version 3.4-0ubuntu102:49
snadgebut the version that comes with maverick is 3.5-0ubuntu102:50
snadgeoh i see the problem.. its a regression that hasn't been reported yet :|02:55
snadgewhere the fuck did the fucking update-motd script go? :P03:40
snadgei want a god damned refund ;)03:40
micahg!ohmy | snadge03:40
ubot2snadge: Please remember that all Ubuntu IRC channels share the same attitude of providing friendly and polite interaction with all users of all ages and cultures. Basically, this means no foul language and no abuse towards others.03:40
snadgei consider myself a reasonably advanced linux user of so many years.. and between launchpad, google, and trying to figure things out for myself.. im kind of blank here03:42
snadgewhenever i run into a problem, i never get as far as actually being able to identify it and fix it.. its so annoying :P03:42
gp5sthttps://bugs.launchpad.net/ubuntu/+source/php-memcached/+bug/658939 does that have enough information?05:06
ubot2Launchpad bug 658939 in php-memcached (Ubuntu) "php5-memcached does not work (affects: 1) (heat: 6)" [Undecided,New]05:06
lou1234Hello05:48
lou1234Can someone help me with a bug report? I found the procedure online to follow05:48
lou1234but this 'feature' is causing ubuntu to completely crash and log me out05:48
lou1234hmm....05:50
lou1234anyone around?05:51
micahglou1234: ubuntu-bug is crashing?05:55
lou1234no06:02
lou1234when i try to reproduce the bug06:03
lou1234ubuntu06:03
lou1234 completely crashes and logs me out06:03
lou1234sorry I am completely new to the bug reporting game. should I still try ubuntu bug?06:05
micahglou1234: which package is crashing the system?06:06
lou1234so  when i open up a pdf06:06
lou1234in firefox06:06
lou1234and then try to print it06:06
lou1234ubuntu completely crashes06:06
lou1234I have the samsung universal print driver installed for my laser printer06:07
lou1234so I am not sure where the problem is06:07
micahglou1234: maybe try ubuntu-bug xorg06:07
persiaWhen you say "ubuntu completely crashes", could you describe that in a bit more detail?06:07
lou1234Sure. I select print and then a box pops up I select print and then my screen goes black and goes to the login menu06:08
lou1234I login and every window I had opened is closed06:08
lou1234it is like a clean login when I restart firefox it comes up with the 'uh oh' firefox crashed screen and wants to restore tabs06:09
persiaOh, excellent.  That is an xorg crash.06:09
lou1234oh06:09
* lou1234 has no idea what it is06:09
persia`ubuntu-bug xorg` and answer the questions and you'll file the right sort of bug.06:09
persiamicahg, What made you know it was xorg that I missed?06:10
micahgpersia: Ubuntu completely crashed implied it, we've had a few of those submissions for Firefox, I'm looking for the bug now06:10
lou1234micahg has this been an issue in 10.10 or has it been there previously?06:11
micahgbug 53977206:11
ubot2Launchpad bug 539772 in xorg-server (Ubuntu Maverick) (and 3 other projects) "[MASTER] Lucid 2.6.32-16 crashed to login screen - miCopyRegion (affects: 48) (dups: 22) (heat: 290)" [High,Fix released] https://launchpad.net/bugs/53977206:11
persiamicahg, Ah, I see.  I'm just never sure if it's xorg or kernel for "completely crashed".06:12
persia(depending on the defintion of "completely)06:12
micahglou1234: can you please file a new bug with ubuntu-bug xorg and mention that bug number I just put in the channel?06:12
lou1234sure!06:13
micahglou1234: thanks06:13
lou1234so im reading the reporting bugs page...06:13
micahglou1234: BTW, just out of curiosity, what type of video card do you have?06:13
lou1234do i need to do any more research or is that it?06:13
lou1234one sec06:13
lou1234let me get the model number06:13
micahglou1234: brand is sufficient in this case06:14
lou1234 ati radeon hd 467006:14
micahgah, yes, ok06:14
lou1234is this a security vulnerability?06:15
persiaLikely only in the denial-of-service sense, and even then, with easy workarounds, so probably not.06:16
micahglou1234: probably not06:16
lou1234oh okay ... im still reading the page06:16
lou1234what exactly are gdm log files ... and is there a way i can view what information it contains?06:19
persia/var/log/gdm/*06:21
persiaShould be text files: so use your favorite test reader06:21
lou1234im in /var/log06:22
lou1234and when I try to cd/gdm it says permission denied... when I try sudo cd/gdm I'm getting  told cd command not found06:22
lou1234any idea what I am doing wrong?06:25
micahglou1234: cd gdm?06:27
micahgalthough that shouldn't work...06:27
micahglou1234: try ls /var/log/gdm06:27
persiaOnly root can see those logs.06:28
persia`sudo ls /var/log/gdm` and similar06:28
micahgright06:29
lou1234basically i just don't want my username posted out there06:29
lou1234so if there is a quick way for me to edit that out06:29
lou1234i would have no problem handing the logs out to help peeps with this bug06:30
persialou1234, If your username is "wakk0", you've already indicated that in a public manner.  If not, feel free to edit the logs to claim it is :)06:34
lou1234haha06:34
lou1234fair enough06:35
lou1234If I am doing a backtrace do I need to completely backout of the bug report - do the backtrace and then refile it?07:00
persiaNo.07:01
persiaYou can attach the stacktrace to the bug later.07:01
lou1234oh ok07:02
lou1234does this title work - firefox causes xorg to crash07:02
persiaI'd recommend something involving the printing action.07:03
persiaOnce the PDF is open, firefox is no longer the primary application.07:03
lou1234oh07:04
lou1234now that i submitted it do i need to do anything else?07:22
persiaWait, mostly.07:28
persiaIdeally, someone will either find a solution or ask for more information.07:29
lou1234if they ask for more info07:35
lou1234will i get an email?07:36
persiaIf LP has your email address, you ought, yes.07:36
lou1234LP?07:38
lou1234oh nevermind07:38
lou1234okay07:38
lou1234thanks for all of the help!07:38
lou1234have a good one!07:38
lou1234bye bye!07:38
=== AbhiJit_ is now known as AbhiJit
danagei'm looking for an issue in which a dist-upgrade kills the window decorator task resulting in a dialogue being in the background that cannot be brought to the front, thus failing the dist-upgrade process. i've searched launchpad and didn't fint it09:31
popeypersia: I see you're in a helpful mood this morning with regards to bugs :)10:55
popeypersia: any chance someone (anyone) could tell me how we get bug 619663 as an SRU for maverick? basically dual screen on intel is broken, fixed in xorg-edgers.10:56
ubot2Launchpad bug 619663 in libdrm (Ubuntu) (and 2 other projects) "[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor (affects: 28) (dups: 6) (heat: 172)" [High,Fix committed] https://launchpad.net/bugs/61966310:56
popeydebdiff available too https://bugs.edge.launchpad.net/ubuntu/+source/libdrm/+bug/619663/+attachment/1679043/+files/libdrm_2.4.21-1ubuntu2.1.debdiff10:56
ubot2Launchpad bug 619663 in libdrm (Ubuntu) (and 2 other projects) "[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor (affects: 28) (dups: 6) (heat: 172)" [High,Fix committed]10:57
ikoniathat would be helpful to resolve, that's been quite a keen one in #ubuntu recently10:58
persiaAnyone tested the debdiff?10:58
persiaAh, yes, it is tested.10:59
persiaOK.  Bug needs to be subscribed to the sponsors team (ubuntu-sponsors).11:00
persiaSomeone needs to upload it (who can upload X)11:00
persiathen it goes into -proposed, and we need folk both affected and unaffected to try it to verify it fixes the issue and doesn't cause regressions.11:00
persiaIf that's true, it drops into -updates in about a week.11:00
popeyshould I be looking for someone who can upload to x ?11:06
persiaThat's what subscribing "ubuntu-sponsors" does.  I can do the subscription if you don't want.11:06
popeyah11:07
persiaThere's a report generated every few minutes based on all the bugs that are subscribed to sponsors (which are supposed to have debdiffs), and developers are encouraged to review that, and sponsor some fixes for stuff they can upload regularly.11:07
persiapopey, So, I'm kinda blind to how opaque all these processes are, as I'm intimately involved in many of them.  Do you think it's worth trying to prepare some guidance on how to get things moving from the viewpoint of someone less familiar?  I imagine it would help you, but, as ikonia mentioned elsewhere, also reduces the bar for folks to maybe push things that aren't ready.11:09
ikoniapopey: I would be happy to help you with that11:10
popeyyes11:11
popeyi have found that some bugs I can "fire and forget" such as those relating to CUPS11:11
popeyTill is massively _on_ the ball there11:11
popeywhereas others, X, kernel, nautilus.. I can file a bug and see no action other than a bugsquad person pasting a boilerplate repy11:12
popey*reply11:12
popeyI can hang out in channels and poke people, but that's suboptimal, doesn't scale and places more 'importance' on 'my' bugs relative to other peoples who dont have direct access to developers11:12
ikoniathat burns me11:12
ikoniais there currently a guide/process/work-flow for bugsuad members on dealing with a bug ?11:14
zeroseven0183Hi ikonia. Here are some of the pages that are useful when triaging bugs11:17
zeroseven0183BugSquad : https://wiki.ubuntu.com/BugSquad11:17
zeroseven0183How To Triage https://wiki.ubuntu.com/Bugs/HowToTriage11:17
zeroseven0183Common Tasks : https://wiki.ubuntu.com/Bugs/CommonTasks11:17
zeroseven0183responses https://wiki.ubuntu.com/Bugs/Responses11:18
zeroseven0183Checklist https://wiki.ubuntu.com/Bugs/Checklist11:18
ikonianice11:18
ikoniathanks11:18
zeroseven0183Be sure you have a Launchpad account11:18
ikoniaI do11:18
ikoniaI just want to read what the process is11:18
zeroseven0183I also suggest watching this video tutorial: Bug Triage 101 http://blip.tv/file/321936811:19
ikoniaalways work a look11:19
zeroseven0183:-)11:20
persiapopey, Till is an example of the sort of monomanaically-focused developer that gets as close to "maintainer" as we have :)11:20
persiaikonia, I'm happy to be a counterparty to be asked questions for any process/procedure that's tricky over the bug management/development range, the more so if the result is a document that is useful to people who aren't me.11:21
ikoniawell thats the game, get a process in place that allows people to contribute, but also puts some form of quality control in place11:33
ikoniaand also makes sure the bugs are filled with useful information and the correct status11:33
persiaYep :)11:35
mistryniteshbug controllers, bug #659075 is a wishlist11:38
ubot2Launchpad bug 659075 in libaugeas-ruby (Ubuntu) "Please backport 'clear' into lucid - puppet claims support for it (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/65907511:38
ikoniais there a bug status for wishlist or request ?11:40
mistryniteshikonia: 'wishlist' is a value for importance11:41
ikoniaah11:42
mistryniteshonly members of bug-control team can change it, so I am requesting them11:43
persiamistrynitesh, It5's not wishlist: it's filed against the wrong project.11:44
persianeeds to be filed against the lucid-backports project.11:44
persiahttps://bugs.launchpad.net/lucid-backports11:45
mistrynitesh:S oh, ok11:45
mistryniteshwhat should be done for Bug #659074 , it is written in polish and the reporter asks to speak Polish :(11:47
ubot2Launchpad bug 659074 in firefox (Ubuntu) "margorlik@gmail.cm (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/65907411:47
persiamistrynitesh, We usually turn those into questions (in polish), hoping the support team can file a bug on their behalf.11:51
persiamistrynitesh, if you happen to know polish, or can understand the bug without further coordination with the submitter, may as well just translate the bug, and move forward towards resolution.11:51
mistryniteshpersia: I had no idea what it meant. Just found it was polish by trial at translate.google.com 8-)11:53
persiaIf you're up for it, maybe grab someone in #ubuntu-pl to help integrate with the local support team.11:53
persiaI suspect that they have a procedure (I know there is one for a few other LoCo support teams) to handle these, and if we align with it, we'll provide best service for the user.11:54
mistryniteshhmmm will check out11:54
persiaI guarantee there is at least one person in #ubuntu-pl able to communicate in English (as it is a requirement to set up the channels properly with the LoCo Council), although they may not be online at the moment.11:54
mistryniteshpersia: is there something by the name of lucid-backports? Nearest search I could find was ubuntu-ruby-backports-ppa12:02
persiahttps://bugs.launchpad.net/lucid-backports12:03
mistryniteshthen why doesn't it show up in the search list when I click on 'choose' alongside the package name and type 'backports' or 'lucid-backports'12:05
persiaBecause launchpad doesn't have a working search facility for terms that are subsets of other terms.12:06
persiaSo if you search for "foo" and "foobar" happens to exist, you'll probably never find "foo"12:06
mistryniteshis it okay if I manually type 'lucid-backports' in the package field of bug report?12:07
mistryniteshsounds misterious :) will change the package to 'lucid-backports'12:08
mistryniteshpersia: oopsie, when I type 'lucid-backports' in the package field and click 'Save Changes' launchpad gives the error "Launchpad doesn't know of any source package named 'lucid-backports' in Ubuntu"12:12
persiaYou need "Also Affects Project"12:12
persiaNot "Also affects Distribution"12:13
persiaSource package is correct.12:13
mistryniteshokay!12:14
mistryniteshpersia: thanks for guiding :)12:22
persiamistrynitesh, Thanks for helping put bugs in the right place, and asking if you weren't sure.12:23
mistryniteshmy pleasure12:23
=== zyga is now known as zyga-break
=== bladernr is now known as bladernr_
=== ogra_ is now known as ogra
=== zyga-break is now known as zyga
=== yofel_ is now known as yofel
Olivier_BlazikenSorry, when will by the meeting14:26
yofelOlivier_Blaziken: 17:00 UTC we currently have 13:29 UTC14:29
yofel(use 'date -u' in a terminal to get the UTC time)14:29
Olivier_Blazikenok Thx14:29
nigelbcharlie-tca: entertaining the crowd, I'm from classroom team :)15:01
charlie-tcaOh, okay! Great job on it15:01
* charlie-tca thought nigelb was just trying to confuse him15:02
nigelbcharlie-tca: heh :)15:02
=== zyga is now known as zyga-afk
=== ivoks-afk is now known as ivoks
jibelbdmurray, hi, do you know if the number of people affected by a specific bug is increased when the report matches a bug pattern ?15:48
elderMy X session crashes whenever I run "gitk" on another system using my 10.10 laptop as the DISPLAY.15:50
bdmurrayjibel: No, I don't believe so due to the order of apport operations.  The duplicate notification would be displayed before there is an Oauth token for apport so writing to the bug isn't possible yet.  I believe I reported a bug about wanting to increase the user affected count.15:56
=== deryck is now known as deryck[lunch]
bdmurrayjibel: bug 48731615:58
ubot2Launchpad bug 487316 in apport (Ubuntu) "apport should metoo bug reports that match a pattern (affects: 1) (heat: 10)" [Wishlist,Triaged] https://launchpad.net/bugs/48731615:58
hggdhelder: please open a bug on this15:58
jibelbdmurray, we could use login_anonymously starting from lucid and make authentication transparent to the user ?16:05
jibelbdmurray, the problem is that a bug with a bug pattern associated just vanishes16:06
bdmurrayjibel: the affects_user call requires a user16:06
jibel:/16:06
bdmurrayjibel: there is some talk of permissions redesign for launchpadlib but I'm not on top of that at the moment16:07
bdmurrayhggdh: did you extend xttejx?16:10
bdmurrayhggdh: er xteejx16:10
hggdhbdmurray: yes, I did, he is back and was going to expire in 2 days, I think16:11
bdmurrayhggdh: cool, thanks16:12
hggdhbdmurray: BTW -- yofel gave us two patches for the responses. The first one (additional </comment> looks good16:13
hggdhbdmurray: the second -- updating the dev release to N -- I am not sure it is already time16:14
bdmurrayhggdh: right so just don't use it! ;-)16:14
hggdhbdmurray: heh. The actual question is... let's accept the first one?16:15
bdmurrayhggdh: they've both been merged and push16:15
hggdhyeee!16:16
* hggdh bows to the bugmeister16:16
=== zyga-afk is now known as zyga
bcurtiswx_would someone send an e-mail reminder to the list about the meeting at 1ET or 17UTC16:37
* bcurtiswx_ is in the middle of something, but wanted to get one out16:37
micahgbcurtiswx_: I think pedro did yesterday16:37
=== simar__ is now known as simar
* bcurtiswx_ has a lot of mail to check.. thx micahg16:41
=== zyga__ is now known as zyga
xteejxAfternoon all16:57
=== deryck[lunch] is now known as deryck
hggdhcheers xteejx17:11
xteejxhggdh: ?? What did I do lol17:11
micahgwow, we have a meeting chair now, cool17:12
xteejxmicahg: Am I interrupting a meeting here??17:12
hggdhxteejx: you are back :-)17:12
hggdhxteejx: not by ~47min17:13
* xteejx didn't realise he was missed *that* much ;)17:13
xteejxahh 5pm UTC duh - I should've worked that our is 6pm here (UK)17:14
xteejxoh well it'll be back to normal UTC=my time in a few weeks17:14
xteejxhttps://wiki.ubuntu.com/BugSquad/Meeting/Minutes are minutes not being kept now or have we missed 10 months or meetings?17:16
xteejx*of17:16
bcurtiswx_micahg, does that mean you want to chair our next meeting?17:19
bcurtiswx_:P17:19
* charlie-tca hs missed not quite 10 months of meetings17:19
xteejx:P17:19
* micahg hopes to be sitting in a chair for the next meeting bcurtiswx17:20
bcurtiswx_<drum hit>17:20
* xteejx will be sitting on a sofa17:21
charlie-tcameeting is in here, right?17:29
=== ivoks is now known as ivoks-afk
xteejxcharlie-tca: I assume so :)17:33
hggdhyes indeed17:34
bcurtiswx_charlie-tca, yup :)17:34
xteejxDammit, how do you import .flv audio into audacity17:34
xteejxOops, should've said that to #ubuntu :)17:35
nigelbo/17:35
nigelbhello all :)17:35
* bcurtiswx_ takes a giant blade of grass and slaps xteejx with it :P17:36
xteejxlol bcurtiswx_ :P17:37
xteejxI'm trying to make a funny video, I'll link my youtube in when its done ;)17:37
* micahg will be back in about 40 minutes17:49
bcurtiswx_no meeting for you 'eh17:50
micahgbcurtiswx_: like I said, I hope to be sitting in a chair ;)17:50
bcurtiswx_haha, OK micahg :)17:51
bcurtiswx_vish, did you want to lead the mentor subject?17:52
xteejxbcurtiswx_: No, I'll be here, my expertise is in video/audio production17:53
xteejxDone it in time...just17:53
bcurtiswx_?17:54
xteejxSorry, thoguth you meant I woon't be here cuz I was mesing with videos :)17:54
bcurtiswx_OK17:55
hggdh~ô~17:59
bcurtiswx_1 minute17:59
xteejx20 seconds17:59
bcurtiswx_OK, WHo's Ready for some meeting fun?!?!?!?18:00
bcurtiswx_#startmeeting18:00
meetingologyMeeting started Tue Oct 12 16:57:38 2010 UTC.  The chair is bcurtiswx_. Information about MeetBot at http://wiki.ubuntu.com/AlanBell.18:00
meetingologyUseful Commands: #topic #action #link #idea #voters #vote #chair #action #agreed #help #info #endmeeting.18:00
xteejxYup18:00
devildanteI forgot it! :p18:00
* charlie-tca waves18:00
* devildante waves too18:00
* xteejx waves back18:00
bcurtiswx_Welcome all.  I will be your chair today.18:00
bcurtiswx_I want to make sure that if you add a topic to the meeting wiki, you put your name next to it, so the next chair knows who's going to be talking about what18:00
* charlie-tca notes we got us a meeting bot too18:01
bcurtiswx_So Today I plan on posting the topic and if the person who added it is here , they can speak up at that time18:01
bcurtiswx_First things first:18:01
bcurtiswx_#topic Intro to new meeting bot. -bcurtiswx18:02
meetingologyTOPIC: Intro to new meeting bot. -bcurtiswx18:02
devildanteI lol'd at the name :p18:02
bcurtiswx_So , for those who aren't using text to speech, should be able to see that we have a meeting bot :)18:02
* xteejx wonders how we would use TTS for IRC (one for another day I guess)18:03
bcurtiswx_Please use the following link to check out the commands in detail (it's not the exact commands, but it's quite close)18:03
bcurtiswx_#link https://wiki.ubuntu.com/ScribesTeam/MootBot18:03
bcurtiswx_Future chairs should use this bot, as it simplifys the meeting minutes (posts the log to a website)18:04
bcurtiswx_when I end the meeting it will post a link to the log18:04
bcurtiswx_Any questions on the bot?18:05
* xteejx thinks it seems pretty effective18:05
nigelb+1 nice idea18:05
xteejx+118:05
charlie-tcaYou have to preceed all commands with # ?18:05
Olivier_Blaziken+118:05
bcurtiswx_if anyone has an idea they need to do the following, for it to be logged18:05
bcurtiswx_#idea , note that this command adds an entry into the log18:05
bcurtiswx_well it should... i can say it is still in beta.18:06
bcurtiswx_we'll have to see, lol18:06
simar_is the bug squad meeting going on??18:07
nigelbyes18:07
bcurtiswx_#topic Mentorship program update from Mentors.18:07
meetingologyTOPIC: Mentorship program update from Mentors.18:07
bcurtiswx_did someone want to lead this?18:07
bcurtiswx_vish? ^^18:07
nigelbits for all mentors18:07
charlie-tcaWe need all mentors to give us an update, please.18:07
bcurtiswx_all present mentors o/18:08
Olivier_Blaziken+118:08
simar_i will proceed18:08
nigelbo/18:08
charlie-tcaGo ahead, simar18:08
bcurtiswx_simar_ go ahead and start18:08
simar_charlie-tca, :)18:08
bcurtiswx_All Present mentors who haven't o/ please do so i can come to you18:08
hggdh\o18:09
simar_stanley_robertso has been online two days back only. He was out of country and busy so I finally able to cantact him after two months18:09
* nisshh doesnt think his mentor is around right now :|18:09
simar_otherwise ahmed my other student is doing well .. he working on touchpad18:10
charlie-tcagreat, simar_18:10
Olivier_BlazikenThat will be nice18:10
charlie-tcadrew212: update?18:10
* devildante can do an update18:11
charlie-tcajibel: here?18:11
simar_hes finding the topic a bit harder but interresting .. and stanley is also interested in kernel .. i hope he will also work on the same package18:11
simar_over for me..18:11
simar_thanks :)18:11
charlie-tcahggdh: ??18:12
* nigelb coughs18:12
* devildante coughs too18:12
hggdhI have not seen kangorooo for quite a while18:12
bcurtiswx_nigelb, devildante, charlie's taken this segment :)18:13
charlie-tcahggdh: any update on your other two?18:14
hggdhoops18:14
nigelbheh18:14
hggdhhold on, let me check them18:14
* charlie-tca wishes people were not always logged in to IRC18:15
bcurtiswx_lol18:15
hggdhholstein has asked to be temporarily dropped, too busy with school right now18:15
hggdhojap is going nicely on :-)18:15
charlie-tcaGood to hear18:16
hggdhyes indeed. One out of three, but at least one18:16
charlie-tcawill you update the wiki and launchpad on holstein ?18:16
bilalakhtarIs a meeting going on here?18:16
devildanteyep18:16
simar_bilalakhtar, ya18:16
* bilalakhtar joins18:16
=== simar_ is now known as simar
charlie-tcanigelb: next?18:17
nigelbok18:17
nigelbI've been assigned 2 students who're finally showing some signs of interest in working18:17
charlie-tca:-)18:17
nigelbflipe is going well, he's asking me or asking in the channe when he has doubts18:17
nigelbHe's very much interested in learning and helping out :)18:18
nigelbgigacore got it touch with me the day he was assigned, not heard from him since18:18
nigelbthat's about it from me18:18
charlie-tcadevildante:18:18
devildanteok18:19
devildantesamwho is doing progress, even though he's busy at times with IRL university work18:19
devildantemy other assigned student, I sent him an email but he has not responded yet18:19
devildanteI should probably send him another e-mail18:20
devildantethat's it for me, thanks :)18:20
charlie-tcabdmurray: here??18:20
charlie-tcabcurtiswx:18:21
charlie-tcayou may as well take it18:21
bcurtiswx_cagordon hasn't gotten back to my e-mails. it's onyl been a week, since my last two assigned both dropped out.  I will email cagordon again soon.18:21
bdmurraycharlie-tca: yes, I'm here18:22
charlie-tcaany update on your mentee?18:22
bcurtiswx_davely has shown interest, and i then told him to meet me in IRC and start reading guides.. but no show on IRC so far.. and no emails since then18:22
bcurtiswx_both i will email soon for a follow up18:23
charlie-tcaexcellent.18:23
bdmurrayI didn't think I was on the list with my launchpad work ...18:23
charlie-tcaheh, looks like someone gave you a mentee again18:24
charlie-tcaWe will work on that one18:24
charlie-tcabcurtiswx: we will need anyone not present to send an update to the mailing list18:24
charlie-tcaEveybody is doing a really super job with this program. Keep up the great work!18:25
bcurtiswx_#action Mentors not at meeting need to report to the mailing list on their mentees18:25
meetingologyACTION: Mentors not at meeting need to report to the mailing list on their mentees18:25
bcurtiswx_Thanks charlie-tca18:25
charlie-tca(and don't let the "drop me" 's mess with you.)18:26
bcurtiswx_OK moving on18:26
bcurtiswx_#topic Regression tags and workflow.18:26
meetingologyTOPIC: Regression tags and workflow.18:26
bcurtiswx_nobody assigned.  who wanted to talk about this?18:26
hggdhjibel: there?18:26
hggdhOtherwise I can talk about it18:27
hggdhWe have discussed regression tags on our last meeting18:27
bcurtiswx_hggdh, go ahead, and jibel can pipe in if he gets in18:27
hggdhWe have also sent an email to -devel talking about it, and asking for feedback18:28
bcurtiswx_Quick summary for those not present before?18:28
nigelbliky to the thread?18:28
devildanteyes please :)18:28
hggdhNow, with the feedback we received we are going to start implementing it18:28
hggdhthe change: we are dropping the 'regression-potential' tag18:29
hggdhIt only created more work (mostly when a development release got promoted to stable, like right now with Maverick18:29
xteejx+118:29
bcurtiswx_i see, +118:30
devildanteso what would be the tag that will replace it?18:30
hggdhinstead we are going to mark regressions as 'regression(release|proposed|update)' followed by the version we found it in18:30
hggdhlike maverick, lucid, etc18:30
xteejxhggdh: Can we have an example?18:30
devildante+42 then :)18:30
bcurtiswx_regression-proposed-maverick for instance?18:30
hggdhno. 'regression-release maverick'18:30
bdmurrayactually ['regression-proposed', 'maverick']18:31
hggdhtwo different tags: one identify a regression, the other identify the version it was *found* on18:31
bdmurrayso 2 separate tags18:31
bcurtiswx_OK18:31
xteejxGot it18:31
hggdhthere are some reasons18:31
bcurtiswx_any questions on this topic?18:31
devildante"regression-release natty" for unstable releases?18:31
hggdh- we identify a regression on Maverick, but it was present since Jaunty18:31
hggdhdevildante: yes18:32
hggdhas we find releases affected, we *nominate* them on the bug18:32
xteejxSo essentially, is a regression or not, no more "could be"'s?18:32
hggdhyes, essentially. If it is not a regression, no nomination, or the nomination is rejected18:32
xteejxOk18:33
bcurtiswx_hggdh, anything else?18:33
hggdhmost regression-potential never got changed to -release18:33
hggdhwe will start to implement it now, for the Natty cycle.18:33
bdmurraybug day!18:33
xteejxIs this being removed from LPGM script and LP?18:33
bcurtiswx_bdmurray would know about LPGM18:34
hggdhyes. And it will be removed from the regression wiki pages18:34
bdmurrayxteejx: good question!18:34
hggdhthis as bdmurray points out, is a serious candidate for a bug day18:34
bcurtiswx_#action Bug Day to be created for regression-potential tags18:34
meetingologyACTION: Bug Day to be created for regression-potential tags18:34
bcurtiswx_who wants to take this action up?18:35
hggdh<sigh/> ;-)18:35
bcurtiswx_charlie-tca, could you email mentors not at meeting today about posting to ML ?18:35
* hggdh volunteers, before getting volunteered18:35
charlie-tcabcurtiswx: yes18:35
bcurtiswx_TY hggdh :)18:35
bcurtiswx_charlie-tca, thx as well18:35
nigelbhggdh: I shall help you18:35
bdmurray#action bdmurray to remove regression-potential as an official bug tag for Ubuntu18:35
meetingologyACTION: bdmurray to remove regression-potential as an official bug tag for Ubuntu18:35
bdmurrayfor the bug day I'd ignore all linux bugs18:36
devildantewhy's that?18:36
bcurtiswx_OK, I should move on18:36
hggdh#action hggdh to prepare a bug day excepting kernel18:36
meetingologyACTION: hggdh to prepare a bug day excepting kernel18:36
bcurtiswx_please PM hggdh for further comments18:36
devildante'kay :)18:36
bcurtiswx_#topic Review of the ReportingBugsAlternate page.18:37
meetingologyTOPIC: Review of the ReportingBugsAlternate page.18:37
hggdh#action hggdh to clean up the Regression wiki pages18:37
meetingologyACTION: hggdh to clean up the Regression wiki pages18:37
bcurtiswx_i think this may have been taken car eof18:37
devildanteyes :p18:37
bcurtiswx_did we move the ReportingBugsAlternate page already ?18:37
devildanteyes18:37
bcurtiswx_OK, that was quick.. lol18:37
bcurtiswx_moving on again18:37
bcurtiswx_#topic Review the re-writes of the wiki. It is now using two different headers and triage pages are missing the meeting and BugDay headers. Example: https://wiki.ubuntu.com/Bugs/HowToTriage and https://wiki.ubuntu.com/Bugs/FindRightPackage --charlie-tca18:37
meetingologyTOPIC: Review the re-writes of the wiki. It is now using two different headers and triage pages are missing the meeting and BugDay headers. Example: https://wiki.ubuntu.com/Bugs/HowToTriage and https://wiki.ubuntu.com/Bugs/FindRightPackage --charlie-tca18:37
nigelbI have something for this item o/18:37
bcurtiswx_nigelb, we'll come back at end, sorry18:38
nigelbbcurtiswx_: about the wiki18:38
nigelb(the current one)18:38
bcurtiswx_oh, so you post about my topic before i post about the topic.. :P nice18:38
charlie-tcaWell, I wanted to know the meeting date and time. I went to my trusty wiki page, /HowToTriage and the heading is missing. No problem, I will go to events.18:38
nigelbUnofficially, I have heard that the wiki theme is going to change to a new theme light.  You can see in your wiki preferences page right now.18:39
charlie-tcaThat fails too. As a matter of fact, I don't think you can find the meeting from that page any more18:39
nigelbThedate for that theme's launch is set to be tomorrow - this might mean a massive redsign of the wiki - especially the headers18:40
charlie-tcaIf the bugsquad is connected to these wiki pages, we should have a single heading format. Right now, we have two headings in use, and they do not even reference each others pages18:40
charlie-tcaAll these changes are great, but they are not making it any easier to find anything.18:40
charlie-tcaI suggest we somehow get the same headings on all the pages, or at least get some links to the other sections for the bugsquad to use18:41
bcurtiswx_charlie-tca, OK.  Who would have the time to edit for similar headers?. someone other than charlie plz.. hes already doing stuff :)18:41
nigelbarg, cornered o/18:42
charlie-tcaHowToTriage has grown ridiculously long, but does not even link to many of the pages we need any more18:42
bcurtiswx_#action nigelb to edit bugsquad headers to be similar or link to each other appropriately18:42
meetingologyACTION: nigelb to edit bugsquad headers to be similar or link to each other appropriately18:42
bcurtiswx_thanks nigelb :)18:42
devildantecharlie-tca: HowToTriageAlternate will come one day :p18:42
nigelbnp :)18:43
devildantethanks nigelb :)18:43
charlie-tcaIt is not needed, devildante18:43
devildanteyou said it was too long :p18:43
bcurtiswx_OK moving on..18:43
bcurtiswx_nice segway devildante18:43
charlie-tcaall that is needed is to use the headings properly, and put some references back instead of trying to squeeze everything in to it18:43
bcurtiswx_#topic Discussion regarding lengthyness of HowToTriage page - BrianMurray18:43
meetingologyTOPIC: Discussion regarding lengthyness of HowToTriage page - BrianMurray18:43
bcurtiswx_bdmurray, ^^ ?18:43
devildanteI did not expect that :p18:44
bdmurrayI was looking at HowToTriage recently and it really seems quite long18:44
mistryniteshhttps://wiki.ubuntu.com/Bugs/FindRightPackage#Sound page asks to report hardware related issues against alsa-base, but Bug Reports link on http://packages.ubuntu.com/maverick/alsa-base indicates alsa-driver. Time to update wiki?18:44
bdmurrayI was wondering if other people feel the same way18:44
* charlie-tca nods18:44
devildanteI think you have a point here :)18:44
* bcurtiswx_ asks attendees to visit http://wiki.ubuntu.com/Bugs/HowToTriage18:44
bdmurrayI guess I'd like to see a HowToTriage and HowToTriageAdvanced page18:45
devildanteI'd like to see a LOT of images on HowToTriage18:45
bdmurrayHowToTriage would just be "try to recreate and set status to confirmed.  Now you are triaging!"18:45
devildantea picture is worth a thousand words :)18:45
charlie-tcaand give a reference to meetings and to other pages18:46
bdmurrayOtherwise the triaging process seems overwhelming and hard to be a part of18:46
hggdhI agree18:46
bdmurraybut really its rather easy18:46
devildantethe biggest problem IMO is that it isn't even "ordered"18:46
xteejx+1 it should be made as simple as possible18:46
bdmurrayadd a tag - bam! you are triaging18:46
xteejxor package assignment, maybe that's Intermediate though...18:47
bcurtiswx_OK, any volunteers for taking action on splitting the HowToTriage page up ?18:47
devildanteme :)18:47
bcurtiswx_remember, just getting it started will be great for next months meeting18:47
bcurtiswx_#action devildante to split HowToTriage page up into a simple page and an advanced page18:47
meetingologyACTION: devildante to split HowToTriage page up into a simple page and an advanced page18:47
bcurtiswx_thanks devildante18:47
devildanteyw :)18:47
charlie-tcaI honestly can't take anymore until after uds18:48
devildanteI'd like extended feedback first on the page, that will be on the ML though :)18:48
bcurtiswx_OK, for another 8 minutes18:48
bcurtiswx_#topic open discussions18:48
meetingologyTOPIC: open discussions18:48
bcurtiswx_anyone?18:48
devildanteI have an idea I want to discuss18:48
bcurtiswx_devildante, you have the floor18:49
bcurtiswx_..so to speak.. :P18:49
devildantethanks :)18:49
devildanteCurrently, we only accept bug reports in English18:49
devildantemaking it nearly impossible for people not fluent in English to report a bug18:50
devildanteWhat I would like to propose is to propose to each language community (ubuntu-fr, ubuntu-es...) to have small groups of bug triagers18:51
devildantethat can talk both English and their foreign language18:51
micahgs/foreign/native :)18:51
devildantethey triage bugs from people in the local community, then get it on Launchpad all translated18:51
devildantemicahg: yes, thanks :)18:52
bcurtiswx_I see.  What about urging reporters to report in english, if not then we can use something like google translate.. and request the appropriate groups to finish18:52
seb128hey18:52
* bcurtiswx_ waves to seb12818:52
seb128just lurking but don't start translating bugs18:52
* micahg uses Google Translate for foreign bugs and has not been attacked for incorrectness yet18:52
xteejxI don't mean to burst the bubble, but wouldn't it just be easier to copy/paste from Google translate into LP18:52
seb128we have bugs over want we can triage and work on18:52
* charlie-tca uses google translate, too18:52
seb128there is no need to try to get lower quality technically ones adding to that18:53
xteejxOr better yet...18:53
seb128especially when you can't ask questions without having a translator18:53
bcurtiswx_seb128, so in essence asking the reporter to translate will decrease workload drastically ?18:53
devildanteI use it too, but it's not always perfect + by doing this, you make the "not-talking-english" reporters refrain from posting other bugs IMO18:53
xteejxOn th report a bug page, have a small "if English is not your native language, please type here and choose your language and it will be translated to English" explnation in each language and implement the Google API into the webpage?18:54
bcurtiswx_what about LP using something like google translate automatically ?18:54
bdmurrayLong term we'd like non-english speakers to be able to report bugs too we just really aren't in a position to deal with them now.18:54
bcurtiswx_if it recognized non english words it will auto translate.. then maybe add a tag saying ti was auto translated ?18:54
micahgbcurtiswx_: that seems more prone to error18:55
xteejxYeah, an "expect badly broken English" message ;)18:55
bcurtiswx_well the tag would let us know it's not going to eb perfect18:55
xteejx+118:55
devildanteadvantage of the approach I proposed is that those bugs, rather than in a foreign language, would be triaged and ready for fixing18:55
bdmurrayIts not just about reporting the bug but having a conversation between the reporter and the triager.  This conversation can be hard enough with native English speakers.18:55
micahgbcurtiswx_: the LP bug devs have more important fish to fry IMHO18:55
bcurtiswx_micahg, sounds fine to me.. just offering suggestions :P18:56
xteejxOn the flip side, that counts most of us English speaking triagers who may be more knowledgable than those in the Loco teams18:56
seb128why do you want to translate bugs?18:56
seb128what issues do you try to fix?18:56
seb128we want less bug in better quality18:56
bdmurrayIn the event that there is a bug report not in English by all means have someone look at it but lets not encourage non-English bug reports at this point in time.18:56
seb128not extra bugs coming from automatic translations where the submitter will not be able to understand and reply to questions18:56
seb128if the submitter is not writting english chances are that he's not technical enough to submit a bug anyway18:57
bcurtiswx_bdmurray, OK.  I see both sides.  It's fair to keep it as is18:57
xteejxI'm guessing some already use Google to file bugs18:57
devildantexteejx: we can offer help to those LoCo teams18:57
seb128users issues should go to the answer tracker18:57
hggdh+118:57
micahgthat's the important thing that needs more attention18:57
devildanteseb128: since when we do require bug reporters to have technical knowledge?18:57
xteejxThere's always the -es/-fr/-de IRC channels18:57
seb128bugs are technical descriptions of issues18:57
hggdhwe do not, and this is a problem, devildante18:58
seb128"... doesn't work, please help me to solve it" are for the answer tracker18:58
charlie-tcaI was wondering the same thing. Are we going to require the bug reporters to learn to program, too?18:58
xteejxwith those coming from Mac and Windows, this shoul dbe as easy as possible18:58
devildantethe technical descriptions should come from bug triagers, who identify the problem18:58
seb128oh come on18:58
bcurtiswx_OK. i'd ask that we stop and continue this dicsussion in the mailing list.  devildante woudl you start an e-mail?18:58
seb128we have bugs over want we can triage18:58
seb128what is the point to make easier to report lower quality bugs18:58
devildantebcurtiswx_: okay :)18:58
micahgcharlie-tca: simple steps to reproduce and knowing that it's a bug not a how-to is what seb128 is saying I think18:58
seb128just get users to file their issues on the answer tracker18:58
devildantelater though, I have some work to do18:59
seb128than you can review the answer trackers and switch those to bugs if you want18:59
bcurtiswx_#action: devildante to start e-mail thread in mailing list about translations of bug reports18:59
meetingologyACTION: : devildante to start e-mail thread in mailing list about translations of bug reports18:59
xteejxGood point18:59
hggdhI agree with seb12818:59
xteejxSame18:59
bcurtiswx_I'm moving on, please continue discussion in the mailing list.18:59
* micahg agrees as well18:59
* devildante will be afk for a while, but agrees about the ML part19:00
=== devildante is now known as devildanteafk
micahg!away > devildanteafk19:00
bcurtiswx_#topic chair for next meeting November 9th 17:00 UTC19:00
ubot2devildanteafk, please see my private message19:00
meetingologyTOPIC: chair for next meeting November 9th 17:00 UTC19:00
bcurtiswx_any volunteers for chairing?19:00
xteejxI would, but not respected enough lol :)19:00
* hggdh volunteers19:00
micahg+119:01
hggdhxteejx: you *can*19:01
xteejxNo it's ok :)19:01
xteejxhggdh +1 to chair19:01
hggdhmicahg: you mean you also volunteer?19:01
bcurtiswx_#action hggdh to chair next meeting19:01
meetingologyACTION: hggdh to chair next meeting19:01
bcurtiswx_#endmeeting19:01
charlie-tcayay for volunteers19:01
meetingologyMeeting ended Tue Oct 12 17:58:58 2010 UTC.  Information about MeetBot at http://wiki.ubuntu.com/AlanBell . (v 0.1.4)19:01
meetingologyMinutes:        http://mootbot.libertus.co.uk/ubuntu-bugs/2010/ubuntu-bugs.2010-10-12-16.57.moin.txt19:01
bcurtiswx_Thanks for attending19:01
micahghggdh: no, I second your nomination :)19:01
bcurtiswx_the link has the log for today19:01
hggdhwell, I had to try ;-)19:01
xteejxDamn that's clever19:01
charlie-tcabcurtiswx: Thanks for chairing. Good job19:01
hggdhbcurtiswx_: thank you very much19:01
micahghggdh: the time doesn't work out that I can guarantee availability19:02
xteejxThanks bcurtiswx_ :)19:02
micahgthanks bcurtiswx19:02
hggdhmicahg: I know, I just did not resist :-)19:02
bcurtiswx_everyone, yw.  have a great week :)19:02
xteejxOn a lighter note, I know it's aside from triaging, but might make you all smile a little19:02
xteejxhttp://www.youtube.com/watch?v=KbkzXiLTk7o19:03
nigelbxteejx: good work19:03
xteejxnigelb: Not really, I just heavily edited the audio and used the video from the Examples folder19:05
xteejxlol19:05
bcurtiswx_hggdh: for next meeting, you have a whole bunch of action items to get updates on.  They're all listed in the log19:06
hggdhbcurtiswx_: will do, thank you19:06
bcurtiswx_how do i do a double indent on the wiki>19:20
bcurtiswx_got it, nvm19:23
=== ivoks-afk is now known as ivoks
=== devildanteafk is now known as devildante
devildantesorry, micahg :)19:51
jibelhggdh, sorry I couldn't attend the bugsquad meeting, it was late and I had to deal with the kids. I'll take the actions to organize the bugday and update the wiki pages.19:52
hggdhjibel: np problem, and thank you :-)19:53
jibelhggdh, thanks to you for presenting the workflow so perfectly :-)19:53
devildantejibel: I have to say, that workflow is much much better, so thank you both :)19:54
jibeldevildante, thanks, we will see when applying it to real bugs.19:55
nigelbbug Could not load one of the supported DNS libraries (dnspython or pydns).19:57
nigelbgah19:57
devildantelol19:57
nigelbdebian bug 41345719:57
ubot2Debian bug 413457 in python-xmpp "python-xmpp: DNS warning on import" [Normal,Open] http://bugs.debian.org/41345719:57
nigelbright, so this is fixed, okay :)19:58
xteejxwow so many expired bugs are just a load of old crap20:09
devildantexteejx: that's the idea behind it ;)20:09
xteejxi.e. no replies to requests for info, getting thru at a good rate :)20:09
xteejxdevildante: lol20:10
njincan someone triage this https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/65750420:13
ubot2Launchpad bug 657504 in alsa-driver (Ubuntu) "Sound on the headphones doesn't work (affects: 1) (heat: 8)" [Undecided,Confirmed]20:13
xteejxI'll take a look20:14
devildanteShouldn't those bugs be reported against linux?20:14
xteejxdevildante: I was always cautious about sound ones, could be either, more likely alsa20:15
xteejxnjin: This doesn't need triaged, there was a request by Felix for the reporter to try a live CD (10.10) but it hasn't been done20:15
devildantexteejx: it was njin (Fabio) who requested that :p20:16
xteejxlol20:16
njincan someone triage this https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/65507820:17
ubot2Launchpad bug 655078 in nvidia-graphics-drivers (Ubuntu) "Beta 10.10 Nvidia update broke Sony Vaio VPCF136FM installation (affects: 11) (heat: 62)" [Undecided,Opinion]20:17
xteejxThere isn't any apport information in the alsa report...that's the first thing20:17
njinI think that is a broken module20:18
xteejxnjin: The nvidia problem is a known issue, it's in the release notes20:18
njinxteejx:thanks, at now i don't have time to do nothing20:19
xteejxI'll sort it if you want20:19
njinok, thanks20:20
njinxteejx:^^20:20
xteejx:)20:20
=== ivoks is now known as ivoks-afk
shaunowhat's the best way to go about filing a bug when you genuinely have no idea what package is at fault?22:11
devildanteshauno: you can ask us :)22:14
devildanteshauno: what's your bug?22:14
shaunomy touchpad doesn't work, at all, under maverick22:15
devildanteshauno: do an "ls /proc/bus/input/devices" in a terminal, please22:17
devildanteoops, no, forget that22:18
shaunoit's there, with 444 perms22:19
devildantereport it against linux22:19
devildantedevelopers should know whether it's a kernel or xorg problem22:19
micahgshauno: https://wiki.ubuntu.com/DebuggingTouchpadDetection22:19
shaunofairly sure it's X, because click works (so it's using the right device).  just zero movement22:20
micahgdevildante: ^^22:20
devildanteyes, I saw that page22:20
shaunomicahg: looks promising.  just grabbing elinks now :)22:20
devildantemicahg: but the instructions are a little outdated, I think22:20
micahgdevildante: k, that I don't know, if you know what the updates are, feel free to fix22:21
devildantemicahg: "If you do not find a Touchpad in you /proc/bus/inpus/devices, ..." but /proc/bus/input/devices is a file for me22:21
BUGabundooias22:21
devildantemicahg, that's the problem, I don't know how to fix that :-/22:22
charlie-tcaheh, too many mentions of Hal, too22:22
shaunodevildante: the touchpad is mentioned in that file22:23
devildanteah22:23
=== BUGabundo is now known as BUGa_vacations
shaunohttp://pastebin.com/pGPbT7Cb22:24
charlie-tcaBUGa_vacations: did they open our channel again yet?22:24
BUGa_vacationsnoooooo22:24
BUGa_vacations:(((22:24
BUGa_vacationstsimpson: ping ping ping :P22:24
devildanteshauno: oh god, I have the same exact specs :p22:24
charlie-tca8 changes for natty today22:25
shaunohah, mbp3,1 ?22:25
devildantebut my apple trackpad is working22:25
devildanteah, no, 7,122:25
* micahg needs to subscribe to natty-changes22:25
* devildante updates his natty now22:25
shaunothis used to work in 8.04.  in 10.04 it worked, but needed gsynaptics to set the tracking speeds (which were all set to zero).  now gsynaptics has gone22:26
charlie-tcafile the bug using ubuntu-bug linux . someone can change the package if needed, then22:26
devildanteyeah, it's the best way :)22:27

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