We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
--
pidgin crashed with SIGSEGV i
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: pidgin (Ubuntu)
Hey,
I have not used gdb (backtrace) before, but from what I can tell you need to
make the program crash again? It only did the problem on the first use,
after that it worked fine. (yes I'm new to de-buging)
Chad. E
On Wed, Apr 8, 2009 at 4:30 PM, Sebastien Bacher
wrote:
> Thank you for tak
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
** Visibility changed to: Public
--
pidgin crashed with SIGSEGV in g_main_context_dispatch()
https://bugs.launchpad.net/bugs/353592
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
