gdm-simple-slave crashed with SIGSEGV in g_object_ref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
New
|
Undecided
|
Unassigned | ||
gdm (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After installing updates from July 16 on Ubuntu GNOME 13.10 and rebooting from Software Updater, GDM failed to load and got stuck on the initial GNOME default wallpaper splash screen. I could drop to tty and I tried "service restart gdm" but this just made the screen flicker and pushed me back to Plymouth.
Apport is claiming that I've modified /etc/init.d/gdm but I've never touched it.
I also attempted "startx" in tty, which failed and mentioned something about a timeout on .Xauthority.
After force shutting down the computer and booting up again, GDM loaded successfully without changing anything, so I'm still not sure why this happened.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gdm 3.8.1.1-0ubuntu5
ProcVersionSign
Uname: Linux 3.10.0-3-generic x86_64
NonfreeKernelMo
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Wed Jul 17 13:06:34 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-06-06 (41 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f427810f8ca <vfprintf+154>: callq 0x7f4278159b30 <strchrnul>
PC (0x7f427810f8ca) ok
source "0x7f4278159b30" (0x7f4278159b30) ok
destination "(%rsp)" (0x7fffee011ff0) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gdm
StacktraceTop:
g_object_ref () from /usr/lib/
?? ()
?? ()
?? () from /usr/lib/
g_signal_
Title: gdm-simple-slave crashed with SIGSEGV in g_object_ref()
UpgradeStatus: Upgraded to saucy on 2013-06-28 (19 days ago)
UserGroups:
mtime.conffile.
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 #1160356, 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.