gnome-tweak-tool crashed with SIGSEGV in sem_post@@GLIBC_2.1()

[Danny Houtworm]

this happens like every time i make a change in the top bar its like they are binded and restarting the top bar is making the application crash its nothing really bad since i can restart it easy its just a little bit annoying

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-tweak-tool 3.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Sat Aug 31 05:05:00 2013
ExecutablePath: /usr/bin/gnome-tweak-tool
InstallationDate: Installed on 2013-08-27 (3 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha i386 (20130724)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gnome-tweak-tool
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb779fe15 <sem_post@@GLIBC_2.1+5>: mov (%ebx),%eax
 PC (0xb779fe15) ok
 source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-tweak-tool
StacktraceTop:
 sem_post@@GLIBC_2.1 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/sem_post.S:41
 PyThread_release_lock ()
 PyEval_ReleaseLock ()
 ?? () from /usr/lib/python2.7/dist-packages/gi/_gobject/_gobject.so
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-tweak-tool crashed with SIGSEGV in sem_post@@GLIBC_2.1()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #1195544, 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.