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

Bug #1385598 reported by Behrooz Nobakht
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Invalid
Undecided
Unassigned

Bug Description

**NOTE** The same crash happens whenever an attempt is made to open a *combobox*.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gnome-tweak-tool 3.14.0-1ubuntu1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Oct 25 09:47:58 2014
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/gnome-tweak-tool
InstallationDate: Installed on 2012-07-21 (825 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gnome-tweak-tool --debu
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: gnome-tweak-tool
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-tweak-tool crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to utopic on 2014-10-24 (0 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Behrooz Nobakht (nobeh) wrote :
information type: Private → Public
Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
Changed in ubuntu-gnome:
status: New → Invalid
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libgirepository-1.0-1: package version 1.42.0-0ubuntu1~utopic2 dbgsym version 1.41.4-0ubuntu1
outdated debug symbol package for libgnome-desktop-3-10: package version 3.14.1-1ubuntu1~utopic2 dbgsym version 3.12.2-2ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
Patrizio Bruno (desertconsulting) wrote :

here's a stacktrace with complete debugging symbols

Revision history for this message
Behrooz Nobakht (nobeh) wrote :

I also think that this bug/crash report should be moved to ppa:gnome3-team/gnome3 as it relates to GNOME 3.14 on Ubuntu 14.10.

Revision history for this message
Behrooz Nobakht (nobeh) wrote :

Similarly, when I try to access an application menu (e.g. in gnome-terminal -> Edit), a similar crash happens.

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.