pidgin crashed with SIGSEGV in call_init()

Bug #1434209 reported by Clon
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Pidgin 2.10.9 crashed on Lubuntu Vivid Vervet when launched from panel menu.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: pidgin 1:2.10.9-0ubuntu8
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic i686
ApportVersion: 2.16.2-0ubuntu3
Architecture: i386
CrashCounter: 1
CurrentDesktop: LXDE
Date: Thu Mar 19 18:45:46 2015
Disassembly: => 0x5: Cannot access memory at address 0x5
ExecutablePath: /usr/bin/pidgin
InstallationDate: Installed on 2013-03-16 (733 days ago)
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
ProcCmdline: pidgin
SegvAnalysis:
 Segfault happened at: 0x5: Cannot access memory at address 0x5
 PC (0x00000005) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/pidgin/libpurpletorchat.so
 ?? () from /usr/lib/pidgin/libpurpletorchat.so
 call_init (l=0xb788c950, argc=8388608, argc@entry=1, argv=argv@entry=0xbfdee314, env=env@entry=0xbfdee31c) at dl-init.c:64
 call_init (env=0xbfdee31c, argv=0xbfdee314, argc=1, l=<optimized out>) at dl-init.c:36
Title: pidgin crashed with SIGSEGV in call_init()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video

Revision history for this message
Clon (fillip1) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 call_init (l=0xb788c950, argc=8388608, argc@entry=1, argv=argv@entry=0xbfdee314, env=env@entry=0xbfdee31c) at dl-init.c:64
 call_init (env=0xbfdee31c, argv=0xbfdee314, argc=1, l=<optimized out>) at dl-init.c:36

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in pidgin (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for gcc-5-base
no debug symbol package found for dmsetup
no debug symbol package found for libisc-export95
no debug symbol package found for gconf-service
no debug symbol package found for multiarch-support
no debug symbol package found for libflac8
no debug symbol package found for libdevmapper1.02.1
no debug symbol package found for libirs-export91
no debug symbol package found for libperl5.20
no debug symbol package found for perl-base
no debug symbol package found for xdg-user-dirs
no debug symbol package found for libgtkspell0
no debug symbol package found for debianutils
no debug symbol package found for libisccfg-export90
no debug symbol package found for libdns-export100
no debug symbol package found for sed
no debug symbol package found for libtag1c2a
ca-certificates version 20141019ubuntu0.14.10.1 required, but 20141019 is available
no debug symbol package found for iproute2
no debug symbol package found for libgtkspell0

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
Clon (fillip1)
information type: Private → Public
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.