← Back to team overview

desktop-packages team mailing list archive

[Bug 759640] Re: pidgin crashed with SIGSEGV in g_closure_invoke()


Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner.  Ubuntu 10.04 is no longer
supported so I would usually close this bug.

Is there any chance you can reproduce on 14.04 or 15.04?

** Changed in: pidgin (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.

  pidgin crashed with SIGSEGV in g_closure_invoke()

Status in pidgin package in Ubuntu:

Bug description:
  Binary package hint: pidgin

  pidgin crashed when trying to establish an audio-connection via jabber

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: pidgin 1:2.7.11-1ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Apr 13 12:06:06 2011
  ExecutablePath: /usr/bin/pidgin
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
  ProcCmdline: pidgin
   Segfault happened at: 0x7f1e84a1454c:	mov    0x38(%rbp),%rbp
   PC (0x7f1e84a1454c) ok
   source "0x38(%rbp)" (0x00000038) not located in a known VMA region (needed readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: pidgin
   ?? () from /usr/lib/libpurple.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: pidgin crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to natty on 2011-04-03 (9 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to: