unity-greeter crashed with SIGSEGV in background_loader_load()

Bug #934040 reported by Eric Hartmann
50
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Unity Greeter
Fix Released
Undecided
Unassigned
unity-greeter (Ubuntu)
Fix Released
High
Michael Terry

Bug Description

The unity-greeter is crashing everytime since update from 02/16/2012

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-greeter 0.2.3-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Feb 17 08:54:16 2012
ExecutablePath: /usr/sbin/unity-greeter
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x40abb8: mov (%rdx),%ecx
 PC (0x0040abb8) ok
 source "(%rdx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-greeter
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: unity-greeter crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2011-12-21 (57 days ago)
UserGroups:

modified.conffile..etc.lightdm.unity.greeter.conf: [modified]
mtime.conffile..etc.lightdm.unity.greeter.conf: 2011-11-13T21:00:20.247869

Revision history for this message
Eric Hartmann (hartmann-eric) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 background_loader_load (self=0x1a1b5c0) at background.c:381
 background_load_background (self=0x1b3c0b0, filename=0x1b3f1c0 "/usr/share/backgrounds/warty-final-ubuntu.png") at background.c:2149
 background_real_size_allocate (base=0x1b3c0b0, allocation=<optimized out>) at background.c:1474
 g_closure_invoke (closure=0x41c13d, return_value=0x0, n_param_values=<optimized out>, param_values=0x1d08e30, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.31.16/./gobject/gclosure.c:784
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity-greeter (Ubuntu):
importance: Undecided → Medium
summary: - unity-greeter crashed with SIGSEGV in g_closure_invoke()
+ unity-greeter crashed with SIGSEGV in background_loader_load()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-greeter (Ubuntu):
status: New → Confirmed
Changed in unity-greeter (Ubuntu):
assignee: nobody → Michael Terry (mterry)
visibility: private → public
Changed in unity-greeter (Ubuntu):
importance: Medium → High
Changed in unity-greeter (Ubuntu):
assignee: Michael Terry (mterry) → Robert Ancell (robert-ancell)
Revision history for this message
Michael Terry (mterry) wrote :

This happens whenever all a user's monitors have the same size. Which happens with NVidia TwinView at least. Patch coming.

Changed in unity-greeter (Ubuntu):
assignee: Robert Ancell (robert-ancell) → Michael Terry (mterry)
status: Confirmed → In Progress
Michael Terry (mterry)
Changed in unity-greeter:
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity-greeter - 0.2.3-0ubuntu4

---------------
unity-greeter (0.2.3-0ubuntu4) precise; urgency=low

  * debian/patches/do_not_crash_with_twinview.patch:
    - Don't crash when all monitors have the same size (as can happen with
      TwinView) LP: #934040
 -- Michael Terry <email address hidden> Fri, 17 Feb 2012 17:43:37 -0500

Changed in unity-greeter (Ubuntu):
status: In Progress → Fix Released
Changed in unity-greeter:
status: Fix Committed → Fix Released
Revision history for this message
Eric Hartmann (hartmann-eric) wrote :

Sorry for the late response. I confirm that the bug is now fixed.

Thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.