I don't understand why this bug was marked invalid. I got a crash with
the exact same stack trace, and the original report fits the pattern I
saw, as a crash triggered by an incoming message will happen without any
apparent action by the user.
I did some testing, and wrote up a set of steps that can be used to
reproduce the crash (on my system, at least).
Sebastien, did you try the test case described in comment 5 before
closing this?
I don't have time to do further testing at the moment, but I believe
there is sufficient information in this report for someone else to
reproduce this bug in a test environment as requested.
** Changed in: pidgin (Ubuntu)
Status: Invalid => New
--
pidgin crashed with SIGSEGV in g_list_append()
https://bugs.launchpad.net/bugs/357542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
