[03:13] <TheLordOfTime> how do we set a bug to affect a different version of Ubuntu, i.e. Precise or Lucid (given that bugs against packages *without* a specific distro attached are assumed to be against Quantal/latestDev)
[03:24] <TheLordOfTime> does anyone know?
[03:38] <lifeless> TheLordOfTime: target to series
[14:10] <PjotrOrial> So when I was using the beta version and a program crashed, i was redirected into my webbrowser to describe the bug. Now that precise is stable and I get bugs where are those bugs redirected to? Can I do anything else than just clicking 'yes submit this bug please' ?
[14:11] <PjotrOrial> I submitted at least 25 bugs by accident
[14:11] <PjotrOrial> since I wanted to get rid of the box when I tracked down the bug
[14:11] <PjotrOrial> now the bug is reported manually here https://bugs.launchpad.net/ubuntu/+source/gcc-defaults-armel-cross/+bug/1014658
[14:11] <ubot2> Ubuntu bug 1014658 in gcc-defaults-armel-cross "arm-linux-gnueabi crashes with "Please submit a full bug report, with preprocessed source if appropriate."" [Undecided,New]
[14:12] <PjotrOrial> but I'd rather want to know where the bugreports are accessible of the stable ubuntu release
[14:13] <PjotrOrial> that is when I'd have only clicked on the button in the lower right at this window http://dl.dropbox.com/u/6520164/Screenshot%20from%202012-06-18%2016%3A12%3A45.png
[14:14] <PjotrOrial> where are those error reports directed to?
[14:20] <hggdh> PjotrOrial: error reports are accumulated at errors.ubuntu.com (which has restricted access, so you may, or may not see the entries)
[14:21] <hggdh> and maintainers look at it to find current (or critical) issues, and then open a bug if needed & work on them
[14:22] <PjotrOrial> hggdh: probably not then, I was just asking out of curiosity as now in the stable release it seems to the user that the bugreporting process is finished after you click on continue, so no further description or so by the user is required?
[14:22] <hggdh> PjotrOrial: if this is  a crash, no, no other entry is required.
[14:23] <hggdh> this is dealt now with whoopsie -- the error report collector
[14:24] <hggdh> assuming most will allow for the reporting, we will have a nice database of the most common issues, and will be able to address these faster than if we still required users to login to LP and report
[14:26] <PjotrOrial> sure, but at most bugs you need to attach further files and describe exactly what you are doing? Thanks for the background information :)
[14:27] <hggdh> it may, or maynot be needed. I would expect it would be needed for the most uncommon issues; for the most common, it should (theoretically) be easier to reproduce. But, on need, we can change the collector to ask for additional data
[14:28] <hggdh> and, then, put the collector back to "minimal data"
[14:28] <PjotrOrial> so the collector changes its appearance/behaviour on the type of error detected? so a common but hard to track error could still redirect to LP?
[14:30] <hggdh> the collector _may_ do that. I am not sure if the additionally collected data would go to a bug
[14:31] <hggdh> I would not direct it to a bug, though, open collections like these can add a truckload of comments
[14:31] <hggdh> but this is my personal view
[14:32] <PjotrOrial> heh, thanks for telling me, I just wondered that with release the bugtracking changed :)