gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()

Bug #1332595 reported by Cristian Aravena Romero
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Not see image of user.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gdm 3.10.0.1-0ubuntu6
Uname: Linux 3.16.0-031600rc1-lowlatency x86_64
ApportVersion: 2.14.3-0ubuntu2
Architecture: amd64
Date: Fri Jun 20 11:40:03 2014
ExecutablePath: /usr/lib/gdm/gdm-session-worker
InstallationDate: Installed on 2014-04-27 (54 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
ProcCmdline: gdm-session-worker\ [pam/gdm-password]
SegvAnalysis:
 Segfault happened at: 0x7f6f349388b0 <act_user_is_loaded>: movzbl 0xe8(%rdi),%eax
 PC (0x7f6f349388b0) ok
 source "0xe8(%rdi)" (0x000000e8) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gdm
StacktraceTop:
 act_user_is_loaded () from /usr/lib/x86_64-linux-gnu/libaccountsservice.so.0
 ?? ()
 ?? ()
 ?? ()
 pam_vprompt () from /lib/x86_64-linux-gnu/libpam.so.0
Title: gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 act_user_is_loaded (user=0x0) at act-user.c:1806
 ?? ()
 ?? ()
 ?? ()
 pam_vprompt (pamh=0x2522b90, style=1, response=0x7fff18b5e260, fmt=0x7f6f2bbebfa1 "%s", args=args@entry=0x7fff18b5e178) at pam_vprompt.c:83

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 gdm (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for gdm

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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