[03:26] <mfisch> bdmurray: I assume your ~brian @ people.ubuntu.com?
[03:27] <mfisch> bdmurray: if so, this page https://wiki.ubuntu.com/Bugs/EasyTasks links to an invalid URL at that site, look at the line that says "Bugs without a package with attachment(s)"
=== Guest48311 is now known as dmogle
=== dmogle is now known as Guest6584
[04:53] <dlentz> the bug watch updater keeps overriding changes in this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/863504
[04:53] <ubot2> Launchpad bug 863504 in ubuntu "Steelseries Xai mouse causing slow resume from suspend" [Undecided,Fix released]
=== Guest6584 is now known as dmogle
=== dmogle is now known as Guest14278
[09:43] <iceroot> can someone mark this as high/critical? https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/976425
[09:43] <ubot2> Launchpad bug 976425 in flashplugin-nonfree "Flashplugin-installer not giving flash in browsers" [Undecided,Confirmed]
[09:57] <iceroot> or maybe i am just getting the bug wrong (#4) :)
=== MCR is now known as Guest67241
[13:24] <mrp> trying to work out whether I should lodge a bug about cifs see http://pastebin.com/dp5i1tb2
[13:24] <mrp> ~/media is a cifs mounted share
[13:24] <mrp> seems to not like 128k chunks
=== krnekhelesh is now known as nik90
[16:35] <penguin42> is there some docs about what this new whoopsie thing does?
[16:38] <kklimonda> penguin42: http://wiki.ubuntu.com/ErrorTracker
[16:39] <penguin42> kklimonda: I read that, it's a design doc that doesn't seem to match reality
[16:39] <penguin42> kklimonda: certainly crashes.ubuntu.com doesn't seem to exist
[16:40] <kklimonda> penguin42: it's http://daisy.ubuntu.com ALTHOUGH the browsing is not enabled yet ;)
[16:40] <penguin42> kklimonda: So, how's it supposed to work in the future when triaging stuff?
[16:41] <kklimonda> so I think you get a blank page when you go there
[16:43] <kklimonda> penguin42: I can't really open the ErrorTracker page at the moment (my network connection is an equivalent of 33.6kbit modem) but whoopsie should be doing what's described there (or on a similar page - I was sure I read about it there) i.e. sending crash reports to the centralized DB and handling duplicated "reports" without requiring users to register on LP
[16:45] <penguin42> kklimonda: So is whoopsie sending data for more things than stuff that was currently lp bugs, or does it always file a corresponding lp bug if there isn't a match?
[16:45] <kklimonda> penguin42: I haven't seen any bugs filled by whoopsie, I don't expect it doing this
[16:46] <penguin42> kklimonda: So it files crash data without bugs?
[16:46] <kklimonda> penguin42: I think the difference is whoopsie will be running also after the release
[16:46] <kklimonda> penguin42: yeah, that's the most sensible thing to do
[16:47] <kklimonda> penguin42: it doesn't require users to register to LP and it doesn't give you any way of contacting them
[16:47] <penguin42> kklimonda: OK, so as a triager when do I look at that data, do I browse through crash reports in there on a package I'm interested in, or does something tie them up to other lp bugs?
[16:48] <kklimonda> penguin42: I don't think it's been yet decided - so far "we" (triagers and most developers) don't even have access to this new database.
[16:48] <penguin42> kklimonda: That makes for an interesting situation
[16:51] <kklimonda> penguin42: oh, how so?
[16:52] <penguin42> kklimonda: Well for those of us just helping on triage doesn't it make it harder for us?
[16:52] <kklimonda> (I do agree that there is very little info about what whoopsie is, and how does it fit with LP - what I know is what I got from reading through the source, and ubuntu wiki)
[16:53] <penguin42> Yeh, I'd kind of hope someone who knew would mail bug-{squad/control}
[16:53] <kklimonda> penguin42: we can just ignore the new DB completely
[16:55] <penguin42> kklimonda: So bugs reported using ubuntu-bug will still get the stuff uploaded to lp in the same way?
[16:55] <dlentz> penguin42, the bug you fixed for me is possessed: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/863504
[16:55] <ubot2> Launchpad bug 863504 in ubuntu "Steelseries Xai mouse causing slow resume from suspend" [Undecided,Fix released]
[16:55] <kklimonda> penguin42: most likely, whoopsie collects only crashes
[16:56] <penguin42> dlentz: Yes I know, I'm not sure what to do about it, any ideas kklimonda
[16:56] <kklimonda> penguin42: and crashes are too hard to triage for most volunteers not familiar with the affected software anyway
[16:56] <penguin42> kklimonda: Yeh but those are the type of crashes I tend to triage (and fix)
[16:58] <penguin42> kklimonda: It's like bugs 432861 and 965341 that I fixed a few days ago - simple segs
[16:58] <ubot2> Launchpad bug 432861 in procps "kill -s crashed with SIGSEGV" [Medium,Triaged] https://launchpad.net/bugs/432861
[16:58] <ubot2> Launchpad bug 965341 in procps "watch command line utility crashes with segfault when processing binary output" [Medium,Triaged] https://launchpad.net/bugs/965341
[16:58] <kklimonda> penguin42: well, I guess they'll make it easy to convert whoopsie crashes into LP bugs, and cross reference them with each other for those of us who can actually make something out of them. But I think it's developers who are the primary target of this service - now if only we made it easy for them to update software we'd be all set
[17:00] <penguin42> kklimonda: Nod, it would be nice to see someone involved explain how it's supposed to work
=== dmogle is now known as Guest55440
=== Guest55440 is now known as dmogle
=== dmogle is now known as Guest7972
=== Guest7972 is now known as dmogle