bzr-notify crashed with SIGSEGV in g_return_if_fail_warning()

Bug #929621 reported by Tiago Carrondo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bzr-gtk (Ubuntu)
New
Undecided
Unassigned

Bug Description

at boot

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bzr-gtk 0.103.0+bzr769-1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CheckboxSubmission: e5497f2e52527dbfce3e1bc7e97eaecc
CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
CrashCounter: 1
Date: Thu Feb 9 15:35:47 2012
ExecutablePath: /usr/bin/bzr-notify
ExecutableTimestamp: 1324481098
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110817)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/bzr-notify
ProcCwd: /home/tiago
SegvAnalysis:
 Segfault happened at: 0x831896 <vfprintf+166>: movl $0x25,0x4(%esp)
 PC (0x00831896) ok
 source "$0x25" ok
 destination "0x4(%esp)" (0xbf7d6fe4) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: bzr-gtk
StacktraceTop:
 g_return_if_fail_warning () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_type_get_qdata () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
Title: bzr-notify crashed with SIGSEGV in g_return_if_fail_warning()
UpgradeStatus: Upgraded to precise on 2012-01-20 (20 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
Tiago Carrondo (tcarrondo) 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 #903696, 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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.