Since this bug has enough information provided for a developer to begin
work, I'm going to mark it as confirmed and let them handle it from
here. NOTE: Stacktrace is included in the description. Thanks for taking
the time to make Ubuntu better!
** Changed in: pidgin (Ubuntu)
Importance: Undecid
Is that included in the original report? If that is a complete gdb
trace, it looks good. The problem with including it that way is I could
not determine if it was complete, or a partial trace copied from one of
the log files. It is much better to attach such things as separate plain
text files.
I
I'll try to get this again, but I can't get it on command.
But to be clear, what is wrong with the backtrace I originally attached?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665736
Title:
pidgin
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
--
pidgin SIGSEGV
https://bugs.launchpad.net/bugs/665736
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
