Crash on login, after installing on Lubuntu

Bug #834793 reported by Julien Lavergne
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Light Display Manager
Fix Released
Undecided
Unassigned
lightdm (Ubuntu)
Fix Released
High
Robert Ancell
Oneiric
Fix Released
High
Robert Ancell

Bug Description

To reproduce :
Install Lubuntu with a daily ISO
After the installation, login to Lubuntu session
Install lightdm and use it by default
Reboot
Log in Lubuntu session
You shoudl have a black screen with nothing else, and a report in /var/crash which apport refuse to report.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: lightdm 0.9.3-0ubuntu8
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Date: Fri Aug 26 16:57:42 2011
InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110825)
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Julien Lavergne (gilir) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, why does apport refuse to report it? what reason does it give? could you use apport-retrace on it and add the stacktrace manually?

Changed in lightdm (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

could perhaps be bug #833619 or similar, what greeter are you using? Could you add the lightdm.log to the bug?

Revision history for this message
Julien Lavergne (gilir) wrote :

I'm using lightdm-gtk-greeter, I attached lightdm.log.
When running aport-bug on the .crash file, it displays this message :
======================================================
*** Error: Invalid problem report

This problem report is damaged and cannot be processed.

ValueError('Report does not contain "ProblemType" field',)

Press any key to continue...
======================================================

apport-retrace also crashed :

sudo apport-retrace -s /var/crash/_usr_sbin_lightdm.0.crash
Traceback (most recent call last):
  File "/usr/bin/apport-retrace", line 294, in <module>
    if report['ProblemType'] == 'KernelCrash':
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'ProblemType'

Changed in lightdm (Ubuntu):
status: Incomplete → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you add the apport file to the bug? do you have anything in the other lightdm logs?

Revision history for this message
Julien Lavergne (gilir) wrote :
Download full text (9.1 KiB)

Ok, second try generated a valid report crash, apport-retrace also made (I hope) a usefull stacktrace :

--- stack trace ---
#0 0x0805ffbc in xsession_start (session=0x8e4e060) at xsession.c:80
        path = <optimized out>
        error = 0x0
#1 0x0805943f in session_start (session=0x8e4e060) at session.c:226
        user = <optimized out>
        orig_path = <optimized out>
        result = <optimized out>
        __PRETTY_FUNCTION__ = "session_start"
#2 0x0804e962 in start_user_session (display=0x8e28c10, authentication=0x8e45538) at display.c:799
        user = <optimized out>
        log_filename = 0x8e44560 "sbin:/bin:/usr/games"
        result = 0
#3 0x080501f6 in greeter_session_stopped_cb (display=0x8e28c10, session=<optimized out>) at display.c:507
        started_session = <optimized out>
#4 greeter_session_stopped_cb (session=0x8e4e010, display=0x8e28c10) at display.c:483
No locals.
#5 0x00c70f6c in g_cclosure_marshal_VOID__VOID (closure=0x8e398d0, return_value=0x0, n_param_values=1, param_values=0x8e4d850, invocation_hint=0xbfe024b0, marshal_data=0x0) at /build/buildd/glib2.0-2.29.16/./gobject/gmarshal.c:85
        callback = 0x80500b0 <greeter_session_stopped_cb>
        cc = 0x8e398d0
        data1 = 0x8e4e010
        data2 = <optimized out>
        __PRETTY_FUNCTION__ = "g_cclosure_marshal_VOID__VOID"
#6 0x00c6fa5c in g_closure_invoke (closure=0x8e398d0, return_value=0x0, n_param_values=1, param_values=0x8e4d850, invocation_hint=0xbfe024b0) at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c:773
        marshal = 0x804b5f0 <g_cclosure_marshal_VOID__VOID@plt>
        marshal_data = 0x0
        in_marshal = 0
        __PRETTY_FUNCTION__ = "g_closure_invoke"
#7 0x00c83ec0 in signal_emit_unlocked_R (node=0x8e19ff0, detail=0, instance=0x8e4e010, emission_return=0x0, instance_and_params=0x8e4d850) at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c:3271
        tmp = <optimized out>
        handler = 0x8e1e120
        accumulator = 0x0
        emission = {next = 0x0, instance = 0x8e4e010, ihint = {signal_id = 7, detail = 0, run_type = G_SIGNAL_RUN_FIRST}, state = EMISSION_RUN, chain_type = 4}
        class_closure = 0x8e19fc8
        hlist = 0x8e43e78
        handler_list = 0x8e1e120
        return_accu = 0x0
        accu = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
        signal_id = 7
        max_sequential_handler_number = 30
        return_value_altered = 0
#8 0x00c8cb8f in g_signal_emit_valist (instance=0x8e4e010, signal_id=7, detail=0, var_args=0xbfe0265c "\364?\377") at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c:3002
        instance_and_params = 0x8e4d850
        signal_return_type = 4
        param_values = 0x8e4d864
        node = 0x8e19ff0
        i = <optimized out>
        n_params = 0
        __PRETTY_FUNCTION__ = "g_signal_emit_valist"
#9 0x00c8cd03 in g_signal_emit (instance=0x8e4e010, signal_id=7, detail=0) at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c:3059
        var_a...

Read more...

Changed in lightdm (Ubuntu):
status: New → Confirmed
Changed in lightdm (Ubuntu Oneiric):
assignee: nobody → Robert Ancell (robert-ancell)
tags: added: rls-mgr-o-tracking
Revision history for this message
Sebastien Bacher (seb128) wrote :

is that still an issue with the current version?

Revision history for this message
Julien Lavergne (gilir) wrote :

Working with the version on oneiric, thanks :)

Changed in lightdm (Ubuntu Oneiric):
status: Confirmed → Fix Released
Changed in lightdm:
status: New → Fix Released
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.