pidgin crashed with SIGSEGV in malloc()

Bug #239797 reported by Carl Karsten
This bug report is a duplicate of:  Edit Remove
6
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

around Jun 10, did apt-get upgrade, now pidgin crashes on start:

carl@dell29:~$ time pidgin
Segmentation fault (core dumped)

real 0m6.197s
user 0m0.468s
sys 0m0.128s

ProblemType: Crash
Architecture: i386
Date: Fri Jun 13 11:04:31 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.4.1-1ubuntu2
PackageArchitecture: i386
ProcCmdline: pidgin
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/username/bin
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 opendir () from /lib/tls/i686/cmov/libc.so.6
Title: pidgin crashed with SIGSEGV in malloc()
Uname: Linux 2.6.24-18-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Carl Karsten (carlfk) wrote :
Revision history for this message
Carl Karsten (carlfk) wrote :

I noticed NonfreeKernelModules: nvidia, so I remoed it, rebooted, made sure:
(II) Loading /usr/lib/xorg/modules/drivers//nv_drv.so
ran pidgin, got segfault, but apport didn't come up.

carl@dell29:~$ cat /etc/default/apport
# set this to 0 to disable apport, or to 1 to enable it
enabled=1

carl@dell29:~$ cat /etc/apport/blacklist.d/apport
/usr/bin/wine-preloader

If someone can tell me how to get it up, I'll send in another set of files that don't use NonfreeKernelModules.

also, how do I satisfy need-i386-retrace ?

Revision history for this message
Carl Karsten (carlfk) wrote :

" Remember, this bug report is a duplicate. Comment here only if you think the duplicate status is wrong. "
" Sorry, you don't have permission to access this page. "

Which might explain why "...duplicate of bug #238594" isn't that a link to #238594, but
A) it is natural for someone to want to see what else has been reported, so might as well make it easy to find out it is private by providing a link to it.
B) don't say "Comment here only if.." if I can't comment there.

Revision history for this message
Carl Karsten (carlfk) wrote :

todays update seems to have fixed this.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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