This bug happened when I started a GNOME Classic session.
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-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Aug 28 18:02:09 2013
ExecutablePath: /usr/bin/gnome-tweak-tool
InstallationDate: Installed on 2013-05-20 (100 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
ProcEnviron:
LANGUAGE=fr_CA:fr
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f2e06de61c0 <sem_post>: mov (%rdi),%eax
PC (0x7f2e06de61c0) 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-08-28 (0 days ago)
UserGroups: adm cdrom dip fuse kvm libvirtd lpadmin plugdev sambashare sudo vboxusers
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.