Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.

** Changed in: lightdm (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/963025

Title:
  lightdm assert failure: *** glibc detected *** lightdm: double free or
  corruption (!prev): 0x0000000001c34f30 ***

Status in “lightdm” package in Ubuntu:
  Incomplete
Status in “pam-fprint” package in Ubuntu:
  New

Bug description:
  The ubuntu not login and return to lighgm. I change to gdm and work.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.1.9-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  AssertionMessage: *** glibc detected *** lightdm: double free or corruption 
(!prev): 0x0000000001c34f30 ***
  Date: Fri Mar 23 07:50:07 2012
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120315)
  ProcCmdline: lightdm --session-child 12 25
  ProcCwd: /
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: lightdm
  Title: lightdm assert failure: *** glibc detected *** lightdm: double free or 
corruption (!prev): 0x0000000001c34f30 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/963025/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to