gnome-tweak-tool crashed with SIGSEGV in sem_post()

[starkus]

Hm, strange... Looks like some system restart with opened programs which were still saved in temp.
Reinstalled some nautilus extensions which were installed further but for some days not. Restarted the system. Error report appeared.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-tweak-tool 3.10.0-0ubuntu1~saucy1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 28 13:42:52 2013
ExecutablePath: /usr/bin/gnome-tweak-tool
ExecutableTimestamp: 1380110043
InstallationDate: Installed on 2013-08-16 (43 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gnome-tweak-tool
ProcCwd: /home/commodore
SegvAnalysis:
 Segfault happened at: 0x7f0b9b21c1c0 <sem_post>: mov (%rdi),%eax
 PC (0x7f0b9b21c1c0) ok
 source "(%rdi)" (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 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_post.S:33
 PyThread_release_lock ()
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_backend_changed () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-tweak-tool crashed with SIGSEGV in sem_post()
UpgradeStatus: Upgraded to saucy on 2013-09-01 (26 days ago)
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 #1196062, 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.