[00:02] <hggdh> we will get there
[01:18] <nullack> Is anybody else running tselliots new nvidia 177.70 driver OK on Intrepid? Im finding X isnt happy with it
[04:00] <bcurtiswx> question, i marked a bug as incomplete and at the same time asked the bug creator if the problem was still existing (a really old bug).  If they don't reply in a week am i allowed to set as invalid or does it really matter?
[04:17] <philwyett> Yes you are allowed to close it. Be brave :-)
[04:18] <bcurtiswx> another one.. if a user says they don't experience the bug anymore.. does that mean its invalid or fix released?
[04:20] <bcurtiswx> or once again... does it matter? :D
[04:20] <philwyett> Can be either. However if it was fixed in the next release go with 'Fix released'. If they are on same version and it vanished it can be a toss up. I usually go with invalid.
[04:21] <bcurtiswx> thx
[04:21] <philwyett> Users are like eye witnesses - Very unreliable! :-D
[04:44] <Awsoonn> Hi guyz, I upgrades my system to intrepid today, as expected it exploded
[04:44] <Awsoonn> I'm starting on the first broken thing, the nvidia driver for the latest kernel, are there any known issues?
[04:46] <philwyett> Many known issues. :-)
[04:47] <philwyett> I would wait for alpha 5. Alpha 4 + updates is a bit of a nightmare at the minute. And we know a new kernel bump is coming from .26 to .27.
[05:25] <bcurtiswx> im a triager, and i need some help with what to do.. anyone around to help?
[05:30] <philwyett> Sup bcurtiswx?
[05:31] <bcurtiswx> bug 212662
[05:31] <bcurtiswx> what do i do next?
[05:31] <philwyett> Let me look
[05:32] <philwyett> bcurtiswx: Ask them to see if this happens under intrepid alpha 4 plus updates.
[05:33] <bcurtiswx> but they are using hardy
[05:34] <philwyett> Empathy is very alpha software even under intrepid and for hardy it is there but IMO should not be in the repo.
[05:34] <philwyett> Anything empathy related under the SRU for an LTS s not likely to get fixed.
[05:35] <philwyett> Empathy as default I believe is now on hold fr intrepid and will not be included until intrepid+1.
[05:35] <philwyett> s/fr/for
[05:36] <bcurtiswx> its a pidgin libpurple one according to sebastian bacher
[05:38] <philwyett> It accessing libpurple, but it's not a complete trace. If you are not a coder, I would skip that bug.
[05:38] <bcurtiswx> ok
[05:38] <bcurtiswx> ty
[10:50] <ph8> im gay
[10:59] <amireldor> ph8 ?
[15:00] <knorr> wgrant: Is it you from bug 262292 ?
[15:00] <wgrant> knorr: This is me.
[15:01] <knorr> wgrant: Jesper Larsen here. I need a little help understanding the status
[15:01] <wgrant> knorr: "Fix Committed" means that a fix has been committed to the repository.
[15:01] <wgrant> Bugs in that state will normally be ignored, because nothing further really needs to be done.
[15:02] <wgrant> In general, don't twiddle the state past Confirmed unless you really know what you're doing.
[15:02] <knorr> wgrant: In the wiki: For a bug task about an upstream project: the fix is in CVS/SVN/bzr or committed to some place
[15:02] <wgrant> That bug task is not about an upstream project.
[15:02] <wgrant> It's about a distribution source package.
[15:02] <knorr> Ah okay.
[15:03] <knorr> I see. Cheers. Just trying to learn here. ;)
[15:03] <wgrant> Sure, always good.
[15:03] <wgrant> Now to restart X to try to get the Synaptics driver working properly with input properties.
[15:30] <Rocket2DMn> can somebody please look at bug 179918 and tell me if more information is needed to mark it as Triaged?  I don't know enough about codecs.
[16:19] <Ampelbein> hi! could some member of bug-control please have a look at bug #261370 ? I think it can be set to status triaged/low importance. Thanks.
[17:49] <Awsoonn_> Ampelbein: *thumbs up*
[17:51] <Ampelbein> Awsoonn: Thanks.
[21:08] <Turl> hi
[21:09] <Turl> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473396
[21:10] <Turl> what does Julien mean there with arranging sponsorship?
[21:13] <knorr1> Turl: He needs a sponsor to get the description in the trunk. A sponsor is a user from a group that validate work of under-priviliged contributers.
[21:14] <Turl> oh
[21:14] <Turl> so it'll be included soon?
[21:17] <knorr1> Turl: I can't really know. He doesn't have the "power" to do it himself. So it depends when a sponsor sees it and confirms it.
[21:18] <Turl> MOTUs are the sponsors? or they are two different things?
[21:42] <knorr1> I've added a patch for bug 263082. Do I subscribe ubuntu-universe-sponsor?
[21:43] <hggdh> knorr1, you should mark the attachment as a patch
[21:44] <knorr1> hggdh: Of course... ;)
[21:44] <hggdh> :-)
[21:44] <hggdh> for Intrepid this is in main
[21:44] <knorr1> hggdh: Okay. Should I subscribe ubuntu-main-sponsor then?
[21:45] <hggdh> I guess so, knorr1
[21:45] <hggdh> Knorr, BTW, thank you for helping ;-)
[21:47] <Knorr> hggdh: No worries. Still a bit confusing, but it's getting better.
[21:48] <hggdh> Knorr, we are trying to update all docs dealing with bug triaging
[21:48] <hggdh> hopefully, it will get less confusing as we get through it
[21:49] <Knorr> hggdh: Nice. Don't know if the material it self is too bad. It's just presented quite bad. Spread out on many different topics and such
[21:49] <Knorr> BTW, should I change the status to something else than Confirmed?
[21:51] <hggdh> Knorr, we can set it to Triaged
[21:51] <hggdh> can you do it, or should I do it?
[21:52] <Knorr> I don't have the power...
[21:52] <hggdh> k, hold on
[21:53] <hggdh> Knorr, done
[21:56] <Knorr> Cheers