bzr-notify crashed with SIGSEGV in g_return_if_fail_warning()

Bug #942921 reported by Jeroen T. Vermeulen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bzr-gtk (Ubuntu)
New
Undecided
Unassigned

Bug Description

Still getting these, apparently.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bzr-gtk 0.103.0+bzr769-1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
NonfreeKernelModules: wl
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CheckboxSubmission: e56271c144a9c8f9f675c77e2e4edb56
CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b
CrashCounter: 1
Date: Tue Feb 28 23:05:31 2012
ExecutablePath: /usr/bin/bzr-notify
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/bzr-notify
ProcEnviron:
 LC_TIME=en_DK.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb73da896 <_IO_vfprintf_internal+166>: movl $0x25,0x4(%esp)
 PC (0xb73da896) ok
 source "$0x25" ok
 destination "0x4(%esp)" (0xbf692f74) 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-14 (45 days ago)
UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin netdev plugdev pulse pulse-access sambashare video

Revision history for this message
Jeroen T. Vermeulen (jtv) 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.