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

Bug #1211991 reported by Zsolt Fatér
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-tweak-tool (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was disable an extension.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-tweak-tool 3.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
Uname: Linux 3.11.0-1-generic i686
ApportVersion: 2.12-0ubuntu3
Architecture: i386
Date: Tue Aug 13 23:30:30 2013
ExecutablePath: /usr/bin/gnome-tweak-tool
InstallationDate: Installed on 2012-02-29 (530 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gnome-tweak-tool
ProcEnviron:
 LANGUAGE=hu
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb77abe15 <sem_post@@GLIBC_2.1+5>: mov (%ebx),%eax
 PC (0xb77abe15) 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: Upgraded to saucy on 2013-06-15 (59 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Zsolt Fatér (fzs) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-i386-retrace
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

It seems that the bug #1195544 has disappeared...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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