Comment 14 for bug 1187005

@penalvch: the bug I reported is definitely the same as bug #1184262. The symptoms, at least, are exactly the same, and the fix provided in bug #1184262 works for me too. That's why I marked this bug as a duplicate of bug #1184262. Now, if you really insist on this bug not being a duplicate of #1184262, feel free to keep this one opened, but I'm not going to bother investigating any more, as the problem is now fixed for me thanks to the updated package provided on bug #1184262.

Thanks.