Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a .crash file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.
If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.
If you are using Ubuntu with the Gnome desktop environment - launch nautilus
and navigate to your /var/crash directory and double click on the crash report
you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using
/usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a
terminal - where _my_crash_report.crash is the crash you would like to report.
Also, just because it crashed in glib doesn't automatically make it a
glib crash - it's more likely to be a pidgin bug. For example, I can
write an application that passes a NULL pointer to strcmp - it will
crash in libc6, but it's still an application bug.
I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently. Thanks in advance for your cooperation and understanding.
** Package changed: glib2.0 (Ubuntu) = pidgin (Ubuntu)
** Changed in: pidgin (Ubuntu)
Status: New = Invalid
--
random crash on pidgin related to libglib2.0
https://bugs.launchpad.net/bugs/512846
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
