[05:56] <palhmbs> Hey! I've found a bug on a ubuntu website @ https://help.launchpad.net/BlueprintRoadmaps
[05:56] <palhmbs> where do I go to file bugs against it?
[05:56] <palhmbs> their is an invalid link on that page
[05:57] <palhmbs> also, could somebody point me to a blog post / some help, cause I want to create my own blueprint for a crazy cool idea I have.
[06:46] <micahg> palhmbs: you should probably file a question (answer) against the launchpad project on launchpad
[06:48] <palhmbs> thanks - will do, is there any wiki / tutorial / blog on how to write a blueprint that isn't currentl connected to a project?
[06:48] <palhmbs> I'm guessing it just isn't possible...
[06:49] <palhmbs> I'm sorry, probably the wrong place to ask
[07:08] <micahg> palhmbs: launchpad support questions should go in #launchpad, but no, that's not possible at the moment
[07:39] <palhmbs> thanks again micahg - I got the page fixed
[07:39] <palhmbs> they took it down :D
[10:13] <kamel> hi, is it possible to get a nomination of bug 789259 and 789268 for natty. thanks
[10:13] <ubot4> Launchpad bug 789259 in batman-adv-kernelland (Ubuntu) "Please remove batman-adv-kernelland from the Ubuntu archives (FTBFS) (affects: 7) (dups: 6) (heat: 60)" [Undecided,New] https://launchpad.net/bugs/789259
[10:13] <ubot4> Launchpad bug 789268 in batmand (Ubuntu) "Please remove batmand-gateway-(source|dkms) from the Ubuntu archives (FTBFS) (affects: 8) (dups: 9) (heat: 80)" [Undecided,New] https://launchpad.net/bugs/789268
[10:14] <micahg> kamel: we  generally don't remove a package from a stable release without a *really* good reason
[10:15] <kamel> is: it doesnt build and work - and is replaced by a module already in linux-2.6 not a good reason?
[10:16] <micahg> kamel: our kernels are very different
[10:16] <kamel> so different that they included batman-adv.ko earlier than the debian kernel
[10:17] <micahg> kamel: ugh, I shouldn't say very different, but they are not derived from one another
[10:25] <micahg> kamel: if nothing bad happens when people try to use it, there's no reason to remove the stable release
[10:29] <kamel> there are just upset people which don't know what they do, but report bugs about things they don't know but were installed
[10:30] <micahg> kamel: ok, well, the sponsors will review the bugs and take appropriate action, I see you mentioned in the description about natty
[10:49] <xelister> is there any bug making fglrx not work on maverick recently?
[11:41] <xelister> blargh.
[11:46] <benonsoftware> Quick question
[11:47] <benonsoftware> At the top of PChat it says the next meeting is on the 6/9/11 is that the 9th or 6th month?
[11:48] <JoshuaL> benonsoftware, i assume june 9th
[11:48] <jibel> benonsoftware, 2011-06-09
[11:48] <jibel> benonsoftware, 2nd thursday of each month
[11:48] <benonsoftware> Thanks for that.
[11:49] <benonsoftware> I just saw the meeting Wiki page :)
[11:55] <benonsoftware> Is anyone here wanting to mentor someone age 12?
[12:36] <ohsix> christ, can't get ahead; compiz update that just dropped a while ago really messes up drag/snap edges
[16:05] <roadmr> Hi folks! I have a bug that's actually about a feature not implemented in the package, should it be wishlist? (as I don't see any reports or discussion upstream) bug 793831
[16:05] <ubot4> Launchpad bug 793831 in gcalctool (Ubuntu) "3!! is not equal to 720 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/793831
[16:09] <roadmr> I think triaged/wishlist and open a feature request upstream, hopefully I'm not too wrong :)
[16:11] <pedro_> roadmr, that sounds good, please also update the description / title
[16:12] <roadmr> pedro_: OK, i'll do that then, thanks
[16:12] <pedro_> you're welcome, thanks for helping :-)
[16:35] <roadmr> pedro_: coudl I trouble you with the importance (wishlist) for bug 793831? I opened and linked an upstream request, set it to triaged and changed the title to be more descriptive
[16:35] <ubot4> Launchpad bug 793831 in gcalctool (Ubuntu) (and 1 other project) "Feature request: support for double factorial (!!) operator (affects: 1) (heat: 8)" [Undecided,Triaged] https://launchpad.net/bugs/793831
[16:35] <pedro_> roadmr, sure, doing it now
[16:36] <pedro_> roadmr, btw you should be able to change the importance :P
[16:36] <pedro_> your team is part of bug control now
[16:37] <pedro_> btw done
[16:37] <roadmr> thanks!
[17:51] <RedSingularity> chrisccoulson: ping
[17:52] <chrisccoulson> RedSingularity ?
[17:52] <chrisccoulson> you should add some context to your ping btw ;)
[17:53] <RedSingularity> chrisccoulson: yeah i just figured ;)  Anyway, bug 728797 is not update-manager.  Gnome-control-center maybe?
[17:53] <ubot4> Launchpad bug 728797 in update-manager (Ubuntu) "When using "Make Caps Lock an additional Ctrl" keyboard option, doing a dist-upgrade causes caps lock to revert to a caps lock key (affects: 1) (heat: 36)" [Undecided,Confirmed] https://launchpad.net/bugs/728797
[17:53] <RedSingularity> or something more specific you think?
[17:54] <chrisccoulson> RedSingularity, i'm not sure, sorry. i'm probably not the best person to ask ;)
[17:54] <RedSingularity> chrisccoulson: I thought you work the control-center?
[17:54] <chrisccoulson> RedSingularity, not really
[17:55] <RedSingularity> chrisccoulson: my mistake.  Know anyone who does?
[17:55] <RedSingularity> Thats not my area :)
[17:55] <chrisccoulson> hmm, not sure
[17:56] <RedSingularity> chrisccoulson: alright, thanks anyway :)  Will ask around.
[18:21] <micahg> RedSingularity: pedro_ should be able to help you
[18:28] <penalvch> Hey I'd like a 2nd opinion on bug 733128 it looks like a kernel panic on a Release Candidate kernel cause a LibreOffice dataloss and seems invalid due to old kernel... what do you think?
[18:28] <ubot4> Launchpad bug 733128 in libreoffice (Ubuntu) "Libreoffice doesn't start (affects: 3) (heat: 16)" [Medium,Confirmed] https://launchpad.net/bugs/733128
[18:29] <penalvch> old/non-stable kernel
[18:31] <bdmurray> RedSingularity: bug 769751 might be what you are looking for
[18:31] <ubot4> Launchpad bug 769751 in libravatar "Allow images to be marked as private (affects: 1) (heat: 3)" [Wishlist,Triaged] https://launchpad.net/bugs/769751
[18:31] <bdmurray> RedSingularity: bug 769571 might be what you are looking for
[18:31] <ubot4> Launchpad bug 769571 in console-setup (Ubuntu) "updates cause caps lock to revert until a reboot (affects: 2) (dups: 1) (heat: 82)" [Low,Triaged] https://launchpad.net/bugs/769571
[18:31] <bdmurray> or at least that is probably the right package
[18:33] <charlie-tca> penalvch: is the bug still present in final release of natty?
[18:34] <charlie-tca> The user should verify if the bug is still present now.
[18:37] <penalvch> charlie-tca: I don't know if/think  the panic is reproducible in current kernel. I'll request reproduction of the panic w/ current kernel to see if it causes LO dataloss. Thanks for the help!
[18:49] <njin> Hello, are we tracking gallium ?
[18:50] <njin> bug 793834
[18:50] <ubot4> Launchpad bug 793834 in ubuntu "Gallium\r300g doesn't enable 3D acceleration unless S-video output detects a TV. (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/793834
[21:07] <brendand> is it bad form to touch hug day bugs before the hug day ? :)
[21:09] <micahg> brendand: nope
[21:09] <pedro_> brendand, nope :-)
[21:10] <roadmr> as long as you leave a couple for the rest :)
[21:10] <micahg> nope, pedro_ can always add more :)
[21:10] <pedro_> oh yes we have plenty :-)
[21:12] <jpiche> hi. i've been struggling with bug 775950 for a while, and I'm wondering if someone could help me figure out the best way to debug or fix it
[21:12] <ubot4> Launchpad bug 775950 in linux (Ubuntu) "fixing recursive fault but reboot is needed! upon boot (always reproducible on battery only, but sometimes on AC too) (affects: 18) (heat: 92)" [Undecided,Confirmed] https://launchpad.net/bugs/775950
[21:29] <brendand> seems like it should be critical
[21:31] <brendand> jpiche - do you have an ATI card?
[21:33] <jpiche> braiam, yes I do
[21:33] <jpiche> I'm actually the original reporter of the bug
[21:34] <jpiche> brendand, sorry. not braiam.
[21:34] <brendand> jpiche - i know :) i looked at it just now
[21:34] <brendand> jpiche - and you are using fglrx. have you tried with using radeon?
[21:35] <jpiche> brendand, not yet. When I get time, I'll try that next--switching from fglrx to radeon is a bit of a pain
[21:36] <brendand> jpiche - you can just use jockey?
[21:36] <roadmr> how about booting in rescue mode (single), does the problem happen then?
[21:37] <jpiche> roadmr, most of the time it still happens in single. About 1 / 10 reboots, single will work.
[21:40] <jpiche> brendand, jockey doesn't always work for me because I switch secondary monitors all the time and the last time I tried it, my X config got a bit messed up--just annoying though, not a real problem
[21:40] <roadmr> jpiche: no useful logs in /var/log? that might help
[21:42] <jpiche> roadmr, no. I've tried reading through them after plugging in and booting up, but I've never seen anything out of the ordinary
[21:42] <roadmr> jpiche: so, the actual kernel panic log doesn't get written to disk
[21:43] <jpiche> roadmr, that's what it seems like. it happens pretty quick
[21:46] <braiam> Im a bit used to it
[21:47] <braiam> jpiche: ↑
[21:47] <roadmr> hmm. One way to capture a useful log would be via remote syslog, but it's a bit involved to setup, and it'd require an extra pc
[21:48] <roadmr> not sure it would even work, if the kernel can't set up networking before panicking
[21:54] <brendand> jpiche - what's your kernel version?
[21:54] <brendand> probably on the bug
[21:55] <brendand> 2.6.38-8
[21:55] <brendand> that's the original kernel (fresh install)
[21:56] <jpiche> brendand, yeah 2.6.38-8-generic
[21:56] <brendand> my own feeling would be that someone from bug control should set it to critical. at least high
[21:56]  * micahg wonders where jFo is...
[22:06] <komputes> bdmurray: ping
[22:07] <komputes> bdmurray: I was reviewing the BugControl wiki page and found the following line which doesn't seem right:
[22:07] <komputes> One of the team's administrators should e-mail the team's application to ubuntu-bugcontrol AT lists.launchpad.net. Please give us:
[22:07] <hggdh> komputes: that sounds weird
[22:07] <hggdh> no
[22:07] <hggdh> this is correct
[22:07] <micahg> why is that weird, makes sense for team apps
[22:07] <hggdh> :-)
[22:07] <hggdh> komputes: this is for team applications
[22:08] <komputes> It could read easily as, Please email your team application to...
[22:08] <komputes> ...and include:
[22:08] <hggdh> komputes: as long as it is one of the admins, yes
[22:09] <hggdh> komputes: we only want to hear from team admins; I agree it could be better worded, but the restriction must be present
[22:10] <micahg> I think being explicit in this case is better
[22:10] <komputes> ok
[22:15] <RedSingularity> bdmurray: ah yeah, that looks like it...
[22:18] <RedSingularity> bdmurray: great, i will link it to that.  Thanks :)
[22:21] <RedSingularity> micahg: thanks for that info btw.  I wasn't aware he worked that package :/
[22:23] <micahg> RedSingularity: no, he's the defect analyst for the desktop team
[22:23] <RedSingularity> micahg: ahhh, ok
[22:48] <bcj> How do I open a bug on an update to a driver?
[22:48] <bcj> iwlagn was updated yesterday by the Ubuntu 10.04 auto-update tool and it's broken my wireless.
[22:48] <bcj> It looks like the latest driver no longer supports the firmware I have
[22:49] <charlie-tca> ubuntu-bug DRIVER
[22:49] <charlie-tca> and explain in comments that the update for 2011-06-06 broke it
[22:49] <RedSingularity> bcj: may I ask what driver?
[22:49] <bcj> iwlagn
[22:49] <bcj> I think
[22:50] <RedSingularity> ok never mind then :)
[22:50] <bcj> iwlagn 0000:04:00.0: Driver unable to support your firmware API. Driver supports v5, firmware is v0.
[22:50] <RedSingularity> thought it may have been another one....
[22:51] <bcj> I'll try opening a bug
[22:52] <RedSingularity> bcj: yeah follow charlie-tca's advice
[22:52] <bcj> ubuntu-bug DRIVER doesn't work, nor does ubuntu-bug iwlagn
[22:53] <RedSingularity> charlie-tca: ^ maybe it doesnt have the hooks....?
[22:53] <charlie-tca> !info iwlagn
[22:54] <ubot4> charlie-tca: Package iwlagn does not exist in maverick
[22:54] <bcj> ...so how do I find out what to raise the bug against?
[22:54] <bcj> (you can probably tell that I keep knocking the ethernet cable out)
[22:54] <charlie-tca> bcj: ubuntu-bug module-init-tools
[22:55] <charlie-tca> That includes iwlagn
[23:06] <bcj> Thanks for the help all; here is the bug: https://bugs.launchpad.net/ubuntu/+source/module-init-tools/+bug/794291
[23:06] <ubot4> Launchpad bug 794291 in module-init-tools (Ubuntu) "iwlagn driver update breaks compatibilty with firmware (affects: 1) (heat: 6)" [Undecided,New]