pidgin crashed with SIGSEGV in __strcpy_chk()

Bug #563631 reported by Christian Klotz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

This seems to happen only when chatting with MAC-Users via ICQ Protocol.
Pidgin Version is 1:2.6.6-1ubuntu4, so are pidgin-data, libpurple0 an libpurple-bin
I'm runnung Lucid Beta2

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: pidgin 1:2.6.6-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Apr 15 10:27:07 2010
ExecutablePath: /usr/bin/pidgin
ProcCmdline: pidgin
ProcEnviron:
 LC_TIME=de_DE.UTF-8
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4153953fb0 <__strcpy_chk+80>: mov (%rsi),%rax
 PC (0x7f4153953fb0) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 __strcpy_chk () from /lib/libc.so.6
 oscar_normalize ()
 purple_normalize () from /usr/lib/libpurple.so.0
 purple_find_conversation_with_account ()
 purple_conv_present_error ()
Title: pidgin crashed with SIGSEGV in __strcpy_chk()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers www-data
XsessionErrors: (polkit-gnome-authentication-agent-1:1772): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Christian Klotz (redknight) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Do you get the same with Lucid or Maverick? Thanks in advance.

Changed in pidgin (Ubuntu):
status: New → Incomplete
Revision history for this message
Christian Klotz (redknight) wrote :

Updating to Pidgin 2.7.1 (from pidgin-developers PPA) solved the problem for me

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for pidgin (Ubuntu) because there has been no activity for 60 days.]

Changed in pidgin (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.