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

[Nebojsa Sabovic]

Fired up gnome-tweak-tool, went to extensions, clicked on a properties button for one extension and got the extension properties window. In that window, I clicked the button with the extension name, got the list of extensions. Tweak tool crashed while this properties window did not.

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 x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Fri Sep 6 14:09:31 2013
ExecutablePath: /usr/bin/gnome-tweak-tool
InstallationDate: Installed on 2012-11-01 (309 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gnome-tweak-tool
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3457f971c0 <sem_post>: mov (%rdi),%eax
 PC (0x7f3457f971c0) 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-06-07 (91 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.