Ubuntu
unity-settings-daemon package

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

Bug #1285005 reported by M.C. Botha on 2014-02-26

This bug report is a duplicate of: Bug #1284521: unity-settings-daemon crashed with SIGSEGV in g_bit_lock(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	unity-settings-daemon (Ubuntu)	New	Undecided	Unassigned

Bug Description

None

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
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
Date: Wed Feb 26 08:45:13 2014
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2014-02-26 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140224)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
ProcEnviron:
LANGUAGE=en_ZA:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_ZA.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0xb6ef94d0 <g_bit_lock+64>: lock bts %ebp,(%esi)
PC (0xb6ef94d0) 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:

Tags:

Revision history for this message

M.C. Botha (mcbotha) wrote on 2014-02-26:

Dependencies.txt Edit (10.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2014-02-26: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1284521, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.