[00:27] <chrisccoulson> greg-g - i uploaded f-spot to my ppa
[00:46] <greg-g> chrisccoulson: and of course I'm running amd64 :)
[00:47] <chrisccoulson> yeah, i've no idea why thats failed. it builds fine at home, and I'm running it ok
[00:47] <chrisccoulson> i sent an e-mail to lp-users
[00:47] <chrisccoulson> if you download the diff.gz, then you could probably build it locally
[00:47] <greg-g> oh right, of course
[00:47] <greg-g> I'll do that later, working on homework now
[00:48] <chrisccoulson> no problem"!
[00:48] <bdmurray> clearly ;)
[00:48] <chrisccoulson> lol
[00:48] <greg-g> hey now!
[00:48] <greg-g> ;)
[00:52] <chrisccoulson> wow, tracker's memory footprint has grown a bit in intrepid hasn't it?
[00:52] <chrisccoulson> 128.6MB on my machine! i think it must be leaking
[02:03] <mrooney> Is anyone following the fun in bug 276594?
[02:03] <mrooney> other than wgrant of course
[02:03] <Hobbsee> green?
[02:04]  * Hobbsee loads it
[02:05] <mrooney> there is indeed green
[02:05] <mrooney> and purple
[02:05] <mrooney> but moreso it is just a lot of people complaining that they hate the background and wondering where their promised new theme is
[02:05] <Hobbsee> mrooney: can you comment on the bug and say it's being changed, and perhaps change the title too?
[02:07] <mrooney> Hobbsee: sure, so it is being changed? is there any useful link that I might reference
[02:08] <LiquidRain> Hey guys, hope this is the right place. Bit of a wall of text inbound.
[02:08] <LiquidRain>  I'm having vsync issues on movies (gxine, vlc, totem - with X11 or OpenGL output) with a Thinkpad X60s laptop with an Intel 945G regardless of input format.  Anyone have any help available for that? (searched google, forums, wiki, tried editing xorg.conf) I'm at wits end with this. :)
[02:09] <Hobbsee> mrooney: kwwii said yesterday in #ubuntu-devel that it would be.  You could use the logs from that, if you liked.
[02:09] <mrooney> Hobbsee: thanks!
[02:09] <Hobbsee> mrooney: you're welcome!
[02:10] <mrooney> LiquidRain: hmm, I can think of anything I would do other than google "ubuntu vsync", which you surely have done
[02:11] <LiquidRain> yeah I've tried example xorg.confs that others have posted.
[02:19] <LiquidRain> nothing seems to be getting vsync which is terribly frustrating.  I know this is a really bad graphics processor, but.. :/
[02:21] <mrooney> LiquidRain: Have you filed a bug? That might help get the right people to notice
[02:21] <mrooney> also there might be a channel for video type stuff
[02:22] <LiquidRain> I'd like somebody to help me narrow it down before I file a bug. (I dislike filing bugs unless there's a clear cause and test case)
[02:29] <mrooney> LiquidRain: there are many unlike you in that regard :)
[02:29] <mrooney> and we are pretty good at sorting bugs out, but hopefully someone here can point out at least what package it would be
[02:29] <Hobbsee> LiquidRain: so it's only movie players?
[02:30] <Hobbsee> LiquidRain: and does it happen on both the gstreamer engine and the xine engine?
[02:30] <LiquidRain> It's everything, actually.  Gens (Genesis emulator) and Compiz also tear.
[02:30] <Hobbsee> ah
[02:30]  * Hobbsee guesses filing against xorg, then.
[02:31] <Hobbsee> they'll be able to give you a list of what they want - although i think there's a wiki page on taht
[02:33] <LiquidRain> and trying to disable glx to see if I can just get it working with DRI is not working - something is overriding my xorg.conf
[02:36] <Hobbsee> i'm not sure how much xorg.conf gets used anymore :-S
[02:37] <LiquidRain> barely, it seems.  not that I'm complaining about that, as long as I know where else things get configured from.
[02:39] <Hobbsee> i'm not sure.  ask in #ubuntu-x in a few hours - they're the X overlords.
[02:40] <LiquidRain> hmm that'll have to be tomorrow then.  OK.  Thanks.
[02:40] <mrooney> Does anyone know if Compiz 0.7.8 is planned to make it into Intrepid?
[02:40] <Hobbsee> but i would file the bug with the stuff you have so far, so they can use it as a reference point, and mention it when you talk to them.
[02:41] <Hobbsee> mrooney: no idea.  unlikely, i guess, as mvo's on leave.  is there a bug about it?
[02:42] <Hobbsee> ahh, people have already reported the bugs i keep seeing.
[02:43] <Hobbsee> https://bugs.launchpad.net/ubuntu/+source/xine-ui/+bug/231507 is kinda annoying.
[02:44] <mrooney> Hobbsee: not that I know of, just wondering
[02:44] <mrooney> mvo never responds to any of my emails :[
[02:44] <mrooney> well, he did once.
[02:45] <Hobbsee> hmm.  no bug.  wonder if he even knows yet.
[02:46] <mrooney> Hobbsee: well I found out from his blog http://mvogt.wordpress.com/2008/09/24/compizcompiz-fusion-078-availale/ :)
[02:47] <Hobbsee> mrooney: oh :)  i've not looked at planet
[03:46] <mrooney> Hobbsee: is there a better title you would prefer for bug 276594?
[03:46] <mrooney> I've added an explanatory comment and the status seems good, but you mentioned a new title and I am not sure what might be better
[03:55] <Hobbsee> mrooney: not sure.  Something people would actually read.  [In Progress] at the front of it or something.
[04:00] <Hobbsee> mrooney: or say
[04:01] <mrooney> there I updated the title and added an update in the description, that should be good I think!
[04:01] <Hobbsee> mrooney: edited :)
[04:01] <Hobbsee> hm, i think we got it at the same time
[04:02] <Hobbsee> i just thought of saying it was temporary
[04:03] <mrooney> I better not even give it an importance
[04:03]  * Hobbsee shrugs
[04:03] <mrooney> anything short of Critical will cause backlash
[04:03] <Hobbsee> it'd probably get a critical one
[04:03] <mrooney> haha
[04:03] <Hobbsee> that's what i was thinking
[04:03] <Hobbsee> you could mark it low, just to piss people off :P
[04:03] <mrooney> Wishlist :)
[04:03] <mrooney> deferred for Jaunty+1
[04:03] <Hobbsee> that too!
[04:04] <mrooney> WontFix
[04:04] <Hobbsee> haha, yes :)
[04:05] <mrooney> and that's why BugControl requires applications :)
[04:07] <persia> If there's not already, it  may be worth filing a bug against malone : it seems like a UI failure to have to put the bug status duplicate in the title.
[04:09] <mrooney> persia: do you mean it should be more obvious on Launchpad?
[04:14] <persia> mrooney, Indeed : if there's a need to add it to the title, then it ought to be shown differently : as soon as that bug gets closed, the title will be wrong.
[04:15] <mrooney> but someone like myself will change the title
[04:16] <mrooney> persia: I think it is just a tiny case of bugs where you have upset, impatient users who aren't going to read much, and we just want to head it off as much as possible
[04:21] <persia> mrooney, I guess.  Still seems like a UI failure.  Just because most bugs aren't noisy enough that people complain about the UI issue doesn't mean it's not there.
[04:22]  * persia has the same issue with adding [Needs Packaging] to the title, but knows there is a bug filed about having greater visibility of tags, and so is waiting for implementation, rather than complaining about that one.
[04:23] <SteckelBud> Anyone out there having issues with udev on Vmware infrastructure?  Can't call it a "bug" yet, but have issues with udev taking 100% of partition when using a sudo cp command...just curious.
[04:24] <SteckelBud> Running hardy btw
[06:16] <thekorn> hi all,
[06:19] <thekorn> ogasawara, hi, one question about todays hug day (when you are arround again):
[06:20] <thekorn> on the incomplete list there are some bug which have open tasks for linux-source-2.6.*
[06:20] <thekorn> they are not 'incomplete' but 'confirmed'
[06:21] <thekorn> how should we handle this bugs?
[06:21] <thekorn> e.g. bug 71772
[06:22] <thekorn> especially: what to do about this tasks
[08:01] <ogasawara> thekorn: hi, re bug 71772 I'd close the linux-source-2.6.20 task as Won't Fix as it's not SRU worthy.  And even if it were a candidate for SRU it needs to be resolved in the actively developer kernel before a fix can be backported.
[08:02] <ogasawara> thekorn: and since there has been no feedback regarding the actively developed kernel, it's not likely to be resolved for 2.6.20
[08:06] <ogasawara> thekorn: I went ahead and posted a comment and closed the 2.6.20 task
[08:07] <thekorn> ogasawara, ok, super
[08:07] <thekorn> thanks
[08:24] <thekorn> dholbach, hi, when you have a minute, can you please update lp:five-a-day it is on version 0.55 where the package has version 0.56
[08:35] <dholbach> thekorn: sorry, sorry, sorry
[08:35] <dholbach> thekorn: will do in a sec
[08:35] <thekorn> no problemo
[10:54]  * popey hopes that someone else has two batteries on their laptop to confirm bug 279552
[10:54] <popey> or if someone can suggest more detail i could provide for that bug..
[11:11] <persia> popey, Can you get a stacktrace?  crashes are always easier to debug with a stacktrace.
[11:11] <popey> what? strace gnome-power-manager?
[11:12] <james_w> popey: https://wiki.ubuntu.com/DebuggingProgramCrash
[11:12] <popey> ok, wilco
[11:12] <james_w> using gdb, after installing dbgsym packages
[11:12] <james_w> popey: also "gnome-power-manager --no-daemon --verbose" output would be great
[11:13] <james_w> gnome-power-manager --verbose --no-daemon 2>&1 | tee gpm.debug.log.txt
[11:13] <popey> heh, doing a dist-upgrade, i looked over at my laptop and the icon for gpm has changed
[11:13] <james_w> and attach gpm.debug.log.txt to the bug report
[11:13] <popey> do you want one with it crashing and one without or just a crashy one?
[11:13] <james_w> just a crashy one should be fine
[11:14] <james_w> the stacktrace will perhaps be more useful though, just harder to get
[11:16] <popey> bah, it's not crashing now
[11:16] <popey> hmm, it crashes if i dont specify --no-daemon
[11:16] <popey> ah no, it is the --verbose
[11:17] <james_w> --verbose means that it doesn't crash?
[11:17] <popey> yes
[11:17] <james_w> weird
[11:17] <james_w> have you installed the dbgsym packages?
[11:18] <popey> not yet, doing that next
[11:18] <james_w> thanks
[11:18] <james_w> give me a shout when you've got them, I think you'll need to pass gpm arguments inside gdb to get a helpful trace
[11:18] <popey> ok
[11:20] <james_w> no upstream reports jump out for "two batteries" or "multiple batteries"
[11:21] <popey> amusingly about a year ago i offered hughsie a  laptop with two batteries for just this kind of situation :)
[11:21] <james_w> heh :-)
[11:29] <popey> james_w: the debugsyms for gpm aren't the same version of gpm, does that matter?
[11:30] <popey> gpm is 2.24.0-0ubuntu3, debugsym is 2.22.1-1ubuntu4.1
[11:34] <RAOF> popey: That matters very much; I'm surprised that you can even install that.
[11:37] <popey> RAOF: what makes you think i installed it? :)
[11:38] <popey> I just looked at the versions with apt-cache show, before installing
[11:46] <james_w> popey: did you add the Intrepid ddebs repo?
[11:48] <james_w> I see 2.24.0-0ubuntu3
[11:49] <popey> oops
[11:59] <popey> ok james_w going through https://wiki.ubuntu.com/Backtrace i get to step 4, and when i do "backtrace full" it says "No stack" is that good or bad?
[12:00] <persia> That's unfortunate, as it means there's nothing available to trace :(
[12:00] <james_w> popey: did you do "gdb gnome-power-manager"
[12:00] <popey> yes
[12:00] <james_w> ok, quit back out, and do that again
[12:00] <popey> with > and tee etc
[12:01] <popey> ok, at (gdb)
[12:01] <james_w> then when you get the prompt do the pagination thing, but before running it, do "set args --no-daemon"
[12:01] <popey> ok
[12:01] <popey> then run?
[12:01] <james_w> yup
[12:01] <james_w> hopefully you'll get a stack this time
[12:02] <popey> yeah, lots of "stuff"
[12:04] <popey> ok, attached it to bug 279552
[12:07] <popey> thanks for the help james_w - it's appreciated, beer++ at the release party :)
[12:07] <james_w> woo! :-)
[12:07] <james_w> I owe you a few, so we may end up quite drunk
[12:08] <popey> i dont see how you could possibly owe me beer! :)
[12:08] <popey> but I accept
[12:08] <popey> :)
[12:09] <james_w> I'm a big fan of the podcast
[12:09] <popey> :)
[12:09] <james_w> and you helped me a lot with screencasts
[12:09] <popey> cool
[12:09] <popey> beer it is then
[12:10] <steve555> Hi everyone!
[12:11] <steve555> I've read in one of my e-mails that #ubuntu-bug is talking about the kernel.
[12:12] <james_w> popey: you think it's becuase you've got two batteries because it only happens on that machine, or because it works if you pull one out?
[12:13] <popey> it works with only one battery
[12:13] <popey> interestingly..
[12:13] <popey> it's specific to one battery
[12:13] <popey> i.e. if i pull out the internal battery and leave the "slice" one attached, it crashes
[12:14] <popey> if i pull out the slice battery and leave the internal one, it doesnt crash
[12:14] <popey> (both batteries are new as of a month or so ago, and both work perfectly as batteries go)
[12:18] <james_w> interesting
[12:18] <james_w> the stacktrace is a bit confusing
[12:18] <james_w> and the fact that --verbose fixes it even more so
[12:19] <james_w> and the code :-)
[12:19] <popey> interestingly if gpm is already running with the ac on, and i yank it, gpm doesnt crash
[12:23] <james_w> the stacktrace suggests that it crashes while adding the "primary" battery
[12:23] <james_w> popey: how familiar are you with hal?
[12:23] <popey> i am aware of it
[12:23] <popey> "familiar" is pushing it
[12:23] <james_w> ah, the wiki page helpfully gives the exact command
[12:24] <james_w> hal-find-by-capability --capability "battery" | xargs -n 1 hal-device
[12:24] <james_w> could you add that to the report please?
[12:24] <popey> added
[12:25] <james_w> thanks
[12:26] <popey> i always thought acpi etc started counting at zero
[12:26] <popey> not one
[12:26] <james_w> yeah
[12:26] <james_w> do you know which is which?
[12:27] <popey> g71c0006k210 is http://www.hexparts.com/Toshiba-Satellite-R20-R25-Portege-M400-M405-Tecra-M7-Series-Expansion-Battery_p_2-259.html
[12:27] <james_w> there's info.product and battery.serial keys
[12:27] <popey> which is the external one
[12:27] <james_w> that's the crashy one?
[12:27] <popey> so BAT1 is internal, BAt2 is extrnal
[12:27] <james_w> cool
[12:28] <popey> wonder if they aren't using bat0 because i have yanked/reinstalled them both over the last hour or so
[12:31] <james_w> --verbose output would be pretty useful, could you try again?
[12:32] <popey> sure, just popping out to lunch
[12:32] <popey> brb
[12:32] <james_w> no problem
[12:43] <popey> nope, --verbose, it runs fine
[12:44] <james_w> damn, could you provide the output please?
[12:44] <popey> it's just two lines
[12:44] <popey> did you want it with --no-daemon too?
[12:45] <james_w> ah, yes please
[12:45] <james_w> killall gnome-power-manager first if you have one running
[12:45] <popey> ok
[12:47] <popey> done
[12:47] <popey> killed it after ~10 seconds
[12:48] <james_w> that should be plenty, thanks
[12:50] <james_w> ** (gnome-power-manager:9532): CRITICAL **: gpm_cell_array_charge_low_cb: assertion `engine != NULL' failed
[12:50] <james_w> that may be relevant
[12:51] <popey> certainly _looks_ interesting :)
[12:53] <james_w> which one is likely to be "percent 3.4"
[12:53] <james_w> i.e. almost discharged
[12:54] <popey> thats the external one
[12:55] <james_w> good
[12:55] <james_w> at least that makes sense
[14:12] <afflux> morning
[14:12] <thekorn> hi afflux
[14:12] <afflux> bdmurray: I just read the mail you sent me. The changes to the script all look good, I'll look at the TODOs now.
[14:13] <afflux> bdmurray: just one thing.. is ~/.lpcookie.txt created by some other tool?
[14:14] <afflux> hi thekorn ;)
[14:19] <afflux> oh my god.
[14:19] <afflux> someone responded to every single mail of a "mass duplicate moving" with "understood"....
[14:19] <Pici> ouch.
[14:43] <hggdh> afflux, a mass 'understood'?
[14:44] <afflux> yup
[14:47] <hggdh> cool
[14:52] <afflux> not really ;)
[14:52] <afflux> bdmurray: you got a new mail ;)
[15:03] <niadh> I've got a bug I marked as lightgreen on the wiki for today
[15:03] <niadh> but not sure if it should be left as is or wont fix
[15:04] <niadh> bug 74179
[15:07] <niadh> in fact, I CAN'T set won't fix
[15:10] <afflux> niadh: do you mean the .22 task?
[15:11] <niadh> For that and another bug, I don't have the privelage to set status to 'wishlist' or 'won't fix'
[15:14] <afflux> niadh: .22 is gutsy, isn't it? IIRC linux-source-2.6.22 is still a valid target
[15:14] <niadh> I'm just following through what the wiki page tells me to mark the bugs as...
[15:14] <afflux> which one?
[15:15] <niadh> https://wiki.ubuntu.com/UbuntuBugDay/20081007#preview the bug in particular is one of the 200 incomplete bugs
[15:16] <afflux> uh? wontfix for expired bugs?
[15:17] <afflux> hm, I'm not sure whether this is correect or a mistake
[15:18] <joumetal> bug 184547 is fixed in debian :)
[15:25] <niadh> I need a bit of help with this bug 72775, looks fixed, just not sure how to procede with it
[15:28] <thekorn> niadh, let me check the bug
[15:29] <niadh> kk
[15:30] <thekorn> niadh, I would close the  linux (ubuntu)  task as fix relaesed based on the feedback in comment #39
[15:31] <thekorn> and ask to file a new bug if it is still a problem
[15:32] <niadh> fix commited or released?
[15:32] <thekorn> released
[15:34] <niadh> thekorn: Is it just you and me working through those incomplete bugs?
[15:35] <thekorn> niadh, right now, but I think people will start working on this list soonish
[15:36] <niadh> thekorn: fair enough, just didn't appear to be many working on it is all.
[15:37] <niadh> thekorn: What should I set bug status to be if I can't use 'wont fix'?
[15:41] <thekorn> niadh, unfortunatly won't fix is a restricted status,
[15:42] <thekorn> niadh, and in my opionion there is not alternative status for the ones in the "incomplete" list on the hugday wiki page
[15:42] <niadh> Ah, right, there's really not much I can do in the incomplete list then
[15:43] <thekorn> niadh, right, sorry, but maybe working on the other list is intresting too
[15:43] <niadh> Oh it's interesting, but my issue is understanding it all ;)
[15:44] <thekorn> niadh, just aks your questions here
[15:44] <niadh> Same with triaged, right, I can't set that either?
[15:45] <hggdh> niadh, these are restricted status. You need to be a member of bug-control to set them
[15:45] <hggdh> but you can ask here, and we will do it for you
[15:46] <niadh> Right, so that leaves me with Testing bugs I can work on today
[15:46] <hggdh> niadh, if you think a bug deserves to be traiged, just ask
[15:46] <hggdh> s/traiged/triaged/
[15:47] <niadh> hggdh: Be easier if I work on the incomplete bugs, since I have the privs and knowledge to do that ;)
[15:48] <hggdh> niadh, we are glad you are helping out. But... the offer stands ;-)
[15:48] <niadh> hggdh: Well there were a couple of bugs I added the appropriote comments to, but obviously couldn't set the status on
[15:49] <niadh> hggdh: I'll point you at those bugs and you can decided
[15:49] <hggdh> give us the bug numbers. write them as bug xxxxxx or bug #xxxxx
[15:49] <hggdh> and ubottu will happily provide us with a link
[15:50] <joumetal> What is right status to bug 27253? though it is not in list.
[15:50] <hggdh> also -- you *can* promote to 'confirmed'.
[15:50] <joumetal> sorry wrong number
[15:51] <joumetal> bug 272537
[15:52] <niadh> Not sure what to do with this bug, it's part of the testing bugs, that are flagged to be marked as incomplete, but it appears to be complete and fixed.
[15:52] <niadh> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/261376
[15:52] <joumetal> it is probably due to ubuntu kernel configuration change. incomplete is not right anymore.
[15:53] <hggdh> joumetal, I would say confirmed
[15:53] <hggdh> joumetal, wasn't there a package for toshiba laptops?
[15:53] <hggdh> niadh, looking at it
[15:53] <niadh> hggdh: this is one of the bugs I can't change the status of 20977
[15:54] <hggdh> bug 20977
[15:54] <hggdh> niadh, what is the issue with 261376?
[15:55] <niadh> hggdh: It's marked to be flagged as incomplete, but it appears to have been fixed, do I just turn it green on the hug day wiki and leave the bug as is?
[15:55] <hggdh> niadh, yes
[15:55] <niadh> ok
[15:56] <joumetal> hggdh: toshiba-acpi is not compiled as module anymore. replacement is tlsup in ubuntu supplied third party device drivers if I understand correctly.
[15:57] <hggdh> niadh, bug 20977 already has an assignee -- no need to touch it (although the assignee should have changed it to "in progress"
[15:57] <nullack> seb128 Im testing bug 261596 - xchat is working fine now. Ill leave the bug open for the other bloke with the issue but for me its fixed, thanks
[15:57] <hggdh> joumetal, thanks -- I remembered something about it, but not much
[15:57] <niadh> hggdh: I'm leaving 20977 as is, that was just the one I was looking at that I couldn't change the status of.
[15:58] <seb128> nullack: thanks for testing, the enchant bug is closed, you probably still have the dictionnary issue though
[15:59] <nullack> seb128 Anytime mate I like testing :) Also on bug 260765 I understand your position.
[16:00] <nullack> I currently dont know how to compile resindvd but I will learn and test the svn version
[16:00] <nullack> IMHO DVD playback is a core user feature so Ill work on it
[16:01] <nullack> Unless anyone knows of a deb for svn resindvd
[16:01] <seb128> nullack: right, it's not high priority on my list because dvd playing is crappy in gstreamer anyway and most dvd will not play due to dvdcss anyway
[16:01] <nullack> seb128 theres a nice script that brings done the decrypter from medubuntu which solves that for users so resindvd problems is the only real barrier left from having a great experience now
[16:02] <seb128> what is resin?
[16:02] <seb128> there was still dvdmenus code in gstreamer previous time I tried
[16:03] <niadh> I have a duplicate bug, apparently, should I just mark it as invalid?
[16:03] <nullack> seb128 I understand that resindvd is the dvd menu code that is providing the current dvd menu support in gstreamer
[16:03] <seb128> niadh: mark it as duplicate of the other one
[16:04] <seb128> nullack: there is no dvdmenu in gstreamer, or that's very new
[16:04] <niadh> wait, no, it's not a dup
[16:04] <nullack> seb128 Its there, I just tested it :)
[16:04] <seb128> nullack: and if there is one I'm not sure totem is using it
[16:04] <nullack> seb128 Im on a defayult build and it is using it
[16:05] <joumetal> seb128: Does bug 184547 need some more info? It's fixed in Debian.
[16:06] <seb128> joumetal: no, just too much to do, I'll upload the patch to intrepid later
[16:06] <nullack> seb128 I have to go offline but I will continue the tests with DVD menus, theres three bugs Ive found so far. And I'll do a svn compile of resindvd to see how that effects the tests
[16:06] <nullack> Thanks, bbl
[17:12] <niadh> got a bug marked as invalid, what should i do with it?
[17:13] <persia> niadh, Which bug?
[17:13] <niadh> bug 254995
[17:14] <persia> niadh, That's a test bug.  Just ignore it :)
[17:14] <niadh> Am going through the hug day wiki checking off the new bugs to be marked as invalid under Testing bugs, new.
[17:14] <persia> And that came up in the search?  Amusing.  Yeah, that's not a real bug.
[17:27] <MTecknology> Hey, my battery is going to die soon so not much discussion but - Would it be possible to go through all bugs prior to say 8.04 and flag them incomplete, invalid, or fix released? Something? I was just thinking that in almost all cases, the users that reported the bugs in these versions have probably since stopped using these versions and the version they're using has probably solved these issues...
[17:28] <persia> MTecknology, It's a matter of investigating each one.  Personally, I've a few bugs that *still* affect me since warty, and I'd be exceedingly annoyed if someone tried to close them without some attempts at verification and discussion.
[17:29] <MTecknology> what about a pass to ask the reporter and anybody subscribed if it's still an issue?
[17:29] <MTecknology> then a pass w/ my previous though
[17:32] <persia> MTecknology, That's loosely done on an ongoing basis.  The general guideline is to only make noise on a bug once a release unless there is discussion : if it's still present, and unsolved, and verifiable, then it waits.
[17:32] <persia> Linking upstream can be a big help there, especially for the sorts of bugs that remain unsolved for very long periods of time.
[17:32] <MTecknology> It might not be an idea that can work out, but I was looking over some statistics for bugs that are in the wild and when looking at the "ubuntu" bugs it looks like there's a lot out there, but when looking at 8.04 and 8.10 specifically, it's pretty impressive as far as fixed bugs goes
[17:34] <MTecknology> How can I go through and take care of those if I set a large chunk of time aside? Take a 7.04 bug, add it to 8.10 and mark them both incomplete?
[17:35] <MTecknology> and if they sit there for a long time, mark them invalid or fix released?
[17:36] <MTecknology> I wouldn't do anything unless I'm sure I can help, and more than likely not until december
[17:37] <persia> MTecknology, Generally, bugs shouldn't be targetted against specific releases unless either 1) it's part of a release update or security update, 2) it's being considered release critical for a given release, or 3) there's some reason it needs to be fixed in that release as distinct from just being fixed.
[17:37] <MTecknology> persia: I meant the ones that were already targetted at 7.04 and such
[17:38] <persia> For the vast majority of bugs, the correct task state is only that they should be fixed, and they are then fixed at some point, without deep concern for release tracking.  This is even true for the majority of bugs that are specifically opened and closed during a specific development cycle, and known to both affect that cycle and to be closed in that cycle.
[17:39] <persia> No, please don't do that.  If something has open tasks in e.g. 7.10 and 8.04, then it's probably considered a candidate for a stable release update or a security fix, and changing that would be both bad and wrong.
[17:39] <persia> Often these sorts of bugs *are* fixed in newer releases, but they still need to be considered for the older releases, and either fixed or a determination made that they should not be fixed in that release.
[17:43] <MTecknology> persia: I'm lost... I was looking at the stats I was building up.... Why is there 44% of "new bugs here... If you look in all versions, there's no reason for that many
[17:43] <MTecknology> as far as each release goes, most of them are fixed
[17:44] <MTecknology> I looked at things and I realized exactly what you're talking about
[17:44] <persia> MTecknology, Remember, the vast majority of bugs are not tracked against a release.
[17:44] <MTecknology> DOH!
[17:44]  * MTecknology facepalms
[17:45] <MTecknology> thanks for the lesson :)
[17:46] <persia> Generally, release tracking is only used when it's important to distinguish the work done for the same bug in two (or more) separate releases.  While there are exceptions, we don't usually engage in the level of detail of project management that makes it worthwhile to check : if it's October 2008, we're working on 8.10.  If it's November, we're working on 9.04.
[17:46] <persia> The primary exceptions are stable release updates and security updates, which, for perhaps obvious reasons, the usual answer of "have you tried this in the latest release" is not the best way to manage the bug :)
[17:48] <MTecknology> ya, I need to learn about the best way to manage bugs and try to help out. I've tried to help out and been able to close a decent share of bugs, but I'm not doing them the best as I could
[17:54] <MTecknology> battery's about gone - ty for helping me figure out a few things - You helped me notice a lot more than you actually said. ;)
[19:58] <bdmurray> seb128: wrt bug 260765 what should be happening?  Should dvd menus show up or should the main title just start playing?
[19:59] <seb128> totem-gstreamer has no dvdmenu in current stable version, I didn't follow svn work but until now it's supposed to play the movie only
[19:59] <seb128> that might change using the svn version
[19:59] <seb128> not sure what is the issue in intrepid and it's new though
[20:05] <bdmurray> If I right click on a DVD and choose open with movieplayer it starts with the movie only, if I launch totem them try to open the dvd I get an error message about the playlists
[20:06] <seb128> that seems similar to what I recall having when trying on hardy
[20:06] <seb128> there was no error about the playlist but it was starting the movie when the dvd is detected and the menu item was not working correctly
[20:07] <seb128> basically dvd playing is something which doesn't work correctly in totem gstreamer
[20:31] <Yoghurt> Hey people... What does it mean if a bug is Triaged?
[20:32] <bdmurray> https://wiki.ubuntu.com/Bugs/Status has the answer
[20:34] <Yoghurt> But if i have the same problems with the same drivers etc. is that enough to set the status to Confirmed?
[20:34] <bdmurray> Yoghurt: yes, it probably is
[20:34] <Yoghurt> Oh.... great...another Dane
[20:35] <Yoghurt> okay, thank you bdmurray
[20:43] <greg-g> Yoghurt: but if it is already set to Triaged then you dont' want to set it to confirmed.  Just making sure; I may have misunderstood you.
[20:44] <Yoghurt> oooh.... maybe I have misunderstood something..
[20:44] <greg-g> what is the bug number?
[20:46] <Yoghurt> greg-g: 248881
[20:47] <greg-g> bug 248881
[20:47] <greg-g> yeah, it is alredy set to Triaged, so you don't want to set it to Confirmed
[20:48] <Yoghurt> okay.... thanks :)
[20:48] <greg-g> Confirmed _merely_ means that you can reproduced.
[20:49] <greg-g> Triaged is there is information to start working on a fix for it, ie: a better state for the bug to be in :)
[20:49] <greg-g> Yoghurt: you are very welcome, thanks for being involved
[22:02] <chrisccoulson> whilst everyone here is busy triaging kernel bugs, i have a question.
[22:03] <chrisccoulson> i've come across a report from a user who's keyboard and mouse doesn't work in Xorg.
[22:03] <chrisccoulson> It turns out that ehy have no /dev/input/event* device nodes
[22:03] <chrisccoulson> so you think that is a kernel bug?
[22:03] <chrisccoulson> do you think, even ***
[22:20] <tobi_> should bugs that concern components that have their very own bug tracker be file in both with linking each other, or should they be file in the upstream tracker only?
[22:31] <RAOF> tobi_: First in the Ubuntu tracker.  If you're sure it's an upstream problem, also file an upstream bug and link it.
[22:32] <tobi_> ok thank you