Uhm, I did follow the fucking guide you moron.
Like hell you did. You read the first step, did it, read the second step, and said - and I'm quoting directly here - "fuck this debugging bullshit I need my ass wiped for me"!
Maybe you are not aware that Windows reports look highly different to Linux ones, I didn't use attachments like the other guy either.
Sweetheart, I was on Windows
when you were still sucking your mother's tits. The only thing I see there is a BSoD that puked all over what would've otherwise been a coherent bug report.
I only got the pidgin.RPT contents and posted them because you have to run under a commandline to get the other. Fuck that, I need desktop space - usually they don't need the other report anyway and if they do they request it.
So you're going to withhold information because you don't REALLY want Pidgin to get fixed so that you have just cause to bitch about... IT NOT WORKING? That's low, John, even for YOU.
Also, they are two different bugs READ THE VERSION NUMBERS. Mine got fixed, with my help or not I have no idea. A new one came along.
Regressions never happen! I must bitch about
something so I'll bitch about how the version number in my sole bug report doesn't match up with the version number in a bug that RELATES TO PIDGIN CRASHING ON VISTA! My 2.5.0 report got pulled for excessive fucktardedness so I guess I'll just copypasta my /b/ rant here!
PS: the other debug log submitted in the ticket opened on A DIFFERENT ISSUE which might be what I am having contains nothing of interest, as usual.
No, I think I hit the money on this one, YOU NEED YOUR MEDS NOW. As in YESTERDAY. You're so goddamn incoherent that I honestly can't tell whether you're bashing an irrelevant debug log, your inherent disinterest in any functional solutions to your problem (MEDS WORK IF YOU LET THEM), or some lame attempt at bashing me. Keep at it, though - I rather enjoy your little bouts of idiocy.
Refalm, maybe you should note who started this shitstorm and why letting this continue is such a bad idea.