Ubuntu
indicator-messages package

indicator-messages-service crashed with SIGSEGV in dirname()

Bug #963870 reported by Frederic Urban on 2012-03-24

This bug report is a duplicate of: Bug #761463: edquota crashes when used with libnss-db. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	indicator-messages (Ubuntu)	Invalid	Medium	Unassigned
	libnss-db (Ubuntu)	Triaged	High	Unassigned

Bug Description

Using gnome 3 fresh install without any specific setting...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-messages 0.5.94-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Sat Mar 24 13:42:27 2012
ExecutablePath: /usr/lib/indicator-messages/indicator-messages-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120324)
ProcCmdline: /usr/lib/indicator-messages/indicator-messages-service
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANGUAGE=fr:en
LANG=fr_FR.UTF-8
SegvReason: executing writable VMA /usr/lib/indicator-messages/indicator-messages-service
Signal: 11
SourcePackage: indicator-messages
Title: indicator-messages-service crashed with SIGSEGV in dirname()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

Frederic Urban (frederic-urban) wrote on 2012-03-24:

Dependencies.txt Edit (2.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (640 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (25.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (805 bytes, text/plain; charset="utf-8")
Registers.txt Edit (809 bytes, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (240 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (846 bytes, text/plain; charset="utf-8")
StacktraceTop.txt Edit (182 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-24:

StacktraceTop:
dirname ()
internal_setent (file=0x7fd350ea96e7 "/var/lib/misc/passwd.db", dbp=0x7fd3510ab288, dbenvp=0x7fd3510ab290) at db-open.c:66
lookup (key=0x7fffd3d4c800, result=0x7fffd3d4c8e0, buffer=0x775850, buflen=1024, errnop=0x7fd359a368e0) at db-XXX.c:116
_nss_db_getpwnam_r (name=0x7fffd3d4efba "furban", result=0x7fffd3d4c8e0, buffer=0x775850 "gdm", buflen=1024, errnop=0x7fd359a368e0) at files-pwd.c:33
__getpwnam_r (name=0x7fffd3d4efba "furban", resbuf=0x7fffd3d4c8e0, buffer=0x775850 "gdm", buflen=1024, result=0x7fffd3d4c918) at ../nss/getXXbyYY_r.c:256

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-24: Stacktrace.txt

Stacktrace.txt Edit (2.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-24: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (11.6 KiB, text/plain)

Changed in indicator-messages (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Sebastien Bacher (seb128) on 2012-03-27

visibility:

private → public

Revision history for this message

Olli Ries (ories) wrote on 2012-03-27:

Charles, please see if you we have enough information

Changed in indicator-messages:
status:	New → Triaged
importance:	Undecided → High
assignee:	nobody → Charles Kerr (charlesk)

Revision history for this message

Charles Kerr (charlesk) wrote on 2012-03-28:

This isn't an indicator-messages bug, its call is a simple one to g_get_user_cache_dir (). And I don't think it's glib's fault either -- the final steps before the dirname() call are all nss-db.

Thanks for reporting this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #761463, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

affects:	indicator-messages → libnss-db (Ubuntu)
Changed in libnss-db (Ubuntu):
assignee:	Charles Kerr (charlesk) → nobody
Changed in indicator-messages (Ubuntu):
status:	New → Invalid

Revision history for this message

jablko (ms419) wrote on 2012-09-09:

Bug #761463 was apparently fixed upstream by making "dirname" variable static

http://sourceforge.net/tracker/index.php?func=detail&aid=3300978&group_id=18136&atid=118136

I tested the same fix applied to seen-db.c in indicator-messages and confirm that after I rebuilt indicator-messages, this crash ceased

> @@ -26,7 +26,7 @@
>
> GHashTable * seendb = NULL;
> gchar * filename = NULL;
> -gchar * dirname = NULL;
> +static gchar * dirname = NULL;
> guint write_process = 0;
>
> /* Build the hashtable and then see if we have a keyfile that