Comment 7 for bug 977069

> The unity-greeter is affected as well, but you read "lightdm-gtk-greeter" is the description, so you reassign to lightdm-gtk-greeter and ignore the unity-greeter issue

? the bug didn't state that unity-greeter was affected, I quote the title "After installaing and removing lightdm-gtk-greeter lightdm is left in a not working state", so I assigned it to the package listed in the title because that's where it needs to be fixed..

> so that you've less bugs showing on your qa stats, I guess?

what sort of weird comment in that?
- I don't "own", "maintain", or "work on" lightdm, I just help triaging desktop bugs coming
- the bug didn't get closed, that would be no "stats" change
- where are those "qa stats" you talk about?
- why should I let a bug assigned to the wrong comment?

> So we can argue all day about your incredible bad faith, or we can think about something to fix this bug, your call.

oh, personal attacks now? you should calm down, I only reassigned the bug to the package listed in the title (like I reassign a dozen bugs from lightdm to unity-greeter every week), what's the issue to have bugs on the correct source? I didn't stop that unity-greeter had the same issue until you mentioned it and then I didn't reassign back but did "also affect" to show it affects 2 sources (though it seems I failed to do lightdm->unity-greeter for the second line at the same time)