trashapplet crashed with SIGSEGV in strcmp()

[Brian Murray]

Binary package hint: gnome-applets

I was logging into my desktop session and this happened.

ProblemType: Crash
Architecture: amd64
Date: Fri Sep 28 19:10:52 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/gnome-applets/trashapplet
NonfreeKernelModules: fglrx
Package: gnome-applets 2.20.0-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/lib/gnome-applets/trashapplet --oaf-activate-iid=OAFIID:GNOME_Panel_TrashApplet_Factory --oaf-ior-fd=19
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: gnome-applets
StacktraceTop:
 strcmp () from /lib/libc.so.6
 ?? () from /usr/lib/libfontconfig.so.1
 FcNameRegisterObjectTypes ()
 XftInit () from /usr/lib/libXft.so.2
 qt_init_internal () from /usr/lib/libqt-mt.so.3
Title: trashapplet crashed with SIGSEGV in strcmp()
Uname: Linux flash 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip family floppy lpadmin plugdev pulse pulse-access scanner video
SegvAnalysis:
 Segfault happened at: 0x2b795bcf35b2 <strcmp+2>: cmp (%rsi),%al
 PC (0x2b795bcf35b2) ok
 source "(%rsi)" (0x2b796563dae9) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading unknown VMA

[Apport retracing service (apport)]

StacktraceTop:strcmp () from /lib/libc.so.6
FcObjectHashInsert (object=0x2aaaac4e5040, copy=1) at fcname.c:209
IA__FcNameRegisterObjectTypes (types=<value optimized out>, ntypes=3) at fcname.c:272
XftInit (config=<value optimized out>) at ../../src/xftinit.c:37
qt_init_internal (argcptr=0x0, argv=0x0, display=0x635340, visual=0, colormap=0) at kernel/qapplication_x11.cpp:2051

[Sebastien Bacher (seb128)]

looks like a xft or fontconfig issue

[xteejx (xteejx)]

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.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.