[08:13] bdmurray: the udev handler is not installed [08:13] mlankhorst: I see that it is not installed for Trusty. Why is that? [08:15] always disabled on release, to prevent data from being leaked [08:16] there is sensitive data here? https://errors.ubuntu.com/oops/b65606bc-e4a2-11e3-a166-fa163e707a72 [08:19] in practice, probably not, but in theory.. [08:22] mlankhorst: well crashes are reported from supported (not development) releases to errors and I thought the same thing would be useful for the gpu errors. if not then close the bug as invalid or won't fix. [08:23] maybe the handler could be split to put the trigger-happy "sensitive" part in a separate thing that's removed before release [08:24] hmm wait [08:24] what are the sensitive parts? whoopsie doesn't include all the data from apport [08:24] it still reports these gpu lockups? [08:26] no, they are not reported from "supported" / released releases [08:26] right this was from utopic [08:26] I'm suggesting that it might be useful to send them to errors [08:26] for Trusty [08:27] Well, I mean errors is for collecting information from development and supported releases so you might want to send the gpu errors there for the LTS [08:27] well, most of these tend to come from "hangs" the user doesn't notice at all, the gpu recovers itself [08:28] If it isn't interesting data for fixing them for the LTS then don't send them. [08:33] it shouldn't send anything for the lts, since the handler is disabled [08:33] the fixes will arrive in point-releases, we don't do much driver sru's anyway [08:34] since it's tedious, can't update versions [08:34] not that -intel has had a stable release since some time last year [08:35] guess it'll be replaced with -modesetting & xserver glamor anyway [08:35] I understand the handler is disabled, I'm suggesting that you might enable it and if you do then should include the fix I made to xdiagnose. [08:35] right [08:36] sure