← Back to team overview

touch-packages team mailing list archive

[Bug 1425362] Re: unity8 crashed with SIGSEGV in QLightDM::GreeterImpl::authenticateWithPam() when logging in

 

This bug was fixed in the package unity8 -
8.02+15.10.20150518.1-0ubuntu1

---------------
unity8 (8.02+15.10.20150518.1-0ubuntu1) wily; urgency=medium

  [ Albert Astals Cid ]
  * Add overrides to override functions
  * Implement "rating-edit" preview widget (LP: #1318144)
  * Make the DashContent::test_mainNavigation test more stable (LP:
    #1450809)
  * Use art height as implicitHeight when the header is overlayed and
    there's no summary

  [ CI Train Bot ]
  * New rebuild forced.
  * Resync trunk.

  [ Daniel d'Andrada ]
  * Introducing FloatingFlickable
  * Make Ubuntu.Gestures components install TouchRegistry by themselves

  [ Michael Terry ]
  * Fix a possible crash in our PAM threading code. (LP: #1425362) (LP:
    #1425362)
  * Fix the lockscreen becoming unresponsive after testing an app on the
    device from QtCreator. (LP: #1435364)

  [ Nick Dedekind ]
  * Fixed desktop stage app focus.
  * Fixed issue in laggy indicator autpilot tests (LP: #1446846)

 -- CI Train Bot <ci-train-bot@xxxxxxxxxxxxx>  Mon, 18 May 2015 23:04:39
+0000

** Changed in: unity8 (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1425362

Title:
  unity8 crashed with SIGSEGV in
  QLightDM::GreeterImpl::authenticateWithPam() when logging in

Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 source package in Vivid:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  I'm trying to run unity8 in a vivid vmware session (mir works fine here).
  But unity8 crashes when logging in, and it happens again everytime I insert my password in the u8 lockscreen.
  ---
  The only way to successfully log in unity8 was to add myself to the "nopasswdlogin" group. This made the unity8 pam module checks, and thus no crash.

  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb 24 18:09:32 2015
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>:	repnz scas %es:(%rdi),%al
   PC (0x7fb33b34c3a9) ok
   source "%es:(%rdi)" (0xffffffff) not located in a known VMA region (needed readable region)!
   destination "%al" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11SourcePackage: unity8
  StacktraceTop:
   _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=<optimized out>, format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at vfprintf.c:2039
   __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at vasprintf_chk.c:66
   __asprintf_chk (result_ptr=<optimized out>, flags=<optimized out>, format=<optimized out>) at asprintf_chk.c:32
   pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0
   pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: unity8 crashed with SIGSEGV in _IO_vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


References