unity-settings-daemon crashed with SIGSEGV in g_bit_lock()

Bug #1284521 reported by manu
46
This bug affects 9 people
Affects Status Importance Assigned to Milestone
OEM Priority Project
Won't Fix
Low
Unassigned
unity-settings-daemon (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

by starting up ubuntu it comes this report but system has no problems, i think it is a report bug.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-settings-daemon 14.04.0+14.04.20140221.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
Date: Tue Feb 25 00:05:16 2014
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2014-02-16 (8 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140216)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0xb6f5f4d0 <g_bit_lock+64>: lock bts %ebp,(%esi)
 PC (0xb6f5f4d0) ok
 source "%ebp" ok
 destination "(%esi)" (0x00000010) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
 g_bit_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_n_children () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_iter_init () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/unity-settings-daemon-1.0/libkeyboard.so
 g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: unity-settings-daemon crashed with SIGSEGV in g_bit_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
manu (thelonwolfpac) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_bit_lock (address=address@entry=0x10, lock_bit=lock_bit@entry=0) at /build/buildd/glib2.0-2.39.90/./glib/gbitlock.c:209
 g_variant_lock (value=0x0) at /build/buildd/glib2.0-2.39.90/./glib/gvariant-core.c:221
 g_variant_n_children (value=value@entry=0x0) at /build/buildd/glib2.0-2.39.90/./glib/gvariant-core.c:929
 g_variant_iter_init (iter=iter@entry=0xbff5ada0, value=value@entry=0x0) at /build/buildd/glib2.0-2.39.90/./glib/gvariant.c:2941
 user_notify_is_loaded_cb (object=0x9cafa48, pspec=0x9c3a310, user_data=0x9c7c530) at gsd-keyboard-manager.c:1034

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity-settings-daemon (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
Ara Pulido (ara) wrote :

Confirming this is fixed with the latest dist-upgrade

Changed in unity-settings-daemon (Ubuntu):
status: Confirmed → Fix Released
status: Fix Released → Confirmed
Revision history for this message
Ara Pulido (ara) wrote :

Back to Confirmed, wrong bug, sorry

Ara Pulido (ara)
Changed in oem-priority:
importance: Undecided → Low
status: New → Triaged
importance: Low → Medium
status: Triaged → New
Ara Pulido (ara)
Changed in oem-priority:
importance: Medium → Low
Ara Pulido (ara)
Changed in oem-priority:
status: New → Confirmed
Revision history for this message
Ara Pulido (ara) wrote :

Marking as Won't Fix in the OEM priority queue. It does not seem a crasher that common to spend too much time on it.

Changed in oem-priority:
status: Confirmed → Won't Fix
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.