[00:08] <kermiac> anyone know of a master bugreport for changing minimse/maximise/close to left? or are we just invalidating them with a link to upstreams decision?
[00:21] <kermiac> anyone?? ^^
[01:08] <m0ar> I've got an awful problem. Right after I log on, the next time I press enter my X-server gets restarted. Any ideas? Is this known?
[01:08] <ddecator> m0ar, yah it's known, let me find the report...
[01:09] <ddecator> m0ar, i'm guessing you're on lucid?
[01:09] <m0ar> ActionParsnip: ddecator Yep
[01:09] <m0ar> ddecator: yep*
[01:09] <ddecator> m0ar, bug 532047
[01:09] <ubot4> Launchpad bug 532047 in xorg-server (Ubuntu) (and 1 other project) "Plymouth text-mode splash causes X to crash on first run due to shared tty7 (affects: 84) (dups: 11)" [Undecided,Invalid] https://launchpad.net/bugs/532047
[01:10] <m0ar> ddecator: Yeah, my TTY7 is
[01:10] <ddecator> they're working on a fix right now
[01:10] <m0ar> Bugged
[01:10] <m0ar> So, what can I do?
[01:10] <m0ar> Anything?
[01:10] <ddecator> there is a workaround on the report i believe
[01:20] <hggdh>  OK. eeeBotu is back. Sorry for the problems.
[01:24]  * BUGabundo <3 hggdh
[01:33] <kermiac> ddecator: re no pic in me-menu. already reported bug 525951
[01:33] <ubot4> Launchpad bug 525951 in indicator-me (Ubuntu) (and 1 other project) "Selecting a user image does not apply in the Me Menu (affects: 18) (dups: 2)" [Medium,Fix committed] https://launchpad.net/bugs/525951
[01:34]  * kermiac needs to improves his launchpad-searching-foo
[01:34] <ddecator> haha, good deal, thanks kermiac
[01:34] <kermiac> :)
[01:35] <ddecator> kermiac, doing a google search for "site:bugs.launchpad.net <search terms>" works best for me
[01:35] <kermiac> thanks ddecator I'll have to try that. been using google, but not with the "site:" part
[01:53] <hggdh> yo BUGabundo
[01:58] <kermiac> hggdh: I want to ask your opinion wrt bug reports concerning window controls on the left. I have seen that bug 532633 was invalidated. Do you think it'd be safe to invalidate similarm bug reports & poiny them to https://wiki.ubuntu.com/Brand#New%20GtkThemes, advising that it's a design decision?
[01:58] <ubot4> Launchpad bug 532633 in light-themes (Ubuntu) "[light-theme] please centre window title and order window controls (affects: 7)" [Undecided,Invalid] https://launchpad.net/bugs/532633
[01:58] <kermiac> s/similarm/similar
[01:59] <kermiac> s/poiny/point - bah, fingers not working today
[02:00] <kermiac> or maybe dupe that report (532633) using it as a "master" & invalidate
[02:52] <jamalta> hi there, i have a question abou thtis bug: https://bugs.edge.launchpad.net/ubuntu/+source/f-spot/+bug/533615
[02:52] <ubot4> Launchpad bug 533615 in f-spot (Ubuntu) "F-Spot PicasaWeb export fails when "Export Tags" is checked (affects: 1)" [Undecided,New]
[02:52] <jamalta> that's an upstream bug, right? should i also report it to the gnome bug tracker? if so, how do i link an upstream bug?
[02:52] <jamalta> or do i have to request for someone with more privileges to do so
[02:53] <micahg> jamalta: also affects project allows you to add an upstream bug
[02:53] <greg-g> if you have the upstream bug url, that is :)
[02:53] <jamalta> micahg: ah! thanks :)
[02:53] <nigelb> jamalta: you don't need more rights to add an upstream tracker, you can add it yourself
[02:53] <jamalta> greg-g: of course, will report to gnome's bugtracker
[02:53] <jamalta> nigelb: thanks
[02:53] <jamalta> you guys are helpful! :)
[02:54] <greg-g> we try :) thank you for participating!
[02:54] <jamalta> should i paste the ubuntu-bug output to gnome's bugtracker? i think that might come in handy, no?
[02:54] <nigelb> not entirely
[02:54] <jamalta> oh
[02:54] <nigelb> just give the version of f-spot that you're using
[02:54] <jamalta> nigelb: ok, thanks :)
[02:55] <kermiac> as noone really wants to comment on the issue, I've made bug 532633 a "master bug" for all bugs related to recent "wm controls on the left" change
[02:55] <ubot4> Launchpad bug 532633 in light-themes (Ubuntu) "[light-theme] please centre window title and order window controls (affects: 11) (dups: 2)" [Undecided,Invalid] https://launchpad.net/bugs/532633
[02:56] <nigelb> kermiac: whoa :)
[02:56] <jamalta> thanks everyone for your help
 min,max,close buttons on the left is a bug, right? ;) </sarcasm>
