Comment 8 for bug 180884

I've narrowed down the bug to wacom device "erasor" with a bit of help upstream. There's a suggested patch on their tracker which seems harmless enough -- I don't know the callers to that function, but it's clear that its possible to get a null pointer back and something should be done there to avoid a segfault.