evince crashed with SIGABRT in raise()

[americo]

crashed while trying to save pdf file after some editing

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evince 3.5.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
Uname: Linux 3.4.0-5-generic i686
ApportVersion: 2.1.1-0ubuntu2
Architecture: i386
Date: Sun Jun 10 13:25:48 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
KernLog:
 Jun 10 10:36:34 amjnnmcd-desktop kernel: [ 4364.143265] type=1400 audit(1339349794.539:27): apparmor="DENIED" operation="open" parent=1 profile="/usr/bin/evince-previewer" name="/home/amjnnmcd/.cache/dconf/user" pid=3039 comm="evince-previewe" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000
 Jun 10 13:25:48 amjnnmcd-desktop kernel: [14518.198151] type=1400 audit(1339359948.596:28): apparmor="DENIED" operation="open" parent=1 profile="/usr/bin/evince" name="/dev/tty" pid=2325 comm="evince" requested_mask="rw" denied_mask="rw" fsuid=1000 ouid=0
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=6130007d-afe0-421d-ae03-336b1b6ff6e0 ro quiet splash vt.handoff=7
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: evince
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: evince crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #955505, 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.