[02:56] <kermiac> yeah... there is at least one other dupe, but I think it needs to be split into 3 diff bug reports
[02:56] <nigelb> yup, its a wishlist
[02:56]  * kermiac grins
[02:57] <kermiac> we're likely to see a whole lot more bugs file regarding that issue
[02:57] <micahg> jamalta: I thoguht that was a design decision
[02:57] <nigelb> yeah
[02:57] <jamalta> micahg: i know, i'm joking :)
[02:57] <nigelb> anyone familiar with flac encoding?
[03:06] <kermiac> micahg: Have you seen firefox utilising around 10% of cpu & 20% or ram? upto 1.5GB sometimes.... I'm thinking it's probably a rogue extension, but I'm not sure
[03:06] <micahg> kermiac: both of those are subjective
[03:06] <micahg> kermiac: how many tabs and what are you doing?
[03:06] <kermiac> ok, that's true :)
[03:06] <micahg> also, what version?
[03:07] <kermiac> I know I use a LOT of windows/ tabs - currently 8 windows open each with around 10 or more tabs. FF ver 3.6
[03:08] <micahg> 8 windows wit 10 each?
[03:08] <kermiac> yeah, that's almost definately my problem then. I need to stop doing so much at once
[03:09] <micahg> kermiac: only if you don't have the RAM :)
[03:09] <kermiac> I've got 32bit karmic installed, so it only sees 3GB ;)
[03:09] <micahg> kermiac: use PAE
[03:10] <kermiac> yeah, I would but that messes with me using usb-creator
[03:10] <micahg> kermiac: why?
[03:10] <kermiac> some older machines don't seem to like pae
[03:11] <micahg> kermiac: I'd say that's a bug :)
[03:11] <micahg> and what old machine supports > 2GB RAM?
[03:11] <kermiac> yeah? I thought that usb-creator would utilise whatever kernel the machine creating the startup disk uses
[03:12] <micahg> idk, shouldn't matter IMHO
[03:12] <micahg> kermiac: I thought it just runs the installer?
[03:13] <kermiac> some of the old clunkers at work don't handle pae kernel - never really looked into it further. I've just avoided installing the pae kernels on the machines I use to create startup disks
[03:13] <kermiac> I don't know exactly what it does, but it copies files from whatever computer you create it on
[03:13] <micahg> kermiac: I thought it copies from the ISO
[03:14] <kermiac> & if I create on a machine using a pae kernel it creates a usb disk with pae kernel
[03:15] <kermiac> Although I haven't tried it on a machine with pae kernel in over 6 months... sounds like I need to take another look at it :)
[03:15] <kermiac> I'll load up a vm & install pae kernel & check
[03:18] <micahg> kermiac: well, are you generating a startup disk from an ISO or from the current system?
[03:18] <micahg> not env, but source
[03:20] <kermiac_> bah, brown-outs :(
[03:23] <kermiac> and the fun begins... already having reports regarding wm controls unduped & set to confirmed :(
[03:23] <bcurtiswx> kermiac: still having brown outs?
[03:24] <kermiac> bcurtiswx: yeah - it's this house. but the electrician can't find the cause :(
[03:24] <bcurtiswx> that does suck
[03:24] <kermiac> yup.. so at least twice a day I have to go flick the switch in the powerbox
[03:27] <bcurtiswx> get a new house
[03:27] <bcurtiswx> :P
[03:28] <nigelb> ddecator: hey, what do you mean by realestate used by rhythmbox?
[03:31] <ddecator> nigelb, hey, there just seems to be more space used then there needs to be. for example, the area that shows the trackbar and the title of the song playing could be shorter and doesn't need to cover the entire width of the player, the buttons are larger than they need to be imo...just little stuff that, if it reduced the amount of space things took up, then there would be more room for browsing music (and eventually the ubuntu
[03:31] <ddecator> one store)
[03:32] <nigelb> ddecator: it just uses up the space because of the track listing
[03:32] <nigelb> actually, in the small version, its much smaller
[03:33]  * ddecator tries small version
[03:34] <ddecator> that doesn't change the height of it for me...the search bar could also be redesigned so that it doesn't have to take up as much space either...but it's more of a personal preference, i like things like that to be as minimal as possible ;)
[03:34] <nigelb> ddecator: since its going to be hidden all the time, I really dont mind the size ;)
[03:36] <ddecator> nigelb, true haha, i just think it would be more user-friendly if the browsing area was larger...for example, moving the trackbar up to in-between the control buttons and the volume would save a lot of room and raise the height of the browsing area quite a bit
[03:36] <nigelb> ddecator: yes it would, but I think its a gnome standard
[03:37] <nigelb> its like a tool bar
[03:38] <ddecator> well it works and there isn't anything inherently wrong with the design, it just doesn't fit my personal preferences =)
[03:41] <ddecator> nigelb, i do think something should be done with the "home" button (not sure what it's called) since it doesn't portray it's function very well...
[03:42] <nigelb> ddecator: home?
[03:43] <ddecator> nigelb, the button that displays a house, but adjusts the view in the browsing area (either has the Artist and Album filters or not)
[03:43]  * nigelb sees no such button
[03:44] <ddecator> ...
[03:44] <ddecator> lucid?
[03:44] <nigelb> nope
[03:44] <nigelb> ah
[03:45] <ddecator> next to the visualization button?
[03:45] <nigelb> must be new feature
[03:46] <ddecator> huh, let me get a screenshot so you can see what i mean...
[03:47] <ddecator> nigelb, http://imgur.com/OtV1e.png
[03:48] <nigelb> ddecator: you say it takes too much space? the karmic one takes more
[03:48] <nigelb> and i have no clue what it does.  need to update to lucid sometime
[03:49] <ddecator> nigelb, that house button just makes the Artist and Album filters either display or be hidden, so it doesn't communicate it's function well at all imo (i can file a wishlist bug if you want)
[03:49] <nigelb> ddecator: please do.  upstream ;)
[03:50] <ddecator> nigelb, and yes, this is similar to what i would like to see rhythmbox look like: http://www.omgubuntu.co.uk/2010/03/rhythmbox-reimagined-prepare-to-wow.html
[04:01] <ddecator> nigelb, ah, it changes depending on your icon theme...
[04:08] <nigelb> ddecator: oh, then you need to file against the theme
[04:08] <ddecator> nigelb, yah, that's what i figured, i'm trying to find the icons so i can figure out what the title of the icon is...
[04:08] <nigelb> ddecator: ah :)
[04:27] <ddecator> nigelb, you wouldn't happen to know a way for me to see what file rhythmbox looks for to use for that button? i have no idea what size or category it will be under...
[04:27]  * nigelb looks into source
[04:29] <nigelb> ddecator: can you give me the tooltip text for it
[04:29] <ddecator> nigelb, "Change the visibility of the browser"
[04:39] <nigelb> ddecator: no clue buddy.  tried
[04:40] <ddecator> nigelb, thanks, i appreciate you trying. i'm just trying to find the icon so i can know what exactly is going on...
[04:41] <nigelb> ddecator: ask vish or qense, they should know
[04:41] <ddecator> nigelb, thanks
[04:41] <ddecator> vish, you around?
[04:53] <vish> kermiac: tried searching in the light themes?
[04:53] <nigelb> vish:  how do we see the icon calls in source?
[04:53] <kermiac> vish: huh?
[04:53] <ddecator> vish, was that meant for me?
[04:53] <vish> kermiac: upstream in this case is ubuntu[themes] , not gnome
[04:54] <kermiac> vish: sorry, didn't know what you were referring to for a sec ;)
[04:54] <vish> kermiac: ubuntu[themes] is probably not the exact package name.. , the project has not been made public anywhere , so there is no upstream link yet
[04:55] <kermiac> so far I've just duped all of the bug reports I have found so far into one master bug report as there was already a fair amount of discussion regarding the issue in bug 532633
[04:55] <ubot4`> Launchpad bug 532633 in light-themes (Ubuntu) "[light-theme] please centre window title and order window controls (affects: 15) (dups: 4)" [Undecided,Invalid] https://launchpad.net/bugs/532633
[04:56] <ddecator> ohhh, that, haha
[04:58] <vish> !test
[04:58] <ubot4`> hrm?
[04:58]  * kermiac laughs
[04:59] <vish> hmm , damn irc lag :/
[05:00] <kermiac> micahg: wrt usb-creator & pae - seems like the issue may have been a local &/or old problem. It doesn't copy the pae kernel over now :)
[05:01] <micahg> k
[05:02] <vish> kermiac: the bug is not invalid , the themes are still expected to undergo a lot of changes
[05:02]  * vish setting it to confirmed until a final decision is made
[05:03] <kermiac> vish: I didn't invalidate it
[05:03] <kermiac> it was already set to invalid
[05:04] <kermiac> i was wanting some more advice on the issue earlier as I wasn't sure if I should set it back to confirmed or not
[05:04] <kermiac> I just cleaned up the excess reports for now until I could find someone else to discuss the issue with
[05:06] <ddecator> vish, does that also mean i shouldn't file a bug with the ubuntu-mono-light icon theme?
[05:08] <kermiac> ty for clearing that up vish :)
[05:08] <vish> ddecator: which bug?  my irc is a bit lagging.. i might have missed something..
[05:09] <vish> which icon bug*
[05:09] <nigelb> vish: slow connection?
[05:09] <vish> nigelb: nah , i had transmission set to unlimited ;)
[05:10] <nigelb> vish: that was next :p
[05:10] <vish> just now stopped it and got back pages of scrollback :(
[05:10] <ddecator> vish, with rhythmbox the "Change the visibility in the browser" button is a house with the ubuntu-mono-light theme...which makes no sense
[05:10] <nigelb> set it to 30 for sanesness
[05:11] <vish> ddecator: sure file one , with the screenshot.. none of the canonical themes/icons are yet hosted publicly , when it is will be decided
[05:11] <vish> they are still WIPs , just been pushed early due to UI freeze
[05:12] <nigelb> vish: how do we see the code for that thing
[05:12] <nigelb> i.e. the code for the icon to see where it is referenced?
[05:12] <ddecator> vish, alright, what package would i file it against?
[05:12] <vish> nigelb: ubuntu-mono, i guess
[05:12] <nigelb> vish: shouldn't rhythmbox code have a call to an icon or theme?
[05:13] <ddecator> ah, there it is...
[05:13] <vish> nigelb: hmm , you can check the icon name in the /usr/share/icons
[05:13] <nigelb> vish: aha :)
[05:14] <ddecator> i haven't actually filed a report in so long...
[05:14] <nigelb> hehe
[05:15] <nigelb> ddecator: I got lost a bit when I had to file one for FFE too ;)
[05:15] <ddecator> nigelb, so does that mean you know what icon rhythmbox is calling for so i can include it in the report?
[05:15] <ddecator> nigelb, haha, i used to do this a lot, but never on lp...
[05:15] <nigelb> ddecator: i'm not on lucid, so you have to check at your end
[05:15]  * vish still doesnt know which the icon ddecator and nigelb are talking about
[05:16] <vish>  screenshot would help ;)
[05:16] <nigelb> vish: http://i.imgur.com/OtV1e.png
[05:16] <ddecator> vish, in rhythmbox, the "Change the visibility of the browser" icon is a house...
[05:16] <nigelb> vish: thoughts on possible replacement?
[05:16] <vish> hmm... that is an icon from humanity
[05:17] <vish> the rhythmbox is the culprit here , it uses that icon
[05:17] <vish> iirc
[05:17] <vish> ddecator: hasnt it been that way for a long time?
[05:17] <ddecator> vish, idk, but it changes for some icon themes
[05:18] <ddecator> i just started using it today because of songbird problems
[05:18]  * ddecator stops filing report
[05:18]  * micahg switched to banshee actually...
[05:18] <nigelb> vish: I dont see that thing for karmic RB
[05:18]  * nigelb is going to check RB source to see if its a new feature
[05:18] <vish> nigelb: hmm , its been that way since karmic
[05:19] <nigelb> vish: then for some reason I have it disabled.  I dont see the house icon
[05:19] <ddecator> depending on the icon theme, i either get a house, or a stack of cds...
[05:19] <ddecator> nigelb, what do you see?
[05:19] <nigelb> ah, I get a stack of CDs ;)
[05:19] <ddecator> aha!
[05:19] <vish> ddecator: yeah , gnome is a stack of cd's
[05:19] <ddecator> still not a very good icon imo
[05:20] <vish> ddecator: somewhere we seem to have added an extra symlink..
[05:20] <ddecator> vish, gonna be honest, not sure what that means...
[05:21] <vish> ddecator: instead of using a separate icon for that there is probably an extra symlink somewhere which points to the house icon.. [not sure how to explain]
[05:22] <ddecator> vish, ah, ok, i get what you're saying. so is that an upstream or downstream problem?
[05:22] <nigelb> downstream, theme specific
[05:22] <ddecator> fair enough
[05:23] <vish> nigelb: it is upstream theme specific as well ;)
[05:23] <nigelb> vish: bah! themes are complicated
[05:23] <ddecator> ...so file on both?
[05:24] <vish> ddecator:  sure you can ..
[05:25] <ddecator> vish, alright, i'll let you guys determine whether or not they should be linked
[05:25] <vish> ddecator: linked? humanity is hosted in lp
[05:26] <ddecator> vish, right, but my suggestion will be to have a pre-determined icon instead of having it be theme-dependent
[05:27] <nigelb> ddecator: all icons change with themes
[05:27] <nigelb> they need to
[05:27] <nigelb> or else we'd have white icons in a dark theme ;)
[05:27] <ddecator> huh, i thought apps could set their own icons for use within the app
[05:28] <vish> ddecator: seeing that humanity and rhythmbox would probably be dropped for lucid +1 .. we are spending way too much time on this bug ;p
[05:28] <nigelb> vish: isnt banshee coming in?
[05:29] <ddecator> vish, true, but isn't the ubuntu-mono-* theme going to be used? that's what i'm using right now and it's using the same icon, unless they are going to be changed
[05:29] <vish> nigelb: probably for lucid+1 ..
[05:30] <nigelb> but since it will only be main -> universe, it still significant ;)
[05:30] <vish> ddecator: ubuntu-mono is not a complete theme.. ;) it has only the panel icons , the rest of the icons are from humanity
[05:30] <vish> ddecator: that one is a humanity icon
[05:31] <ddecator> vish, ah, gotcha...so should i still file the report, or is it not going to be looked at? haha
[05:31] <vish> ddecator: file one , if i have time i'll fix it :)
[05:31] <ddecator> vish, fair enough
[05:31] <ddecator> i thought rhythmbox was going to be around for a while since it will have the ubuntu one music store first...
[05:32] <persia> rhythmbox is likely to be around for a while whether it's default or not.  If it's buggy, please triage as usual and try to get stuff fixed.
[05:33] <persia> Given that banshee won't even start on some architectures, I'm certain it will continue to have users.
[05:33] <ddecator> persia, good point
[05:33] <micahg> persia: banshee is slated to be default at some point?
[05:34] <persia> micahg: There are rumours to that effect.  I have no idea how true they may be.
[05:34] <vish> micahg: it was supposed to be in Karmic itself , but upstream didnt have a stable tarball in time and there were a few other confusions as well
[05:34] <persia> (for some value of "supposed to be")
[05:34] <nigelb> well, there is the store
[05:34] <nigelb> right now its only in
[05:34] <nigelb> RB
[05:34] <persia> Anyway, doesn't matter.
[05:35] <vish> nigelb: yup , since it is default ;)
[05:35] <persia> Some people use one thing.  Some people use another.  We ought try to support both.
[05:35] <nigelb> main -> universe is not much
[05:35] <micahg> we have many music players :)
[05:35] <nigelb> we still support the thing
[05:35]  * vish still uses rhythmbox :)
[05:35]  * nigelb too!
[05:35] <persia> Bugs don't get less interesting just because they are in non-default apps: they just get less commonly-reported.
[05:35] <vish> persia: that makes life more easy ;)
[05:37] <vish> persia: re: (for some value of "supposed to be") , that was what the desktop team mentioned as the reason for dropping banshee for karmic
[05:38] <persia> vish: My issue is that "supposed to be" implies there is some strong driving force, rather than just people reviewing which packages happen to meet what they believe to be common use cases better each cycle.
[05:38] <persia> vish: So, there's absolutely no reason we especially like rhythmbox or banshee or mpd or any of the others.
[05:39] <persia> The one that a given flavour's developers think happens to integrate best for each release gets selected by default, and lots of users choose alternates.
[05:40]  * micahg needs to work on getting Songbird into archive..maybe lucid +1
[05:40]  * ddecator would appreciate that
[05:41] <vish> persia: AFAIK , there was a driving force for banshee as default.. but that stopped with slow upstream , [i vaguely recall uds-k also having a discussion on the change]
[05:41] <micahg> banshee is what I use since it supports shoutcast and poodcsts
[05:41] <persia> vish: There was no driving force: it was a result of some people thinking it was good and an analysis of integration and support for use cases.
[05:42] <vish> persia: ah , gotcha..
[05:42] <persia> vish: Don't assume that there exists a secret cabal that says "This is the direction": UDS exists precisely because of the absence of such a body.
[05:42] <persia> Some people argue with greater weight than others, but that's a matter of mutual respect, rather than a matter of who "controls" stuff.
[05:43] <persia> Also, not all flavours agree on the right solution, so there is often divergence within Ubuntu (and on official images).
[05:44] <vish> persia: hehe , didnt assume secrets cabal  , for karmic papercuts  , banshee was kept in the loop for sometime , then we dropped it from the papercuts , since the desktop team was no longer interested , thats how i knew of this :)
[05:44] <nigelb> well, one thing I gotta tell ya. the rhthmbox upstream is a great bunch who's friendly
[05:44] <nigelb> well, there are a couple pissed off with ubuntu moments, but generally, they're pretty nice
[05:45] <ddecator> i should get to know some upstream mozilla people...
[05:45] <persia> That's always going to be the case with distro/upstream discussions *)
[05:45] <vish> persia: i'm not having a personal opinion on either players , i use rhythmbox.. didnt like banshee when i tried it long time ago ;)
[05:45] <persia> vish: Understood.  I just try to argue against imprecise language that implies all of Ubuntu isn't a cooperative venture when I encounter it :)
[05:46] <vish> ;)
[05:59] <ddecator> wow, upstream rhythmbox people are on top of things...
[05:59] <nigelb> ddecator: got a reply already?
[05:59] <ddecator> nigelb, they already marked it a dupe X)
[06:00] <nigelb> ddecator: I told you so ;)
[06:00] <nigelb> johnathan?
[06:00] <ddecator> yup, no h in his name though
[06:00] <nigelb> I spell bad
[06:00] <ddecator> haha
[06:01] <ddecator> i saw that report too and i didn't look because i didn't think there was any way it was what i was looking for...oops
[06:06] <ddecator> micahg, do you generally recommend having people try bugs in safe mode, or with a new profile?
[06:07] <micahg> new profile
[06:08] <ddecator> what's the best way to do that? 'firefox -p --no-remote' ?
[06:11] <micahg> ddecator: http://pastebin.ubuntu.com/390119/
[06:11] <ddecator> micahg, perfect, thanks
[06:24] <ddecator> oh good, two bugs that the reporters made public with coredumps...
[06:26] <persia> ddecator: Happens sometimes.  Simple to clean up, and at least it was the *reporter* that exposed it.
[06:26] <ddecator> persia, very true. i'm marking them private again and letting them know why
[06:26] <micahg> ddecator: you can vote for bug 505370
[06:26] <ubot4`> Launchpad bug 505370 in malone "disable ability to make public if attachments should be private (affects: 2)" [Low,Triaged] https://launchpad.net/bugs/505370
[06:26] <ddecator> micahg, will do
[06:27] <persia> ddecator: In those cases, I usually remove the coredump and leave them public.
[06:28]  * persia goes to argue against 505370
[06:28]  * micahg is curious to see persia's argument
[06:28] <wgrant> Unfortunately removing attachments isn't very effective.
[06:28] <ddecator> persia, what if retrace failed? should i make it private and let someone look at it?
[06:30] <ddecator> and in the other it still needs retrace, so shouldn't the coredump stay attached for now?
[06:30] <micahg> bug 39298 is the one that really should be fixed
[06:30] <ubot4`> micahg: Bug 39298 on http://launchpad.net/bugs/39298 is private
[06:30] <micahg> oops
[06:31] <micahg> I meant bug 39674
[06:31] <ubot4`> Launchpad bug 39674 in malone "Attachments of private bugreports are public (affects: 1) (dups: 3)" [Medium,Triaged] https://launchpad.net/bugs/39674
[06:31] <wgrant> The Private PPA infrastructure makes that feasible now.
[06:31] <persia> I can't even see bug 39298
[06:31] <ubot4`> persia: Bug 39298 on http://launchpad.net/bugs/39298 is private
[06:31] <micahg> persia: wrong bug
[06:31] <wgrant> Although it's hard to privatise public files.
[06:32] <persia> Ah.
[06:32] <persia> Attempting to "privatise" public files is just a false impression.  The file may have been (and perhaps has provably been) exposed previously.
[06:32]  * nigelb agrees with persia's argument
[06:33] <nigelb> (in the bug)
[06:34] <ddecator> the extra warning is a good idea
[06:35] <nigelb> especially when changing from private -> public
[06:35] <micahg> persia: I would assume similar ACLs to the report a bug could be instituted so -control members can do what they want
[06:35] <wgrant> Restricting bug permissions should not be done lightly.
[06:36] <persia> micahg: Potentially, but that doesn't help upstream developers :)
[06:37] <micahg> persia: upstream devs that want to can become part of -control
[06:38] <ddecator> one bug failed retrace, the other still hasn't been retraced, so coredumps should stay attached and reports made private for now as a precaution, yes? that's my understanding from the wiki (but i haven't had to deal with this much before)
[06:39] <persia> ddecator: That's correct, but once a bug is public, it can't really be made private again, because it's been posted to the ubuntu-bugs ML.
[06:40] <ddecator> persia, right, but it's better than nothing i suppose...
[06:41] <persia> Really, no.  The artifacts have already been exposed.
[06:41] <persia> It doesn't make any difference.
[06:43] <micahg> persia: the links are sent to the ML?
[06:43] <persia> micahg: Most upstream devs aren't involved enough to know how.  Also, lots of folk are helpful, and may know the upstream code, but may not be able to convince jcastro they qualify as "upstream devs".
[06:45] <micahg> persia: fine, but I'd say most users don't know that coredumps might contain private info and make the bugs public
[06:45] <micahg> users can be subscribed to private bugs so they can see them AFAIK
[06:46] <persia> The links are sent to the ML for all attachments (check your bugmail).  Lots of users don't know better, but that doesn't need to break things for people that do.
[06:46] <micahg> the other way is not true
[06:46] <persia> We can't cure a lack of erudition by technical means.
[06:58]  * persia curses OTR
[06:58] <persia> micahg: Users can only be subscribed to private bugs.  They cannot subscribe to private bugs.
[06:59] <micahg> persia: right, but the point is you can get someone to look at your bug if you want, it doesn't work the other way around
[07:00] <persia> I don't understand.  Could you rephrase?
[07:02] <micahg> you can subscribe an upstream dev to a bug to have him look at it, you can't really make a bug private again once it's public
[07:03] <persia> We're arguing about different things.
[07:03] <persia> I completely agree you can't make a public bug private.
[07:04] <micahg> persia: I'm saying that there's a workaround for your issue, but not for mine
[07:04] <persia> I disagree that we can identify the set of folk who want to work on a bug unless we are them.
[07:04] <persia> I also disagree that specific artifacts are inherently private, although I agree that some artifacts are more likely to contain private information than others.
[07:05] <persia> What's the workaround for my issue?  I'd have to know in advance who would be able to look at the coredump.
[07:05] <micahg> persia: right, so we would have the option to determine if an artifact isn't private and change the status of the bug/artifact
[07:05] <persia> If I don't know, I can't expose it, even if I know it contains no private information.
[07:05] <micahg> persia: no, YOU would be able to, but not a regular user
[07:06] <micahg> I should add that to my bug
[07:06] <persia> If we change Malone so that we can't make a bug public if it has certain classes of artifact, we can't do that.
[07:06] <persia> That's my only argument against 505370.
[07:06] <persia> If it can be made public, then I'm fine.
[07:06] <micahg> persia: I wuold suggest the same type of ACL that the Report a bug feature has in UBuntu
[07:06] <micahg> only -control can see/do it
[07:07] <persia> That assumes that members of bug control know more about privacy.
[07:07] <micahg> persia: that's one of the requirements for -control I thought...
[07:07] <ddecator> knowing how to handle private bugs is
[07:07] <persia> I argue that whether someone has done something to become a member of some group on launchpad is entirely unrelated to whether they understand if particular information is private.
[07:07] <ddecator> knowing exactly how to determine if there is private info is not
[07:08] <persia> Yes, it's a requirement for control that one knows, but there are folk who are not in control that also know.
[07:08] <persia> And there are lots of *other* projects that use Malone that have nothing to do with Ubuntu.
[07:08] <micahg> persia: true, but I'm suggesting this for Ubuntu only
[07:08] <persia> (and may have completely different processes and procedures)
[07:08] <persia> Malone doesn't work that way.
[07:09] <micahg> persia: sure it does, we have special things in Ubuntu
[07:09] <persia> Like what?
[07:09] <micahg> the report a bug link is only hidden in UBuntu AFAIK
[07:11] <persia> No, it can be hidden for any project, as determined by project bug contact (or maybe owner or drivers, I forget)
[07:11] <wgrant> Uh, well, actually.
[07:11] <wgrant> The thing that redirects to the wiki page is an Ubuntu-specific hack.
[07:11] <micahg> I don't see a link like that anywhere
[07:11] <wgrant> 'ubuntu' is hardcoded.
[07:12] <wgrant> There are one or two other Ubuntu-specific hacks.
[07:12] <persia> Surely those are bugs though, and we shouldn't be introducing more.
[07:12] <wgrant> Precisely.
[07:13]  * persia uses @ubuntu.com as default on LP (and it works).  That just happens to be very fragile, and doesn't currently work for new people setting @ubuntu.com as default.
[07:13] <wgrant> The ubuntu.com hack isn't actually in LP.
[07:13] <wgrant> It just uses the LP database.
[09:07] <arand> Bug #300777 as a dupe of Bug #418135, correct? (Just wanted another pair of eyes since they're security bugs.)
[09:07] <ubot4`> Launchpad bug 300777 in nautilus (Ubuntu) (and 1 other project) "cut and paste of link alters permissions of linked file. (dup-of: 418135)" [High,Triaged] https://launchpad.net/bugs/300777
[09:07] <ubot4`> Launchpad bug 418135 in glib2.0 (Ubuntu Karmic) (and 6 other projects) "Permissions of symlinked source file/folder set to 777 if symlink is copied via nautilus (affects: 4) (dups: 1)" [Medium,Fix released] https://launchpad.net/bugs/418135
[12:36] <persia> nigelb: I guess, but see comment #7
[12:36] <nigelb> persia: oh no
[12:36] <persia> hrm?
[12:37] <nigelb> the bug is somewhere deep in pymsn code
[12:37] <persia> Ah.
[12:37] <persia> So there is a bug there, but no patch yet.
[12:37] <nigelb> or perhaps I should say deep in pymsn code too!
[12:38] <persia> Well then.  That's a triaged bug, but doesn't have a patch yet.
[12:38] <persia> So you get to choose: triage a new bug, hunt a new patch, or go play pymsn developer :)
[12:38]  * nigelb chooses first option
[12:38] <nigelb> or second
[12:38] <persia> heh
[12:39] <persia> I think most of us would :)
[12:39] <nigelb> do you want me to followup that bug?
[12:39] <persia> Immaterial to me.  I don't use the software :)
[12:39]  * nigelb too
[12:39] <nigelb> I dont use msn either
[12:39] <persia> The bug appears to be triaged, and doesn't have a patch.
[12:40] <persia> Needs someone to dig deep.
[12:40] <nigelb> someone who knows this stuff
[12:40] <persia> Indeed.  Some of us may fall into that category, but I'm not sure either you or I do.
[12:41] <nigelb> I thought you did, but I certainly dont
[12:41] <nigelb> did you get a copy of the mail I sent to brian?
[12:41] <persia> I did.
[12:42] <nigelb> can you poke him when you catch a hold of him so we can get things moving?
[12:42] <nigelb> I see a lot of patches that could be rejected right away
[12:42] <persia> Nah.  I know *lots* about shell and make, and I can usually fix a crash for any language (because 99% of the time it happens because the programmer didn't read the API docs carefully or the code is old), but when it comes to stuff like that, I'm lost.
[12:42] <persia> nigelb: On which grounds?
[12:43] <nigelb> oh, forget. silly me
[12:43] <nigelb> its a debdiff, thats supposed to be marked as patches :)
[12:44] <nigelb> we need a way to remove the ones that have already been fixed out of the way
[12:44] <persia> Other than "Fix Released" ?
[12:44] <persia> What's an example?
[12:44] <nigelb> bug 437446
[12:44] <ubot4`> Launchpad bug 437446 in ubuntu-docs (Ubuntu) "Need documentation on Grub2 (affects: 6) (dups: 2)" [High,Fix committed] https://launchpad.net/bugs/437446
[12:44] <nigelb> its a doc team bug
[12:44] <stdouts> hi I've got some problems with opensource radeon drivers, Xorg hangs and I dont know where to find any logs
[12:45] <persia> stdouts: Generally using `apport-bug xserver-xorg` will grab the right logs, etc.
[12:46] <stdouts> I will try, but I have to manually reboot (with the power switch) after Xorg hangs
[12:46] <persia> And X hangs whenever you boot?
[12:47] <persia> Or does it stay up long enough to file a bug?
[12:47] <stdouts> as soon as I run opengl apps
[12:48] <persia> nigelb: That looks like the right status to me: rocket2dmn has set Fix Committed after committing to lucid.
[12:48] <persia> nigelb: Just needs to be tracked so if/when an upload happens it gets closed.
[12:48] <nigelb> yup, thats where I was getting
[12:48] <nigelb> I removed Fix Commited bugs out of the way
[12:48] <nigelb> no its down to 1990
[12:48] <persia> Ah, in your advanced search :)
[12:49] <nigelb> yup
[12:49] <nigelb> isn't that the right way to go about it?
[12:49] <persia> What's that URL again?
[12:49]  * persia feels like doing one
[12:49] <stdouts> persia it mostly occurs if I run full screen opengl apps e.g. games/screen savers/s it usually crashes before I can get any feedback from console
[12:49] <persia> Well, some people might set the wrong status, but that happens for all kinds of bugs.
[12:49] <persia> stdouts: Then reboot and file a bug *before* you play a game.
[12:50] <persia> If more details are required, the team that reviews those bugs will surely ask.
[12:50] <stdouts> ok thanks
[12:50] <nigelb> persia: http://bit.ly/aHAaBP
[12:50] <nigelb> (its long to be pasted in one shot)
[12:50] <persia> heh.
[12:51] <nigelb> ah yes.  we also need a way to remove bugs that has fix ready
[12:51] <persia> https://bugs.launchpad.net/ubuntu/+bugs?orderby=-date_last_updated&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.omit_dupes=on&field.has_patch=on is shorter, but does the same thing.
[12:53] <nigelb> aha, how did you do that?
[12:54] <persia> Took out all the &foo=& entries.  If they are going to be null anyway, no point including them in the URL.
[12:54] <nigelb> custom edit, cheater ;)
[12:55] <nigelb> take a look at bug 520685
[12:55] <ubot4`> Launchpad bug 520685 in nautilus (Ubuntu) (and 1 other project) "Opening "Computer" with nautilus fails 1st time after login when using Extra Pane view (A.K.A "split view mode") (affects: 3)" [Low,Triaged] https://launchpad.net/bugs/520685
[12:56] <persia> nigelb: that's in the sponsors queue, and looks like it just needs a sponsor.
[12:56]  * persia is increasingly thinking we need to find a way to get sponsors queue stuff *out* of the bugtracker.
[12:56] <nigelb> persia: oh, well, your cup of tea ;)
[12:57]  * persia can't sponsor that.  Needs a desktop dev or core dev
[12:57] <persia> (LP thinks I am, but I'm not really)
[12:57] <nigelb> me too.  I have seen at least 4 bugs in sponsor queue or release queue
[12:57]  * nigelb looks on tweaking that link even furhter
[12:57] <persia> LP can't handle negative subscription searches, unfortunately.
[12:58] <nigelb> oh no
[12:58] <nigelb> so, we need to work with tags
[12:58] <vish> persia: actually , someone added the sponsors for that.. isnt the new process to add the review team first?
[12:58] <persia> vish: Why?  That's a candidate for sponsoring.
[12:58] <nigelb> actually, review is already there
[12:58] <persia> Doesn't need review.  Done by a developer, etc.
[12:58] <persia> vish: As I understand it, it works like this:
[12:59] <persia> If there is a patch or suggested solution, the review team reviews it, makes sure it's been reported to the right places, etc.  Basic triage stuff.
[12:59] <persia> Once it's known good, someone on the review team uploads it.
[12:59] <persia> Sometimes that person needs a sponsor, sometimes they don't.
[13:00] <persia> But stuff in the sponsors queue is *already* reviewed and prepared for upload.  Nothing for us to care about.
[13:00] <nigelb> vish: that doesn't need patch tag :)
[13:00] <vish> ersia: righto , didnt know arand was a nautilus dev.. i just thought it was a proposed patch
[13:00] <persia> (well, nothing for us, as triagers, to care about.  Some of us are also developers)
[13:00] <nigelb> debdiff != patch
[13:00] <nigelb> its already ready
[13:00] <persia> Well, a debdiff *is* a patch, but a patch is not always a debidff.
[13:01] <persia> Kinda like squares and rectangles.
[13:01] <nigelb> well, you got what I meant
[13:01] <vish> nigelb: heh ;p , i just followed what brian has been doing ;)  even a debdiff needs review
[13:01] <nigelb> vish: nope
[13:01] <nigelb> vish: debdiff is ready for upload
[13:01] <persia> vish: debdiff doesn't usually need review from the reviewers team.  That's for the sponsors.
[13:01] <persia> vish: I think you're getting confused between what bdmurray does personally, and what bdmurray's scripts do.
[13:02] <vish> persia: ah maybe, gotcha
[13:03] <nigelb> but that bug needs release team and an ffe though
[13:03] <persia> Needs a bunch of stuff, but that's arand's tasks (although we can help if asked or if it ages).
[13:03] <vish> nigelb: the extrapane bug needs FFE?
[13:03] <nigelb> anything not uploaded yet needs ffe
[13:04] <persia> vish: Sure.  It's a new feature, right?  An extra pane?
[13:04] <persia> nigelb: That's not true.  Lots of stuff doesn't need FFe.  especially stuff like crash bugs.
[13:04] <vish> persia: it is a bug in the extra pane , not adding new feature
[13:04] <persia> Oh, then it doesn't need FFe.
[13:04] <persia> Does it change the UI?
[13:04] <persia> (for screenshots & stuff)
[13:05] <nigelb> persia: oh yeah! sorry.  mistook UI freeze for the beta freeze
[13:05] <vish> persia: nope.. it is a bug caused when the extra pane is visible , which is not the default
[13:05] <nigelb> vish: lucid specific?
[13:05] <vish> nigelb: yup
[13:05] <persia> vish: defaults don't matter for freezes.
[13:05] <vish> nah , i was mentioning how the bug happens
[13:05] <nigelb> vish: aha, no wonder I couldn't reproduce it.  someone should mention it there
[13:06] <persia> vish: If it changes the UI, it needs a UIFe.  If it doesn't, it doesn't.  Simple.
[13:06] <nigelb> or I need to look for it ;)
[13:06] <nigelb> persia: well, until thursday ;)
[13:06] <vish> nigelb: its int he first comment ;)
[13:06] <vish> the*
[13:06] <nigelb> vish: like I said, I need to start reading ;)
[13:06] <persia> nigelb: That would be a BFe.
[13:07] <nigelb> persia: hm, a bug I fixed need an IFe
[13:07] <persia> nigelb: What's that?
[13:08] <nigelb> persia: the short name thing
[13:08] <nigelb> I only noticed now that it changes UI and no one got it before then
[13:08] <persia> Oh, UIFe.
[13:08] <persia> Yeah, probably.
[13:08] <vish> persia: yup , FF and UIF are clear , but i had one doubt , is the upstream string freeze the same as our FF
[13:09] <persia> vish: I don't tend to track upstream schedules.  Our string freeze is 25th March this year.
[13:10] <vish> ah k..
[13:10] <persia> (which is why UI Freeze is so important: the docteam only has 3 weeks to complete all the docs)
[13:11] <nigelb> thoughts on whether I should go for UIFe or leave as such to be fixed upstream?
[13:12] <flyingstar16> stupid question: anybody knows if the membership to the bugsquad requires an approval time, after posting to the list (and being answered from - as I was - Marcos Vanetta?
[13:12] <nigelb> flyingstar16: it needs as much time as an admin needs to see it
[13:12] <vish> nigelb: why UIFe ? i still dont see the UI change there? [nautilus bug]
[13:13] <nigelb> vish: not that, I was talking about a bug I fixed
[13:13] <vish> nigelb: ah.. nvm me
[13:13] <nigelb> vish: bug 529744
[13:13] <ubot4`> Launchpad bug 529744 in gnome-system-tools (Ubuntu) (and 2 other projects) "When creating a new user, "Shortname" should really be "Username" . (affects: 1)" [Low,Triaged] https://launchpad.net/bugs/529744
[13:13] <vish> oh that one
[13:14] <nigelb> flyingstar16: wait till tuesday, if no one replies, come in here and ask again :)
[13:14] <nigelb> vish: thoughts?
[13:14]  * persia has a feeling it used to be "username" and someone changed it at some point
[13:14] <nigelb> persia: yup.
[13:15] <vish> nigelb: probably needs a UIFe , there might be the need to update the documentation , probably you can ping seb128 to get that uploaded soonish
[13:15] <nigelb> worth taking is the trouble is my question ;)
[13:15] <flyingstar16> nigelb: thanks, I asked because I thought malev was an admin and forgot to approve :)
[13:15] <persia> nigelb: In your dealing with patches thing, also consider those like bug #497149 where there's no patch for any of the current tasks.  We need to make those go away.
[13:16] <ubot4`> Launchpad bug 497149 in virtualbox-ose (Ubuntu) (and 15 other projects) "Packages using DKMS should make use of /usr/lib/dkms/common.postinst (affects: 1)" [Undecided,Fix released] https://launchpad.net/bugs/497149
[13:16] <nigelb> persia: only tags can fix them.
[13:17] <nigelb> persia: there is a patch and its already used.  so we need to remove all patch tags out of there
[13:18] <persia> RIght, but that has to happen in a way that the script doesn't put them back.
[13:18] <nigelb> the script might need to be killed at some point or deal with only new bugs
[13:18] <persia> Maybe.  Check with bdmurray.
[13:19] <persia> also needs a clear definition of "New" being recent, being status "New", etc.
[13:19] <nigelb> persia: this is bound to be complex
[13:19] <persia> yep :)
[13:20] <nigelb> some time when brian gets the time, we need to have a chat with him (you need to be there too)
[13:23] <flyingstar16> I cannot reach search.gmane.org (bug trail follow link - launchpad-gm-scripts). Is it a known problem?
[13:24] <nigelb> seems to be down
[13:26] <flyingstar16> nmapping rain.gmane.org with the -PN option shows a lot of open ports, while nmapping search.gmane.org (which is a CNAME for rain.gmane.org) says "all scanned ports closed or filtered. That's strange
[13:33] <nigelb> suggestions on dealing with bug 346095
[13:33] <ubot4`> Launchpad bug 346095 in notify-osd (Ubuntu) "notify-osd doesn't honor my preference (affects: 27) (dups: 5)" [Wishlist,Confirmed] https://launchpad.net/bugs/346095
[13:33] <nigelb> close as Won't Fix?
[13:33] <nigelb> it went onto a philosophic discussion about Ubuntu
[13:36] <vish> nigelb: we can leave the wont fixes to the devs
[13:36] <vish> nigelb: or to the adopters ;p
[13:36] <persia> Why?
[13:37] <vish> persia: for that notify-osd bug especially
[13:37] <persia> vish: But why generally?
[13:37] <persia> vish: More specifically, on what basis do you think we ought not treat a bug?
[13:37] <vish> persia: isnt a "wont fix" supposed to be decided by the actual dev who is gonna say , "no"
[13:38] <persia> It already got made "Invalid" in comment #3
[13:38]  * persia is still reading
[13:39] <vish> hehe , i'm in there too..
[13:40] <vish> macslow has set it to confirmed and dbarth the status to wishlist..
[13:40] <nigelb> vish: feels notalgic doesn't it ;)
[13:40] <vish> ;)
[13:43] <persia> nigelb: I think that the patch in comment #80 got lost in the noise.
[13:43] <nigelb> persia: its turned philisophical at some point
[13:43] <persia> Indeed, but none of that matters, really.
[13:44] <nigelb> so, its a patch for 9.04
[13:44] <persia> nigelb: so in comment #90 mpt listed a wiki page talking about how the patch in comment #80 should work.
[13:44] <vish> persia: there is an option for gravity , it needs to be set.
[13:44] <persia> I'd call that needswork (also because the patch is outdated).
[13:45] <persia> vish: The GRAVITY patch was applied upstream, and is available in lucid?
[13:45] <vish> it has been available since karmic.. the notification can be set to top right or middle
[13:45] <vish> not sure ,if that was the patch used though
[13:45] <persia> vish: Ah, that's different than the extended gravity support in the patch in comment 80.
[13:46] <persia> That patch gives *lots* more options for gravity.
[13:46] <persia> (no UI, just gconf keys for those that want it)
[13:47] <vish> oh , but[i think] it would give problems with the append option in notify-osd..
[13:48] <vish> persia: eitherway , the lower position was supposed to be done for lucid , and no one seems to have fixed
[13:48]  * nigelb is going to add tag patch-needswork
[13:48] <vish> there was a huge discussion regarding this on ayatana :s
[13:48] <vish> https://wiki.ubuntu.com/NotifyOSD#Work%20for%20Lucid
[13:48] <persia> vish: The patch seems to be available.
[13:49] <persia> vish: Just needs someone to test the patch, and get it applied.
[13:50] <vish> persia: yup it needs work, iirc the patch was supposed to place it in the lower corner, which would cause problems when text gets appended.. that was why the position of a little higher in the lower right was considered
[13:50] <persia> Ah.  Needs delicate work :)
[13:50] <vish> supposed to allow user to*
[13:51] <persia> vish: So you think patch-submitted-upstream + patch-rejected-upstream are better tags?
[13:51] <persia> vish: Or just patch-submitted-upstream + patch-needswork ?
[13:52] <nigelb> I remember bug 533369 from -motu
[13:52] <ubot4`> Launchpad bug 533369 in debootstrap (Ubuntu) "Fails to debootstrap squeeze chroot due to missing apt-get (affects: 1)" [Undecided,New] https://launchpad.net/bugs/533369
[13:52] <vish> patch-needswork is probably closer..  but the problem is more there than the patch , it would allow setting it but the background work in notify-osd isnt done yet :(
[13:52] <nigelb> shall I propose an SRU for this ?
[13:53] <persia> nigelb: That's a question better asked in -motu, but I'd think so.
[13:54] <nigelb> its submitted for patch review :)
[13:54] <persia> Well, review the patch then.  But if you're processing as SRU, you're probably acting as a developer.
[13:54] <persia> Although there are certainly some cases where triagers propose SRUs
[13:55] <persia> (patch review is a messy area, somewhere between the two groups)
[13:55] <nigelb> yeah, its a mix of -motu, -devel, and -bugs ! ugh!
[13:55] <persia> That might be how it fell through the cracks :)
[13:56] <nigelb> after being a tool which all devs have handy
[14:06] <nigelb> later folks.  off
[17:02] <BUGabundo> boas
[17:39] <mtx_init> is there a good rss feed or something to keep track of major bugs in Foss in general?
[17:49] <mrand> mtx_init: Would that be major bugs reported, or confirmed?  Would it include bugs in unreleased code, or only released stuff?  I don't know how you'd possibly keep up with such a thing.  There are simply too many projects.
[17:50] <mtx_init> mrand: Like the recent sudo bug with sudoedit, as a unix admin that would help me,  But I just dont have the time in the day to read tons of mailing lists,
[17:51] <mtx_init> maybe just really critical ones.
[17:52] <vish> bdmurray: not that is matters anymore, found a trasnlations channel >  #ubuntu-translators  ;)
[17:52] <vish> it*
[18:06] <mrand> mtx_init: Ok, so only criticial bugs in released/deployed versions.  Interesting idea.  The hard part would be figuring out how to gather the info.  I suppose it could rely on submissions to a moderated email list (for archive purposes), which echoed to rss and all the social networks.  It would need to be moderated to keep the signal to noise ratio high, for the exact reason you describe.
[18:09] <mtx_init> mrand: software could be writer to watch mailing lists, presenting items most popular.
[18:12] <mrand> mtx_init: sounds complicated.   How does it filter out important stuff, which may actually only have a single notification/message, while ignoring flame war topics? each -announce type mailing lists are low volume enough, but they also typically contain new version notifications.  If you aggregate those together, I think the volume might still be much higher than what you are looking for.
[18:12] <mtx_init> yeah
[18:21] <mrand> mtx_init: ubuntu-security-announce mailing list might be the closest to what you're looking for.
[18:25] <crimsun> ok, triaged all 540 pulse bugs over the past couple days. 0 new bugs.
[18:26] <mrand> crimsun: WOW.  outstanding!
[18:26] <crimsun> this is hardly the first time I've done it
[18:27] <mrand> Doesn't make it less impressive ;-)
[18:27] <mtx_init> mrand: thank you
[18:27] <mtx_init> il take a look
[18:39] <bcurtiswx_> crimsun: show off
[18:40] <crimsun> bcurtiswx_: eah, cos I *love* bugs.
[18:41]  * micahg needs to find time to do that for firefox :)
[18:41] <bcurtiswx_> crimsun: you're such a bug hugger!
[18:41] <crimsun> it's much easier when I have coffee, noise cancelling headphones, and metal \m/
[18:42] <BUGabundo> \o/
[18:42] <BUGabundo> micahg: ahah
[18:42] <bcurtiswx_> don't like coffee, love no noise, and can't stand metal \m/.. i find classical to be more focus assisting
[18:42] <crimsun> takes all sorts
[18:42] <BUGabundo> oh I think FF has more then 500 bugs :D
[18:43] <micahg> BUGabundo: approx 1500 NEW bugs :)
[18:43] <crimsun> I haven't even started linux and alsa-driver :-)
[18:43] <bcurtiswx_> yeah crimsun: why isn't PA perfect yet.. huh huh huhhhh??
[18:43] <micahg> BUGabundo: after Lucid release I think I'll go on a bug spree :)
[18:44] <crimsun> bcurtiswx_: no one got me a pony, duh
[18:44] <bcurtiswx_> crimsun: i blame Ted
[18:44] <BUGabundo> micahg: the longer you wait, the bigger it gets
[18:44] <micahg> BUGabundo: my goal is to get good software in Lucid archive first :)
[18:45] <micahg> then make it better
[18:45] <bcurtiswx_> micahg: skip FFX, make a better flash player :P
[18:45] <micahg> bcurtiswx_: can you get me the source :P
[18:46] <bcurtiswx_> micahg: i meant start from scratch... O:-)
[18:46] <micahg> bcurtiswx_: after Lucid I might try to hack JIRA as a bug tracker for LP which will allow us to link to upstream flash bugs
[18:46] <bcurtiswx_> micahg: awesome, gl with that
[18:47] <BUGabundo> bcurtiswx +1
[18:50] <bcurtiswx_> #532799 what do I say. I just don't think thats worth of a bug and/or wishlist
[18:50] <bcurtiswx_> bug #532799
[18:50] <ubot4`> Launchpad bug 532799 in empathy (Ubuntu) "the first chan window takes 5 seconds to appear (affects: 1)" [Low,Incomplete] https://launchpad.net/bugs/532799