indicator-session-service crashed with SIGSEGV in strlen()

Bug #1301589 reported by Dave Lee
58
This bug affects 9 people
Affects Status Importance Assigned to Milestone
indicator-session (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Happened after initial log on after power up.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: indicator-session 12.10.5+14.04.20140324-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
Date: Wed Apr 2 16:02:54 2014
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
InstallationDate: Installed on 2014-03-28 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7f729bc0392a <strlen+42>: movdqu (%rax),%xmm12
 PC (0x7f729bc0392a) ok
 source "(%rax)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%xmm12" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-session
StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: indicator-session-service crashed with SIGSEGV in strlen()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Dave Lee (dlee-48162) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 g_strdup (str=0x1 <Address 0x1 out of bounds>) at /build/buildd/glib2.0-2.40.0/./glib/gstrfuncs.c:355
 schedule_call_in_idle (call_type=CALL_TYPE_NAME_VANISHED, client=0x21ae1b0) at /build/buildd/glib2.0-2.40.0/./gio/gdbusnamewatching.c:192
 do_call (client=0x21ae1b0, call_type=CALL_TYPE_NAME_VANISHED) at /build/buildd/glib2.0-2.40.0/./gio/gdbusnamewatching.c:213
 ffi_call_unix64 () at ../src/x86/unix64.S:76

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 indicator-session (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Rafal (1szafarz) wrote :

That may help (works in my case):

sudo dpkg --purge indicator-session
sudo apt-get install indicator-session

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in indicator-session (Ubuntu):
status: New → Confirmed
tags: added: utopic
Revision history for this message
Matt (mforrest) wrote :

I have the same issue, but may have found the source & potential workaround.

When I use a monolithic site-wide passwd file, indicator-session crashes. When I strip it down to just a local account, everything is fine. After I stop showing the users for quick user switching, it stops crashing!

Possible workaround: Run the command below as the affected user.
dconf write /apps/indicator-session/user-show-menu false

I've actually applied this as a manditory setting on a system-wide level. Apply the attached tarball, then run 'sudo dconf update'

tags: added: wily
Revision history for this message
Sebastien Bacher (seb128) wrote :

Interesting, could you share your passwd file or a modified version that is enough to expose the issue?

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.