[00:00] <hggdh> waste. I am from the time a large computer had 160K
[00:00] <bcurtiswx> well other empathy chat rooms, youll see users icons.
[00:00] <bcurtiswx> hahaha, i think it would be a great wishlist bug to suggest an improvement with telepathy-idle (or empathy is thats what does that)
[00:02] <bcurtiswx> its still devel, so i imagine it will change before karmic
[00:02] <bcurtiswx> and a suggestion like yours may make it in
[00:03] <hggdh> mine? I have no power here
[00:04] <bcurtiswx> i mean in a telepathy-idle or empathy bug report wishlist suggesting the space be reduced
[00:04] <bcurtiswx> (im asking in #telepathy now)
[00:05] <hggdh> yes. And I see no room list
[03:17] <micahg1>  /nick micahg
[04:40] <jj__> im using ubuntu 64bit,, after the new kernel update with the new fglrx drivers from ubuntu it randomly freezes
[04:41] <jj__> i have removed the prop drivers and now using open source video drivers and it works fine
[04:41] <micahg> which version?
[04:41] <jj__> which version?  im using ubuntu 64bit edition
[04:42] <jj__> the drivers installed from hardware drivers
[04:42] <jj__> but removing them and using opensource all works now
[04:44] <micahg> I suggest going to amd's site and downloading the latest drivers
[04:44] <micahg> the amd installer can generate debian packages for your ubuntu version
[04:45] <micahg> or you can use the open source drivers
[04:46] <jj__> i am fine with opensource but drawback is no 3d.. but even before the kernel update prop drivers from amd or ubuntus  hardware drivers  have issues with the graphic card i have
[04:46] <micahg> which card do you have?
[04:46] <jj__> 3450
[04:46] <jj__> hd 3450
[04:46] <jj__> mobile version
[04:47] <micahg> is that a new card?
[04:47] <jj__> yes its not the newest but it has been out for a while now
[04:47] <micahg> I have the hd 3200
[04:47] <micahg> I just use the installer for amd to build the latest drivers
[04:49] <jj__> do you have any issues?
[04:49] <micahg> nope
[04:49] <jj__> the thing is .... how would you remove it?
[04:49] <micahg> what version of Ubuntu?
[04:49] <micahg> jaunty?
[04:49] <micahg> remove what?
[04:49] <jj__> ive installed the amd installer and removing it is a pain
[04:49] <jj__> lol
[04:49] <jj__> the driver if its trouble
[04:50] <micahg> no
[04:50] <micahg> use the installer to generate .deb packages
[04:50] <micahg> run it with --help
[04:50] <micahg> and it'll give you the command switch
[04:50] <jj__> ive never tried using the --help before thank you
[06:43] <dholbach> good morning
[06:44] <jj_> is there any way to enable the newly installed video driver without rebooting?
[06:45] <dholbach> jj_: restart X?
[06:45] <jj_> dholbach,  how is that done without logging off or rebooting?
[06:47] <dholbach> I dunno if just logging out and logging in is good enough - to be safe: log out, ctrl-alt-f1, log in, type "sudo /etc/init.d/gdm restart; exit", log in normally
[06:48] <jj_> dholbach,  well i didnt wanna cancel downloads or anything,, guess i'll wait :P
[06:48] <dholbach> that probably makes sense :)
[06:50] <YoBoY> good morning
[06:51] <dcraven> Hi, I think this bug should be set to Wishlist --> bug #391359
[06:51] <ubot4> Launchpad bug 391359 in ubuntu "Feature request: System restore" [Undecided,New] https://launchpad.net/bugs/391359
[06:51] <dcraven> Apparently I'm supposed to post those here :)
[06:58] <YoBoY> checkpoints ... :]
[08:58] <paxster> Bug #391804 should most likely be categorized as wishlist
[08:58] <ubot4> Launchpad bug 391804 in hundredpapercuts "nautilus-open-terminal should be included in default Ubuntu install" [Undecided,Confirmed] https://launchpad.net/bugs/391804
[09:00] <Hobbsee> !info nautilus-open-terminal karmic
[09:00] <ubot4> Hobbsee: nautilus-open-terminal (source: nautilus-open-terminal): nautilus plugin for opening terminals in arbitrary local paths. In component universe, is optional. Version 0.13-2 (karmic), package size 41 kB, installed size 780 kB
[09:01] <Hobbsee> that'd be nice
[09:07] <shadeslayer> if i cannot reproduce a issue in a old release of KDE with a newer release of KDE,what should i mark that bug as?
[09:07] <shadeslayer> bug 361129
[09:07] <ubot4> Launchpad bug 361129 in tagua "calendar widget messes taskbar up" [Undecided,New] https://launchpad.net/bugs/361129
[09:11] <paxster> what should bug 391945 regarding the pidgin/yahoo issue be marked as?
[09:11] <ubot4> Launchpad bug 391945 in pidgin "unable to connect  yahoo" [Undecided,New] https://launchpad.net/bugs/391945
[09:12] <shadeslayer> paxster:i think a fix has been comitted
[09:12] <shadeslayer> !yahoo
[09:12] <ubot4> At the moment there are many pidgin users experiencing problems connecting to Yahoo IM, you can try changing your paging server to cs101.msg.mud.yahoo.com and see if that helps.
[09:13] <shadeslayer> or give that as a comment
[09:13] <paxster> i gave a comment telling them to get the fixed version, 2.5.7
[09:13] <paxster> I never had any luck changing the paging server
[09:14] <shadeslayer> paxster: depends on person to person...
[09:14] <paxster> true
[09:14] <shadeslayer> paxster: i think it works in koepet
[09:14] <shadeslayer> *kopete
[09:15] <paxster> shadeslayer: connecting to yahoo?
[09:16] <shadeslayer> paxster: yeah...im trying right npw
[09:16] <shadeslayer> *now
[09:16] <shadeslayer> nope...
[09:17] <paxster> shadeslayer: there is a pidgin release that fixes the problem - so I directed them there and gave the other work around - hopefully that will help
[09:17] <shadeslayer> that will hopefully fix the problem..
[09:18] <shadeslayer> i hate it when mail providers overhaul their servers....
[10:39] <lesshaste> hi all
[12:07] <xteejx> hi guys
[12:08] <BUGabundo> hey xteejx
[12:08] <BUGabundo> and hello everyone
[12:08] <BUGabundo> hi YoBoY
[12:08] <xteejx> hey BUGabundo :)
[12:09] <YoBoY> hi BUGabundo
[12:09] <YoBoY> hi everyone
[12:34] <dupondje> bugs that are reported on launchpad, concerning a ppa package, thats invalid right ?
[12:39] <Ampelbein> dupondje: That depends on the bug. If it can be reproduced with the package in the archive, it is not invalid.
[12:39] <Ampelbein> dupondje: can you give the bugnumber?
[12:41] <dupondje> https://bugs.launchpad.net/ubuntu/+source/wammu/+bug/388905
[12:41] <ubot4> Launchpad bug 388905 in wammu "package conflict and failed dependencies" [Undecided,New]
[12:44] <Ampelbein> dupondje: yeah, that's invalid. the packager supposedly made a mistake in packaging (not adding appropriate Replaces/Conflicts). It would be nice to know, which ppa the reporter used to install so that we can track the issue down.
[12:46] <niadh> I have a new bug can't reproduce, do i mark it invalid (am taking part in the banshee bug day having been away doing my thesis for almost a year)
[12:46] <dupondje> Ampelbein: so invalid or incomplete ? ;)
[12:47] <niadh> I thought invalid since I can't reproduce it using the criteria I was given
[12:47] <Ampelbein> dupondje: invalid.
[12:47] <niadh> I am using a later version though
[12:47] <niadh> Can always ask em to try the PPA version themselves
[12:48] <Ampelbein> niadh: Even if you can't reproduce, the bug could still be valid, e.g. on a different architecture. Can you give the bugnumber?
[12:48] <niadh> 389659
[12:48] <Ampelbein> bug 389659
[12:48] <ubot4> Launchpad bug 389659 in banshee "System file queue not played correctly" [Undecided,New] https://launchpad.net/bugs/389659
[12:48] <niadh> Being a C# application why would it behave different on different architecture?
[12:50] <Ampelbein> niadh: that was only one reason why it could still be a valid report.
[12:51] <niadh> Fair enough, I didn't mean to sound as if it I was saying you were wrong, just curious
[12:51] <Ampelbein> niadh: no offense taken ;-)
[12:53] <dupondje> https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/392081
[12:53] <dupondje> lol :D
[12:53] <ubot4> Launchpad bug 392081 in evolution "I've received yesterday a message with date of today !" [Undecided,New]
[12:53] <dupondje> funny one
[12:55] <niadh> Should I mark this bug as incomplete then?
[12:58] <Ampelbein> niadh: I'd ask to test with a daily live-cd and set status to incomplete, see https://wiki.ubuntu.com/Bugs/Responses#Needing%20testing%20in%20the%20development%20release
[12:59] <niadh> okies, cool
[13:01] <seb128> niadh, rather than testing on a CD ask for a screenshot and a copy of the message to see if that's due to the email
[13:02] <dupondje> https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/376065 <- chinese language = incomplete ? :P
[13:02] <ubot4> Launchpad bug 376065 in evolution "issue 1  email problem with evolution the sent and sent and receive  position does not operate the message saying the gnome pilot seems to be not installed , then the issue 2 is during  the software update there is a message saying E: dpkg is interupted " [Undecided,New]
[13:02] <niadh> to see if what's due to the email?
[13:04] <Ampelbein> seb128: i was suggesting to ask for bug 389659, not the evolution one.
[13:04] <ubot4> Launchpad bug 389659 in banshee "System file queue not played correctly" [Undecided,New] https://launchpad.net/bugs/389659
[13:04] <seb128> Ampelbein, ah ok, I joined the channel after that one
[13:17] <niadh> There's a single stand alone bug in todays bug day list a patch has been written, it's been confirmed by a user or two but a comment states it's been fixed upstream, I'm not quite sure what to do
[13:17] <niadh> it's bug: 338695
[13:17] <pedro_> bug 338695
[13:17] <ubot4> Launchpad bug 338695 in banshee "Banshee album art is blurred in notification bubbles" [Low,Fix committed] https://launchpad.net/bugs/338695
[13:21] <pedro_> niadh: the patch is for banshee 1.4.3 but that's a small detail and doesn't qualify as an SRU
[13:21] <niadh> SRU?
[13:21] <pedro_> niadh: Stable Release Updates : https://wiki.ubuntu.com/StableReleaseUpdates
[13:22] <niadh> Ah security fix
[13:23] <pedro_> niadh: and it's fixed on 1.5.0 anyways but that version is still not available on karmic
[13:23] <pedro_> niadh: just add a comment with that information and mark the bug as triaged (lightgreen) on the hug day page
[13:23] <niadh> But it IS fixed so it can be marked off the list anyway because there is a confirmed fix?
[13:23] <pedro_> niadh: yeap
[13:23] <niadh> cool
[13:24] <pedro_> niadh: thanks for the help :-)
[13:24] <niadh> Your welcome, been working on my thesis all this academic year, felt bad I couldn't do any bug stuff
[13:32] <niadh> If a bug has been attached to an upstream bug do I can't mark it as confirmed even if I have the bug happen to me can I? I have to wait for upstream, right?
[13:36] <pedro_> niadh: if a bug was sent upstream you can mark it as confirmed yes, please do also check if the upstream report contains all the information available on the ubuntu report, such reports should be marked as triaged if you don't have the rights to do so, just ask here in the channel for someone to do it for you
[13:38] <niadh> it has been marked as triged I believe, its bug 253785 if you are interested
[13:38] <ubot4> Launchpad bug 253785 in exaile "Apps can't sync with Rockbox" [Medium,Confirmed] https://launchpad.net/bugs/253785
[13:39] <pedro_> niadh: ah yeap i was just looking that
[13:39] <pedro_> niadh: the bug that was linked into the banshee tasks was wrong it was the same as the rhythmbox one btw
[13:39] <niadh> Ah, I'll let you deal with it then since you'll know more
[13:39] <pedro_> niadh: i've just looked on the upstream bts and link that one
[13:40] <niadh> is that is more or less done with then?
[13:41] <pedro_> niadh: yeap, I've just marked it as triaged so we're done with it
[13:41] <niadh> cool
[13:45] <niadh> This bug: 340401 am pretty sure it's a limitation of gtk not banshee, I didn't think the folder select widget in GTK allowed you to select multiple folders, or am I wrong?
[13:46] <pedro_> bug 340401
[13:46] <ubot4> Launchpad bug 340401 in banshee "Import from Local Folder should allow you to select more than one folder to import from" [Undecided,New] https://launchpad.net/bugs/340401
[13:54] <pedro_> niadh: you can set that property on the gtkfilechooser, it's just a matter to the banshee import dialog to set that
[13:54] <pedro_> niadh: may you send that upstream?
[13:55] <niadh> I could do if you think we should?
[13:55] <pedro_> niadh: instructions on how to do it are here: https://wiki.ubuntu.com/Bugs/Upstream/GNOME
[13:55] <pedro_> niadh: yeap it's a valid enhancement request
[13:55] <niadh> cool
[13:58] <niadh> can also use this time to bring this bug to peoples attention: 272161 it's not one I personally suffer from but one I know lots of my friends have
[13:58] <niadh> I submitted it quite some time ago and it's not seen much attention since
[14:09] <yofel> hey, any vim users here that could confirm bug 392086 ?
[14:09] <ubot4> Launchpad bug 392086 in vim "[karmic] vim-7.2.148-2ubuntu2 - broken regexp in debchangelog.vim" [Undecided,New] https://launchpad.net/bugs/392086
[14:12] <niadh> pedro_: I'm not actually sure how to upstream something
[14:12] <niadh> Do I need to create a new upstream bug or something?
[14:12] <pedro_> niadh: yes sr
[14:12] <pedro_> niadh: you need to create an account there if you don't have one already and create a new bug on the product you're forwarding to in this case banshee
[14:13] <pedro_> niadh: if you want to, just create the account and i'd help you trough the process
[14:13] <niadh> Ok, am pretty sure I have a bugzilla acount, but will check
[14:13] <pedro_> alrighty
[14:16] <niadh> pedro_: am into bugzilla
[14:18] <pedro_> niadh: super, before sending one bug there we need to look if there's one reported already
[14:18] <pedro_> niadh: just click on the search link at the top of the bugzilla page
[14:18] <niadh> yup
[14:18] <pedro_> it will lead you to a page that says: Short Bug Search Form
[14:19] <niadh> yup
[14:19] <pedro_> ok so we only want to search on the banshee bugs so we use something like:
[14:19] <pedro_> product:banshee keywords
[14:19] <pedro_> when keywords are the ones we want to search for there
[14:19] <pedro_> with "product:banshee" we are just searching on that product and not in the whole bugzilla database
[14:20] <niadh> yeah
[14:20] <pedro_> which will take much more  longer
[14:20] <niadh> there doesn't appear to be a bug similar to this one already in bugzilla
[14:21] <pedro_> niadh: ok let's report a new one then, click on New bug on the top left of the page
[14:22] <niadh> so it's either a usablity bug or feature
[14:22] <pedro_> or here: http://bugzilla.gnome.org/enter_bug.cgi
[14:23] <pedro_> niadh: seems more like a feature request to me but not an usability issue
[14:23] <niadh> I thought feature but I just thought it might be argued it could be a usablity one
[14:23] <pedro_> niadh: well you can add a keyword for that in you think it's an usability issue
[14:24] <pedro_> niadh: let's fill the report first
[14:24] <niadh> Nah feature is fine
[14:24] <niadh> Banshee is listed in other applications so I found
[14:24] <pedro_> http://bugzilla.gnome.org/enter_bug.cgi?product=banshee <-
[14:24] <pedro_> right
[14:24] <niadh> importing looks like a good tag
[14:25] <pedro_> select the right component, version and severity
[14:25] <pedro_> component in this case is : importing
[14:25] <niadh> version well should i put latest or git-master?
[14:25] <pedro_> severity: enhancement
[14:25] <pedro_> niadh: yeap it's still an issue with it so yes
[14:26] <pedro_> git-master is ok
[14:26] <niadh> copy and paste the bug details from lp into bz?
[14:26] <pedro_> niadh: yes, and copy the relevant comments if there's one
[14:26] <pedro_> and also a link to the bug on lp
[14:27] <niadh> not sure many of the comments are relevant
[14:28] <niadh> seem to discuss english language specific meaning rather than bug details
[14:28] <pedro_> after doing all that and submitted the bug, you need to create a bug watch on the lp report: https://wiki.ubuntu.com/Bugs/Watches
[14:28] <pedro_> niadh: yeap
[14:29] <niadh> so it's an also affects this project tag?
[14:30] <pedro_> niadh: what do you mean?
[14:31] <niadh> well when I link the upstream bug
[14:31] <niadh> I presume it's that it affects the project not distro?
[14:31] <pedro_> niadh: yeap you need to click on the also affects project and put the link of the upstream one you reported there
[14:32] <niadh> Thought so :)
[14:32] <pedro_> nice :-)
[14:33] <pedro_> niadh: after doing that, just put a nice comment on the report  saying that you sent the bug upstream and also add a link to that report
[14:33] <pedro_> then you can mark it as confirmed and i'll add the wishlist importance and set it to triaged for you
[14:33] <niadh> ok
[14:34] <niadh> Do I wait for the upstream project to confirm the bug in their system and confirm the first instance of reporting in lp?
[14:35] <pedro_> niadh: yes
[14:35] <pedro_> niadh: don't forget to put a link to the report on lp at the upstream one
[14:35] <niadh> so link to downstream from upstream?
[14:36] <pedro_> niadh: yeah, so they can read about it as well, just add a new comment there saying something like "this report was first filed here: link"
[14:37] <xteejx> Question: As a triager, if I am using Ubuntu and GNOME, with KDE crashes/bugs etc, is it a problem asking them to try and reproduce it in a later version, as I can't do it. ?
[14:38] <xteejx> with me using gnome and them KDE, I kno i can install kubuntu-desktop but I dont have the space
[14:42] <pedro_> xteejx: well i often triage bugs of software i can test with, but would be good to ask them to reproduce it with newer release (ie: Jaunty) if nobody else asked that already
[14:43] <yuriy> xteejx: it's not really a problem, but it's probably better if you work on bugs for software you are familiar with and can test
[14:43] <xteejx> of course guys, but theyre the really old ones, i tend to work back to front :)
[14:43] <xteejx> and dont have kubuntu
[14:43] <pedro_> you can always try with a live cd btw ;-)
[14:43] <yuriy> if they're really old, then please ask
[14:44] <xteejx> mind if i give an example?
[14:45] <xteejx> KDE 3.5 on feisty for instance.....KDE4 and jaunty > user has same problem, they may be using an old version. I use Ubuntu and gnome and do not have the space to install kubuntu-desktop, will i get shouted at by mr murray if i simply ask them to update and try again?
[14:45] <pedro_> niadh: i've marked the bug as triaged-wishlist for you, feel free to mark it as close on the hug day page :-)
[14:45] <niadh> I have done :)
[14:46] <pedro_> rock on !
[14:46] <xteejx> ps pedro, thanks for closing all them incomplete bugs recently for me :)
[14:46] <pedro_> now you know how to forward a bug upstream ;-)
[14:46]  * pedro_ hugs niadh
[14:46] <niadh> I do yes :D
[14:46] <pedro_> xteejx: my pleasure ;-)
[14:46] <xteejx> can i have a hug as well...just for being a bug control member? heh
[14:47] <yuriy> xteejx: if it's feisty then certainly ask. feisyt isn't even supported anymore
[14:47]  * pedro_ hugs xteejx
[14:47] <pedro_> ;-)
[14:47] <niadh> I'm actually going into business for myself soon, hoping at least either tuesday or thursdays I can dedicate to triaging bugs, since I wanna support ubuntu for customers
[14:47] <xteejx> yayy!! lol
[14:48] <pedro_> niadh: awesome, if you have further questions just ask here in the channel , there's always people willing to help :-)
[14:48] <xteejx> yuriy, its a problem in jaunty as well and version differences between their version and current is like 1.1 to 1.1-0ubuntu5 or something, so i have asked them to update :)
[14:49] <niadh> this bug: 342465 claims to have a fix and I can see the star outlines using a dark theme
[14:50] <xteejx> bug 342465
[14:50] <ubot4> Launchpad bug 342465 in banshee "Rating Menu Item not Shown Properly on Themes with Darks Menus" [Undecided,Confirmed] https://launchpad.net/bugs/342465
[14:51] <xteejx> niadh, perhaps it was fixed in latest dev release of gnome, but not in our repos yet
[14:52] <niadh> Nah I tested it in the PPA 1.5 version of banshee I can see the bug is fixed
[14:53] <niadh> It's a confirmed bug but looks fixed so just wondering if I should just mark it off todays list
[14:54] <niadh> also anyone have an integrated card reader on their machine?
[14:58] <xteejx> on my other laptop but its due in for repair lol
[15:00] <niadh> cos there's a bug in the list today that requires access to a non-usb card reader which I don't have access to
[15:47] <bddebian> Boo
[16:07] <xteejx> hey bddebian
[16:07] <xteejx> bencrisford, Still alive then? hehe :)
[16:07] <bddebian> Hello xteejx
[16:07] <bencrisford> hey xteejx, and yeah, just about :)
[16:08] <xteejx> bencrisford, hehe hows ermm "work"? lol
[16:08] <bencrisford> schools school
[16:08] <bencrisford> :P
[16:09] <xteejx> hehe ;)
[16:09] <xteejx> i was being polite calling it work...should have said prison :P
[16:09] <bencrisford> i dont see why its polite,
[16:09] <bencrisford> it beats work work
[16:12] <xteejx> nahh you get paid at work work hehe
[16:12] <xteejx> !info nautilus jaunty
[16:12] <ubot4> xteejx: nautilus (source: nautilus): file manager and graphical shell for GNOME. In component main, is optional. Version 1:2.26.2-0ubuntu2 (jaunty), package size 1226 kB, installed size 3204 kB
[16:21] <xteejx> where did i go?
[16:21] <xteejx> !info kaffeine intrepid
[16:22] <ubot4> xteejx: kaffeine (source: kaffeine): versatile media player for KDE. In component universe, is optional. Version 0.8.6-2ubuntu2 (intrepid), package size 3198 kB, installed size 7116 kB
[17:26] <niadh> I have a confirmed bug that the upstream bug has been fix, do i mark as fix committed or fix released, committed, right?
[17:44] <GrueMaster> If the fix is in the repository but not available for updates, it is committed.  If the fix is available for general updates, it is released.
[17:49] <niadh> I thought so
[17:49] <niadh> So do I mark the launchpad instance of the bug as fix released with the gnome-bugs one as fix commited?
[18:17] <niadh> this bug was marked for deletion 134 days ago and has not yet been deleted 219028
[18:18] <micahg> bug 219028
[18:18] <ubot4> Launchpad bug 219028 in banshee "Crash when editing smart playlist containing more/less than x years criteria" [Undecided,Incomplete] https://launchpad.net/bugs/219028
[18:19] <micahg> niadh: is this your first time triaging bugs?
[18:20] <niadh> No, but I've not done it in about year, and when I was doing it there were somethings I haddn't actually done, this is one of them
[18:20] <micahg> ok, no problem
[18:20] <micahg> just wanted to know how much to explain  :)
[18:21] <micahg> so, the expiration is an automated count once a bug is marked incomplete
[18:21] <micahg> it doesn't necessarily mean it should be deleted
[18:21] <niadh> Oh, I thought it was?
[18:21] <micahg> but in this case, the reporter noted that the bug no longer exists in new versions
[18:22] <micahg> it just means how much time has passed since the last post in teh incomplete state
[18:22] <micahg> so, you can mark invalid with the standard comment
[18:22] <micahg> https://wiki.ubuntu.com/Bugs/Responses#Bugs%20resolved%20after%20update%20or%20config%20change
[18:24] <niadh> cool, thanks
[18:25] <micahg> thank you for triaging :)
[18:28] <niadh> micahg: I have another two bugs I think I can cross off todays bug list if I just know how to do it, they both have upstream reports and both upstream reports are fix released and I am thinking I change the launch pad instance of the bug to fix commited and mark them off the list, is this correct?
[18:30] <micahg> well, are the fixes available in a downloadable package upstream?
[18:31] <micahg> https://wiki.ubuntu.com/Bugs/Status
[18:34] <niadh> One of them I can confirm with my computer that the bug appears to be fixed with the version I am running
[18:34] <micahg> well
[18:34] <micahg> are you running a newer version that the reporter?
[18:34] <niadh> Yes
[18:34] <micahg> ok
[18:35] <micahg> and that version is in the ubuntu repo?
[18:35] <niadh> nope, but it's in a PPA
[18:35] <micahg> ok
[18:35] <micahg> that means it's publicly available
[18:36] <micahg> so Fix Released is fine
[18:36] <niadh> I thought so
[18:36] <micahg> I'm assuming it's a release version in a ppa and not a nightly build
[18:40] <bdmurray> A bug fix in a PPA does not mean the bug is Fix Released
[18:40] <micahg> well, that's why I was asking if it was an actual release or not
[18:41] <micahg> I caught myself after I said it
[18:42] <micahg> ping niadh
[18:42] <niadh> Am here, yes
[18:42] <niadh> Do I need to change something
[18:42] <niadh> ?
[18:42] <micahg> did you catch my second remark?
[18:42] <micahg> I wanted to verify the ppa version was a release version upstrema
[18:42] <bdmurray> The ubuntu bug task should only be fixed released if it is fixed in the official ubuntu package
[18:42] <micahg> bdmurray: that's not what the wiki says
[18:43] <niadh> Change fix released to fix commited then?
[18:43] <micahg> I was wondering about that
[18:43] <micahg> bdmurray: Fix Released: For a bug task about upstream projects: a release tarball was announced and is publicly available
[18:44] <bdmurray> so if a bug has two tasks and one is empathy and one is empathy (ubuntu).  the emapthy one could be fix released and the ubuntu one not
[18:44] <niadh> Am sure banshee 1.5 is a marked release and can be downloaded publically well yes 1.5 is also known as 1.6 beta 1
[18:45] <bdmurray> niadh: Do you have a bug report we can look at?
[18:45] <micahg> ok, so I guess I was unclear on how that worked than
[18:45] <niadh> I have both yes
[18:45] <niadh> 342465 and 326827
[18:45] <bdmurray> micahg: Do you have any ideas on how I can clarify the language?
[18:46] <savvas> bug #342465 bug #326827
[18:46] <ubot4> Launchpad bug 342465 in banshee "Rating Menu Item not Shown Properly on Themes with Darks Menus" [Undecided,Fix released] https://launchpad.net/bugs/342465
[18:46] <ubot4> Launchpad bug 326827 in banshee "Podcasts downloading can't be finished" [Undecided,Fix released] https://launchpad.net/bugs/326827
[18:46] <micahg> bdmurray: maybe just add a note that the Ubuntu task should stay triaged until a maintainer adds teh fix?
[18:46] <micahg> or the new release is avaialable in an ubuntu repo
[18:47] <micahg> I thought it was referring to UPstream vs Ubuntu bugs
[18:47] <bdmurray> micahg: okay, I'll poke at it some today
[18:47] <micahg> now I see the word task staring at me :)
[18:47] <bdmurray> I think I'll do something like "Upstream task - ..."
[18:47] <bdmurray> and then "Ubuntu task - ...."
[18:48] <micahg> yes bdmurray, sounds good to me :)
[18:49] <niadh> So the bugs need to be marked as something else?
[18:50] <micahg> It should be marked triaged until someone commits it to an ubuntu repo
[18:51] <micahg> right bdmurray?
[18:51] <micahg> the fix is in the banshee changelog for 1.5
[18:51] <micahg> and we have 1.4.3-5 in karmic
[18:51] <bdmurray> right, but the comment about which version of Banshee to watch for the fix in is quite helpful
[18:52] <hggdh> bdmurray, I opened bug 391623 for the apport hook
[18:52] <ubot4> Launchpad bug 391623 in evolution "apport hook for Evolution" [Undecided,New] https://launchpad.net/bugs/391623
[18:53] <micahg> niadh: does this bug prevent the app from working?
[18:53] <niadh> Which bug did you mean, the podcast one or the dark menu thing?
[18:54] <micahg> podcast
[18:54] <niadh> not stop the application as a whole from working but it's a broken key feature that shipped with a release version packaged for Ubuntu
[18:56] <micahg> hggdh: is banshee a core app in Ubuntu?
[18:56] <savvas>      1.4.3-3ubuntu2 0
[18:56] <savvas>         500 http://rs.archive.ubuntu.com jaunty/universe Packages
[18:56] <hggdh> micahg, I do not think so
[18:56] <savvas> universe means it's not
[18:57] <micahg> ok
[18:57] <micahg> so core is defined as main
[18:57] <savvas> I think there are talks to be installed by default.. but they are still just talks :)
[18:57] <hggdh> if it is core, it must be in main
[18:57] <micahg> ok :)
[18:57] <micahg> niadh: I marked the podcast bug triaged, you can close it for bugday
[18:58] <micahg> thank you
[18:58] <niadh> well yeah it's not installed by default but it still shipped broken
[18:58] <niadh> anyways
[18:58] <niadh> I have another question
[18:58] <niadh> If a bug has been marked as importance
[18:58] <niadh> as a wishlist
[18:58] <niadh> what do I do
[18:59] <niadh> If the bug is also marked as 'new' as well
[18:59] <micahg> well, if it's an upstream request, you can try to find it upstream in teh bugtracker
[18:59] <niadh> I could confirm it, but by what critieria? The reporter can confirm he wants the feature?
[18:59] <micahg> niadh: reporters cannot confirm their own bugs
[19:00] <micahg> niadh: https://wiki.ubuntu.com/Bugs/Status
[19:00] <micahg> you can confirm if you feel it's a valid request
[19:00] <yofel> hey, any vim users here that could confirm bug 392086 ?
[19:00] <ubot4> Launchpad bug 392086 in vim "[karmic] vim-7.2.148-2ubuntu2 - broken regexp in debchangelog.vim" [Undecided,New] https://launchpad.net/bugs/392086
[19:01] <niadh> I can see where it might be useful, not sure I'd ever use it but I can see it's validity so confirm it, mark it off, move on?
[19:04] <micahg> niadh: do you have a bug #
[19:04] <niadh> 237687
[19:05] <micahg> bug 237687
[19:05] <ubot4> Launchpad bug 237687 in banshee "pause playback on screen lock" [Wishlist,New] https://launchpad.net/bugs/237687
[19:06] <micahg> niadh: I'd say check upstream for a similar request
[19:06] <niadh> fair enough
[19:06] <micahg> if there isn't one, you can file one and add it to the report
[19:06] <micahg> then someone in here can marked it traiged
[19:06] <niadh> right, I can do that
[19:07] <niadh> And for bugs marked as incomplete which I cannot confirm because the bugs don't occur when I follow the reproduction steps?
[19:08] <micahg> niadh: only bug control can mark triaged
[19:08] <niadh> fair enough, is it worth me posting I cannot confirm?
[19:08] <hggdh> yofel, would you mind attaching a diff to your change?
[19:09] <bdmurray> Yes, and please include information about the specific package version you used for testing
[19:09] <micahg> sorry, I've got to get going, can someone else take over please :)
[19:10] <niadh> bdmurray: I can do that :)
[19:29] <niadh> am kinda stuck on this bug 342463 not sure how to continue with it
[19:29] <ubot4> Launchpad bug 342463 in banshee "Wrong Cursor Icon It's Shown On Last.fm LogIn Dialog" [Undecided,Incomplete] https://launchpad.net/bugs/342463
[19:43] <pedro_> niadh: looking
[19:49] <pedro_> niadh: i'm still getting that with git master version
[19:49] <pedro_> niadh: there's some code in banshee for creating that button and it seems to call the right cursor type
[19:50] <pedro_> private static Gdk.Cursor hand_cursor = new Gdk.Cursor(Gdk.CursorType.Hand1);
[19:50] <pedro_> niadh: would be good to have some upstream eyes on it ,could you send it upstream?
[19:51] <pedro_> i'm not 100% sure that it's a gtk# issue
[20:07] <niadh> I could yeah
[20:09] <niadh> pedro_: Just report it upstream, that's all that's needing done?
[20:10] <pedro_> niadh: in that case yeah, then we can mark it as triaged for you
[20:10] <niadh> Cool
[20:11] <pedro_> it's a really small detail though so the severity on the upstream report should be something like "Trivial"
[20:12] <niadh> pedro_: Was gonna ask how it should be marked ;)
[20:12] <niadh> feature or usability?
[20:13] <pedro_> niadh: none of them, it's just a normal issue
[20:14] <pedro_> feature is more when you're requesting something new to be included in the program like youtube video support on banshee for example
[20:14] <niadh> Normal: The application is not functioning correctly.
[20:15] <niadh> I didn't know that the bug fell under that catagory
[20:15] <pedro_> niadh: Trivial is the right severity there
[20:15] <niadh> in the gnome bugzilla trivial isn't an option
[20:15] <pedro_> http://bugzilla.gnome.org/page.cgi?id=bug-status.html#bug_severity
[20:16] <pedro_> niadh: file it as normal if you want to and i change the severity for you
[20:16] <niadh> Ah okies
[20:16] <pedro_> Trivial: Cosmetic problem like misspelled words or misaligned text.
[20:16] <pedro_> which is what we're talking about here
[20:16] <niadh> Cosmetic issue?
[20:16] <niadh> yup
[20:16] <niadh> got it
[20:17] <pedro_> yeah
[20:21] <niadh> Do I need to confirm the bug to link it upstream?
[20:24] <pedro_> niadh: if you sent it upstream, yes the bug on lp should be confirmed
[20:35] <niadh> cool, did wonder why I couldn't link upstream
[20:38] <niadh> bug crossed off
[20:38] <pedro_> niadh: great, just marked it as Triaged and Importance as Low since as said it's just a cosmetic detail
[20:39] <niadh> pedro_: What do I do with bug 355323
[20:39] <ubot4> Launchpad bug 355323 in banshee "Banshee needs to depend on gstreamer0.10-alsa" [Undecided,Confirmed] https://launchpad.net/bugs/355323
[20:39] <pedro_> niadh: feel free to mark it as closed on the wiki,  Thanks for helping out :-))
[20:39] <pedro_> looking
[20:40] <niadh> pedro_: Every time I sort a bug out I deal with it on the wiki
[20:46] <pedro_> niadh: the dependency is already there on the karmic package, you can mark that bug as fixed
[20:46] <pedro_> niadh: just state that on the comment
[20:46] <niadh> ok, thanks
[20:47] <niadh> which fixed? Released or commited?
[20:48] <pedro_> niadh: the package containing the fix is already on the repositories, so fix released
[21:15] <niadh> do we support bugs in the bug tracker for PPC architecture?
[21:17] <micahg> bdmurray: ^^^^
[21:18] <bdmurray> Most likely what bug is it?
[21:19] <niadh> bug 378613
[21:19] <ubot4> Launchpad bug 378613 in banshee "banshee won't start on Jaunty powerpc (Mono.Data.SQLiteClient exception thrown)" [Medium,Triaged] https://launchpad.net/bugs/378613
[21:22] <niadh> looks like it was created on a development branch of ubuntu though
[21:23] <bdmurray> that package version is the final one for jaunty though
[21:23] <BUGabundo> hi everuone
[21:24] <niadh> I mean in the log it says [jaunty (development version)]
[21:25] <bdmurray> niadh: okay, but later they say "banshee is at version 1.4.3-3ubuntu2" which is the official banshee one for jaunty
[21:25] <bdmurray> I think the bug is in a fine state
[21:25] <niadh> I don't think it's a banshee bug, I think it's a bug in the dll that banshee links to
[21:26] <micahg> bdmurray: you got a minute to talk about milestones?
[21:28] <bdmurray> niadh: ppc is a best effort support if I recall correctly, but that doesn't mean it should be won't fix
[21:28] <niadh> Yeah it's not officially supported so I didn't know if we dealt with ppc bugs
[21:29] <bdmurray> micahg: okay
[21:30] <micahg> so, with my new found knowledge of Status, once upstream fixes teh bug, do I change the milestone to whenever I would expect the package to enter ubuntu?
[21:31] <bdmurray> No milestones are for indicating that something needs to be fixed by a certain time
[21:31] <micahg> ah
[21:31] <micahg> so it's a dealine type of thing
[21:31] <micahg> *deadline
[21:31] <micahg> do we have documentation on that?
[21:32] <bdmurray> https://wiki.ubuntu.com/RCBugTargetting
[21:32] <niadh> could bug 381555 be a matter of installing a lame package?
[21:32] <ubot4> Launchpad bug 381555 in banshee "banshee does not transcode oga to mp3 when sending to ipod" [Undecided,Incomplete] https://launchpad.net/bugs/381555
[21:35] <micahg> bdmurray: so milestones are only for bugs with nominations that have been accepted?
[21:35] <BUGabundo> hey kristina
[21:35] <BUGabundo> hi micahg bdmurray torkiano
[21:36] <kristina> hi
[21:36] <torkiano> BUGabundo, hola ;)
[21:37] <bdmurray> micahg: or "developers may use milestone targeting to indicate an intention to deliver the fix for the bug in time for that milestone"
[21:38] <micahg> bdmurray: so, as a triager, do I need to be setting these?
[21:39] <bdmurray> micahg: Nope
[21:39] <micahg> ok
[21:39] <hggdh> normally no, micahg
[21:39] <micahg> thanks :)
[21:39] <hggdh> but there are nominations, that a triager can put in
[21:40] <hggdh> (with a lot of good sense)
[21:40] <micahg> he's my query
[21:40] <micahg> *here's
[21:40] <BUGabundo> hey hggdh
[21:40] <hggdh> hey BUGabundo good evening
[21:40] <micahg> if I see that it's fix released and in debian, but not Ubuntu, what is the normal course of action?
[21:41] <micahg> fix released upstream
[21:41] <hggdh> well. It may be fix released upstream, but still in (say) git
[21:41] <micahg> hggdh: wouldn't that be Fix Commited upstream?
[21:41] <hggdh> i.e., upstream has not yet delivered a disgtribution
[21:42] <hggdh> no. Usually upstream will consider fix released when it is in the source code control system they use
[21:42] <micahg> I guess that brings up anotehr question
[21:42] <micahg> or maybe not
[21:42] <hggdh> for example, gnome -- we have a new version every 6 months, and interin versions in between (for both stable and unstable code)
[21:42] <micahg> ok
[21:43] <micahg> let's assume that it's an actual release
[21:43] <hggdh> ok
[21:43] <micahg> so, if I see it in debian, but not in ubuntu, do I need to do anything?
[21:44] <micahg> assuming after import freeze?
[21:44] <hggdh> it depends. If it is a crasher issue, then you could propose an SRU for it
[21:45] <hggdh> heh. Hold on -- there is *stable* code, and *development* code. Which are you talking about?
[21:45] <micahg> let's say it's not, and it's the development version
[21:45] <micahg> stable code
[21:45] <micahg> release version of upstream
[21:45] <micahg> not in ubuntu devel version
[21:45] <micahg> but in debian unstable
[21:45] <hggdh> for stable and supported code, an upstream fix may be accepted as a SRU
[21:46] <hggdh> for development code, if it is after a the final freeze, it will not be accepted unless it is a critical issue
[21:46] <niadh> what package is it that converts ogg files to mp3 inside banshee?
[21:47] <hggdh> while in normal development, either a sync/merge will do; if sync/merges are done and gone, then you can cherry-pick and propose a debdiff
[22:04] <micahg> ok, thanks hggdh
[22:13] <hggdh> micahg, so we will only go to fix committed/released when the upstream fix is applied in -proposed or -update
[22:19] <micahg> It's nice to know that hggdh :)
[22:26] <niadh> on the bug day wiki, if a confirmed bug needs to be checked to see if it's still an issue, I presume it's fine to check it off if the bug was actually confirmed as a bug only 8 days ago?
[22:27] <micahg> niadh: the next step would be to make sure that it's upstream
[22:27] <micahg> if it needs to be
[22:27] <niadh> it's a jaunty regression, or has claimed to have been
[22:28] <niadh> bug 337075
[22:28] <ubot4> Launchpad bug 337075 in banshee "[jaunty regression] transcoding flac to mp3 for ipod no longer works" [Undecided,Confirmed] https://launchpad.net/bugs/337075
[22:28] <niadh> but with three bugs left on the wiki page I thought I'd see if I can't actually finish the list
[22:30] <micahg> If it's indeed a banshee bug, I'd check upstream to see if it's noted as a regression in that version
[22:32] <micahg> niadh: can you test an intrepid LiveCD to see if that bevavior previously existed?
[22:33] <niadh> No, I don't have a working iPod
[22:34] <micahg> niadh: I'd still suggest searching upstream for something relatesd
[22:34] <niadh> I already have done
[22:34] <micahg> ok, nothing?
[22:34] <niadh> Nothing :(
[22:34] <micahg> did you check resolved bugs as well?
[22:36] <niadh> I put a search in with 'banshee transcode flac mp3' and only got one bug which was to do with coverart size
[22:37] <micahg> try banshee ipod transcode or comething like that
[22:37] <micahg> *something
[22:39] <niadh> nope nothing
[22:40] <micahg> is there a banshee irc channel?
[22:40] <niadh> yeah
[22:40] <micahg> I'd say jump in there and see if that behavior existed previously
[22:40] <niadh> Well I'll do that when I get back then
[22:41] <micahg> thanks niadh
[22:42] <micahg> niadh: there seem to be 2 bugs for this
[22:43] <micahg> bug 381555 and bug 337075
[22:43] <ubot4> Launchpad bug 381555 in banshee "banshee does not transcode oga to mp3 when sending to ipod" [Undecided,Incomplete] https://launchpad.net/bugs/381555
[22:43] <ubot4> Launchpad bug 337075 in banshee "[jaunty regression] transcoding flac to mp3 for ipod no longer works" [Undecided,Confirmed] https://launchpad.net/bugs/337075
[22:43] <micahg> or at least similar
[22:44] <niadh> they're similar yeah but not sure if they are duplicates, one user maintains they could once transcode the other has never been able to
[22:44] <niadh> both I believe are on amd64 arch
[22:44] <micahg> ah, ok
[22:44] <niadh> I have found amd64 and ppc to be bad archs if you want mono libraries
[22:45] <niadh> anyways
[22:45] <niadh> back in about 20-30 min
[23:25] <micahg> Is there anything special for CVE bugs?
[23:26] <bdmurray> micahg: someone on the security team like kees could best answer that
[23:26] <micahg> ping kees
[23:27] <niadh> bk
[23:29] <jdstrand> micahg: just click the security check box and use the Link to CVE functionality in launchpad
[23:29] <micahg> ah
[23:29] <micahg> didn't know that was ther
[23:29] <micahg> is that available to everyone?
[23:29] <micahg> is that after I create the report?
[23:29] <jdstrand> after creating the report
[23:29] <micahg> ah
[23:29] <micahg> thanks
[23:30] <micahg> what type of summary do I need if any?
[23:30] <jdstrand> though, iirc, if you have CVE-2009-xxxx in the report, it may automatically link it
[23:30] <jdstrand> micahg: a link to the patch or another vendor's advisory is nice if it exists
[23:30] <micahg> ok
[23:30] <micahg> thanks
[23:30] <jdstrand> otherwise, just the CVE summary is fine
[23:31] <micahg> jdstrand: if it's public on phpmyadmin.net, I don't need to mark private, right?
[23:32] <jdstrand> micahg: correct
[23:33] <jdstrand> micahg: since you just mentioned a universe package, I might also point out the universe is community supported. if you are able, supplying a debdiff by following https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures would be great
[23:33] <jdstrand> s/out the/out that/
[23:34] <micahg> ok, but I won't be able to get to that for a little while
[23:34] <jdstrand> micahg: any help is appreciated :)
[23:35] <micahg> If upstream markes as critical, does that impact importance in Ubuntu
[23:35] <jdstrand> if it is in main, we prioritize based on criticality
[23:36] <micahg> I'm saying do I mirror the upstream importance or do I rate it based on the Ubuntu criteria?
[23:36] <jdstrand> universe is supported by community members. as such, things get fixed as much as people want to fix stuff
[23:36] <jdstrand> micahg: sure, that is a fine place to start-- it can be adjusted if needed