[00:17] <BUGabundo> ahhh my pillow called... she wants me back. see you tomorrow µfriends
[00:18] <charlie-tca> good night, BUGabundo
[02:16] <snadge> hmm.. 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:17] <snadge> so which is it? :P
[02:28] <snadge> whats the name of the program which is supposed to update the login banner?
[02:29] <snadge> ahh /etc/motd
[02:31] <snadge> https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/400462
[02:31] <ubot2> Launchpad 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:48] <snadge> can someone explain to me how to get the fixed version of update-motd for maverick?
[02:49] <snadge> on the launchpad bug page, it says it was fixed in version 3.4-0ubuntu1
[02:50] <snadge> but the version that comes with maverick is 3.5-0ubuntu1
[02:55] <snadge> oh i see the problem.. its a regression that hasn't been reported yet :|
[03:40] <snadge> where the fuck did the fucking update-motd script go? :P
[03:40] <snadge> i want a god damned refund ;)
[03:40] <micahg> !ohmy | snadge
[03:40] <ubot2> snadge: 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:42] <snadge> i 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 here
[03:42] <snadge> whenever i run into a problem, i never get as far as actually being able to identify it and fix it.. its so annoying :P
[05:06] <gp5st> https://bugs.launchpad.net/ubuntu/+source/php-memcached/+bug/658939 does that have enough information?
[05:06] <ubot2> Launchpad bug 658939 in php-memcached (Ubuntu) "php5-memcached does not work (affects: 1) (heat: 6)" [Undecided,New]
[05:48] <lou1234> Hello
[05:48] <lou1234> Can someone help me with a bug report? I found the procedure online to follow
[05:48] <lou1234> but this 'feature' is causing ubuntu to completely crash and log me out
[05:50] <lou1234> hmm....
[05:51] <lou1234> anyone around?
[05:55] <micahg> lou1234: ubuntu-bug is crashing?
[06:02] <lou1234> no
[06:03] <lou1234> when i try to reproduce the bug
[06:03] <lou1234> ubuntu
[06:03] <lou1234>  completely crashes and logs me out
[06:05] <lou1234> sorry I am completely new to the bug reporting game. should I still try ubuntu bug?
[06:06] <micahg> lou1234: which package is crashing the system?
[06:06] <lou1234> so  when i open up a pdf
[06:06] <lou1234> in firefox
[06:06] <lou1234> and then try to print it
[06:06] <lou1234> ubuntu completely crashes
[06:07] <lou1234> I have the samsung universal print driver installed for my laser printer
[06:07] <lou1234> so I am not sure where the problem is
[06:07] <micahg> lou1234: maybe try ubuntu-bug xorg
[06:07] <persia> When you say "ubuntu completely crashes", could you describe that in a bit more detail?
[06:08] <lou1234> Sure. I select print and then a box pops up I select print and then my screen goes black and goes to the login menu
[06:08] <lou1234> I login and every window I had opened is closed
[06:09] <lou1234> it is like a clean login when I restart firefox it comes up with the 'uh oh' firefox crashed screen and wants to restore tabs
[06:09] <persia> Oh, excellent.  That is an xorg crash.
[06:09] <lou1234> oh
[06:09]  * lou1234 has no idea what it is
[06:09] <persia> `ubuntu-bug xorg` and answer the questions and you'll file the right sort of bug.
[06:10] <persia> micahg, What made you know it was xorg that I missed?
[06:10] <micahg> persia: Ubuntu completely crashed implied it, we've had a few of those submissions for Firefox, I'm looking for the bug now
[06:11] <lou1234> micahg has this been an issue in 10.10 or has it been there previously?
[06:11] <micahg> bug 539772
[06:11] <ubot2> Launchpad 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/539772
[06:12] <persia> micahg, 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] <micahg> lou1234: can you please file a new bug with ubuntu-bug xorg and mention that bug number I just put in the channel?
[06:13] <lou1234> sure!
[06:13] <micahg> lou1234: thanks
[06:13] <lou1234> so im reading the reporting bugs page...
[06:13] <micahg> lou1234: BTW, just out of curiosity, what type of video card do you have?
[06:13] <lou1234> do i need to do any more research or is that it?
[06:13] <lou1234> one sec
[06:13] <lou1234> let me get the model number
[06:14] <micahg> lou1234: brand is sufficient in this case
[06:14] <lou1234>  ati radeon hd 4670
[06:14] <micahg> ah, yes, ok
[06:15] <lou1234> is this a security vulnerability?
[06:16] <persia> Likely only in the denial-of-service sense, and even then, with easy workarounds, so probably not.
[06:16] <micahg> lou1234: probably not
[06:16] <lou1234> oh okay ... im still reading the page
[06:19] <lou1234> what exactly are gdm log files ... and is there a way i can view what information it contains?
[06:21] <persia> /var/log/gdm/*
[06:21] <persia> Should be text files: so use your favorite test reader
[06:22] <lou1234> im in /var/log
[06:22] <lou1234> and when I try to cd/gdm it says permission denied... when I try sudo cd/gdm I'm getting  told cd command not found
[06:25] <lou1234> any idea what I am doing wrong?
[06:27] <micahg> lou1234: cd gdm?
[06:27] <micahg> although that shouldn't work...
[06:27] <micahg> lou1234: try ls /var/log/gdm
[06:28] <persia> Only root can see those logs.
[06:28] <persia> `sudo ls /var/log/gdm` and similar
[06:29] <micahg> right
[06:29] <lou1234> basically i just don't want my username posted out there
[06:29] <lou1234> so if there is a quick way for me to edit that out
[06:30] <lou1234> i would have no problem handing the logs out to help peeps with this bug
[06:34] <persia> lou1234, 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] <lou1234> haha
[06:35] <lou1234> fair enough
[07:00] <lou1234> If I am doing a backtrace do I need to completely backout of the bug report - do the backtrace and then refile it?
[07:01] <persia> No.
[07:01] <persia> You can attach the stacktrace to the bug later.
[07:02] <lou1234> oh ok
[07:02] <lou1234> does this title work - firefox causes xorg to crash
[07:03] <persia> I'd recommend something involving the printing action.
[07:03] <persia> Once the PDF is open, firefox is no longer the primary application.
[07:04] <lou1234> oh
[07:22] <lou1234> now that i submitted it do i need to do anything else?
[07:28] <persia> Wait, mostly.
[07:29] <persia> Ideally, someone will either find a solution or ask for more information.
[07:35] <lou1234> if they ask for more info
[07:36] <lou1234> will i get an email?
[07:36] <persia> If LP has your email address, you ought, yes.
[07:38] <lou1234> LP?
[07:38] <lou1234> oh nevermind
[07:38] <lou1234> okay
[07:38] <lou1234> thanks for all of the help!
[07:38] <lou1234> have a good one!
[07:38] <lou1234> bye bye!
[09:31] <danage> i'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 it
[10:55] <popey> persia: I see you're in a helpful mood this morning with regards to bugs :)
[10:56] <popey> persia: 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] <ubot2> Launchpad 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/619663
[10:56] <popey> debdiff available too https://bugs.edge.launchpad.net/ubuntu/+source/libdrm/+bug/619663/+attachment/1679043/+files/libdrm_2.4.21-1ubuntu2.1.debdiff
[10:57] <ubot2> Launchpad 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:58] <ikonia> that would be helpful to resolve, that's been quite a keen one in #ubuntu recently
[10:58] <persia> Anyone tested the debdiff?
[10:59] <persia> Ah, yes, it is tested.
[11:00] <persia> OK.  Bug needs to be subscribed to the sponsors team (ubuntu-sponsors).
[11:00] <persia> Someone needs to upload it (who can upload X)
[11:00] <persia> then 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] <persia> If that's true, it drops into -updates in about a week.
[11:06] <popey> should I be looking for someone who can upload to x ?
[11:06] <persia> That's what subscribing "ubuntu-sponsors" does.  I can do the subscription if you don't want.
[11:07] <popey> ah
[11:07] <persia> There'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:09] <persia> popey, 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:10] <ikonia> popey: I would be happy to help you with that
[11:11] <popey> yes
[11:11] <popey> i have found that some bugs I can "fire and forget" such as those relating to CUPS
[11:11] <popey> Till is massively _on_ the ball there
[11:12] <popey> whereas others, X, kernel, nautilus.. I can file a bug and see no action other than a bugsquad person pasting a boilerplate repy
[11:12] <popey> *reply
[11:12] <popey> I 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 developers
[11:12] <ikonia> that burns me
[11:14] <ikonia> is there currently a guide/process/work-flow for bugsuad members on dealing with a bug ?
[11:17] <zeroseven0183> Hi ikonia. Here are some of the pages that are useful when triaging bugs
[11:17] <zeroseven0183> BugSquad : https://wiki.ubuntu.com/BugSquad
[11:17] <zeroseven0183> How To Triage https://wiki.ubuntu.com/Bugs/HowToTriage
[11:17] <zeroseven0183> Common Tasks : https://wiki.ubuntu.com/Bugs/CommonTasks
[11:18] <zeroseven0183> responses https://wiki.ubuntu.com/Bugs/Responses
[11:18] <zeroseven0183> Checklist https://wiki.ubuntu.com/Bugs/Checklist
[11:18] <ikonia> nice
[11:18] <ikonia> thanks
[11:18] <zeroseven0183> Be sure you have a Launchpad account
[11:18] <ikonia> I do
[11:18] <ikonia> I just want to read what the process is
[11:19] <zeroseven0183> I also suggest watching this video tutorial: Bug Triage 101 http://blip.tv/file/3219368
[11:19] <ikonia> always work a look
[11:20] <zeroseven0183> :-)
[11:20] <persia> popey, Till is an example of the sort of monomanaically-focused developer that gets as close to "maintainer" as we have :)
[11:21] <persia> ikonia, 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:33] <ikonia> well thats the game, get a process in place that allows people to contribute, but also puts some form of quality control in place
[11:33] <ikonia> and also makes sure the bugs are filled with useful information and the correct status
[11:35] <persia> Yep :)
[11:38] <mistrynitesh> bug controllers, bug #659075 is a wishlist
[11:38] <ubot2> Launchpad 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/659075
[11:40] <ikonia> is there a bug status for wishlist or request ?
[11:41] <mistrynitesh> ikonia: 'wishlist' is a value for importance
[11:42] <ikonia> ah
[11:43] <mistrynitesh> only members of bug-control team can change it, so I am requesting them
[11:44] <persia> mistrynitesh, It5's not wishlist: it's filed against the wrong project.
[11:44] <persia> needs to be filed against the lucid-backports project.
[11:45] <persia> https://bugs.launchpad.net/lucid-backports
[11:45] <mistrynitesh> :S oh, ok
[11:47] <mistrynitesh> what should be done for Bug #659074 , it is written in polish and the reporter asks to speak Polish :(
[11:47] <ubot2> Launchpad bug 659074 in firefox (Ubuntu) "margorlik@gmail.cm (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/659074
[11:51] <persia> mistrynitesh, We usually turn those into questions (in polish), hoping the support team can file a bug on their behalf.
[11:51] <persia> mistrynitesh, 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:53] <mistrynitesh> persia: I had no idea what it meant. Just found it was polish by trial at translate.google.com 8-)
[11:53] <persia> If you're up for it, maybe grab someone in #ubuntu-pl to help integrate with the local support team.
[11:54] <persia> I 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] <mistrynitesh> hmmm will check out
[11:54] <persia> I 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.
[12:02] <mistrynitesh> persia: is there something by the name of lucid-backports? Nearest search I could find was ubuntu-ruby-backports-ppa
[12:03] <persia> https://bugs.launchpad.net/lucid-backports
[12:05] <mistrynitesh> then 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:06] <persia> Because launchpad doesn't have a working search facility for terms that are subsets of other terms.
[12:06] <persia> So if you search for "foo" and "foobar" happens to exist, you'll probably never find "foo"
[12:07] <mistrynitesh> is it okay if I manually type 'lucid-backports' in the package field of bug report?
[12:08] <mistrynitesh> sounds misterious :) will change the package to 'lucid-backports'
[12:12] <mistrynitesh> persia: 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] <persia> You need "Also Affects Project"
[12:13] <persia> Not "Also affects Distribution"
[12:13] <persia> Source package is correct.
[12:14] <mistrynitesh> okay!
[12:22] <mistrynitesh> persia: thanks for guiding :)
[12:23] <persia> mistrynitesh, Thanks for helping put bugs in the right place, and asking if you weren't sure.
[12:23] <mistrynitesh> my pleasure
[14:26] <Olivier_Blaziken> Sorry, when will by the meeting
[14:29] <yofel> Olivier_Blaziken: 17:00 UTC we currently have 13:29 UTC
[14:29] <yofel> (use 'date -u' in a terminal to get the UTC time)
[14:29] <Olivier_Blaziken> ok Thx
[15:01] <nigelb> charlie-tca: entertaining the crowd, I'm from classroom team :)
[15:01] <charlie-tca> Oh, okay! Great job on it
[15:02]  * charlie-tca thought nigelb was just trying to confuse him
[15:02] <nigelb> charlie-tca: heh :)
[15:48] <jibel> bdmurray, hi, do you know if the number of people affected by a specific bug is increased when the report matches a bug pattern ?
[15:50] <elder> My X session crashes whenever I run "gitk" on another system using my 10.10 laptop as the DISPLAY.
[15:56] <bdmurray> jibel: 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:58] <bdmurray> jibel: bug 487316
[15:58] <ubot2> Launchpad bug 487316 in apport (Ubuntu) "apport should metoo bug reports that match a pattern (affects: 1) (heat: 10)" [Wishlist,Triaged] https://launchpad.net/bugs/487316
[15:58] <hggdh> elder: please open a bug on this
[16:05] <jibel> bdmurray, we could use login_anonymously starting from lucid and make authentication transparent to the user ?
[16:06] <jibel> bdmurray, the problem is that a bug with a bug pattern associated just vanishes
[16:06] <bdmurray> jibel: the affects_user call requires a user
[16:06] <jibel> :/
[16:07] <bdmurray> jibel: there is some talk of permissions redesign for launchpadlib but I'm not on top of that at the moment
[16:10] <bdmurray> hggdh: did you extend xttejx?
[16:10] <bdmurray> hggdh: er xteejx
[16:11] <hggdh> bdmurray: yes, I did, he is back and was going to expire in 2 days, I think
[16:12] <bdmurray> hggdh: cool, thanks
[16:13] <hggdh> bdmurray: BTW -- yofel gave us two patches for the responses. The first one (additional </comment> looks good
[16:14] <hggdh> bdmurray: the second -- updating the dev release to N -- I am not sure it is already time
[16:14] <bdmurray> hggdh: right so just don't use it! ;-)
[16:15] <hggdh> bdmurray: heh. The actual question is... let's accept the first one?
[16:15] <bdmurray> hggdh: they've both been merged and push
[16:16] <hggdh> yeee!
[16:16]  * hggdh bows to the bugmeister
[16:37] <bcurtiswx_> would someone send an e-mail reminder to the list about the meeting at 1ET or 17UTC
[16:37]  * bcurtiswx_ is in the middle of something, but wanted to get one out
[16:37] <micahg> bcurtiswx_: I think pedro did yesterday
[16:41]  * bcurtiswx_ has a lot of mail to check.. thx micahg
[16:57] <xteejx> Afternoon all
[17:11] <hggdh> cheers xteejx
[17:11] <xteejx> hggdh: ?? What did I do lol
[17:12] <micahg> wow, we have a meeting chair now, cool
[17:12] <xteejx> micahg: Am I interrupting a meeting here??
[17:12] <hggdh> xteejx: you are back :-)
[17:13] <hggdh> xteejx: not by ~47min
[17:13]  * xteejx didn't realise he was missed *that* much ;)
[17:14] <xteejx> ahh 5pm UTC duh - I should've worked that our is 6pm here (UK)
[17:14] <xteejx> oh well it'll be back to normal UTC=my time in a few weeks
[17:16] <xteejx> https://wiki.ubuntu.com/BugSquad/Meeting/Minutes are minutes not being kept now or have we missed 10 months or meetings?
[17:16] <xteejx> *of
[17:19] <bcurtiswx_> micahg, does that mean you want to chair our next meeting?
[17:19] <bcurtiswx_> :P
[17:19]  * charlie-tca hs missed not quite 10 months of meetings
[17:19] <xteejx> :P
[17:20]  * micahg hopes to be sitting in a chair for the next meeting bcurtiswx
[17:20] <bcurtiswx_> <drum hit>
[17:21]  * xteejx will be sitting on a sofa
[17:29] <charlie-tca> meeting is in here, right?
[17:33] <xteejx> charlie-tca: I assume so :)
[17:34] <hggdh> yes indeed
[17:34] <bcurtiswx_> charlie-tca, yup :)
[17:34] <xteejx> Dammit, how do you import .flv audio into audacity
[17:35] <xteejx> Oops, should've said that to #ubuntu :)
[17:35] <nigelb> o/
[17:35] <nigelb> hello all :)
[17:36]  * bcurtiswx_ takes a giant blade of grass and slaps xteejx with it :P
[17:37] <xteejx> lol bcurtiswx_ :P
[17:37] <xteejx> I'm trying to make a funny video, I'll link my youtube in when its done ;)
[17:49]  * micahg will be back in about 40 minutes
[17:50] <bcurtiswx_> no meeting for you 'eh
[17:50] <micahg> bcurtiswx_: like I said, I hope to be sitting in a chair ;)
[17:51] <bcurtiswx_> haha, OK micahg :)
[17:52] <bcurtiswx_> vish, did you want to lead the mentor subject?
[17:53] <xteejx> bcurtiswx_: No, I'll be here, my expertise is in video/audio production
[17:53] <xteejx> Done it in time...just
[17:54] <bcurtiswx_> ?
[17:54] <xteejx> Sorry, thoguth you meant I woon't be here cuz I was mesing with videos :)
[17:55] <bcurtiswx_> OK
[17:59] <hggdh> ~ô~
[17:59] <bcurtiswx_> 1 minute
[17:59] <xteejx> 20 seconds
[18:00] <bcurtiswx_> OK, WHo's Ready for some meeting fun?!?!?!?
[18:00] <bcurtiswx_> #startmeeting
[18:00] <meetingology> Meeting started Tue Oct 12 16:57:38 2010 UTC.  The chair is bcurtiswx_. Information about MeetBot at http://wiki.ubuntu.com/AlanBell.
[18:00] <meetingology> Useful Commands: #topic #action #link #idea #voters #vote #chair #action #agreed #help #info #endmeeting.
[18:00] <xteejx> Yup
[18:00] <devildante> I forgot it! :p
[18:00]  * charlie-tca waves
[18:00]  * devildante waves too
[18:00]  * xteejx waves back
[18: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 what
[18:01]  * charlie-tca notes we got us a meeting bot too
[18: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 time
[18:01] <bcurtiswx_> First things first:
[18:02] <bcurtiswx_> #topic Intro to new meeting bot. -bcurtiswx
[18:02] <meetingology> TOPIC: Intro to new meeting bot. -bcurtiswx
[18:02] <devildante> I lol'd at the name :p
[18:02] <bcurtiswx_> So , for those who aren't using text to speech, should be able to see that we have a meeting bot :)
[18:03]  * 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/MootBot
[18:04] <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 log
[18:05] <bcurtiswx_> Any questions on the bot?
[18:05]  * xteejx thinks it seems pretty effective
[18:05] <nigelb> +1 nice idea
[18:05] <xteejx> +1
[18:05] <charlie-tca> You have to preceed all commands with # ?
[18:05] <Olivier_Blaziken> +1
[18:05] <bcurtiswx_> if anyone has an idea they need to do the following, for it to be logged
[18:05] <bcurtiswx_> #idea , note that this command adds an entry into the log
[18:06] <bcurtiswx_> well it should... i can say it is still in beta.
[18:06] <bcurtiswx_> we'll have to see, lol
[18:07] <simar_> is the bug squad meeting going on??
[18:07] <nigelb> yes
[18:07] <bcurtiswx_> #topic Mentorship program update from Mentors.
[18:07] <meetingology> TOPIC: Mentorship program update from Mentors.
[18:07] <bcurtiswx_> did someone want to lead this?
[18:07] <bcurtiswx_> vish? ^^
[18:07] <nigelb> its for all mentors
[18:07] <charlie-tca> We need all mentors to give us an update, please.
[18:08] <bcurtiswx_> all present mentors o/
[18:08] <Olivier_Blaziken> +1
[18:08] <simar_> i will proceed
[18:08] <nigelb> o/
[18:08] <charlie-tca> Go ahead, simar
[18:08] <bcurtiswx_> simar_ go ahead and start
[18:08] <simar_> charlie-tca, :)
[18:08] <bcurtiswx_> All Present mentors who haven't o/ please do so i can come to you
[18:09] <hggdh> \o
[18: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 months
[18:09]  * nisshh doesnt think his mentor is around right now :|
[18:10] <simar_> otherwise ahmed my other student is doing well .. he working on touchpad
[18:10] <charlie-tca> great, simar_
[18:10] <Olivier_Blaziken> That will be nice
[18:10] <charlie-tca> drew212: update?
[18:11]  * devildante can do an update
[18:11] <charlie-tca> jibel: 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 package
[18:11] <simar_> over for me..
[18:11] <simar_> thanks :)
[18:12] <charlie-tca> hggdh: ??
[18:12]  * nigelb coughs
[18:12]  * devildante coughs too
[18:12] <hggdh> I have not seen kangorooo for quite a while
[18:13] <bcurtiswx_> nigelb, devildante, charlie's taken this segment :)
[18:14] <charlie-tca> hggdh: any update on your other two?
[18:14] <hggdh> oops
[18:14] <nigelb> heh
[18:14] <hggdh> hold on, let me check them
[18:15]  * charlie-tca wishes people were not always logged in to IRC
[18:15] <bcurtiswx_> lol
[18:15] <hggdh> holstein has asked to be temporarily dropped, too busy with school right now
[18:15] <hggdh> ojap is going nicely on :-)
[18:16] <charlie-tca> Good to hear
[18:16] <hggdh> yes indeed. One out of three, but at least one
[18:16] <charlie-tca> will you update the wiki and launchpad on holstein ?
[18:16] <bilalakhtar> Is a meeting going on here?
[18:16] <devildante> yep
[18:16] <simar_> bilalakhtar, ya
[18:16]  * bilalakhtar joins
[18:17] <charlie-tca> nigelb: next?
[18:17] <nigelb> ok
[18:17] <nigelb> I've been assigned 2 students who're finally showing some signs of interest in working
[18:17] <charlie-tca> :-)
[18:17] <nigelb> flipe is going well, he's asking me or asking in the channe when he has doubts
[18:18] <nigelb> He's very much interested in learning and helping out :)
[18:18] <nigelb> gigacore got it touch with me the day he was assigned, not heard from him since
[18:18] <nigelb> that's about it from me
[18:18] <charlie-tca> devildante:
[18:19] <devildante> ok
[18:19] <devildante> samwho is doing progress, even though he's busy at times with IRL university work
[18:19] <devildante> my other assigned student, I sent him an email but he has not responded yet
[18:20] <devildante> I should probably send him another e-mail
[18:20] <devildante> that's it for me, thanks :)
[18:20] <charlie-tca> bdmurray: here??
[18:21] <charlie-tca> bcurtiswx:
[18:21] <charlie-tca> you may as well take it
[18: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:22] <bdmurray> charlie-tca: yes, I'm here
[18:22] <charlie-tca> any 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 then
[18:23] <bcurtiswx_> both i will email soon for a follow up
[18:23] <charlie-tca> excellent.
[18:23] <bdmurray> I didn't think I was on the list with my launchpad work ...
[18:24] <charlie-tca> heh, looks like someone gave you a mentee again
[18:24] <charlie-tca> We will work on that one
[18:24] <charlie-tca> bcurtiswx: we will need anyone not present to send an update to the mailing list
[18:25] <charlie-tca> Eveybody 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 mentees
[18:25] <meetingology> ACTION: Mentors not at meeting need to report to the mailing list on their mentees
[18:25] <bcurtiswx_> Thanks charlie-tca
[18:26] <charlie-tca> (and don't let the "drop me" 's mess with you.)
[18:26] <bcurtiswx_> OK moving on
[18:26] <bcurtiswx_> #topic Regression tags and workflow.
[18:26] <meetingology> TOPIC: Regression tags and workflow.
[18:26] <bcurtiswx_> nobody assigned.  who wanted to talk about this?
[18:26] <hggdh> jibel: there?
[18:27] <hggdh> Otherwise I can talk about it
[18:27] <hggdh> We have discussed regression tags on our last meeting
[18:27] <bcurtiswx_> hggdh, go ahead, and jibel can pipe in if he gets in
[18:28] <hggdh> We have also sent an email to -devel talking about it, and asking for feedback
[18:28] <bcurtiswx_> Quick summary for those not present before?
[18:28] <nigelb> liky to the thread?
[18:28] <devildante> yes please :)
[18:28] <hggdh> Now, with the feedback we received we are going to start implementing it
[18:29] <hggdh> the change: we are dropping the 'regression-potential' tag
[18:29] <hggdh> It only created more work (mostly when a development release got promoted to stable, like right now with Maverick
[18:29] <xteejx> +1
[18:30] <bcurtiswx_> i see, +1
[18:30] <devildante> so what would be the tag that will replace it?
[18:30] <hggdh> instead we are going to mark regressions as 'regression(release|proposed|update)' followed by the version we found it in
[18:30] <hggdh> like maverick, lucid, etc
[18:30] <xteejx> hggdh: Can we have an example?
[18:30] <devildante> +42 then :)
[18:30] <bcurtiswx_> regression-proposed-maverick for instance?
[18:30] <hggdh> no. 'regression-release maverick'
[18:31] <bdmurray> actually ['regression-proposed', 'maverick']
[18:31] <hggdh> two different tags: one identify a regression, the other identify the version it was *found* on
[18:31] <bdmurray> so 2 separate tags
[18:31] <bcurtiswx_> OK
[18:31] <xteejx> Got it
[18:31] <hggdh> there are some reasons
[18: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 Jaunty
[18:32] <hggdh> devildante: yes
[18:32] <hggdh> as we find releases affected, we *nominate* them on the bug
[18:32] <xteejx> So essentially, is a regression or not, no more "could be"'s?
[18:32] <hggdh> yes, essentially. If it is not a regression, no nomination, or the nomination is rejected
[18:33] <xteejx> Ok
[18:33] <bcurtiswx_> hggdh, anything else?
[18:33] <hggdh> most regression-potential never got changed to -release
[18:33] <hggdh> we will start to implement it now, for the Natty cycle.
[18:33] <bdmurray> bug day!
[18:33] <xteejx> Is this being removed from LPGM script and LP?
[18:34] <bcurtiswx_> bdmurray would know about LPGM
[18:34] <hggdh> yes. And it will be removed from the regression wiki pages
[18:34] <bdmurray> xteejx: good question!
[18:34] <hggdh> this as bdmurray points out, is a serious candidate for a bug day
[18:34] <bcurtiswx_> #action Bug Day to be created for regression-potential tags
[18:34] <meetingology> ACTION: Bug Day to be created for regression-potential tags
[18:35] <bcurtiswx_> who wants to take this action up?
 ;-)
[18:35] <bcurtiswx_> charlie-tca, could you email mentors not at meeting today about posting to ML ?
[18:35]  * hggdh volunteers, before getting volunteered
[18:35] <charlie-tca> bcurtiswx: yes
[18:35] <bcurtiswx_> TY hggdh :)
[18:35] <bcurtiswx_> charlie-tca, thx as well
[18:35] <nigelb> hggdh: I shall help you
[18:35] <bdmurray> #action bdmurray to remove regression-potential as an official bug tag for Ubuntu
[18:35] <meetingology> ACTION: bdmurray to remove regression-potential as an official bug tag for Ubuntu
[18:36] <bdmurray> for the bug day I'd ignore all linux bugs
[18:36] <devildante> why's that?
[18:36] <bcurtiswx_> OK, I should move on
[18:36] <hggdh> #action hggdh to prepare a bug day excepting kernel
[18:36] <meetingology> ACTION: hggdh to prepare a bug day excepting kernel
[18:36] <bcurtiswx_> please PM hggdh for further comments
[18:36] <devildante> 'kay :)
[18:37] <bcurtiswx_> #topic Review of the ReportingBugsAlternate page.
[18:37] <meetingology> TOPIC: Review of the ReportingBugsAlternate page.
[18:37] <hggdh> #action hggdh to clean up the Regression wiki pages
[18:37] <meetingology> ACTION: hggdh to clean up the Regression wiki pages
[18:37] <bcurtiswx_> i think this may have been taken car eof
[18:37] <devildante> yes :p
[18:37] <bcurtiswx_> did we move the ReportingBugsAlternate page already ?
[18:37] <devildante> yes
[18:37] <bcurtiswx_> OK, that was quick.. lol
[18:37] <bcurtiswx_> moving on again
[18: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-tca
[18:37] <meetingology> 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-tca
[18:37] <nigelb> I have something for this item o/
[18:38] <bcurtiswx_> nigelb, we'll come back at end, sorry
[18:38] <nigelb> bcurtiswx_: about the wiki
[18:38] <nigelb> (the current one)
[18:38] <bcurtiswx_> oh, so you post about my topic before i post about the topic.. :P nice
[18:38] <charlie-tca> Well, 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:39] <nigelb> Unofficially, 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-tca> That fails too. As a matter of fact, I don't think you can find the meeting from that page any more
[18:40] <nigelb> Thedate for that theme's launch is set to be tomorrow - this might mean a massive redsign of the wiki - especially the headers
[18:40] <charlie-tca> If 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 pages
[18:40] <charlie-tca> All these changes are great, but they are not making it any easier to find anything.
[18:41] <charlie-tca> I 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 use
[18: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:42] <nigelb> arg, cornered o/
[18:42] <charlie-tca> HowToTriage has grown ridiculously long, but does not even link to many of the pages we need any more
[18:42] <bcurtiswx_> #action nigelb to edit bugsquad headers to be similar or link to each other appropriately
[18:42] <meetingology> ACTION: nigelb to edit bugsquad headers to be similar or link to each other appropriately
[18:42] <bcurtiswx_> thanks nigelb :)
[18:42] <devildante> charlie-tca: HowToTriageAlternate will come one day :p
[18:43] <nigelb> np :)
[18:43] <devildante> thanks nigelb :)
[18:43] <charlie-tca> It is not needed, devildante
[18:43] <devildante> you said it was too long :p
[18:43] <bcurtiswx_> OK moving on..
[18:43] <bcurtiswx_> nice segway devildante
[18:43] <charlie-tca> all that is needed is to use the headings properly, and put some references back instead of trying to squeeze everything in to it
[18:43] <bcurtiswx_> #topic Discussion regarding lengthyness of HowToTriage page - BrianMurray
[18:43] <meetingology> TOPIC: Discussion regarding lengthyness of HowToTriage page - BrianMurray
[18:43] <bcurtiswx_> bdmurray, ^^ ?
[18:44] <devildante> I did not expect that :p
[18:44] <bdmurray> I was looking at HowToTriage recently and it really seems quite long
[18:44] <mistrynitesh> https://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] <bdmurray> I was wondering if other people feel the same way
[18:44]  * charlie-tca nods
[18:44] <devildante> I think you have a point here :)
[18:44]  * bcurtiswx_ asks attendees to visit http://wiki.ubuntu.com/Bugs/HowToTriage
[18:45] <bdmurray> I guess I'd like to see a HowToTriage and HowToTriageAdvanced page
[18:45] <devildante> I'd like to see a LOT of images on HowToTriage
[18:45] <bdmurray> HowToTriage would just be "try to recreate and set status to confirmed.  Now you are triaging!"
[18:45] <devildante> a picture is worth a thousand words :)
[18:46] <charlie-tca> and give a reference to meetings and to other pages
[18:46] <bdmurray> Otherwise the triaging process seems overwhelming and hard to be a part of
[18:46] <hggdh> I agree
[18:46] <bdmurray> but really its rather easy
[18:46] <devildante> the biggest problem IMO is that it isn't even "ordered"
[18:46] <xteejx> +1 it should be made as simple as possible
[18:46] <bdmurray> add a tag - bam! you are triaging
[18:47] <xteejx> or package assignment, maybe that's Intermediate though...
[18:47] <bcurtiswx_> OK, any volunteers for taking action on splitting the HowToTriage page up ?
[18:47] <devildante> me :)
[18:47] <bcurtiswx_> remember, just getting it started will be great for next months meeting
[18:47] <bcurtiswx_> #action devildante to split HowToTriage page up into a simple page and an advanced page
[18:47] <meetingology> ACTION: devildante to split HowToTriage page up into a simple page and an advanced page
[18:47] <bcurtiswx_> thanks devildante
[18:47] <devildante> yw :)
[18:48] <charlie-tca> I honestly can't take anymore until after uds
[18:48] <devildante> I'd like extended feedback first on the page, that will be on the ML though :)
[18:48] <bcurtiswx_> OK, for another 8 minutes
[18:48] <bcurtiswx_> #topic open discussions
[18:48] <meetingology> TOPIC: open discussions
[18:48] <bcurtiswx_> anyone?
[18:48] <devildante> I have an idea I want to discuss
[18:49] <bcurtiswx_> devildante, you have the floor
[18:49] <bcurtiswx_> ..so to speak.. :P
[18:49] <devildante> thanks :)
[18:49] <devildante> Currently, we only accept bug reports in English
[18:50] <devildante> making it nearly impossible for people not fluent in English to report a bug
[18:51] <devildante> What I would like to propose is to propose to each language community (ubuntu-fr, ubuntu-es...) to have small groups of bug triagers
[18:51] <devildante> that can talk both English and their foreign language
[18:51] <micahg> s/foreign/native :)
[18:51] <devildante> they triage bugs from people in the local community, then get it on Launchpad all translated
[18:52] <devildante> micahg: 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 finish
[18:52] <seb128> hey
[18:52]  * bcurtiswx_ waves to seb128
[18:52] <seb128> just lurking but don't start translating bugs
[18:52]  * micahg uses Google Translate for foreign bugs and has not been attacked for incorrectness yet
[18:52] <xteejx> I don't mean to burst the bubble, but wouldn't it just be easier to copy/paste from Google translate into LP
[18:52] <seb128> we have bugs over want we can triage and work on
[18:52]  * charlie-tca uses google translate, too
[18:53] <seb128> there is no need to try to get lower quality technically ones adding to that
[18:53] <xteejx> Or better yet...
[18:53] <seb128> especially when you can't ask questions without having a translator
[18:53] <bcurtiswx_> seb128, so in essence asking the reporter to translate will decrease workload drastically ?
[18:53] <devildante> I use it too, but it's not always perfect + by doing this, you make the "not-talking-english" reporters refrain from posting other bugs IMO
[18:54] <xteejx> On 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] <bdmurray> Long 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:55] <micahg> bcurtiswx_: that seems more prone to error
[18:55] <xteejx> Yeah, an "expect badly broken English" message ;)
[18:55] <bcurtiswx_> well the tag would let us know it's not going to eb perfect
[18:55] <xteejx> +1
[18:55] <devildante> advantage of the approach I proposed is that those bugs, rather than in a foreign language, would be triaged and ready for fixing
[18:55] <bdmurray> Its 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] <micahg> bcurtiswx_: the LP bug devs have more important fish to fry IMHO
[18:56] <bcurtiswx_> micahg, sounds fine to me.. just offering suggestions :P
[18:56] <xteejx> On the flip side, that counts most of us English speaking triagers who may be more knowledgable than those in the Loco teams
[18:56] <seb128> why do you want to translate bugs?
[18:56] <seb128> what issues do you try to fix?
[18:56] <seb128> we want less bug in better quality
[18:56] <bdmurray> In 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] <seb128> not extra bugs coming from automatic translations where the submitter will not be able to understand and reply to questions
[18:57] <seb128> if the submitter is not writting english chances are that he's not technical enough to submit a bug anyway
[18:57] <bcurtiswx_> bdmurray, OK.  I see both sides.  It's fair to keep it as is
[18:57] <xteejx> I'm guessing some already use Google to file bugs
[18:57] <devildante> xteejx: we can offer help to those LoCo teams
[18:57] <seb128> users issues should go to the answer tracker
[18:57] <hggdh> +1
[18:57] <micahg> that's the important thing that needs more attention
[18:57] <devildante> seb128: since when we do require bug reporters to have technical knowledge?
[18:57] <xteejx> There's always the -es/-fr/-de IRC channels
[18:57] <seb128> bugs are technical descriptions of issues
[18:58] <hggdh> we do not, and this is a problem, devildante
[18:58] <seb128> "... doesn't work, please help me to solve it" are for the answer tracker
[18:58] <charlie-tca> I was wondering the same thing. Are we going to require the bug reporters to learn to program, too?
[18:58] <xteejx> with those coming from Mac and Windows, this shoul dbe as easy as possible
[18:58] <devildante> the technical descriptions should come from bug triagers, who identify the problem
[18:58] <seb128> oh come on
[18: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] <seb128> we have bugs over want we can triage
[18:58] <seb128> what is the point to make easier to report lower quality bugs
[18:58] <devildante> bcurtiswx_: okay :)
[18:58] <micahg> charlie-tca: simple steps to reproduce and knowing that it's a bug not a how-to is what seb128 is saying I think
[18:58] <seb128> just get users to file their issues on the answer tracker
[18:59] <devildante> later though, I have some work to do
[18:59] <seb128> than you can review the answer trackers and switch those to bugs if you want
[18:59] <bcurtiswx_> #action: devildante to start e-mail thread in mailing list about translations of bug reports
[18:59] <meetingology> ACTION: : devildante to start e-mail thread in mailing list about translations of bug reports
[18:59] <xteejx> Good point
[18:59] <hggdh> I agree with seb128
[18:59] <xteejx> Same
[18:59] <bcurtiswx_> I'm moving on, please continue discussion in the mailing list.
[18:59]  * micahg agrees as well
[19:00]  * devildante will be afk for a while, but agrees about the ML part
[19:00] <micahg> !away > devildanteafk
[19:00] <bcurtiswx_> #topic chair for next meeting November 9th 17:00 UTC
[19:00] <ubot2> devildanteafk, please see my private message
[19:00] <meetingology> TOPIC: chair for next meeting November 9th 17:00 UTC
[19:00] <bcurtiswx_> any volunteers for chairing?
[19:00] <xteejx> I would, but not respected enough lol :)
[19:00]  * hggdh volunteers
[19:01] <micahg> +1
[19:01] <hggdh> xteejx: you *can*
[19:01] <xteejx> No it's ok :)
[19:01] <xteejx> hggdh +1 to chair
[19:01] <hggdh> micahg: you mean you also volunteer?
[19:01] <bcurtiswx_> #action hggdh to chair next meeting
[19:01] <meetingology> ACTION: hggdh to chair next meeting
[19:01] <bcurtiswx_> #endmeeting
[19:01] <charlie-tca> yay for volunteers
[19:01] <meetingology> Meeting ended Tue Oct 12 17:58:58 2010 UTC.  Information about MeetBot at http://wiki.ubuntu.com/AlanBell . (v 0.1.4)
[19:01] <meetingology> Minutes:        http://mootbot.libertus.co.uk/ubuntu-bugs/2010/ubuntu-bugs.2010-10-12-16.57.moin.txt
[19:01] <bcurtiswx_> Thanks for attending
[19:01] <micahg> hggdh: no, I second your nomination :)
[19:01] <bcurtiswx_> the link has the log for today
[19:01] <hggdh> well, I had to try ;-)
[19:01] <xteejx> Damn that's clever
[19:01] <charlie-tca> bcurtiswx: Thanks for chairing. Good job
[19:01] <hggdh> bcurtiswx_: thank you very much
[19:02] <micahg> hggdh: the time doesn't work out that I can guarantee availability
[19:02] <xteejx> Thanks bcurtiswx_ :)
[19:02] <micahg> thanks bcurtiswx
[19:02] <hggdh> micahg: I know, I just did not resist :-)
[19:02] <bcurtiswx_> everyone, yw.  have a great week :)
[19:02] <xteejx> On a lighter note, I know it's aside from triaging, but might make you all smile a little
[19:03] <xteejx> http://www.youtube.com/watch?v=KbkzXiLTk7o
[19:03] <nigelb> xteejx: good work
[19:05] <xteejx> nigelb: Not really, I just heavily edited the audio and used the video from the Examples folder
[19:05] <xteejx> lol
[19:06] <bcurtiswx_> hggdh: for next meeting, you have a whole bunch of action items to get updates on.  They're all listed in the log
[19:06] <hggdh> bcurtiswx_: will do, thank you
[19:20] <bcurtiswx_> how do i do a double indent on the wiki>
[19:23] <bcurtiswx_> got it, nvm
[19:51] <devildante> sorry, micahg :)
[19:52] <jibel> hggdh, 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:53] <hggdh> jibel: np problem, and thank you :-)
[19:53] <jibel> hggdh, thanks to you for presenting the workflow so perfectly :-)
[19:54] <devildante> jibel: I have to say, that workflow is much much better, so thank you both :)
[19:55] <jibel> devildante, thanks, we will see when applying it to real bugs.
[19:57] <nigelb> bug Could not load one of the supported DNS libraries (dnspython or pydns).
[19:57] <nigelb> gah
[19:57] <devildante> lol
[19:57] <nigelb> debian bug 413457
[19:57] <ubot2> Debian bug 413457 in python-xmpp "python-xmpp: DNS warning on import" [Normal,Open] http://bugs.debian.org/413457
[19:58] <nigelb> right, so this is fixed, okay :)
[20:09] <xteejx> wow so many expired bugs are just a load of old crap
[20:09] <devildante> xteejx: that's the idea behind it ;)
[20:09] <xteejx> i.e. no replies to requests for info, getting thru at a good rate :)
[20:10] <xteejx> devildante: lol
[20:13] <njin> can someone triage this https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/657504
[20:13] <ubot2> Launchpad bug 657504 in alsa-driver (Ubuntu) "Sound on the headphones doesn't work (affects: 1) (heat: 8)" [Undecided,Confirmed]
[20:14] <xteejx> I'll take a look
[20:14] <devildante> Shouldn't those bugs be reported against linux?
[20:15] <xteejx> devildante: I was always cautious about sound ones, could be either, more likely alsa
[20:15] <xteejx> njin: 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 done
[20:16] <devildante> xteejx: it was njin (Fabio) who requested that :p
[20:16] <xteejx> lol
[20:17] <njin> can someone triage this https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/655078
[20:17] <ubot2> Launchpad 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] <xteejx> There isn't any apport information in the alsa report...that's the first thing
[20:18] <njin> I think that is a broken module
[20:18] <xteejx> njin: The nvidia problem is a known issue, it's in the release notes
[20:19] <njin> xteejx:thanks, at now i don't have time to do nothing
[20:19] <xteejx> I'll sort it if you want
[20:20] <njin> ok, thanks
[20:20] <njin> xteejx:^^
[20:20] <xteejx> :)
[22:11] <shauno> what's the best way to go about filing a bug when you genuinely have no idea what package is at fault?
[22:14] <devildante> shauno: you can ask us :)
[22:14] <devildante> shauno: what's your bug?
[22:15] <shauno> my touchpad doesn't work, at all, under maverick
[22:17] <devildante> shauno: do an "ls /proc/bus/input/devices" in a terminal, please
[22:18] <devildante> oops, no, forget that
[22:19] <shauno> it's there, with 444 perms
[22:19] <devildante> report it against linux
[22:19] <devildante> developers should know whether it's a kernel or xorg problem
[22:19] <micahg> shauno: https://wiki.ubuntu.com/DebuggingTouchpadDetection
[22:20] <shauno> fairly sure it's X, because click works (so it's using the right device).  just zero movement
[22:20] <micahg> devildante: ^^
[22:20] <devildante> yes, I saw that page
[22:20] <shauno> micahg: looks promising.  just grabbing elinks now :)
[22:20] <devildante> micahg: but the instructions are a little outdated, I think
[22:21] <micahg> devildante: k, that I don't know, if you know what the updates are, feel free to fix
[22:21] <devildante> micahg: "If you do not find a Touchpad in you /proc/bus/inpus/devices, ..." but /proc/bus/input/devices is a file for me
[22:21] <BUGabundo> oias
[22:22] <devildante> micahg, that's the problem, I don't know how to fix that :-/
[22:22] <charlie-tca> heh, too many mentions of Hal, too
[22:23] <shauno> devildante: the touchpad is mentioned in that file
[22:23] <devildante> ah
[22:24] <shauno> http://pastebin.com/pGPbT7Cb
[22:24] <charlie-tca> BUGa_vacations: did they open our channel again yet?
[22:24] <BUGa_vacations> noooooo
[22:24] <BUGa_vacations> :(((
[22:24] <BUGa_vacations> tsimpson: ping ping ping :P
[22:24] <devildante> shauno: oh god, I have the same exact specs :p
[22:25] <charlie-tca> 8 changes for natty today
[22:25] <shauno> hah, mbp3,1 ?
[22:25] <devildante> but my apple trackpad is working
[22:25] <devildante> ah, no, 7,1
[22:25]  * micahg needs to subscribe to natty-changes
[22:25]  * devildante updates his natty now
[22:26] <shauno> this 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 gone
[22:26] <charlie-tca> file the bug using ubuntu-bug linux . someone can change the package if needed, then
[22:27] <devildante> yeah, it's the best way :)