tieto team mailing list archive

[Launchpad Bug Tracker <956434@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a private bug by Bolesław Tokarski (boleslaw-tokarski):

It seems that sssd has some issues after the machine started outside the
network providing authentication services, after a successful logon. I
also had some issues where dbus stopped responding and further
authentication attempts were unsuccessful; however in this case, sssd
has restarted sssd_be and I am still able to logon.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: sssd 1.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 14 21:36:40 2012
Disassembly: => 0xb6091440:	Cannot access memory at address 0xb6091440
ExecutablePath: /usr/lib/sssd/sssd/sssd_be
ProcCmdline: /usr/lib/sssd/sssd/sssd_be --domain eu.tieto.com --debug-to-files
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0xb6091440:	Cannot access memory at address 0xb6091440
 PC (0xb6091440) ok
 SP (0xbfdbc090) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: sssd
Stacktrace:
 #0  0xb6091440 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfdbc090
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 1031):
 #0  0xb6091440 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfdbc090
Title: sssd_be crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: sssd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-crash i386 need-i386-retrace precise
-- 
sssd_be crashed with SIGSEGV
https://bugs.launchpad.net/bugs/956434
You received this bug notification because you are a member of Tieto, which is subscribed to the bug report.