desktop-packages team mailing list archive

[Brian Murray <brian@xxxxxxxxxx>]

Hello Dan, or anyone else affected,

Accepted lightdm into precise-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.7 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  indicator-keyboard-service crashed with SIGSEGV in
  xkl_config_rec_get_full_from_server()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in indicator-keyboard package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Fix Released
Status in indicator-keyboard source package in Precise:
  New
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  The bug report details have been generated automatically. I'm not sure if this bug happens with lightdm or later on.
  The "System Problem Detected" dialogue box appears about 15 to 20 seconds after I've logged in (without me running any apps), so it could be that the crash occurs in the lightdm log-in screen but it just takes my system a while to collect the bug info?

  Everything appears to work normally after the "System Problem
  Detected" dialogue, so whatever is crashing seems to restart
  gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 11:15:17 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service
  InstallationDate: Installed on 2013-09-28 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk --use-bamf
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=<set>
   PATH=(custom, no user)
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa5a9482616:	mov    0x18(%rdx),%rax
   PC (0x7fa5a9482616) ok
   source "0x18(%rdx)" (0x00000018) not located in a known VMA region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-keyboard
  StacktraceTop:
   ?? () from /usr/lib/libxklavier.so.16
   lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0
   lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0
   ?? ()
   ?? ()
  Title: indicator-keyboard-service crashed with SIGSEGV in lightdm_get_layouts()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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