desktop-packages team mailing list archive

[whoop <819314@xxxxxxxxxxxxxxxxxx>]

Guys, do you find lightdm using 100% cpu after you log in? Lightdm uses
100% cpu for me all the time.

-- 
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/819314

Title:
  lightdm crashed with SIGSEGV in g_closure_invoke()

Status in Light Display Manager:
  In Progress
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  Perhaps a dupe of #809890 , but LP doesn't allow me to - just sending
  the reports with full update at aug 1st, 2011.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
  Uname: Linux 3.0.0-7-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Aug  1 15:33:24 2011
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: lightdm
  ProcEnviron: PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x416de1:	mov    0x8(%rax),%rcx
   PC (0x00416de1) ok
   source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: lightdm crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to oneiric on 2011-07-27 (5 days ago)
  UserGroups:

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