[00:09] <james_w> sorry, got pulled away.
[00:10] <james_w> persia: yes, I realise that it's a problem, and may prevent us from doing much, but I think that the patches that are there may be less visible than they should be, and that we may be discouraging people from getting involved, and so helping to alleviate the problem further, with the current approach.
[00:11] <james_w> it's definitely something to discuss further though.
[00:12] <persia> james_w: I completely agree.  There's a few bugs open in LP about it to increase visibility, but there's a good bit left to be done.  It's unfortunate when the developers don't look, and there's not good documentation in the w.u.c/Bugs/ namespace about it.
[00:12] <persia> While https://wiki.ubuntu.com/Bugs/HowToFix used to be good advice, I'm not sure everything is in place to handle it right now
[00:12] <james_w> sure, the latter is an easy one to fix, so we can certainly do that.
[00:12] <james_w> I've got to go to bed.
[00:12] <persia> Good night :)
[00:13] <james_w> grab me tomorrow if you want to chat more about it.
[00:13] <james_w> night all.
[01:26] <blueyed> bdmurray: shouldn't the "kernel-team" get removed? seems like there should be only "ubuntu-kernel-team". See https://launchpad.net/~kernel-team
[03:18] <secretlondon> can someone sanity check my solution to bug #193593 please?
[03:18] <ubotu> Launchpad bug 193593 in audacity "Audacity effects missing" [Undecided,Confirmed] https://launchpad.net/bugs/193593
[03:24] <mrooney> secretlondon: which solution do you mean? the "check for ubuntu's version of soundtouch" seems easy and logical
[03:25] <secretlondon> mrooney yeah
[03:25] <secretlondon> it'll be a patch that will need removing again when we get the later version of the lib
[03:26] <secretlondon> ideally we'd want the later version, but it looks a bit unmaintained in debian as we are stuck with the older version
[03:26] <mrooney> secretlondon: so that will require a patch to build against it, and one to look for the right version? the solution requires those two things?
[03:27] <secretlondon> one solution would be to patch audacity to look for our version of the lib
[03:27] <mrooney> secretlondon: but you would still need to add the flag to compile against libsoundtouch, right?
[03:27] <secretlondon> a better solution would be to update the lib (which I imagine they won't like in feature freeze), or get the lib to give the upstream name, not the name debian chose
[03:28] <secretlondon> but then other apps may use this lib, and rely on it being called X
[03:28] <mrooney> well I would agree upgrading is probably to invasive
[03:29] <mrooney> though I don't understand what makes giving a different name better than looking for a different name
[03:29] <mrooney> *too
[03:29] <secretlondon> yeah, even for an obscure sound stretching library
[03:30] <secretlondon> the problem with making it look for our name is that as soon as libsoundtouch gets upgraded audacity will need to be de-patched
[03:30] <mrooney> secretlondon: ahh I see, well unless you can easily check what would depend on it being called the old name, it seems too late to rename it
[03:31] <mrooney> unless you can somehow have it report two names, or check for either, so that it doesn't need a de-patch somehow
[03:31] <secretlondon> yeah so maybe get audacity to look for *either* name, and 1.3.0+
[03:32] <secretlondon> (they appear to have chosen to look for the latest version as that was what they had in gentoo)
[03:32] <mrooney> secretlondon: yeah, so if it can accept either that seems grand, I think
[03:32] <mrooney> I am hardly an expert in dependency checking though, mind you
[03:33] <secretlondon> I think that's what I'll do
[03:36]  * secretlondon thanks mrooney
[03:40] <mrooney> no problem, glad I could help!
[03:42] <mrooney> secretlondon: in return, if you could just fix bug #63352, that would be great :]
[03:42] <ubotu> Launchpad bug 63352 in linux "Creative labs X-Fi sound card unsupported" [Wishlist,Confirmed] https://launchpad.net/bugs/63352
[03:42] <secretlondon> eek
[03:43] <mrooney> I am kidding of course but, I do have no idea whatsoever how that is only "wishlist"
[03:43] <mrooney> I am not even affected by this bug and it seems Medium at least, if not High
[03:43] <secretlondon> its a kernel thing probably
[03:44] <secretlondon> not a lot we can do here, someone would need to write support
[03:44] <mrooney> yeah, I just don't understand how that makes it less important
[03:44] <mrooney> as far as I am aware difficulty of solving does not factor into importance but I could be wrong?
[03:44] <secretlondon> it doesn't, but in practice ubuntu can't fix it
[03:45] <secretlondon> only upstream can fix it, and then we import the fix
[03:52] <mrooney> secretlondon: so, are you saying you agree a greater importance could be hypothetically due?
[03:52] <greg-g> mrooney: it is only wishlist and not low/medium/high because it is a new feature, as in, it has never worked before
[03:52] <secretlondon> I haven't looked. We have a page on the wiki that explains importances
[03:52] <greg-g> something new, no matter how much it is wanted by the populus, is wishlist
[03:52]  * secretlondon nods
[03:53] <mrooney> greg-g: thanks I see, I guess it just depends on philosophy
[03:53] <greg-g> for bugs like that, we should subscribe the offending manufacturer, in this case, support@creative.com or whatever it would be :)
[03:53] <mrooney> 'functioning sound' isn't new, but support for that card would be
[03:53] <mrooney> it seems sticky
[03:54] <mrooney> greg-g: good idea :)
[03:54] <greg-g> functioning sound depends ENTIRELY on the sound card, so this is a new feature
[03:54]  * greg-g will stop beating a dead horse
[03:54] <mrooney> haha sorry
[03:54] <cody-somerville> Triaged is the desirable state now for most bugs, yes?
[03:54] <mrooney> I am just saying to an average user getting a new computer, it is a regression
[03:54] <greg-g> mrooney: no worries ;)
[03:55] <greg-g> define regression
[03:55] <mrooney> well, appears as one
[03:55] <cody-somerville> (like, when they're ready for developers)
[03:55] <greg-g> regression: something used to work, but now doesn't
[03:55] <mrooney> they are used to having sound in ubuntu, now they don't
[03:55] <secretlondon> regression is $thingey worked in gutsy, doesn't work in hardy
[03:55] <greg-g> "something" in this case would be the sound card
[03:55] <greg-g> right
[03:55] <mrooney> greg-g: I really understand what you are saying and I am not disagreeing, just trying to point out how it can also be viewed from another way
[03:56] <mrooney> hmm okay
[03:56] <mrooney> fair enough
[03:56] <greg-g> cody-somerville: getting a bug to "triaged" is by far the most desirable state to get a bug by a triager
[03:56] <greg-g> mrooney: right right
[03:56] <greg-g> I got ya
[03:58] <greg-g> cody-somerville: do you have a question on what it means for a bug to be set to "triaged"?
[03:59] <cody-somerville> No, I just wanted to ensure I understood the new workflow correctly.
[03:59] <cody-somerville> Although, I suppose a review wouldn
[03:59] <cody-somerville> 't hurt :)
[03:59] <greg-g> well, I'm not much in the lecturing mood right now, but if you have any questions, I'll help out in whatever way I can :)
[04:51]  * greg-g sleep
[06:22]  * secretlondon curses soundtouch, and it's debian packaging
[09:52] <ramvi> I reported a hardy bug a couple of days ago. It's pretty serious so here I am to help out
[09:53] <ramvi> I'm not that skilled, but if you need to ask me questions or anything. Take a look at https://bugs.launchpad.net/ubuntu/+bug/213845
[09:53] <ramvi> It isn't possible to change keyboard layouts
[09:53] <ramvi> X hangs
[09:54] <secretlondon> bug #213845
[09:54] <ubotu> Launchpad bug 213845 in ubuntu "Computer brought to complete halt when changing keyboard layouts using fglrx" [Undecided,New] https://launchpad.net/bugs/213845
[09:56] <secretlondon> why do you think it is connected to the graphics driver?
[09:56] <secretlondon> also bugs against "ubuntu" itself often get ignored
[09:56] <ramvi> No. fglrx brings the computer to a complete halt while other drivers just restars x
[09:56] <secretlondon> this is ppc?
[09:57] <ramvi> the fglrx bug is already submitted, logging in and out halts the computer
[09:57] <ramvi> intel
[09:57] <ramvi> just change the heading. removed fglrx
[09:58] <secretlondon> we need a lot more information - you running gnome?
[09:58] <ramvi> Yup
[09:59] <ramvi> Problem 1: Making a change in gnome-keyboard-properties restarts X
[10:00] <ramvi> Problem 2: If I manage to make changes they are "forgotten" / screwed up after a restart of X
[10:00] <ramvi> Probably connected in some way..
[10:01] <secretlondon> ramvi: well if X is crashing then it's highly likely it isn't writing to the config file - it's the same issue
[10:02] <ramvi> Right
[10:10] <ramvi> ﻿secretlondon, still there? It seems to be connected to fglrx in some way. Now I'm using radeonhd and I was able to change the layouts. They were all screwed up after a reboot though. But I can makes changes - something I cant do while using the fglrx driver
[10:11] <secretlondon> I've added a comment to the bug, we need some log files
[10:11] <ramvi> I'll fix that staight away]
[10:13] <secretlondon> you don't say what you actually mean by "complete halt"
[10:13] <secretlondon> i'll add it to the bug
[10:16] <ramvi> I have to do a hard reboot
[10:16] <ramvi> black screen. Nothings works. Dont know if REISUB works cause I dont have a print screen button
[10:17] <secretlondon> please add that to the bug
[10:18] <ramvi> All done
[10:19] <ramvi> I'm going to check the caps lock thing. brb
[12:02] <Iulian> Heya
[13:10] <pedro_> morning bugsquaders!
[13:10] <pedro_> remember that today is the compiz hug day
[13:10] <pedro_> https://wiki.ubuntu.com/UbuntuBugDay/20080410
[13:10] <Iulian> Hello pedro!
[13:10] <Iulian> Happy hug day!
[13:11] <pedro_> feel free to grab any bug of the list and squash it  hard enough :-P
[13:11] <pedro_> heey Iulian! to you too
[13:11] <pedro_> Iulian: are you doing 5-a-day ?
[13:11] <pedro_> dholbach added a new feature to 5-a-day to tag your work
[13:12] <pedro_> I've put some brief instructions on how to do it for todays hug day
[13:12] <pedro_> https://wiki.ubuntu.com/UbuntuBugDay/20080410#head-6503c137a79e423b033c6e453d243467a6fcd2de
[13:13] <Iulian> pedro_: Nop, I was thinking to start to use it but I forget all the time.
[13:13] <Iulian> pedro_: Yea, I noticed :)
[13:13] <Iulian> Ah
[13:15] <Iulian> How are you today?
[13:17] <pedro_> Iulian: I'm good, enjoying the hug day ;-), how about you?
[13:22] <Iulian> pedro_: I just got home from a really funny meeting. I am doing good too, thanks. ;)
[13:33] <sourcercito> happy hug day!
[13:33] <Iulian> Happy hug day to you too, sourcercito!
[13:34] <sourcercito> i see you already start to squash some bugs ;)
[13:34] <sourcercito> nothing like the smell of fresh bugs in the morning
[13:34] <sourcercito> hehehe
[13:34] <Iulian> Whooahh!
[13:34] <Iulian> $true
[13:34] <Iulian> :-)
[13:40] <ramvi> How can I help solve bug #215089? This should really be fixed before hardy release. I've even posted the fix
[13:40] <ubotu> Launchpad bug 215089 in alsa-driver "Crackling Sound on the left Channel on Macbook Pro" [Undecided,New] https://launchpad.net/bugs/215089
[13:42] <ramvi> Should I post something?
[13:42] <james_w> ramvi: I'm not sure the fix that you posted can be applied.
[13:42] <ramvi> I have applied it
[13:42] <james_w> how?
[13:43] <james_w> you edited /etc/modprobe.d/options?
[13:43] <james_w> hi secretlondon
[13:43] <secretlondon> hi james_w
[13:43] <james_w> is 5-a-day working for you again?
[13:43] <ramvi> Don't remember what I did, over half a year ago, but I edited some file and added something
[13:43] <ramvi> Hi secretlondon and james_w
[13:43] <secretlondon> james_w i've not looked, but I doubt it
[13:44] <ramvi> Is there a group for posting 5 bugs a day_
[13:44] <james_w> yeah, the fix in the wiki can't be applied by Ubuntu, as what value should go in there?
[13:44] <james_w> ramvi: it's a group for triaging a few bugs every day.
[13:44] <secretlondon> ramvi: no triaging, but I seem to have posted 5 today..
[13:44] <ramvi> :)
[13:44] <james_w> if you put macbook in there it will not work for people with macminis
[13:45] <james_w> the real fix is to have the module not need to know what type of mac you are on.
[13:45] <ramvi> Right. you fix? :p
[13:45] <ramvi> Can I help out in any way?
[13:46] <james_w> I don't know what the module does with this information
[13:46] <james_w> I also don't know if there is anyway it could detect it.
[13:46] <ramvi> I have no idea
[13:46] <james_w> also, talking to upstream, or at least googling for some discussion upstream would be a help.
[13:48] <ramvi> I dont know what that means
[13:50] <james_w> I'm assuming that the requirement to specify the type of mac has been discussed with the alsa developers before.
[13:50] <james_w> so searching for those discussions and posting links to the bug report would be useful
[13:50] <james_w> and if there is no discussion then starting it would also be useful.
[13:51] <ramvi> right, ok. Thanks
[13:52] <mrooney> happy hug day!
[13:52] <joumetal> Bug 213973 is fixed. I think it was duplicate of Bug 213566. But what to do to bug 213986.
[13:52] <ubotu> Launchpad bug 213973 in ubuntu "Wrong keyboard layout after LTS upgrade" [Undecided,New] https://launchpad.net/bugs/213973
[13:52] <ubotu> Launchpad bug 213566 in xkeyboard-config "dapper->hardy missing files on upgrade" [High,Fix released] https://launchpad.net/bugs/213566
[13:52] <ubotu> Launchpad bug 213986 in ubuntu "Ubuntu 804 french keyboard (dup-of: 213973)" [Undecided,New] https://launchpad.net/bugs/213986
[13:55] <mrooney> do some ubuntu updates actually not have posted changes for awhile? like in Update Manager when it says "The list of changes is not available yet.", is there actually nowhere I can find out what happened?
[13:56] <mrooney> if I go to that package in Hardy and click changelog there is a 404, is that what update manager looks for too?
[13:56] <james_w> I'm not sure
[13:56] <james_w> https://launchpad.net/ubuntu/+source/<source package name> may have the information you want.
[13:57] <Pici> I always use aptitude with apt-listchanges installed.
[14:22] <afflux> morning
[14:23] <pedro_> morning afflux
[14:23] <pedro_> are you ready to squash some bugs ? :-)
[14:23] <afflux> yay
[14:23] <prana> happy bug day
[14:23] <pedro_> today is compiz hug day https://wiki.ubuntu.com/UbuntuBugDay/20080410
[14:23] <pedro_> prana: to you too!
[14:25] <Polo> hi, i'm new here, so what can I do ?
[14:26] <prana> i need a little help closing out bug 213308: it looks like there's a certain WD HD configuration that is not recognized by the -14 and -15 kernels that causes boot to fail, but there's a hardware workaround.  Should that regression be fixed?
[14:26] <ubotu> Launchpad bug 213308 in linux "Update from 2.6.24-12 to -14 or -15 results in ata SRST failed (errno=-16)" [Undecided,Incomplete] https://launchpad.net/bugs/213308
[14:26] <james_w> Polo: welcome
[14:26] <james_w> today is a Hug Day, so you could help out with triaging the bugs listed at https://wiki.ubuntu.com/UbuntuBugDay/20080410
[14:26] <Polo> ok
[14:26] <james_w> feel free to ask here if you need any advice on anything.
[14:27] <prana> if you haven't looked at the bug before, it has some non-related comments so just read the stuff from me and the original reporter.
[14:28] <prana> i could mark it confirmed and assign it to the kernel team, let them sort it out?
[14:31] <james_w> prana: I'm not sure what to do there.
[14:32] <afflux> uh
[14:33] <afflux> the first two bugs I just checked were a.) already touched and b.) in the latest package in hardy, and someone set it to incomplete with "does it still exist?"
[14:33] <afflux> I don't believe this is the correct behaviour for crashreports in current hardy packages.
[14:35] <afflux> btw. I'm starting a bughelper run on moveInitiate (most crashers with updateWindowAttributes), I see a lot of them in the list.
[14:37] <Polo> I'm looking bug 147230, and for me it's not a bug, and I can use easily my touchpad to switch workspace.
[14:37] <ubotu> Launchpad bug 147230 in compiz "Workspace switching via touchpad works badly" [Wishlist,New] https://launchpad.net/bugs/147230
[14:37] <Polo> should I close the bug ?
[14:37] <prana> james_w: the  kernel triage helper for thursday isn't online unfortunately.
[14:37] <james_w> prana: for thursday?
[14:37] <jeromeg> Polo: it's not because it works for you that it works for everybody
[14:37] <james_w> they have a nominated person for each day?
[14:38] <afflux> Polo: no, rather ask for testing in hardy heron. There is a useful stock reply on https://wiki.ubuntu.com/Bugs/Responses, I think under the section "needs testing in a developement release"
[14:39] <james_w> It might also be an input bug rather than a compiz one.
[14:48] <prana> james_w: yes https://wiki.ubuntu.com/KernelTeamBugPolicies see triage days
[14:50] <james_w> prana: thanks, I didn't know that
[14:50] <james_w> prana: you could try -kernel
[14:50] <prana> james_w: oh, good idea, thx.
[14:52] <james_w> Does anyone have an audigy2 sound card?
[14:58] <thekorn> wow, it's hug-day!
[14:58] <thekorn> hi all :)
[15:00] <afflux> hi thekorn
[15:00] <thekorn> can somebody please stop sourcercito ;)
[15:00] <thekorn> hey afflux
[15:01] <afflux> aaaaaaaargh
[15:01] <afflux> someone is triaging the same bugs that I do
[15:02] <afflux> oh. It was apport's fault ;)
[15:03] <Iulian> thekorn: That's impossible. :)
[15:03] <afflux> bug 206866
[15:03] <ubotu> Launchpad bug 206866 in compiz "compiz.real crashed with SIGSEGV in updateWindowAttributes()" [Medium,Confirmed] https://launchpad.net/bugs/206866
[15:03] <afflux> nevermind, just need the short url
[15:22] <qense> hello
[15:23] <afflux> morning qense, happy compiz hug day :)
[15:23] <qense> thx, you too :)
[15:34] <pedro_> haha nice detail
[15:35] <pedro_> triager "Apport :-)"
[15:35] <afflux> that was me
[15:36] <afflux> apport seems to have marked some bugs as duplicates after the list was created, and I thought it would be best to show who triaged them ;)
[15:37] <afflux> also I hope it's okay I added myself as the triager for two bugs because I did some duplicate checking and moving to them after sourcercito triaged them
[15:37] <sourcercito> afflux, mark them as your, since you did a more extensive check of those bugs ;)
[15:38] <sourcercito> s/your/yours/g
[15:38] <pedro_> yeah is ok, mark it as yours
[15:38] <afflux> okay, as you wish ;)
[15:42] <afflux> wow. Changing the "window menu" binding in ccsm ("general options") to "disabled" has severe consequences: simple left click does not work anymore.
[15:42] <afflux> either alt+click or win+click was a "normal" click after that change
[15:43] <afflux> changing it back to "alt+mouse3" reverted the behavior back to normal
[15:43] <afflux> (this is one issue explained in bug 207065)
[15:43] <ubotu> Launchpad bug 207065 in compiz "Bad Compiz Bindings Bug" [Undecided,New] https://launchpad.net/bugs/207065
[16:05] <afflux> *note to myself: check patches added in the debian package which are not from upstream, before forwarding bugs to upstream.
[16:18] <afflux> should I mark bug 209216 as wontfix?
[16:19] <ubotu> Launchpad bug 209216 in compiz "Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered" [Low,New] https://launchpad.net/bugs/209216
[16:22] <pedro_> afflux: better ask mvo about it
[16:22] <pedro_> ahoj andre
[16:22] <andre> hola pedro
[16:23] <afflux> pedro_: okay, will do in a minute, when he finished my other question :P
[17:52] <mvo> afflux: I think it should be reproted upstream, priority low (mostly cosmetic)
[17:55] <bdmurray> Hello, I just ran into a bug report that seemed like it really belonged at the idea tracker - http://brainstorm.ubuntu.com.  I was wondering if anyone else has seen bugs like that?
[18:04] <bdmurray> ogasawara: Has the cx88 driver changed recently?  I'm looking at bug 215144
[18:04] <ubotu> Launchpad bug 215144 in linux "2.6.24-15 boot failure due to cx88_alsa driver" [High,Triaged] https://launchpad.net/bugs/215144
[18:04] <ogasawara> bdmurray: that's probably a dup, just a sec
[18:05] <ogasawara> bdmurray: yup, see 212100
[18:05] <ogasawara> bdmurray: rtg pulled in patches already to fix it
[18:05] <bdmurray> bug 212100
[18:05] <ubotu> Launchpad bug 212100 in linux-ubuntu-modules-2.6.24 "Kernel Oops: NULL pointer dereference caused by hald" [High,Triaged] https://launchpad.net/bugs/212100
[18:06] <ogasawara> bdmurray: bug 212960 has the patch
[18:06] <ubotu> Launchpad bug 212960 in linux-ubuntu-modules-2.6.24 "Hardy: cx88 NULL pointer dereference" [High,Fix committed] https://launchpad.net/bugs/212960
[18:07] <james_w> bdmurray: I've probably seen one or two
[18:07] <bdmurray> ogasawara: Okay, I'll dup it thanks
[18:08] <bdmurray> james_w: okay, I was wondering if adding a standard response would be worthwhile
[18:08] <james_w> it's probably good to have it on there in anticipation
[18:12] <warren_> bug 153493
[18:12] <ubotu> Launchpad bug 153493 in bzr "status gives false positives for text files with CRLF (@win32)" [Critical,Fix released] https://launchpad.net/bugs/153493
[18:12] <warren_> wrong :p
[18:13] <warren_> bug 153943 , can someone look if he/she has the same problem?
[18:13] <ubotu> Launchpad bug 153943 in gdebi "Gdebi-kde uses massive amounts of memory!" [High,Confirmed] https://launchpad.net/bugs/153943
[18:13] <bdmurray> ogasawara: is the alsa-driver task in bug 212960 valid?
[18:13] <ubotu> Launchpad bug 212960 in linux-ubuntu-modules-2.6.24 "Hardy: cx88 NULL pointer dereference" [High,Fix committed] https://launchpad.net/bugs/212960
[18:14] <ogasawara> bdmurray: I believe so as it don't think it's been committed upstream yet
[18:15] <bdmurray> ah, okay
[18:16] <qense> hello
[18:16] <james_w> hi qense
[18:30] <greg-g> so, "add-5-a-day 123456" is now "5-a-day --add 123456" ??
[18:31] <qense> yes
[18:32] <greg-g> shall I update the wiki page then?
[18:32] <qense> I think that would be the best :)
[18:32] <greg-g> :)
[19:07] <james_w> hi all, I've never actually reported a bug with apport, can someone give me a good answer for the last comment of https://bugs.launchpad.net/bugs/210226 please?
[19:07] <ubotu> Launchpad bug 210226 in gnome-settings-daemon "gnome-settings-daemon crashed with SIGSEGV in rw_screen_list_outputs()" [Medium,Fix released]
[19:07] <james_w> is it possible to tell apport an existing bug report, or will it just have filed a new one for him
[19:08] <bdmurray> james_w: /var/crash
[19:08] <bdmurray> In nautilus you can double click on the crash file and apport will launch the reporting wizard
[19:08] <james_w> it sounds like he at least tried to report it.
[19:09] <james_w> I'll ask him for more information about what he did.
[19:14] <greg-g> james_w: it will create a new bug report
[19:15] <james_w> thanks.
[20:09] <Upayavira> Does a compiz bug day also cover XGL? I upgraded to Hardy a couple of days ago, and it is now refusing to start up X with XGL.
[21:20] <pmartren> So, what is left to do in this hug day ?
[21:24] <bdmurray> pmartren: there are a few bugs that are still in the New status
[21:36] <mario_limonciell> bdmurray, ping
[21:36] <bdmurray> mario_limonciell: hello
[21:36] <mario_limonciell> hi bdmurray.  I was here at LF and the intel guys were showing off kerneloops.  you've heard of it?
[21:37] <bdmurray> No, I haven't.  You were there or are there?
[21:38] <mario_limonciell> i am here
[21:38] <mario_limonciell> its a daemon that runs and greps your logs in /var/log
[21:38] <mario_limonciell> for oops's
[21:39] <mario_limonciell> and offers to submit them to kerneloops.org
[21:39] <mario_limonciell> F9 has implemented it
[21:39] <bdmurray> oh, I think ogasawara mentioned that site
[21:39] <mario_limonciell> yeah, well it's in debian and builds cleanly in Ubuntu...
[21:40] <mario_limonciell> so if you think it'd be useful to file an FFe to get it included very last minute i think it seems like a very good tool to bring in
[21:43] <bdmurray> You said its a daemon?
[21:43] <mario_limonciell> yes
[21:43] <mario_limonciell> it then gives you a pop up via dbus/hal
[21:43] <mario_limonciell> saying 'hey you crashed, want to submit it to kerneloops.org'?
[21:44] <mario_limonciell> (well more politely worded)
[21:44] <bdmurray> I wonder if there is some way we could get oops out of LP for the site too
[21:44] <mario_limonciell> the intel rep said that he has also used it to get oops out of mailing lists
[21:45] <mario_limonciell> so i would say that's very probable
[21:45] <bdmurray> Which repo did you have in mind?
[21:46] <mario_limonciell> well it would do the most benefit in main by default, but i'm thinking it's really late for that
[21:46] <mario_limonciell> so universe would have to suffice, with recommendations to install it if you are getting errors
[21:47] <bdmurray> right
[21:48] <mario_limonciell> but you agree it's worthwhile to file an FFe to try to pull it through for hardy?
[21:51] <bdmurray> Do you know if there is a way to search for specific kernel versions at that site?
[21:52] <mario_limonciell> i dont know for sure
[21:52] <mario_limonciell> it would appear that its 2.6.x and that's the only thing listed
[21:53] <mario_limonciell> oh nvm
[21:53] <mario_limonciell> yeah it shows
[21:53] <mario_limonciell> example: http://kerneloops.org/guilty.php?guilty=set_dentry_child_flags&version=2.6.24-release&start=1605632&end=1638399&class=warn
[21:53] <mario_limonciell> they are just organized by the bug reported rather than the kernel
[22:00] <bdmurray> mario_limonciell: I'm not certain how Hardy would benefit from it.
[22:01] <bdmurray> but I do think it would be useful and interesting
[22:02] <mario_limonciell> well as oops reports are submitted, it would be more beneficial to upstream seemingly
[22:02] <mario_limonciell> so as to fix for future kernels
[22:02] <bdmurray> right, and since Hardy is at 2.6.24 and upstream is at 2.6.25 it seems it would be best if we had right when Intrepid comes out
[22:03] <mario_limonciell> well at any time we will always be lagging behind the upstream kernel
[22:05] <bdmurray> True, my thought was that it would be most useful when we were less behind though.
[22:06] <mario_limonciell> ah like during interpid development
[22:07] <bdmurray> Right!
[22:07] <mario_limonciell> okay then i won't try very hard to get it added in now
[22:08] <bdmurray> I think it would be a good thing to have though just maybe not worth a FFe now.
[22:09] <mario_limonciell> ok
[22:13] <afflux> going to bed now, good night!
[22:25] <Nafallo> https://bugs.edge.launchpad.net/ubuntu/+source/f-spot/+bug/210928
[22:25] <ubotu> Launchpad bug 210928 in f-spot "f-spot.exe crashed with SIGSEGV on exit" [Undecided,Invalid]
[22:25] <Nafallo> why is that invalid if it is a duplicate?
[22:35] <bdmurray> perhaps because it has already been reported?
[22:47] <sbarjola> hi all, is there some wiki about debugging debian-installer bugs?
[22:48] <bdmurray> sbarjola: not really what are you curious about?
[22:51] <sbarjola> how to see logs if crash?
[22:53] <bdmurray> sbarjola: ubiquity is a gui front end for debian installer so the same log files, /var/log/syslog and /var/log/partman , should be looked at
[22:55] <sbarjola> oh, should be know it.. thanks
[22:58] <jjesse> intersting i have several times been unable to commit a bug in add-5-a-day due to it telling me it has been already committed 4 minutes ago when I just type it in the first time
[23:14] <mrooney> is there any way to edit your own comment on a bug?
[23:14] <bdmurray> mrooney: no only the description can be edited
[23:14] <mrooney> I said should when I should have said should not and it is very upsetting because it conveys the exact opposite of an important point I was trying to make
[23:14] <mrooney> that will teach me to proof-read I guess :)
[23:15] <bdmurray> You can add another comment then. ;)