lightdm crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lightdm (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Recent update hosed my system. Things are so broken I don't know what caused what or what's relevant to what bug. Help?
X doesn't start automatically. Xorg.0.log suggests a problem with nvidia driver, but it's present in lsmod, and startx works. Well, it starts X anyway... My startx session is lacking Unity, or for that matter, any meaningful menus. I only managed to get firefox open because I got an apport dialog for lightdm segfaulting. There appears to be a window manager running, and a... file manager? I have a menubar at the top that appears to have come off a file manager window, and File->New Window opens the file manager. Nothing else though -- I can't open so much as a terminal without invoking it outside the X session.
I can't do any meaningful testing like this... should I try to fix this or reinstall Precise from scratch?
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: lightdm 1.0.6-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-4-generic x86_64
NonfreeKernelMo
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Dec 12 11:00:33 2011
ExecutablePath: /usr/sbin/lightdm
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: lightdm
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x411138: mov 0x28(%rax),%ecx
PC (0x00411138) ok
source "0x28(%rax)" (0xaaaaaaaaaaaa
destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: lightdm crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2011-12-11 (1 days ago)
UserGroups:
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 #902698, 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.