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

Bug #1507141 reported by W. G.
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-session (Ubuntu)
New
Undecided
Unassigned

Bug Description

crash appeared after login

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: indicator-session 12.10.5+15.10.20150915-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Sat Oct 17 14:47:13 2015
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
InstallationDate: Installed on 2015-10-14 (3 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7fee2a0fd6fa <strlen+42>: movdqu (%rax),%xmm12
 PC (0x7fee2a0fd6fa) 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
W. G. (weimick) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1301589, so 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. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.