Ubuntu
shutter package

shutter crashed with SIGSEGV in raise()

Bug #978892 reported by Amit on 2012-04-11

This bug report is a duplicate of: Bug #969348: shutter crashed with SIGSEGV in raise(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	shutter (Ubuntu)	New	Undecided	Unassigned

Bug Description

ubuntu 12.04

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: shutter 0.88.1-1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
Uname: Linux 3.2.0-22-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Wed Apr 11 14:40:01 2012
ExecutablePath: /usr/bin/shutter
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/perl
PackageArchitecture: all
ProcCmdline: /usr/bin/perl /usr/bin/shutter
ProcEnviron:
LANGUAGE=en
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x80ca394 <Perl_csighandler+36>: testb $0x1,0x6b4(%eax)
PC (0x080ca394) ok
source "$0x1" ok
destination "0x6b4(%eax)" (0x000006b4) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: shutter
StacktraceTop:
raise () from /lib/i386-linux-gnu/libpthread.so.0
?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
g_cclosure_marshal_generic_va () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: shutter crashed with SIGSEGV in raise()
UpgradeStatus: Upgraded to precise on 2012-03-22 (19 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Amit (amitprobable) wrote on 2012-04-11:

Dependencies.txt Edit (7.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-11: 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 #969348, 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.