gnome-clocks crashed with SIGSEGV in _pygi_invoke_closure_free()

Bug #1058408 reported by Georgi Lyubomirov
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-clocks (Ubuntu)
Expired
Medium
Unassigned

Bug Description

It crashed upon first start. It is working well now after the restart.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-clocks 0.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.24-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
Date: Sat Sep 29 03:05:39 2012
ExecutablePath: /usr/bin/gnome-clocks
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gnome-clocks
SegvAnalysis:
 Segfault happened at: 0x7fb291242314: subq $0x1,(%rcx)
 PC (0x7fb291242314) ok
 source "$0x1" ok
 destination "(%rcx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-clocks
StacktraceTop:
 ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
 g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slist_free_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
 ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
Title: gnome-clocks crashed with SIGSEGV in g_slist_foreach()
UpgradeStatus: Upgraded to quantal on 2012-08-07 (52 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Georgi Lyubomirov (georgievgeorgi) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _pygi_invoke_closure_free (data=0x3adc990) at /build/buildd/pygobject-3.4.0/gi/pygi-closure.c:524
 g_slist_foreach (list=<optimized out>, list@entry=0x5214160, func=func@entry=0x7fb291242300 <_pygi_invoke_closure_free>, user_data=user_data@entry=0x0) at /build/buildd/glib2.0-2.34.0/./glib/gslist.c:894
 g_slist_free_full (list=0x5214160, free_func=free_func@entry=0x7fb291242300 <_pygi_invoke_closure_free>) at /build/buildd/glib2.0-2.34.0/./glib/gslist.c:177
 _pygi_make_native_closure (info=0x3adc4a0, scope=GI_SCOPE_TYPE_ASYNC, py_function=py_function@entry=<instancemethod at remote 0x3a13d70>, py_user_data=0x859380) at /build/buildd/pygobject-3.4.0/gi/pygi-closure.c:549
 _pygi_marshal_from_py_interface_callback (state=0x7fff80968b70, callable_cache=0x3ad2c00, arg_cache=<optimized out>, py_arg=<instancemethod at remote 0x3a13d70>, arg=0x52eb748) at /build/buildd/pygobject-3.4.0/gi/pygi-marshal-from-py.c:1368

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-clocks (Ubuntu):
importance: Undecided → Medium
summary: - gnome-clocks crashed with SIGSEGV in g_slist_foreach()
+ gnome-clocks crashed with SIGSEGV in _pygi_invoke_closure_free()
tags: removed: need-amd64-retrace
Jeremy Bícha (jbicha)
information type: Private → Public
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

I'm setting this bug to "Incomplete" as it's not seen any activity for some time. If this is still when using a maintained release of Ubuntu then please let us know otherwise this bug report can be left to expire in approximately 60 days time.

Paul White
[Ubuntu Bug Squad]

Changed in gnome-clocks (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-clocks (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-clocks (Ubuntu):
status: Incomplete → Expired
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.