gnome-session crashed with SIGSEGV in SmsDie()

Bug #454617 reported by Junior
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-session

The encryption of my home is enabled. I enabled autologin. After the next restart i was logedin, but all my setting couldn't be loaded due to missing configuration. I guess the decryption of my home didn't take place.

ProblemType: Crash
Architecture: amd64
Date: Sun Oct 18 13:51:39 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-session
NonfreeKernelModules: wl
Package: gnome-session-bin 2.28.0-0ubuntu4
ProcCmdline: gnome-session
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7fdb7650f791 <SmsDie+1>: mov 0x8(%rdi),%rbx
 PC (0x7fdb7650f791) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-session
StacktraceTop:
 SmsDie () from /usr/lib/libSM.so.6
 ?? ()
 ?? ()
 g_hash_table_find () from /lib/libglib-2.0.so.0
 ?? ()
Title: gnome-session crashed with SIGSEGV in SmsDie()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #437425, 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.

visibility: 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.