Setting up startup script in lightdm.conf causes crash after ubuntu splash.

Bug #1132737 reported by Richard Thunell on 2013-02-25
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
Medium
Unassigned

Bug Description

After attempting to setup a fix (URL to explanation of fix below) which I had successfully used in quantal to display proper resolutions for multiple monitors in unity-greeter. In raring, the system crashes just after the ubuntu splash screen, and I had to return the lightdm.conf file to its original form from the terminal.
The fix worked just fine in precise and quantal. And I had hoped (and still do) that greeter will have the ability to detect and adjust for multiple displays in 13.04

http://askubuntu.com/questions/119843/how-to-force-multiple-monitors-correct-resolutions-for-lightdm

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: lightdm 1.4.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Mon Feb 25 04:34:11 2013
ExecutablePath: /usr/sbin/lightdm
InstallationDate: Installed on 2013-02-21 (4 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130220.2)
LightdmConfig:
 [SeatDefaults]
 user-session=ubuntu
 greeter-session=unity-greeter
MarkForUpload: True
ProcCmdline: lightdm
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x40f3f6: mov %esi,0x1c(%rax)
 PC (0x0040f3f6) ok
 source "%esi" ok
 destination "0x1c(%rax)" (0xaaaaaaaaaaaaaac6) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: lightdm crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Richard Thunell (rickythunell) wrote :

StacktraceTop:
 process_watch_cb (pid=1317, pid@entry=<error reading variable: value has been optimized out>, status=0, status@entry=<error reading variable: value has been optimized out>, data=0xee0770, data@entry=<error reading variable: value has been optimized out>) at process.c:130
 g_child_watch_dispatch (source=source@entry=0xf00780, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.35.8/./glib/gmain.c:5002
 g_main_dispatch (context=0xedcfc0) at /build/buildd/glib2.0-2.35.8/./glib/gmain.c:3054
 g_main_context_dispatch (context=context@entry=0xedcfc0) at /build/buildd/glib2.0-2.35.8/./glib/gmain.c:3630
 g_main_context_iterate (context=0xedcfc0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.35.8/./glib/gmain.c:3701

Changed in lightdm (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers