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

Bug #1228626 reported by john h
This bug affects 160 people
Affects Status Importance Assigned to Milestone
GNOME Tweaks
Fix Released
Medium
gnome-tweak-tool (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Crashes all the time. Usually after a few minutes.

You can reproduce the crash by changing keys entries in dconf-editor or installing extensions from the web interface while gnome-tweak-tool is running.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-tweak-tool 3.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic i686
ApportVersion: 2.12.4-0ubuntu1
Architecture: i386
Date: Sat Sep 21 13:26:36 2013
ExecutablePath: /usr/bin/gnome-tweak-tool
InstallationDate: Installed on 2013-07-25 (58 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha i386 (20130626)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gnome-tweak-tool
SegvAnalysis:
 Segfault happened at: 0xb7757e15 <sem_post@@GLIBC_2.1+5>: mov (%ebx),%eax
 PC (0xb7757e15) 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 lpadmin sambashare sudo

Revision history for this message
john h (aaft1990) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 sem_post@@GLIBC_2.1 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/sem_post.S:41
 PyThread_release_lock (lock=0x0) at ../Python/thread_pthread.h:350
 PyEval_ReleaseLock () at ../Python/ceval.c:265
 pyg_toggle_notify (data=data@entry=0x9167c5c, object=object@entry=0x94aefd0, is_last_ref=is_last_ref@entry=0) at ../../../gi/_gobject/pygobject.c:605
 toggle_refs_notify (object=<optimized out>, is_last_ref=0) at /build/buildd/glib2.0-2.37.93/./gobject/gobject.c:2906

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-tweak-tool (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-tweak-tool (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

In bug #1245304 you can find a stacktrace (from @szx) and a way to reproduce it easily... I copy that here:

To reproduce the bug, do the following:

1) open gnome-tweak-tool and don't do anything with it
2) open dconf-editor
3) go to org.gnome.desktop.wm.preferences
4) change the value of a key (for example, click on titlebar-use-system-font

-> gnome-tweak-tool crashes immediately.

Revision history for this message
Lockal (lockal) wrote :

Another way to reproduce (from bug #1235902):
1) Open gnome-tweak-tool on extensions tab
2) Go to https://extensions.gnome.org/ and enable any extension there (gnome-tweak-tool should be opened)

description: updated
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Any new on this bug? Makes almost impossible to use gnome-tweak-tools...

tags: removed: i386
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

I suspect the upstream is https://bugzilla.gnome.org/show_bug.cgi?id=710530. Asked there, will check back.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Seems the same, and it seems fixed upstream. The problem is that I tested he fix (and the workaround) and it doesn't run on 13.10 --- it needs to be backported by someone with more knowledge than me.

Changed in gnome-tweak-tool:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

I had found the patch that fix the crash --- it's here. https://git.gnome.org/browse/gnome-tweak-tool/commit/?h=gnome-3-10&id=757c4e1eb06031cf1d066047a8032dc071a8843c.

It applies (almost) cleanly to the Ubuntu 3.10 version and works for me; at least you can use g-t-t with it.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "Backported patch from 3.10 upstream branch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Just adding that the patched gnome-tweak-tool (see post #12) is working for me with no problem since more than one month. The patch seems safe, too, and easily applied by hand.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Anything new here? I do not know if it has been shipped...

Revision history for this message
Jeremy Bícha (jbicha) wrote :

This bug was fixed in gnome-tweak-tool 3.10, available in Ubuntu 14.04 LTS.

Changed in gnome-tweak-tool (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.