pidgin crashed with SIGSEGV in g_string_insert_len()

Bug #1326332 reported by magowiz on 2014-06-04
42
This bug affects 5 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Medium
Unassigned

Bug Description

pidgin crashed on launch
$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04

~$ apt-cache policy pidgin
pidgin:
  Installed: 1:2.10.9-0ubuntu3.1
  Candidate: 1:2.10.9-0ubuntu3.1
  Version table:
 *** 1:2.10.9-0ubuntu3.1 0
        500 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1:2.10.9-0ubuntu3 0
        500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
     1:2.10.9-0ubuntu1+pidgin1.14.04 0
        500 http://ppa.launchpad.net/pidgin-developers/ppa/ubuntu/ trusty/main amd64 Packages
     1:2.10.7-0ubuntu4.1.13.10.2 0
        500 http://it.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: pidgin 1:2.10.9-0ubuntu3.1
ProcVersionSignature: Ubuntu 3.13.0-29.52-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jun 4 11:59:39 2014
ExecutablePath: /usr/bin/pidgin
ProcCmdline: pidgin
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd784bce2cd <g_string_insert_len+157>: movb $0x0,(%rdi,%rbp,1)
 PC (0x7fd784bce2cd) ok
 source "$0x0" ok
 destination "(%rdi,%rbp,1)" (0x6f6e61696c696d6d) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 g_string_insert_len () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/purple-2/libskype.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread (arg=0x7fd743f16700) at pthread_create.c:312
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Title: pidgin crashed with SIGSEGV in g_string_insert_len()
UpgradeStatus: Upgraded to trusty on 2014-04-19 (45 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

magowiz (magowiz) wrote :
information type: Private → Public

StacktraceTop:
 g_string_insert_len (string=0x7fd734001a20, pos=<optimized out>, val=<optimized out>, len=<optimized out>) at /build/buildd/glib2.0-2.40.0/./glib/gstring.c:492
 receive_message_loop () at skype_messaging_x11.c:250
 g_thread_proxy (data=0x7fd78aa67450) at /build/buildd/glib2.0-2.40.0/./glib/gthread.c:764
 start_thread (arg=0x7fd743f16700) at pthread_create.c:312
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Changed in pidgin (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

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

Duplicates of this bug

Other bug subscribers