Comment 4 for bug 773390

After I marked this bug Invalid (since it functioned as a question rather than a bug, and Patrick Wilson had already filed a question **containing the exact same text as this bug report**), Patrick Wilson re-reported his problem as bug 773495, as I had suggested that he do. At that point, he also marked this bug as a duplicate of the new bug 773495. Considering Patrick's description of the crash in combination with the stack trace in bug 773495, bug 773495 seemed a lot like a duplicate of bug 529714. Just comparing bug 529714's stack trace and description (together with comments confirming that it also occurred with Banshee) to bug 773495 would have been sufficient to justify marking bug 773495 as a duplicate of bug 529714. But I decided to be more careful, just in case, so I looked at the stack traces of *all* the public duplicates of bug 529714. All were identical in relevant part (i.e., the winbind calls) to bug 773495, several were from Banshee crashes, and a couple were from Banshee crashes and had completely identical stack traces (with the absence of some symbol names not filled in). This confirmed for sure that Patrick Wilson was experiencing bug 529714. So I marked bug 773495 a duplicate of bug 529714. Since *this* bug (i.e., bug 773390) was at that time marked as a duplicate of bug 773495, marking bug 773495 a duplicate of bug 529714 resulted in this bug being marked a duplicate of bug 529714.